Ubuntu distro with lvm2, raid 1, not booting anymore.
Welcome!
I have the serious problem with booting of my machine. It is run on Ubuntu distro (5.10), with lvm2 raid 1 on two identical sata hard disks. Lilo bootloader. The problem is that after small change in lilo.conf and running /sbin/lilo my system is no longer bootable. I see 'kernel panic' message. When I try to run lilo again (from Ubuntu Live! cd) I see some comments somehow related to dev-mapper:
Warning: /proc/partitions does not match /dev directory structure Name change: /dev/cloop 0 -> /tmp/dev.0
(...)
Fatal: is_primary: Not a valid device
I don't know how to handle these problesm. Looking over net didn't help me. So I decided to write on this mailing list. If you can help me anyway, even just redirecting me to appropriate group / chanel where people will help me to deal with these problem, I will appreciate it. Thanks in advance!
My lilo version is 22.6.1
dev-mapper version is 1.11.0
kernel (default of Ubuntu 5.10): 2.6.12-10-386
I will quote the kernel messages:
RAMDISK: ran out of compressed data
invalid compressed format (err=1)
VFS: Cannot open root device "fd02" or unknow-block (253,2) Please append a correct "root=" root option
Kernel panic - not syncing: VFS: Unable to mount root fs
unknown-block (253,2)
That is all. It looks like kernel is doing some hardware recognition and then stops.
Kind regards,
Maciej Slojewski (mslonik)
Quoted 8 lines · Maciej S?ojewski
Welcome!
I have the serious problem with booting of my machine. It is run on Ubuntu distro (5.10), with lvm2 raid 1 on two identical sata hard disks. Lilo bootloader. The problem is that after small change in lilo.conf and running
/sbin/lilomy system is no longer bootable. I see 'kernel panic' message. When I try to run lilo again (from Ubuntu Live! cd) I see some comments somehow related to dev-mapper:Warning:
/proc/partitionsdoes not match /dev directory structure Name change:/dev/cloop0 ->/tmp/dev.0
(...)
Fatal:is_primary: Not a valid device
what is exactly that you are doing to reinstall lilo? i don't use ubuntu, but generally:
you should mount your original root fs on, say, /root mount --bind /dev /root/dev
mount --bind /proc /root/proc
mount --bind /sys /root/sys
chroot /root /sbin/lilo
Quoted 4 lines
I will quote the kernel messages:
RAMDISK: ran out of compressed data
invalid compressed format (err=1)
looks like your initrd is hosed
check that lilo is pointing to a correct initrd and/or regenerate initrd. (no i don't remember the debian way to regenerate initrd)
L.
Signature · 6 lines
Luca Berra -- [email protected] Communication Media & Services S.r.l. /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML MAIL / \
Quoted 7 lines · Luca Berra
Quoted 4 lines · Maciej S?ojewski
Welcome!
I have the serious problem with booting of my machine. It is run on Ubuntu distro (5.10), with lvm2 raid 1 on two identical sata hard disks. Lilo bootloader. The problem is that after small change in lilo.conf and running
/sbin/lilomy system is no longer bootable. I see 'kernel panic' message. When I try to run lilo again (from Ubuntu Live! cd) I see some comments somehow related to dev-mapper:
Quoted 7 lines
what is exactly that you are doing to reinstall lilo? i don't use ubuntu, but generally:
you should mount your original root fs on, say, /root mount --bind /dev/root/dev
mount --bind /proc/root/proc
mount --bind /sys/root/sys
chroot /root/sbin/lilo
Dear Luka,
Thanks a lot for your answer and a clue. Unfortunately it doesn't help me :-(
Here you go, what am I doing after system start:
* Ubuntu Live! CD is booting, I hit <ener> key
* system is starting in graphical mode
* I open terminal window
# sudo su # cd /mnt # mkdir dev proc boot sys # mount -v -t ext3 /dev/PV/boot /mnt/boot dev/mapper/PV-boot on /mnt/boot type ext3 (rw) # mount -v -t ext3 /dev/PV/root /mnt/root dev/mapper/PV-root on /mnt/root type ext3 (rw) #mount -v -t proc none /mnt/proc none on /mnt/proc type proc (rw) #mount -v -t sysfs none /mnt/sys none on /mnt/sys type sysfs (rw)
#chroot /mnt /bin/bash
#lilo
Warning: '/proc/partitions' does not match '/dev' directory structure Name changes '/dev/cloop0' -> '/tmp/dev.0'
Warning: '/dev' directory structure is incomplete; device (240,0) is missing
Warning: '/dev' directory structure is incomplete; device (254,0) is missing
Warning: '/dev' directory structure is incomplete; device (254,1) is missing
Warning: '/dev' directory structure is incomplete; device (254,2) is missing
Warning: '/dev' directory structure is incomplete; device (254,3) is missing
Warning: '/dev' directory structure is incomplete; device (254,4) is missing
Warning: '/dev' directory structure is incomplete; device (254,5) is missing
Warning: '/dev' directory structure is incomplete; device (254,6) is missing
Fatal: is_primary: Not a valid device 0xFE07
:-((( Please help me, what can I do now?
I have regenerated initrd, (update-initrd command). It did not help too.
Kind regards,
Maciej (mslonik)