I have the FM-252S2S-60GBP2 which up until now has worked perfectly. I have not applied any firmware updates yet.
It's in a Toshiba laptop running XP.
- For about the first 30 seconds, the drive works fine. It will boot into windows, you can read and write files
- After 30 seconds the drive will report filesize of all files as 0kb. You can still traverse the filesystem directories, but attempting to open a file will result in an input/output error
- After about a minute the drive will disappear from the OS completely. Attempting to access it will result in an error such as the disk is not formatted or the filesystem type is RAW.
Symptoms are the other day my laptop started blue screening with a Stop 0xF4 (0x3, 0x89blahblah blah) error.
At first I thought it was a recently applied windows update and thought nothing of it. I restarted my laptop and kept using it, but the blue screens began to happen more frequently.
After a while I realised it was the HDD, and I plugged the drive into another computer and the same thing happens, so it is definitely the drive at fault.
This is my first time dealing with a corrupt SSD so I had no idea that they could fail in such a short time. From the first blue screen to the time I realised I had a SSD problem was probably only an hour or two and stupidly I had not backed up all my files.
I have managed to recover most of my files by booting linux of a USB drive and writing a bash script to quickly copy the files to an external drive. By restarting the drive repeatedly I can copy a small amount of files off it at a time (about 300mb at a time) before the drive stops responding. I have dumped the entire filesystem structure to a textfile and I'm going through it now to make sure I haven't missed anything I need.
But how to go about fixing it?
Testdisk reports that the partition, bootsector and backup bootsector are healthy. After 30 seconds or so though it will report the drive is unpartitioned.
Chkdsk runs but does not have time to complete.
The forums here seem to suggest zeroing the drive and applying the firmware update, which I guess I will do once I have made sure I haven't lost anything. I would rather get the drive working again without having to reinstall my OS and apps.
Anyone have a better idea?
-Dron.
It's in a Toshiba laptop running XP.
- For about the first 30 seconds, the drive works fine. It will boot into windows, you can read and write files
- After 30 seconds the drive will report filesize of all files as 0kb. You can still traverse the filesystem directories, but attempting to open a file will result in an input/output error
- After about a minute the drive will disappear from the OS completely. Attempting to access it will result in an error such as the disk is not formatted or the filesystem type is RAW.
Symptoms are the other day my laptop started blue screening with a Stop 0xF4 (0x3, 0x89blahblah blah) error.
At first I thought it was a recently applied windows update and thought nothing of it. I restarted my laptop and kept using it, but the blue screens began to happen more frequently.
After a while I realised it was the HDD, and I plugged the drive into another computer and the same thing happens, so it is definitely the drive at fault.
This is my first time dealing with a corrupt SSD so I had no idea that they could fail in such a short time. From the first blue screen to the time I realised I had a SSD problem was probably only an hour or two and stupidly I had not backed up all my files.
I have managed to recover most of my files by booting linux of a USB drive and writing a bash script to quickly copy the files to an external drive. By restarting the drive repeatedly I can copy a small amount of files off it at a time (about 300mb at a time) before the drive stops responding. I have dumped the entire filesystem structure to a textfile and I'm going through it now to make sure I haven't missed anything I need.
But how to go about fixing it?
Testdisk reports that the partition, bootsector and backup bootsector are healthy. After 30 seconds or so though it will report the drive is unpartitioned.
Chkdsk runs but does not have time to complete.
The forums here seem to suggest zeroing the drive and applying the firmware update, which I guess I will do once I have made sure I haven't lost anything. I would rather get the drive working again without having to reinstall my OS and apps.
Anyone have a better idea?
-Dron.
Comment