- May 19, 2011
- 20,007
- 14,344
- 136
From a customer's computer, but anyway. I thought I'd write up my experiences so far for anyone who is interested.
The customer reported applications crashing all over the place. The event log showed tonnes of disk errors starting for the day in question (and not at all before), and the SMART data was all OK (100% life left, no sector issues etc). A full chkdsk found enough file system issues that it filled up the log entry to the point that the summary was no longer available, but from what there was, it didn't suggest a hardware problem purely from that test. I was a bit nervous because the SSD is a year old and it was replacing a hard drive that had also failed (I was thinking 'what are the chances that the same PC would have two storage failures'), so I tried another SATA cable, no difference. Next I connected the SSD to my own PC via USB3. While reading data went without a hitch, writing data resulted in long delays, controller errors, mangled parts of the file system, etc. I guessed that while reading is OK, writing is where problems occur.
I fired off a support request to Samsung on Friday, still no answer by today (the following Tuesday). I think I will ring them.
As the SSD seemed to be fine for reading I thought I would try doing a complete drive backup and restore onto another SSD to save time having to configure the whole system, so when the new SSD arrived this morning, I connected the old one back up (on its own) to the PC in question, and unfortunately Windows refused to boot citing an unexpected I/O error when reading BCD data, so I guess the SSD is in its death throes. Windows repair from setup didn't work (not even a log file to consult), and I experienced delays when attempting to get directory listings from the command prompt; not huge ones, but I'd expect an SSD to instantly start producing a listing whereas this one was taking a few seconds before showing anything.
I'm glad that partly for testing purposes I did my own backup of the customer's data sooner rather than later. While I would consider this normal practice for a failing HDD, I still had my doubts at the time that it was a failing SSD, and I've only seen one other ailing SSD first-hand (a Crucial one).
The customer reported applications crashing all over the place. The event log showed tonnes of disk errors starting for the day in question (and not at all before), and the SMART data was all OK (100% life left, no sector issues etc). A full chkdsk found enough file system issues that it filled up the log entry to the point that the summary was no longer available, but from what there was, it didn't suggest a hardware problem purely from that test. I was a bit nervous because the SSD is a year old and it was replacing a hard drive that had also failed (I was thinking 'what are the chances that the same PC would have two storage failures'), so I tried another SATA cable, no difference. Next I connected the SSD to my own PC via USB3. While reading data went without a hitch, writing data resulted in long delays, controller errors, mangled parts of the file system, etc. I guessed that while reading is OK, writing is where problems occur.
I fired off a support request to Samsung on Friday, still no answer by today (the following Tuesday). I think I will ring them.
As the SSD seemed to be fine for reading I thought I would try doing a complete drive backup and restore onto another SSD to save time having to configure the whole system, so when the new SSD arrived this morning, I connected the old one back up (on its own) to the PC in question, and unfortunately Windows refused to boot citing an unexpected I/O error when reading BCD data, so I guess the SSD is in its death throes. Windows repair from setup didn't work (not even a log file to consult), and I experienced delays when attempting to get directory listings from the command prompt; not huge ones, but I'd expect an SSD to instantly start producing a listing whereas this one was taking a few seconds before showing anything.
I'm glad that partly for testing purposes I did my own backup of the customer's data sooner rather than later. While I would consider this normal practice for a failing HDD, I still had my doubts at the time that it was a failing SSD, and I've only seen one other ailing SSD first-hand (a Crucial one).