Waiting for device /dev/vg00/root to appear: not found -- exiting to /bin/sh

olimaltar · 01-25-2013, 05:19 PM

Hi -

Im getting errors when booting SUSE Linux 11 SP2 related to LVM:

Quote:

boot logging started on /dev/tty1(/dev/console) at Wed Dec 12 11:22:42 2012

udevadm settle - timeout of 30 seconds reached, the event queue contains:
/sys/devices/pci0000:00/0000:00:03.0/0000:04:00.0 (1650)
/sys/devices/pci0000:00/0000:00:03.0/0000:04:00.1 (1651)
/init: line 17: cat: command not found
/init: line 17: cat: command not found
Partial mode. Incomplete logical volumes will be processed.
6 logical volume(s) in volume group "vg00" now active
Partial mode. Incomplete logical volumes will be processed.
6 logical volume(s) in volume group "vg00" now active
Partial mode. Incomplete logical volumes will be processed.
6 logical volume(s) in volume group "vg00" now active

...

Then I eventually get kicked to the shell. In which case I type 'exit' twice and the normal booting process continues. But its really annoying, occurs all the time.

Quote:

boot/01-devfunctions.sh: line 38: ls: command not found
boot/01-devfunctions.sh: line 21: ( * 0x100000) + : syntax error: operand expected (error token is "* 0x100000) + ")
boot/01-devfunctions.sh: line 27: / 0x100000 : syntax error: operand expected (error token is "/ 0x100000 ")
. Reading all physical volumes. This may take a while...
Found volume group "vg01" using metadata type lvm2
Found volume group "vg00" using metadata type lvm2
6 logical volume(s) in volume group "vg00" now active
6 logical volume(s) in volume group "vg00" now active
6 logical volume(s) in volume group "vg00" now active
not found -- exiting to /bin/sh

The only thing I remember modifying was extending the LVM columes using YaST (I dont see how that could ahve broken anything).

I havent tried much yet, but Ive been reading for over a week.

(a) One thing I could try would to redo the ramdisk using mkinitrd

(b) Following other posts, Ive check that boot.lvm is activated
chkconfig boot.lvm
boot.lvm on

(c) I've also looked in 01-devfunctions.sh. Not sure what to do with it.

Overall, it seems init waits for root to come online, but it cant find it.

First post, if I've forgotten to put anything let me know

pingu · 01-26-2013, 10:54 AM

It seems you have more problems than just an unavailable root?

Did you update / upgrade the system?
If so, can you boot using older kernel & initrd?

When you get kicked to the shell, is / actually mounted?

You know when it started, can you extract from system logs just before?
(Like, on my Debian, "grep "Jan 20" /var/log/messages" )

olimaltar · 01-28-2013, 03:23 PM

No other problem as far as I know, I still think its all related to the same thing.

No update or upgrade, this is a new server.

I was/am not sure what that shell is. I guess I get dropped in single-user mode at a higher run-level? Anyhow, I haven't checked if '/' was mounted or not. I can try next time I have access to the system.

I've attached boot.msg.2013_01_05.log that is the bootup log from SUSE linux. There is nothing in /var/log/messages related to the bootup.

Tks!