Yesterday I was doing a lot of intensive IO with the drive in question, an external 2TB Seagate. At some point in the file transfers Windows could no longer interact with it, though it still showed in Explorer, Disk Management, and diskpart.
Some chkdsking, bad sector repairing overnight, and I found it this morning no longer readable by Windows or OS X. The drive wouldn't spin up.
In an attempt to get the data off it I stripped the USB enclosure, and plugged it into another (known working) USB enclosure. Still doesn't spin.
I then plugged it into a SATA port in the case. What do you know, it works.
I've got my data now, I'm just looking for an explanation. Google turned up a whole lot of people having the opposite issue, but that didn't tell me much. So, what are the differences (if any) between how a SATA controller interacts with a drive and how a USB controller will. If it comes down to OS drivers (like I thought), why did I have the problem cross platform?
Some chkdsking, bad sector repairing overnight, and I found it this morning no longer readable by Windows or OS X. The drive wouldn't spin up.
In an attempt to get the data off it I stripped the USB enclosure, and plugged it into another (known working) USB enclosure. Still doesn't spin.
I then plugged it into a SATA port in the case. What do you know, it works.
I've got my data now, I'm just looking for an explanation. Google turned up a whole lot of people having the opposite issue, but that didn't tell me much. So, what are the differences (if any) between how a SATA controller interacts with a drive and how a USB controller will. If it comes down to OS drivers (like I thought), why did I have the problem cross platform?
Facebook
Twitter
Instagram