I might have found something useful: by removing 'quiet splash' from the end of the 'root=...' line I was able to look at the boot output. I was trying to determine when in the boot process BusyBox was being invoked. The following appears in the output: ... ... Begin: Running /scripts/local-premount ... Done. mount: Mounting /dev/disk/by-uuid/2E0E-0CE2 on /root failed: No such device mount: Mounting /root on /host failed: Invalid argument ALERT! /host/ubuntu/disks/root.disk does not exist. Dropping to a shell!
BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu12) Built-in shell (ash) Enter 'help' for a list of built-in commands. At this point BusyBox has taken over. The strange thing is that the file /host/ubuntu/disks/root.disk DOES exist: [EMAIL PROTECTED]:/host/ubuntu/disks$ ls -alh total 7.5G drwxr-xr-x 4 root root 32K 2008-05-01 01:53 . drwxr-xr-x 6 root root 32K 2008-05-01 01:53 .. drwxr-xr-x 3 root root 32K 2008-05-31 23:40 boot -rwxr-xr-x 1 root root 2.8G 2008-04-26 07:58 root.disk drwxr-xr-x 2 root root 32K 2008-05-01 08:53 shared -rwxr-xr-x 1 root root 954M 2008-05-01 09:58 swap.disk -rwxr-xr-x 1 root root 3.8G 2008-06-01 06:50 usr.disk I'm not sure whats going on here, or why -16 seems to find and mount the file without problems. -- kernel updates get hardy boot stuck in busy box https://bugs.launchpad.net/bugs/236307 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
