I have been downloading a torrent worth 109GB data from one of the private trackers almost close to a fortnight now and halfway through the download, this error popped out of nowhere yesterday! :ashamed:
I wish I could take a screenshot when it happened yesterday but it looks something like this -
This happened on a Samsung N128 netbook with the WD5000BEVT 500GB hard drive. The laptop has not witnessed any random shut downs since it has a battery backup and most power cuts resume before the battery runs out of juice.
I did a quick scan for bad sectors using HD Tune on the drive and it showed no bad sectors. I did not have the patience to run the normal check though.
OTOH the utorrent FAQs seem to suggest that such an error has a possibility that the drive has bad sectors. I am clueless now!
I tried running a CHKDSK operation and it was taking a painfully long time to complete Step 4 of 5, after the reboot happened while running the CHKDSK application. I lost my patience and restarted the netbook! :ashamed:
ATM I am trying to download one file at a time from the torrent file - which btw is happening without the error being reported.
Did anyone here face a similar instance?
I wish I could take a screenshot when it happened yesterday but it looks something like this -
This happened on a Samsung N128 netbook with the WD5000BEVT 500GB hard drive. The laptop has not witnessed any random shut downs since it has a battery backup and most power cuts resume before the battery runs out of juice.
I did a quick scan for bad sectors using HD Tune on the drive and it showed no bad sectors. I did not have the patience to run the normal check though.
OTOH the utorrent FAQs seem to suggest that such an error has a possibility that the drive has bad sectors. I am clueless now!
I tried running a CHKDSK operation and it was taking a painfully long time to complete Step 4 of 5, after the reboot happened while running the CHKDSK application. I lost my patience and restarted the netbook! :ashamed:
ATM I am trying to download one file at a time from the torrent file - which btw is happening without the error being reported.
Did anyone here face a similar instance?