5 ms·
I'm impressed with how long they lasted. I am NOT impressed with the behavior at end of life. In fact it makes it wary of using any SSD. A bad SSD should go r
by ars 12y ago
I'm impressed with how long they lasted.
I am NOT impressed with the behavior at end of life. In fact it makes it wary of using any SSD.
A bad SSD should go read only, and stay that way. Not self-brick, and make the data unrecoverable.
- wnissen 12y agoIs there any explanation for the bricking on power cycle? The reads should be fine forever.
- raverbashing 12y agoNot sure, but I'm imagining it's to avoid someone throwing out a read-only drive filled with sensitive data (and unable to erase it through conventional means - that is, writing to the drive) Of course, there are other solutions to this problem: sledgehammer, etc
- ars 12y agoA bricked device still has the data on it. It's fake security. And you could allow secure erase while still prohibiting normal writes. The cells aren't actually gone or unusable after all, just unreliable. A secure erase would work fine on them.
- thrownaway2424 12y agoAnd, it would be extremely easy to implement, because you only have to assert erase on every page in the device, which can be done in parallel.
- raverbashing 12y ago"A bricked device still has the data on it. It's fake security" No, because they do this http://vxlabs.com/2012/12/22/ssds-with-usable-built-in-hardware-based-full-disk-encryption/ http://vxlabs.com/2012/12/22/ssds-with-usable-built-in-hardw... Erase the AES key -> data is gone
- pkaye 12y agoIt is kind of like when you have a power loss while writing to a file system (like say FAT32 or EXT2) and when it comes back up you have to do a fsck or equivalent. If something gets messed up it may not come back in an consistent manner. Something similar happens at and SSD level. One of the most complex aspects of an SSD to implement and test.
- acqq 12y agoIt sounds easy but it's not: imagine you're the software controling the SSD. Before you do write you don't know if the write will succeed. Once you've written, exactly the information that gives the pointers to the valid data could be the one that is destroyed. Then the "raw" data you can access can be "out of order" but that would still be better than nothing. I can imagine that there would have to be some special "recovery mode" which would allow ythe user to rescue the data blocks even with the uncertain order, in case you are willing to piece some of them together. But almost certainly there aren't much people willing to pay for that. "Read only" after some fixed number of writes would be safer. But then the complaints would be "why can't they just allow me to write as much as I can, I have the backup somewhere anyway." Which is also a valid wish. So it would be the best to be able if user could select the mode.
- ars 12y agoEverything else should still be fine though. And the flash that holds the pointers (redirection table for wear leveling) can be a slightly higher quality flash that lasts just a little bit longer.
- acqq 12y agoWhen the SSD is bricked to read it's the redirection table that is corrupted. The corruption means that the random bits are wrong. Once the random bits are wrong, the redirection is wrong. If the redirection table is in the separate flash, you have to spend more flash for redirection table than for data, as that table will be heavily stressed (the redirections have to be often updated with the writes if you want good wear levelling). If you offload the part of the redirection table to the "normal flash" you're still at the beginning. Some random bits will be wrong after some write and you depend exactly on them to be able to read properly.
- ars 12y agoI would put the entire redirection table on ram, and only write it to disk (to a dedicated area) when turning off the power. By doing that, that area will easily outlast the regular flash.
- cssmoo 12y agoConsidering spinning rust used to fail catastrophically, sometimes very quickly, I'm really not bothered. Plan for the worst, hope for the best. In fact my personal advice is to plan to lose everything since your last backup. If you can't afford that risk, back up more often. No disk technology is perfect nor instantly comparable. I consider this to be purely a 'value for money before it blows up' assessment. The results make me happy as I've been recommending and use 840 pros for a while now.
- ars 12y ago> Considering spinning rust used to fail catastrophically That's one of the things I look for in a hard disk - how does it act when it fails. A "good" failure is some bad sectors, but otherwise OK.
- Klinky 12y ago...and which magical hard drive do you buy that guarantees it will fail gracefully? Customer hard drive reviews are littered with sudden drive deaths and DOAs. If the electronics or motor go on a hard drive, the data is practically toast unless you're ready to pay out the nose for exotic data recovery.
- cssmoo 12y agoThis. ANY error and it goes in the bin regardless of tech.
- digi_owl 12y agoThis is why i really wish that some kind of "floppy" had kept up with HDD capacities. There the drive electronics etc was by design separated from the storage media. As such, having the control board or similar keel over meant getting a new drive.
- DanBC 12y agoIsn't MicroSD what you want? Even when hard discs were tiny they were bigger than any floppies. Zip drives were possibly the closest, but they were only used because they were portable, not because they were any good.
- digi_owl 12y agoSDs still have a level of electronics between the storage IC and the rest of the system. There may have been a solid state format like what i'm thinking about, but i think it is long defunct.
- majormajor 12y agoZip drives could also go bad and screw up your data if the mechanism failed. Stupid click of death... a completely separate storage layer can't always save you.
- digi_owl 12y agoWell the problem there was that, iirc, they had the RW mechanics alongside the platter. Thus they got bumped around during transport. Without that the damage would have been piecemeal as sectors went bad, rather than watching a chip go poof and lose access to everything.
- TylerE 12y agoWhat's wrong with BD-R?
- digi_owl 12y agoCan't really be used in a "drag and drop" fashion.
- ausjke 12y agoExactly, SSD's sudden death is the major reason that I dare not use it for any serious purposes at the moment, good backup scheme does help, but a sudden death is still too bitter to taste in reality.
- dspillett 12y agoThis is why, for anything I care about, I have them in RAID1 or similar. I have a home server with a pair of SSDs for the system volumes (and hosting a few VMs: mail server, web/app servers, play things, ...) and a pile of spinning metal in RAID5 (I'm considering moving to 6 because of the "new error during rebuild as rebuild takes ages on large drives" issue) for media storage. One of the SSDs died a couple of weeks ago (unexpectedly Linux didn't fail safe properly, it fell over trying to read from the broken one and didn't seem to try read from the other instead, upon coming back up it ran from the good drive OK) and RAID saved my much hassle rebuilding from the previous night's backups. The SSDs in my desktop box aren't RAIDed, nor in my laptop (two wouldn't fit), but I can easily survive either of those being out of action for a couple of days and may backup regime involving copies on the local file server and on remote hosts (fingers crossed) should mean nothing gets lost if they do die. I've not found the failer rates of SSDs to be any different to spinning media - I don't trust important data to a single drive of either type.