So tonight while I was just minding my own businesses, programs started locking up one by one. On reboot, my system took a really long time and then upon loading, I noticed that my D: ssd showed up blank ( was there but didn't display used OR free space ). I managed to read data off it using clonezilla, but any interaction with it from inside Windows is causing freezes. Any way to fix this or am I fucked?
e:
an attempt to wipe it using diskpart resulted in an i/o device error. at this point, I have a full clone saved of the drive, so I can do whatever to it ( including replace if necessary )
e2:
Shows up in bios but causes everything else to freeze pretty much upon acknowledging its existence. Somehow Linux still handles it
Sounds like the SSD is fucked, can you read the smart status from it?
I always found Linux to be more forgiving with bad drives.
As for the SSD, smart status means close to nothing. SSDs die unpredictably and mysteriously. Some good metrics smart can provide that may indicate a failing drive is either the wear indicator level, SSD health, or most importantly total writes.
NAND can handle approximately 1000 writes before crashing out. For example, a 480GB SSD should last up to 480TB in writes. However this isn't always the case, some brands like WD,OCZ,Toshiba,Crucial will crap out way before this. If you got an OCZ or crucial just replace it NOW. These drives won't even see 500 cycles, shit some cases won't see 300. They're absolute shit tier NAND. Intel&Samsung have always been able to go away past 1000. I just failed out a SanDisk with over 2000 cycles on it as well. It would detect and would appear writable but would crash randomly and was horribly slow when it was online.
Knowing the aforementioned smart values + make/model/capacity and total writes of the drive will be helpful to know.
Mushkin reactor 1tb, and it outright failed shortly after my last edit. I tried to unfreeze and secure erase, which cleaned off my remaining data but left me unable to format or even partition without an I/o error. Not buying that brand again, next gonna be Intel probably
Sorry, you need to Log In to post a reply to this thread.
