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

Repartition using networked disk images Install
This is about how I installed Linux on a second partition on my Mac, which originally had just one partition containing Panther. It assumes you have access to a second machine on your network, and have installed and know how to use CarbonCopyCloner.
  1. Mount a remote share using SMB. Mounting my Samba shares on my Linux box turned out to be extremely slow (1 MB/s over a gigabit network), so use a Windows server instead. You can also use an NFS share, but see below first.
  2. Start the Disk Utility and create a new read/write (not compressed -- see below) image on the remote share. Don't be cheap! It's better not having to redo everything because you're out of disk space on the image, even if it takes ages to create the image. I think you need twice the amount of space that you will back up in order to make an Apple Software Restore image.
  3. Now make sure there are no mounts in /private/var/automount or CarbonCopyCloner (CCC) will try to backup your entire network! Simply killing the automount process will not work, since it's required by CCC. I shut down the NFS server on my Linux box instead.
  4. Start CCC. In preferences, make sure "Create a disk image on target", "Prepare for Apple Software Restore" and "Read-only" (not compressed!) are checked.
  5. Select source disk and the newly created (and mounted) disk image from step two as target, supply the administrator password and press "Clone." Wait forever while all your data is transferred over the network.
  6. In case you managed to create too small a partition in step two, so that the final step (converting for ASR) fails, you can do it manually using Disk Utility now.
  7. Boot using your OS X CD, repartition and install a basic system. Then log in and transfer the image you created in the previous steps to an empty partition.
  8. Again, boot using the OS X CD. Restore the image that you transferred in the previous step.
  9. Reboot and rejoice for a while.
  10. Install Linux.
NOTE: Something is very wrong in OS X. I don't know what it is, but my machine must have crashed like ten times during the time I tried this. In the end, I had quit using NFS and switched to SMB, created all images using non-journaling filesystems and stopped using sparse disk images. Only then could I complete the backup.

[robg adds: I have not tested this one, and clearly, a FireWire hard drive will make the job much faster -- unless you're lucky enough to have a Gigabit Ethernet network, it's going to take a long time to copy multiple gigabytes of data across the network.]
  • Currently 1.00 / 5
  You rated: 1 / 5 (2 votes cast)

Repartition using networked disk images | 1 comments | Create New Account
Click here to return to the 'Repartition using networked disk images' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Repartition using networked disk images
Authored by: Makosuke on Mar 12, '04 04:56:20PM

There's actually a second useful tip in here; backing up to a networked volume with CCC. CCC can't clone directly to a mounted network volume, and oddly enough it won't even let you attempt a clone operation (to create a disk image) if there isn't a second "physical" drive mounted--network mounts don't count, apparently, even though writing a disk image on one should work just fine.

But, apparently, by creating a 2nd disk image on the target network volume and mounting that, it'll work. Nice solution for backups for people who only have one internal drive/partition, but access to a network.

Also, aside from the fact that SMB networking being jacked up is a known fact, there seems to be some serious hidden issues with Sparse Images in 10.3 (sad, since they've got some very useful features).

Among them: Create a sparse image, copy some files to it, then restart without "ejecting" it. Boom--the files on the image are corrupt. I've also run into once case of the entire image being rendered unreadable, when the image was encrypted.

There are serious, serious bugs there, that I hope Apple fixes in 10.3.3, and I expect they're part of the cause of the crashes the author of this hint mentioned.

[ Reply to This | # ]