said by trparky:
Oh god, I think you're the one who works for Intel. Crap.
I've never worked for Intel directly or indirectly. My CV/resume is on my home page (see profile) if you want to know where I've worked. And my forum signature here applies universally even if I did work for Intel (though if I did, I would not have touched this topic with a ten foot pole; anyone who has worked for enterprise corps knows you avoid commenting on your own company's products if you value your job).
said by trparky:
Narrowing down the fact that I believe that the SSD is the part that's failing is that none of the other devices that are connected to the same SATA ports and controller are having issues.
I have two HDDs and one SSD that are connected to the Intel SATA controller that's on my motherboard.
I went through the process of determining if the port is possibly what went bad. I tried the SSD on SATA Port 1 which another drive that has been known to not have any issues in this system of mine has been connected to for months with no issues. I plugged the SSD into that port, SATA Port 1, and that HDD into SATA Port 0 which effectively not only swapped the ports but also the SATA cables themselves. This revealed no change, I still had the SSD drop off the bus.
Thanks for explaining -- I understand fully what you went through per your description. You ruled out a bad motherboard SATA port, which is excellent. But all you concluded as a result was: "it's the SSD which is dead". Why
it's dead is what's driving my responses here.
The "issue" the Internet dude is talking about pertains to drives falling off the bus as a result of either a) ATA or AHCI-level PM (my guess is ATA-level) or b) being physically disconnected and reconnected to the SATA bus.
You stated your system is a desktop therefore you don't use drive PM (sleep/standby) (which I assume also means you've disabled that capability in (presumably) Windows -- if you haven't, i.e. power management in Windows is actually set to power down the drive after X seconds of it being idle, then you've been using ATA-level PM), and you obviously didn't sit around unplugging the power to your drive (you certainly wouldn't be complaining about the issue had you been doing that).
So how did you determine the root cause for your issue was absolutely what "sandfarce" described?
What I'm getting at here is that it seems to me you jumped on a convenient bandwagon based on little-to-no actual hard data confirming the issue you experienced was the result of this "bug" some guy on a forum said exists.
SSDs die all the time, and the way they die is significantly different than a MHDD solely because they're solid-state. It's akin to a mobile phone ceasing to work, a digital wristwatch ceasing to work, or even a stick of RAM ceasing to work (that's stretching it a bit though; there's a lot more that goes on within an SSD than a DIMM). What you experienced is just a flat out failure, and without an actual engineer to take the drive and do proper analysis of it, I don't think you've provided enough evidence to say "yeah, this random Internet guy said the 520-series drives stop working, and I had my 520-series drive stop working, therefore it must be this thing this guy described".
Generally speaking "tech" people on the Internet are not actual engineers. I'm not talking about you, I'm talking about that guy making wild claims without any hard technical data. They're usually end-users who can do things like, say, build a PC or know how to replace a video card therefore they're somehow skilled at knowing how to determine the root cause of an SSD failure. They know how to do more than their grandparents, or more than the average joe who uses a computer, and this somehow makes them a wizard. To those of us who are engineers, which even the wizards refer to as wizards (
), we look at guys on forums (not you) flailing their arms and making wild claims and say "sigh, dime a dozen".
Please note that I say all of this quite willingly with the admission that when I first heard about the 320-series 8MByte issue I had a very hard time believing it (mainly because I've owned 6 separate 320-series drives during my life, 4 of which were used in server-class hardware which was power-cycled on occasion, and not one experienced the problem). I sat thinking how that problem could actually be a firmware-level problem and it made no sense. I was very, very
surprised when Intel announced that they had found the reason for the problem and fixed it (or possibly worked around it -- I don't know) with a firmware update. I'm still left wondering what the real root cause of that problem was, because there still hasn't been anything highly technical released by Intel or anyone else -- only the symptoms. I have some suspicions but they're purely assumptions until I can get proof, thus I keep my mouth shut. --
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.