• Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.

Reliability of CF/SD media as HDD replacements?

I see in my searches on classic Mac storage solutions that there are several options available for dealing with the aging supply of SCSI devices.  Namely, the SCSI2SD and AztecMonster adapters are of the most frequently suggested, with a chain of SCSI->IDE->? devices as some more complicated endeavors. 

I have experience with Raspberry Pi, and corruption of the SD media.  This happens so frequent, that it is accepted standard practice to boot only from the SD, and immediate move the system over to USB connected media.   I'm wondering if this is a problem on these devices as well.   A casual search only reveals a few select circumstances of corruption.  Is it just a non issue on this platform?  

 
I would think CF would be far more reliable than your average microSD card.  I work for a manufacturer of high-performance storage servers who used CF cards as boot media for many years, and data getting corrupted or cards getting worn out is extremely uncommon and usually caused by a power failure during a write.  If you really want to be sure, use an "industrial" grade CF card with SLC flash.  They aren't cheap, but have very high write endurance.  In all honesty though, a standard CF card from a reputable manufacturer is probably good enough for 99% of retro hobbyist use.

I personally suspect a lot of the Raspberry Pi's SD problems stem from cheap media.  While the Pi itself is surprisingly well made for a computer that can be bought for less than the cost of a movie ticket and popcorn (and I think the fact that it can be manufactured in Wales at a profit says something about those who claim it would be impossible to make iPhones in a first world country profitably), distributors often tend to pair it with the cheapest of the cheap SD cards, WiFi adapters, etc. to keep the price of 'kits' they sell down.

 
I have experience with Raspberry Pi, and corruption of the SD media.  This happens so frequent, that it is accepted standard practice to boot only from the SD, and immediate move the system over to USB connected media.
I haven't heard of this issue, at least not on the Raspberry Pi forums I've frequented.  Granted, I'm not a heavy RPi user, but I do have one and have spent some time on forums for information and hadn't run across this.  Most discussions I recall have centered around the longevity of SD cards, given that they're limited to a certain number of read/write cycles.  Of course, it could just be that I'm not on the forum often enough to hear of corruption issues.

For my own Raspberry Pi, I've used Transcend and Kingston SD cards.  The Transcend has more time on it than the Kingston.  And the Transcend has probably put up with more "abuse."  Since that was the first card I used, I spent more time with it installing, re-installing and whatnot to get it up and running.  And, there were times when I had to shut down improperly (by disconnecting the power rather than going through the shutdown procedure) and that hasn't seemed to affect it.  And, I would think, if an SD card were to suffer corruption, that would be the time most likely for it to happen.

It could be, as TWF and DK have suggested, all in the quality of the media, rather than the type of media.  Or, possibly, the quality of the RPi board being used, since, as I recall, they are available from different manufacturers.  Or maybe I've been lucky or just haven't used the Pi frequently enough to begin to see issues.

 
Thanks for the input.  I'd shelved my Pi a few months back because it kept corrupting the SD.  I'd even purchased two other cards just to make sure it wasn't the media. Power issues?  I tried it with several different ones.  I was in the cost of cards and power supplies several times more than the cost of the dang Pi!  I even RMA'd the Pi and received another one, same issue!  Doing some more searching today, I came across this thread over at the raspberrypi firmware GitHub.  Wouldn't you believe my bad luck...  I had purchased a Samsung and two Transcend cards, which are affected by this kernel level issue.  I guess maybe time to dig the Pi out of the bin and start tinkering with it again, but i now have anger issues with the kit, and it makes me not wanna play.   :(

 
Last edited by a moderator:
I use SCSI to CF adapters, with IBM Microdrives. Hey, remember those anyone? compact flash spinning disk HDD = no corruption = no 1024 boundary speed limitations. 

 
You're going to end up with other problems with IBM microdrives. At that point, why not just use a regular SCSI hard disk?

That said, the Pi (especially the original one) is going to live on swap if you have one of the older ones with 256 megabytes of RAM and you're using it with Linux that has a graphical interface. 256 megs just isn't enough for most Linux setups with GUIs, and if I'm honest, it's barely enough for Ye Olde Text Only Install of Debian at this point.

The thing that really kills flash storage is the write cycles. For all intents and purposes, you can data on a flash media, and read to it an infinite number of times, until the heat death of the universe, and it'll never be corrupted.

So, for the purposes of 68k Macs and early PowerPC systems, you can happily replace the spinning hard disk with either a good SD card or a good CF card. The one thing I recommend considering is trying to run the system without virtual memory. I absolutely and categorically recommend against turning off swap on Mac OS X, literally any UNIX/Linux system, and any Windows NT system. (And it's probably a bad idea on Windows 9x but I'm less familiar with that) -- however, for the most part, system 7 Macs were so slow that whatever difference it'll even make on System 7 (if there is any) is going to be nearly negligible.

Mac OS 9 is kind of a toss-up. I've heard informally that Mac OS 9 is sped up with VM on (even if you have like a gig of RAM) because it allows you to not actually read the entire app file from disk when the app is launched. But, if you're using a faster disk with a lower seek time and there's no limits on reading, then you may not need whatever speed boost would have come from enabling/allowing VM to run.

On Mac OS X, Windows NT, and other Linux/UNIX systems, your computer will crash and burn without enough memory, and with virtual memory or swap turned off. In many cases, there'll be no warning and it will be exceedingly ugly. I can't possibly say enough that I recommend you just don't.

That said, if your machine is also networked to a generously big netatalk server, you can copy the contents of your hard disk to a Disk Copy image stored on the network and then use the 7.5 Network Access Disk should you ever need to restore. (Just be sure the Disk Copy application itself is on the file server, or the 7.5NAD.)

Also, take care of what media you're buying, Samsung Evo media may be worth looking into, and if you're really worried, go for the AztecMonster (or another CF adapter) and a particularly high end card that's meant to endure a large number of write cycles.

For newer PPC PowerBooks with IDE in them, you can consider a regular IDE SSD or an adapter to use an mSATA/m.2 SSD. Modern SATA/M.2 SSDs have completely insane write durability. Most of them are rated to be able to fill the disk over and over again at full speed for 50 years, and many of them will actually last longer than that.

For PCI Mac desktops, you can buy a SATA card and install whatever hard disk or SSD you want.

Another overall option for SCSI is to buy used server hard disks. I can only really recommend this for the biggest and best Macs that have a lot of cooling. I fear the relatively small space and low airflow of something like a Mac IIsi or an LC series system would cause the drive to ultimately die of heat exhaustion, but some people have been running theirs for a while, I don't know under what circumstances.

You'll probably end up paying something for either solution, and for me, I'd rather go with scsi2sd or aztecmonster, knowing that the media's going to be pretty good, and the adapter itself will be relevant for the foreseeable future.

 
You're going to end up with other problems with IBM microdrives. At that point, why not just use a regular SCSI hard disk?
Yea, but I havent had one fail yet. And if it does, Oh well.... I have backup copies of everything anyway. 

 
Last edited by a moderator:
Back
Top