I upgraded to OpenSuse 11.4, and I am getting the following error message on boot:
fsck.ext3 -a -c0 /dev/sdb2
Bad magic number in super-block while trying to open /dev/sdb2
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid andreally contains an ext2 filesystem (and not swap or ufs or something else), then superblock is corrupt and might try running e2fsck with an alternate superblock:
e2fsck -b 183 <device>
fsck failed. Mounting root device read only.
mounting root /dev/sdb2
mount -o ro, acl, user -xattr -t ext3 /dev/sdb/root
EXT2-fs(sdb2) can’t find ext3 fs on dev sdb2
mount: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program or other error. IN some cases, useful info is found in syslog - try dmesg | tail or so.
Could not mount root filesystem – exiting to bin/sh
This looks like that grub menu may be pointing at the wrong kernel. Can you boot to a Linux cd and look to your /boot/grub/menu.lst file and see if the correct kernel is referenced? If it isn’t correct it.
In your partitioning scheme you list sdb2 as LVM2, a logical volume - why would the system be trying to fsck sdb2 directly as a filesystem? Certainly the kernal does no recognise sdb2 as a valid file system, so perhaps it truly is a logical volume. Sdb2 might contain an ext2 logical volume, but your fstab should refer to by its volume name, for example /dev/MyVolGrp/MyLogVol01 or similar. Maybe your /etc/fstab is incorrect in some way.
If sdb2 is not the root partition, you could just comment it out of your /etc/fstab, get the system up and running, and sort this out later (using tools such as lvscan and vgscan).
If you can boot up a repair system from CD you should be able to inspect what LVM thinks is in partition by using lvscan and vgscan, and then mount it and inspect it further.
BTW - the only directly mountable Linux partition listed in your scheme is sda2.