Re: Boot issue - machine ends up in Busybox
On Sun, 16 Mar 2014 14:40:21 -0400
X <lists04@fastmail.fm> wrote:
> Hi,
>
> On Wed, I upgraded my debian box (unstable) using aptitude and then
> shut it down. On booting, it gave me an alert about a disk it
> couldn't find and brought up the Busybox prompt. I have /boot as a
> normal partition and other partitions (/, /home, /tmp, /usr, /var,
> etc.) in a LVM group.
>
> On checking the LVM partitions, everything seemed to be fine. Then I
> did a lvm vgchange -ay and exit, the machine booted up fine after
> that. I rebooted the machine and had to do the activate the
> volumegroup again to be able to boot!
>
> Why isn't it able to scan the lvm groups and volumes? Is it something
> to do with systemd?
>
> The message before it goes to busybox is shown below if it is
> helpful.
>
> ********
> Gave up waiting for root device. Common problems:
> Boot args (cat /proc/cmdline )
> Check root delay = (did the system wait long enough)
> Check root= (did the system wait for the right device?)
> Missing modules (cat /proc/modules; ls /dev)
> ALERT! /dev/disk/by-uuid/66743620-9332-4a1e-a8b1-933eeab1fd89 does not
> exist.
> Dropping to shell!
> modprobe: module ehci-orion not found in modules.dep
> *********
>
Been there, done that, reported the bug. I'm surprised how few people
this has hit. In my case, the /boot and all the LVM partitions except
swap are reiserfs, and in its faulty state, it can see the reiserfs
/boot and the LVM swap but not the LVM reiserfs partitions.
It appears to be an issue with the new grub-pc-bin 2.02~beta2-7. I
downgraded to 2.00-22 along with grub-common, and it booted again. I
then downgraded two other 2.02 packages marked as broken, and all was
well again.
--
Joe
Reply to: