5 ms·

I learned this the hard way a few years ago. Having several drives is not enough. I used to keep my important data replicated on 3 drives, from different brand

I learned this the hard way a few years ago. Having several drives is not enough. I used to keep my important data replicated on 3 drives, from different brands, different capacities, 1 internal, 2 external. One day the internal drive failed, the next day one of the external drives also failed. So... I panicked, shut everything down and bought a brand new hard drive (1tb). While copying from the third drive it also stopped working. So, I had a triple drive failure. I managed to recover most of my data by freezing the external drives and copying from them (until they heated up and had to freeze them again).

H8crilA 5y ago
What are the odds. Did you maybe bring some object with some radioactive material inside?
- kunagi7 5y ago
  Who knows? This happened a decade ago. Maybe it was an electric issue... But that would fry the drive's motherboard instead of making the hard drives click?
- ComputerGuru 5y ago
  This may or may not be the case here, but generally speaking… Pretty high for any parity-based multi-disk system. The remaining disks get stress tested when a disk fails and you need to copy everything over to the replacement. It’s why RAID5 is no longer sufficient with today’s disk sizes and why a RAID10 (which can only lose any one disk plus a specific other disk) is actually real-world safer than RAID6 (which can lose _any_ two disks).
  - seized 5y ago
    Although with RAID10, the disk that absolutely can't fail is the one under all the restore stress. And likely to be the same age as the failed disk. There is also RAIDZ3 for those who want more safety, which is ZFS triple parity.
lloeki 5y ago
In 2005 on a Saturday evening, I lost every bit of digital data I had, in spite of following (and even exceeding) this rule. I had: - One live copy of data on my laptop - One copy on external hard disk, updated ~daily, on-site (home) - One copy on external hard disk, different brand and age, updated ~bi-weekly, off-site (work) - Immutable copies on optical media, persisted ~once a month, on-site Data on the laptop was lost due to operational error: I fat-fingered a command and destroyed the partition table and part of the leading data on disk. Being a reasonably fast disk this ate a lot of structurally critical data quickly. Recovering the filesystem would be really hard, but I had a two days old backup, so didn't think much of it. Now, to the local backup. I booted up a live cd, rebuilt a partition layout, plugged the disk in, and started restoring data. Reboot, and it seemed to work, mostly, but some things that should were not. Immediately jumped to look at the recovered data, it was severely corrupted. Diffed some files and compared to the "originals" (i.e from the backup) and they were identical: data on the backup disk was hopelessly mangled even though the hardware was fine. A cursory analysis seemed to highlight a software bug (filesystem code? drive firmware? whatever, the issue had some logical consistency to it that made it obvious it was unrecoverable, which was my sole goal at this point). And I just restored it over what remained of perfectly valid - if difficultly reachable - data, essentially scrubbing the laptop disk. Sweat was starting to build up. Okay, optical copies were next, even if older. Surely this would get my heart rate down. I put the disk in, closed the tray, and heard the sound of a rattling helicopter. I stored the disk in a closet which I thought would be safe, but it turns out the hot water pipes for the flat above were running behind a thin wall, which build up enough heat over time inside the closet to slowly warp the disk. Well, one of them, because I was paranoid enough to have three disks for a 3 month rotation; but while the other disks were geometrically fine (maybe due to being a different brand), they were stored for a longer amount of time and their data suffered much bitrot. This was going to be a long Sunday. Back at work on Monday, the final disk immediately emitted an ominous clicking noise right away. Shortly after it snapped, never to power on again. I could maybe recover data straight from the platters if I sent it to some firm for a hefty pile of cash, which I had none at hand, neither at that time nor in the foreseeable future. So, in order I experienced: an operational error, a logical error, an environmental issue, and a hardware fault. Luck had it that I had a second computer temporarily lent to me, which I toyed with and where some of my most recent work files turned out to lie from a week before, so I could resume putting food on the table quickly. No amount of hackery was able to restore any meaningful data, so I lost about 10 years of digital photos and older work archives. Psychologically it was fairly interesting, because I thought I would be enraged at myself for multiple reasons, but the perspective of such ridiculous odds of this happening turned the whole thing into a very contemplative experience shortly after.

H8crilA 5y ago

What are the odds. Did you maybe bring some object with some radioactive material inside?

kunagi7 5y ago
Who knows? This happened a decade ago. Maybe it was an electric issue... But that would fry the drive's motherboard instead of making the hard drives click?
ComputerGuru 5y ago
This may or may not be the case here, but generally speaking… Pretty high for any parity-based multi-disk system. The remaining disks get stress tested when a disk fails and you need to copy everything over to the replacement. It’s why RAID5 is no longer sufficient with today’s disk sizes and why a RAID10 (which can only lose any one disk plus a specific other disk) is actually real-world safer than RAID6 (which can lose _any_ two disks).
- seized 5y ago
  Although with RAID10, the disk that absolutely can't fail is the one under all the restore stress. And likely to be the same age as the failed disk. There is also RAIDZ3 for those who want more safety, which is ZFS triple parity.

lloeki 5y ago

In 2005 on a Saturday evening, I lost every bit of digital data I had, in spite of following (and even exceeding) this rule. I had: - One live copy of data on my laptop - One copy on external hard disk, updated ~daily, on-site (home) - One copy on external hard disk, different brand and age, updated ~bi-weekly, off-site (work) - Immutable copies on optical media, persisted ~once a month, on-site Data on the laptop was lost due to operational error: I fat-fingered a command and destroyed the partition table and part of the leading data on disk. Being a reasonably fast disk this ate a lot of structurally critical data quickly. Recovering the filesystem would be really hard, but I had a two days old backup, so didn't think much of it. Now, to the local backup. I booted up a live cd, rebuilt a partition layout, plugged the disk in, and started restoring data. Reboot, and it seemed to work, mostly, but some things that should were not. Immediately jumped to look at the recovered data, it was severely corrupted. Diffed some files and compared to the "originals" (i.e from the backup) and they were identical: data on the backup disk was hopelessly mangled even though the hardware was fine. A cursory analysis seemed to highlight a software bug (filesystem code? drive firmware? whatever, the issue had some logical consistency to it that made it obvious it was unrecoverable, which was my sole goal at this point). And I just restored it over what remained of perfectly valid - if difficultly reachable - data, essentially scrubbing the laptop disk. Sweat was starting to build up. Okay, optical copies were next, even if older. Surely this would get my heart rate down. I put the disk in, closed the tray, and heard the sound of a rattling helicopter. I stored the disk in a closet which I thought would be safe, but it turns out the hot water pipes for the flat above were running behind a thin wall, which build up enough heat over time inside the closet to slowly warp the disk. Well, one of them, because I was paranoid enough to have three disks for a 3 month rotation; but while the other disks were geometrically fine (maybe due to being a different brand), they were stored for a longer amount of time and their data suffered much bitrot. This was going to be a long Sunday. Back at work on Monday, the final disk immediately emitted an ominous clicking noise right away. Shortly after it snapped, never to power on again. I could maybe recover data straight from the platters if I sent it to some firm for a hefty pile of cash, which I had none at hand, neither at that time nor in the foreseeable future. So, in order I experienced: an operational error, a logical error, an environmental issue, and a hardware fault. Luck had it that I had a second computer temporarily lent to me, which I toyed with and where some of my most recent work files turned out to lie from a week before, so I could resume putting food on the table quickly. No amount of hackery was able to restore any meaningful data, so I lost about 10 years of digital photos and older work archives. Psychologically it was fairly interesting, because I thought I would be enraged at myself for multiple reasons, but the perspective of such ridiculous odds of this happening turned the whole thing into a very contemplative experience shortly after.