Oh **** it, **** it, I was having such a nice weekend too!
1TB Western Digital Green Power WD10EADS installed three months ago as a data drive in my main PC (ICH10), lightly used and well cooled. Came home last night, woke the PC out of S3 standby and did some surfing, all seems fine, rebooted PC and it wouldn't load the desktop
Spent 45 mins trying to work out what was going on (ran a diagnostic on the 80GB boot drive, all fine), I then assumed Windows was goofed so I thought I would restore a backup from ACronis I did the other day and thats when I found out the problem . . . . acronis couldn't load the backup from my data drive, uh ohhh . . . .
Unplugged the data drive and the PC booted to the Windows desktop fine! Drive has been tested on different machines, different cables, etc etc . . . it's toast!
More fool me for not having an active backup, managed to scrape about 30% of the data off it but it's really goofed, lots of bad sectors and lots of read-errors, no warning sign . . . .
I'm now wondering if it was just an unlucky drive or using S3 standby a lot did something to it?
1TB Western Digital Green Power WD10EADS installed three months ago as a data drive in my main PC (ICH10), lightly used and well cooled. Came home last night, woke the PC out of S3 standby and did some surfing, all seems fine, rebooted PC and it wouldn't load the desktop
Spent 45 mins trying to work out what was going on (ran a diagnostic on the 80GB boot drive, all fine), I then assumed Windows was goofed so I thought I would restore a backup from ACronis I did the other day and thats when I found out the problem . . . . acronis couldn't load the backup from my data drive, uh ohhh . . . .
Unplugged the data drive and the PC booted to the Windows desktop fine! Drive has been tested on different machines, different cables, etc etc . . . it's toast!
More fool me for not having an active backup, managed to scrape about 30% of the data off it but it's really goofed, lots of bad sectors and lots of read-errors, no warning sign . . . .
I'm now wondering if it was just an unlucky drive or using S3 standby a lot did something to it?