So I was tinkering in my 10.5.8 install today and totally borked it. Not a big deal; I've done it lots--it's a good way to learn.
I booted up from an install disk and did a system restore of my time machine backup. Then I booted up my SL install and from it restored my bootloader. So far all good. I proceeded to boot into the newly restored 10.5.8 partition. It seemed to be booting fine and then there was an error. It wasn't on the screen for very long, something about "couldn't find /dev". Then there was a CPU halt and the screen went black.
Long story short, I compared with a Leopard install disk and found that the folders /dev, /var, and Volumes were not copied to my time machine backups and therefore were not restored. So I copied them from the install disk to my 10.5.8 disk and all was well again.
edit I was mistaken. It was only /dev that wasn't copied; /var and /Volumes do appear in my backups.
I *thought* I had a machine where everything works. Evidently I was wrong.
Any idea what's going on here, and how to fix?
My rig: EP45-UD3L, Q6600, Retail Install, DSDT patched for sound, usb, etc.
In Extra: OpenHaltRestart.kext LegacyHDA.kext fakesmc.kext UUID.kext
I use Netkas Chameleon boot file with EthernetBuiltIn=y GraphicsEnabler=y (before that I used EFI strings)
2 HD, one with SL, and one with 10.5.8--and one external usb for time machine
Full Version: Time Machine Issues
Project OS X Forums > Previous Releases > Mac OS X Leopard 10.5 > Leopard Guides & Tutorials > New Users Discussion
the /dev-directory becomes populated by the devfs during runtime automatically (and depending on the hardware that exists). the only thing that has to exist (iirc) is the /dev-directory itself. i.e.: mkdir /dev && chown root:wheel /dev && chmod 0744 /dev
edit: same goes for /Volumes. this directory holds osx' mount points and those become created (and upon request) dynamically. i.e.: mkdir /Volumes (...)
there is just no need for time machine to back up those two directories and i would expect that time machine, when it's used for doing a full system restore, creates those two (but most likely it takes care of even more things) directories while finishing the process of restoring the system up.
edit: same goes for /Volumes. this directory holds osx' mount points and those become created (and upon request) dynamically. i.e.: mkdir /Volumes (...)
there is just no need for time machine to back up those two directories and i would expect that time machine, when it's used for doing a full system restore, creates those two (but most likely it takes care of even more things) directories while finishing the process of restoring the system up.
QUOTE (aprodigy @ Oct 8 2009, 09:01 AM) 
the /dev-directory becomes populated by the devfs during runtime automatically (and depending on the hardware that exists). the only thing that has to exist (iirc) is the /dev-directory itself. i.e.: mkdir /dev && chown root:wheel /dev && chmod 0744 /dev
edit: same goes for /Volumes. this directory holds osx' mount points and those become created (and upon request) dynamically. i.e.: mkdir /Volumes (...)
there is just no need for time machine to back up those two directories and i would expect that time machine, when it's used for doing a full system restore, creates those two (but most likely it takes care of even more things) directories while finishing the process of restoring the system up.
edit: same goes for /Volumes. this directory holds osx' mount points and those become created (and upon request) dynamically. i.e.: mkdir /Volumes (...)
there is just no need for time machine to back up those two directories and i would expect that time machine, when it's used for doing a full system restore, creates those two (but most likely it takes care of even more things) directories while finishing the process of restoring the system up.
Well that's just it: I *did* do a full restore and time machine *did not* create the /dev directory, and unless I create /dev, the machine is unbootable. I agree that time machine should do those things but it's not. I'm hoping that someone can help me determine why this situation exists on my rig and what I can do to rectify the situation.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.