Binary package hint: initscripts
Hi,
I've been moving my myth box from old hardware to new hardware. Needlessly to say, I'm enjoying my various *buntu boxes immensely. In this connection I've also replaced the smallest disk with a larger disk. To complete this task I had to move / and /var to the new disk. This quite naturally entails making the new file systems and transferring contents (incrementally, until downtime was unavoidable) with commands such as these:
rsync -avxHPS --delete / /mnt/
rsync -avxHPS --delete /var/ /mnt/var/
This is nice and all, but of course it will not make mount points, they are excluded by the -x, but I don't want to copy /sys and /proc y'know. I know of the mount points I've laid out myself, such as /var, and /tmp and so on. And the mounting of /proc and /sys seems pretty robust. When booting from the transfered filesystems networking would _not_ come up.
Start with init=/bin/bash to debug. ... S01mountkernfs.sh printed useful error messages indicating that /var/run and /var/lock did not exist. But why didn't I see this during boot? When redhat has a failing init script it changes away from the splash screen to the init-script console. But... more interestingly, IMHO, why does S01mountkernnfs.sh not make these mountpoints itself? Comming up without networking and no error messages on the console during boot is something I expect of windows, not Linux ;-)
Nicolai
S01mountkernfs.sh cannot make the mountpoints, since at that point, the drive is read-only.
If you shutdown the machine, the mountpoints will be made, and then it'll work on the next reboot - that's about the best we could do.