Here is the short description of my system installed:
The bootloader GRUB was installed on /dev/sda1
RAID array /dev/md0 was created from /dev/sda2 and /dev/sdb2. It was mounted as ‘/’
RAID array /dev/md1 created from /dev/sda3 and /dev/sdb3 was mounted as ‘/home’.
The problem arose after I had updated the kernel - the system would not boot - The GRUB would fall with error 15.
What steps should I take to recover my system?
eldar g,
> The problem arose after I had updated the kernel - the system would not
> boot - The GRUB would fall with error 15.
This is a file not found error. Try starting the box up using the install CD and
select rescue mode. Verify that your boot information is correct.
–
Niclas Ekstedt, CNA/CNE/CNS/CLS
Systems Engineer
Atea Sverige AB
Well, I booted using cd and tried to repair but the opensuse won’t see my raid arrays. rescue cd sees them but I don’t know how to proceed next. Read in the forums that I should proceed with mkinitrd but chroot doesn’t work
I’m completely puzzled, can anyone, please, help me?
eldar g,
when you boot, how far do you get. Do you get the GRUB boot menu or does the
error occured even before the GRUB menu is displayed?
–
Niclas Ekstedt, CNA/CNE/CNS/CLS
Systems Engineer
Atea Sverige AB
I see the GRUB menu. Then the error appears. I tried making mkinitrd but now another error appears: the system says
“mdadm: /dev/md0 has been started”
“resume device not found (ignoring)”
“Waiting for device /dev/md0 to appear: !boot/01-devfunctions.sh: line 68: multipath: command not found”
“!boot/01-devfunctions.sh: line 68: multipath: command not found”
“!boot/01-devfunctions.sh: line 68: multipath: command not found”
“!boot/01-devfunctions.sh: line 68: multipath: command not found”
“!boot/01-devfunctions.sh: line 68: multipath: command not found”
…
“!boot/01-devfunctions.sh: line 68: multipath: command not found”
“Could not find /dev/md0.”
“Want me to fall back to /dev/md0? (Y/n)”
Any idea? Did anyone face something familiar?
Did you upgrade kernel-base and kernel-extra? It seems the system can’t mount /dev/md0. This may happen when RAID module or FS module not loaded (missing?).
Could you mount your root partition and check if /boot/grub/menu.lst points to the correct vmlinux/vmlinuz image?
To chroot you need to mount the root partition somewhere.
2 Lazy_Kent:
How can I load those modules? For instance, when booting system repair? It doesn’t see /dev/md0 and tells that partitions are incorrect offering to fix them, though I know that when I boot a rescue cd and mount raid arrays they are ok.
2 BenderBendingRodriguez:
According to my check /boot/grub/menu.lst points to the correct version but if you provide me, please, with the proper steps to follow, I will check again to make sure I didn’t make a mistake checking the versions before.
Well, I tried mounting but the chroot won’t still work.
I think you should boot from openSUSE DVD and run update of current system (not install!).
Lazy_Kent,
I tried updating to OpenSuse 11.1 but the installer wouldn’t see /dev/md0, it says something like “no partition found with linux installed”
Can you show
# fdisk -l
?
linux:~ # fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00066a56
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 2624 20972857+ fd Linux raid autodetect
/dev/sda3 2625 3146 4192965 82 Linux swap / Solaris
/dev/sda4 3147 60801 463113787+ fd Linux raid autodetect
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00078d0c
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104391 83 Linux
/dev/sdb2 14 2624 20972857+ fd Linux raid autodetect
/dev/sdb3 2625 3146 4192965 82 Linux swap / Solaris
/dev/sdb4 3147 60801 463113787+ fd Linux raid autodetect
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003aac1
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 13 104391 83 Linux
/dev/sdc2 14 2624 20972857+ fd Linux raid autodetect
/dev/sdc3 2625 3146 4192965 82 Linux swap / Solaris
/dev/sdc4 3147 60801 463113787+ fd Linux raid autodetect
Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003aac1
Device Boot Start End Blocks Id System
/dev/sdd1 * 1 13 104391 83 Linux
/dev/sdd2 14 2624 20972857+ fd Linux raid autodetect
/dev/sdd3 2625 3146 4192965 82 Linux swap / Solaris
/dev/sdd4 3147 60801 463113787+ fd Linux raid autodetect
Disk /dev/md0: 21.4 GB, 21476081664 bytes
2 heads, 4 sectors/track, 5243184 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000
Disk /dev/md0 doesn’t contain a valid partition table
Disk /dev/md2: 948.4 GB, 948456390656 bytes
2 heads, 4 sectors/track, 231556736 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000
Disk /dev/md2 doesn’t contain a valid partition table
Disk /dev/sde: 4102 MB, 4102029312 bytes
33 heads, 63 sectors/track, 3853 cylinders
Units = cylinders of 2079 * 512 = 1064448 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sde1 1 3854 4005872 7 HPFS/NTFS
Never have I been so surprised but today when booted from OpenSUSE 11.1 GNOME Live CD. I found /dev/md126 and /dev/md127 raid arrays instead of /dev/md0 and /dev/md2 surpirsingly.
Not only did OpenSUSE 11.1 misassign device names (/dev/md126 = /dev/md2 and /dev/md127 = /dev/md0, consequently) but also it stated /dev/md0 was down according to OpenSUSE 11.1. What’s more discouraging is that when I check installation media, it says it’s incorrect. I burned 3 cd’s with twicely downloaded iso-image on two different PC’s, thinking that there might be mistake when burning. Is there a mistake in the image? I’m upset/
> I burned 3 cd’s with twicely downloaded iso-image on two different PC’s,
> thinking that there might be mistake when burning. Is there a mistake in
> the image? I’m upset/
check the .iso before you burn the disk, and then check the disk
before you begin the install
see that and other important info here: http://tinyurl.com/6jwtg9
if you installed from defective install media there is no telling what
is wrong with your system…
–
goldie
Thank you for your note. I forgot to mention that each time I checked the iso md5sum and it was correct! I thought that my cd-rom was kind of defective and used another cd-rom to burn the image but the result was the same - it would read “check failure” at about 99%
there are postings here on how to burn a good cd/dvd and the
importance of using high quality media and burning at the lowest
possible burn speed
see http://tinyurl.com/6jwtg9
and http://forums.opensuse.org/search.php
–
goldie
Thank you, Goldie for your remarks. Unfortunately, I followed the steps described. But burning cd’s correctly is not my real problem.
Still no answer for my main question.