Hello again all, this is kind of an extension of a problem I had marked solved a few weeks back.. at the time my hard drive seemed to be acting up and the random craziness of the problem had me questioning what exactly was causing the issue.
This time I was lucky enough to be at my computer doing something when the problem (SSD crash) happened.
Long story short, I built a computer a little over a month ago. Starting a few weeks ago (this is the third time it has happened) about every week I would come home to my computer booted up into Linux (I keep a flash drive plugged in that has most of my work/school files and also a Linux Live USB partition). I go to check boot options and sure enough my SSD isn't there. The first couple times, I switched the SSD from SATA 0 to SATA 1.. messed with cables.. tested other components in SATA 0 (all worked fine). I thought maybe it could be a short in a cable somewhere and once I moved it around it was being fixed.
Luckily, the case I chose has a very convenient hot swap dock on the outside (plugged into SATA 1) so after last time once I got it working again I left my SSD plugged into that. That way, if it happened again, I would A) Know it wasn't a problem with SATA 0 or its cables (so most likely an SSD problem) and B) Knowing that, hopefully be able to figure out what was going on through Google and help from you fine folks here at Tom's Hardware.
Turns out, the solution was pretty simple. All I had to do was shut my computer down.. unplug the SSD from the hot swap and plug it back in. Turn computer on, SSD shows back in boot options, works fine...
So now I'm just thoroughly confused. What would cause a SSD to crash and be completely unresponsive (not showing up in boot options or in Linux as a drive) that would be totally fixed by simply unplugging the SSD from its SATA connection and plugging it back in? I assume I'm going to have to send the SSD back to Crucial under warranty (hope their service is good, haven't dealt with them before.. pretty sure Newegg only covers for 30 days) I just want to pick a few brains that are better, stronger and faster than mine for some background before I do.. and basically make sure that it is in fact the drive that is my problem and not some obscure setting or boneheaded thing I'm doing...
Please let me know if there is any other information I can include to help.. and thank you very much for your time and knowledge!
EDIT: Just had the second crash of the day.. same deal, unplug and plug back in and it works again. Situation seems to be deteriorating though.
Specs:
Intel i5 4690k processor, Corsair H100i cooling (still base clock)
Gigabyte z97x-Gaming 5 motherboard
AMD Radeon R9 290 graphics
16 GB G.Skill Ripjaws X 2133 memory (not using XMP yet)
Windows 8.1 Pro OS
512 GB Crucial MX100 SSD (390/476 GB free, if that matters for some reason..)
Thermaltake Toughpower 850W PSU
HP 2159m monitor
This time I was lucky enough to be at my computer doing something when the problem (SSD crash) happened.
Long story short, I built a computer a little over a month ago. Starting a few weeks ago (this is the third time it has happened) about every week I would come home to my computer booted up into Linux (I keep a flash drive plugged in that has most of my work/school files and also a Linux Live USB partition). I go to check boot options and sure enough my SSD isn't there. The first couple times, I switched the SSD from SATA 0 to SATA 1.. messed with cables.. tested other components in SATA 0 (all worked fine). I thought maybe it could be a short in a cable somewhere and once I moved it around it was being fixed.
Luckily, the case I chose has a very convenient hot swap dock on the outside (plugged into SATA 1) so after last time once I got it working again I left my SSD plugged into that. That way, if it happened again, I would A) Know it wasn't a problem with SATA 0 or its cables (so most likely an SSD problem) and B) Knowing that, hopefully be able to figure out what was going on through Google and help from you fine folks here at Tom's Hardware.
Turns out, the solution was pretty simple. All I had to do was shut my computer down.. unplug the SSD from the hot swap and plug it back in. Turn computer on, SSD shows back in boot options, works fine...
So now I'm just thoroughly confused. What would cause a SSD to crash and be completely unresponsive (not showing up in boot options or in Linux as a drive) that would be totally fixed by simply unplugging the SSD from its SATA connection and plugging it back in? I assume I'm going to have to send the SSD back to Crucial under warranty (hope their service is good, haven't dealt with them before.. pretty sure Newegg only covers for 30 days) I just want to pick a few brains that are better, stronger and faster than mine for some background before I do.. and basically make sure that it is in fact the drive that is my problem and not some obscure setting or boneheaded thing I'm doing...
Please let me know if there is any other information I can include to help.. and thank you very much for your time and knowledge!
EDIT: Just had the second crash of the day.. same deal, unplug and plug back in and it works again. Situation seems to be deteriorating though.
Specs:
Intel i5 4690k processor, Corsair H100i cooling (still base clock)
Gigabyte z97x-Gaming 5 motherboard
AMD Radeon R9 290 graphics
16 GB G.Skill Ripjaws X 2133 memory (not using XMP yet)
Windows 8.1 Pro OS
512 GB Crucial MX100 SSD (390/476 GB free, if that matters for some reason..)
Thermaltake Toughpower 850W PSU
HP 2159m monitor
Facebook
Twitter
Instagram