I recently bought a FM-25S2S-60GBP2, which had firmware 2.1.
I had transferred files to the drive and everything seemed to be okay, running a recent Linux kernel.
All of the sudden, the BIOS was not able to recognize the drive.
I tried mounting the drive on several other motherboards (Asus P5B-MX, Asus P5QL-VM DO, Asus P7H55-M PRO) as well as with other third-party SATA-II cards, and none of them was able to recognize the drive. Basically, it appeared as if the drive was being probed, but was hanging.
Then, all of the sudden, the drive was able to be recognized everywhere I mounted it, but to my horror, all of the data was completely gone.
I mounted the drive in Linux, I did a disk dump and made an image of the whole drive. The drive was completely zeroed out, not one single non-zero bit on the whole drive.
What in the heck happened, how in the heck did this happen, and why in the heck did this happen?
Did some internal erase function somehow get triggered? If so, this is frightening.
I had transferred files to the drive and everything seemed to be okay, running a recent Linux kernel.
All of the sudden, the BIOS was not able to recognize the drive.
I tried mounting the drive on several other motherboards (Asus P5B-MX, Asus P5QL-VM DO, Asus P7H55-M PRO) as well as with other third-party SATA-II cards, and none of them was able to recognize the drive. Basically, it appeared as if the drive was being probed, but was hanging.
Then, all of the sudden, the drive was able to be recognized everywhere I mounted it, but to my horror, all of the data was completely gone.
I mounted the drive in Linux, I did a disk dump and made an image of the whole drive. The drive was completely zeroed out, not one single non-zero bit on the whole drive.
What in the heck happened, how in the heck did this happen, and why in the heck did this happen?
Did some internal erase function somehow get triggered? If so, this is frightening.
Comment