Floppy disks were ubiquitous when I was in college. When I got into Linux, I did an experiment raw writing zeros to floppies with dd to see what percentage of them had I/O errors. I tested with a stack of about 50 of them that were left in our computer lab over the years (different brands). The failure rate was staggering. Something like 30-40% of them had bad sectors. After that, I realized that I could never rely on them as a storage medium for anything important without regular backups.
I wonder if anyone made an error correcting driver or file format for unreliable data storage like this. Did anyone ever implement RAId (redundant array of independent diskettes)?
Edit: apparently RAR had an option to add internal error correction data to the archive, and you can also use PAR2 files for another layer (I think that's able to reconstruct the archive if one file is totally unreadable)
Floppy reliability dropped of a cliff in the mid-90s. It came to a point where it wasn't unusual to see I/O errors even on completely new floppies.
But with older drives and older media, produced to a higher standard, they were pretty reliable. (After all, IBM invented them to store CPU microcode, they had to be.)
I can't afford an the recommended Applesauce for Apple II disk preservation so I'm hoping that the Adafruit work which added Apple II drive support will work for me.
Generally it's easier to just copy the data to each new media as you adopt it. In the past this was pretty easy to do as the hard drive held way more data than the floppy disks of old. The next hard drive was an order of magnitude larger than the old one, and so on. Unfortunately this sputtered out during the SSD transition and became even more ephemeral as people started putting data in the cloud where it will eventually be wiped when the accounts stop being paid or lost when the company goes under.
> The next hard drive was an order of magnitude larger than the old one, and so on.
Ah yes, the good old "old PC" folder that you would find on pretty much every Windows PC that used to have another "old PC" folder inside it somewhere, possibly inside an "external HDD (old)" folder :-)
Until the PC (or the HDD inside it) died surprisingly, people didn't have backups, or the backups turned out to be burned CDs that were scratched up and/or sat on a sun illuminated shelf for years.
I was at a class reunion a few years ago where it turned out, I was somehow the only one who still had (digital) photos from early-to-mid 2000s.
> ... even more ephemeral as people started putting data in the cloud where it will eventually be wiped when the accounts stop being paid or lost when the company goes under.
Or the photos they upload gradually degrade in quality as the company repeatedly plays with re-compressing stuff to squeeze more space out.
People have observed old (10+ years) photos on Google Drive to start getting blurry, having weird artifacts, color banding, etc... IIRC there was an article posted on HN at one point with some particular egregious examples. Techmoan also mentioned this in a video some time ago, commenting that the same thing happened to old YouTube uploads of his from the 2000s.
Hehe, I used to use the Old folder in my downloads folder and to a lesser degree in my documents folder, usually once or twice a year. At one point when I realised this had got about 10 levels deep, I switched to yyyy-mm format directories instead of nesting them.
I also used to back up other PCs to each other somewhat regularly, and sometimes I'd end up with those files back on the original PC in a backup of another. Fortunately, when I switched to borgbackup on Windows as well [1], this massive reduplication of files became a solved problem.
[1] borgbackup doesn't officially work on Windows, but I run it in WSL which does reasonably well for all the files I really care about (i.e. the stuff I've made). When they have particular unusual characters in the filenames, it throws up a warning for that file every time, but otherwise seems fine. I've never bothered investigating whether those particular files restore to the correct filename, because I know I've also backed up the zip file those files have come from and it's just accidental that I've backed up the extracted files as well.
> when the company goes under
> when the accounts stop being paid
I've never experienced such case, did you?
Something much more likely is for a person to drop their phone into the toilet, buy a new one, and completely lose access to their only backup which is Google Photos, because they don't own a computer anymore and it is their only device.
Efficient market hypothesis applied to this topic would say that if you really do have a floppy, you should already have made a copy of it. If that’s Not the case, transform it to a punched card and be done with it.
The chance that one would have anything important on a floppy that is not already backed up in the year of 2026 must be close to zero.
Floppy disks were ubiquitous when I was in college. When I got into Linux, I did an experiment raw writing zeros to floppies with dd to see what percentage of them had I/O errors. I tested with a stack of about 50 of them that were left in our computer lab over the years (different brands). The failure rate was staggering. Something like 30-40% of them had bad sectors. After that, I realized that I could never rely on them as a storage medium for anything important without regular backups.
I wonder if anyone made an error correcting driver or file format for unreliable data storage like this. Did anyone ever implement RAId (redundant array of independent diskettes)? Edit: apparently RAR had an option to add internal error correction data to the archive, and you can also use PAR2 files for another layer (I think that's able to reconstruct the archive if one file is totally unreadable)
Floppy reliability dropped of a cliff in the mid-90s. It came to a point where it wasn't unusual to see I/O errors even on completely new floppies.
But with older drives and older media, produced to a higher standard, they were pretty reliable. (After all, IBM invented them to store CPU microcode, they had to be.)
. . . simultaneously over-writing the last remaining copy of the original Linux!
I can't afford an the recommended Applesauce for Apple II disk preservation so I'm hoping that the Adafruit work which added Apple II drive support will work for me.
https://github.com/adafruit/Adafruit_Floppy
It's easy to forget that preserving digital data often comes down to keeping aging physical media alive. Nice practical guide.
Generally it's easier to just copy the data to each new media as you adopt it. In the past this was pretty easy to do as the hard drive held way more data than the floppy disks of old. The next hard drive was an order of magnitude larger than the old one, and so on. Unfortunately this sputtered out during the SSD transition and became even more ephemeral as people started putting data in the cloud where it will eventually be wiped when the accounts stop being paid or lost when the company goes under.
> The next hard drive was an order of magnitude larger than the old one, and so on.
Ah yes, the good old "old PC" folder that you would find on pretty much every Windows PC that used to have another "old PC" folder inside it somewhere, possibly inside an "external HDD (old)" folder :-)
Until the PC (or the HDD inside it) died surprisingly, people didn't have backups, or the backups turned out to be burned CDs that were scratched up and/or sat on a sun illuminated shelf for years.
I was at a class reunion a few years ago where it turned out, I was somehow the only one who still had (digital) photos from early-to-mid 2000s.
> ... even more ephemeral as people started putting data in the cloud where it will eventually be wiped when the accounts stop being paid or lost when the company goes under.
Or the photos they upload gradually degrade in quality as the company repeatedly plays with re-compressing stuff to squeeze more space out.
People have observed old (10+ years) photos on Google Drive to start getting blurry, having weird artifacts, color banding, etc... IIRC there was an article posted on HN at one point with some particular egregious examples. Techmoan also mentioned this in a video some time ago, commenting that the same thing happened to old YouTube uploads of his from the 2000s.
Hehe, I used to use the Old folder in my downloads folder and to a lesser degree in my documents folder, usually once or twice a year. At one point when I realised this had got about 10 levels deep, I switched to yyyy-mm format directories instead of nesting them.
I also used to back up other PCs to each other somewhat regularly, and sometimes I'd end up with those files back on the original PC in a backup of another. Fortunately, when I switched to borgbackup on Windows as well [1], this massive reduplication of files became a solved problem.
[1] borgbackup doesn't officially work on Windows, but I run it in WSL which does reasonably well for all the files I really care about (i.e. the stuff I've made). When they have particular unusual characters in the filenames, it throws up a warning for that file every time, but otherwise seems fine. I've never bothered investigating whether those particular files restore to the correct filename, because I know I've also backed up the zip file those files have come from and it's just accidental that I've backed up the extracted files as well.
I still have a bunch of these called "FromOld".
> when the company goes under > when the accounts stop being paid
I've never experienced such case, did you?
Something much more likely is for a person to drop their phone into the toilet, buy a new one, and completely lose access to their only backup which is Google Photos, because they don't own a computer anymore and it is their only device.
I lost the only recordings of my band when Myspace Music died.
At one point, I also had files on RapidShare. They probably weren't of any value, but I have no idea what they were now.
Dropbox has been around for a while (cue that old hacker news comment)
Where'd you get the title from? It's just Copy That Floppy! (maybe +Imaging floppy disks for long-term preservation if it fits)
https://en.wikipedia.org/wiki/Don't_Copy_That_Floppy
I came here just to post that link. I still have that song in my head when I hear the word "floppy".
Efficient market hypothesis applied to this topic would say that if you really do have a floppy, you should already have made a copy of it. If that’s Not the case, transform it to a punched card and be done with it.
The chance that one would have anything important on a floppy that is not already backed up in the year of 2026 must be close to zero.