Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Install 10.3 after using ext3-formatted Yellow Dog Linux Install
I've been trying Yellow Dog Linux 3.0.1 on my iBook, and it's been great. I've put it on my secondary hardisk on my PowerMac. But now my iBook wants to get back to Panther, so I'll restore the image I made of her HD. What I discovered:
  1. A simple "erase" in Disk Utility didn't work.
  2. A simple partition on disk utilities didn't work.
What would happen? Well I'd erase and then partition the drive as HFS+journaled (same as the backed up disk image) and restore it. I tried Carbon Copy Cloner, Disk Utility's restore function, ASR from the command line and NetRestore. All of them left me with a circle with "/" through it. And running Tech Tool pro 4 resulted in a failure of repairing volume structure. Same with DiskWarrior 3. From TTP4's output:
Precheck Structures This test checks the readability of the various volume structures. Precheck Structures
The only thing that worked -- the only method that allowed me to boot into my backup image -- was using Disk Utility's "Zero all data" and "8-way random write format". Then I used Carbon Copy Cloner to copy from the mounted backup image to my super clean ibook. Now Lynn (the iBook) is now enjoying Aqua goodness!
  • Currently 2.50 / 5
  You rated: 3 / 5 (4 votes cast)

Install 10.3 after using ext3-formatted Yellow Dog Linux | 7 comments | Create New Account
Click here to return to the 'Install 10.3 after using ext3-formatted Yellow Dog Linux' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Install 10.3 after using ext3-formatted Yellow Dog Linux
Authored by: mproud on Feb 27, '04 07:07:34PM

When I was a - well, I guess I would call it a school lab apprentice - we worked with a ton of 5260s, and they kept on having trouble, once in a while, recognizing the startup disk.

Well, after install and install and install, and re-formatting the drive again and again, it turned out zero-ing all data did the trick. It seems like the answer to many hard disk problems; and although it can be a lengthy process (yeah, I was stupid enough to accidentally click this when I formatted a new 60 GB 5k rpm hard drive! It's new - there's no reason - and it took hours!) I'm convinced it's a healthy thing for re-initialization.

[ Reply to This | # ]
same kind of problem here.
Authored by: skeetone on Feb 28, '04 12:31:00PM

I have an old iMac 333 Mhz and I had ydl installed on it, now I'm trying to get os 9 back on it but it says it can't install on the disk (maxtor 60 Gb). Could I maybe use the same method as you explained? To first format it like you explained with a panther install cd and after that install os 9?
I also heard about a script to be able to install os x on an old imac, but do I still need at least 128 mb of internal memory in it (now it's 92 mb)?

Another thing I read was that after a ydl install the boot partition could have the wrong do I know it is faulty and how could I fix that?

anybody who can help me..thank you sooooo much!!!!


[ Reply to This | # ]
same kind of problem here.
Authored by: viscaria on Feb 29, '04 11:59:19AM

You need 128 MB to install OSX, but 10.3 should work on any Mac w/ USB. On older systems it is imperitave that you check for any firmware upgrades before attempting to boot OS X, or you could fry the logic board.

[ Reply to This | # ]
same kind of problem here.
Authored by: johnsawyercjs on Feb 29, '04 05:25:31PM

Actually, it won't fry the logic board as such, but it can scramble the firmware chip which is on the logic board, and the Open Firmware settings, resulting in anything from weird video but a Mac that works otherwise, to a black screen and no boot. There are ways around this if this happens to you; mainly they involve removing the RAM and installing different RAM, which often gets the logic board running well enough to allow you to boot from an OS 9.1 - 9.2.2 hard drive and update the firmware, since when the logic board sees a new RAM configuration, it TEMPORARILY resets some of the scrambled settings as part of its process of storing the new RAM configuration, usually long enough to allow the Mac to boot and allow a firmware update; simply resetting Open Firmware sometimes does the trick, but replacing the RAM works more often. But again the effect is only temporary, so you need to quickly update the firmware once you get the Mac running, which will clear up any remaining messed-up video too. Sometimes you have to replace the RAM several times during this process, with different RAM each time, until you get OS 9 to boot and let you run the firmware updater. Works for me every time (I fix Macs for a living, so I've seen this many times).

[ Reply to This | # ]
same kind of problem here.
Authored by: johnsawyercjs on Feb 29, '04 05:40:11PM

If all you want to do is run OS 9 on your iMac, you don't need to initialize it with OS X's Disk Utility--just boot from the OS 9 installer CD and use its copy of Drive Setup, which also has a 'zero all data' option.

[ Reply to This | # ]
Install 10.3 after using ext3-formatted Yellow Dog Linux
Authored by: johnsawyercjs on Feb 29, '04 05:46:11PM

I've increasingly been finding that the 'zero all data' option fixes a variety of hard drive problems that no diagnostic utility can either fix, or can even detect. Choosing to simply initialize a drive doesn't erase all the blocks on the drive--it just removes all file entries from the directory tracks, and does nothing to actually repair any messed-up blocks that the Mac OS reads as part of its process of interacting with the drive, including the directory tracks, but also including the boot blocks, etc. These blocks can have wrong data, etc., and zeroing all data is the only process that actually erases them (and all the other blocks on the drive) and resets them to a condition that Apple is happy with. How these blocks get bad in this way, I don't yet know--possibly the result of crashes, buggy software, etc.--the usual. Blocks that are bad like this won't be detected by utilities that scan for bad blocks, since these utilities just look for blocks that are so messed up that they can't be read at all--these utilities can't know whether the data stored in those blocks is correct or not, they only detect scrambled "header/footer" identifiers that bracket the data in each block, or blocks that sit on a location on the disk where there's actual physical damage. Another possible thing that zeroing all data may fix, is blocks that are "weak" magnetically, though this is just my theory.

[ Reply to This | # ]
Install 10.3 after using ext3-formatted Yellow Dog Linux
Authored by: le fromager on Jul 25, '04 03:37:10AM
I had this problem too. With Mandrake. This problem can be fixed with MountX, a system extension for OS 9 that enables you to mount the Linux ext2 partition, and then format it. Now the problem is where to find it. It seems that the file was hosted here:
and here:
but it's not there anymore. If you find it, please tell me. Another way is a Preference Pane for OS X that mounts the ext2 partition too. It's called Ext2 Filesystem. It can be found at! I've not tested it yet, but Version Tracker says that it works.. Good Luck!

[ Reply to This | # ]