Hi, Kevin, Glynn
Thanks for you answers and questions :)
>Glynn
>Change the "root=..." setting in lilo.conf.
>
>Essentially, your problem is that you're trying to boot directly from
>a software RAID device, but the device doesn't exist at boot time.
>
>You have to pass additional options to the kernel in order to tell it
>which devices (partitions) make up the RAID array. See
>Documentation/md.txt for details.
My lilo.conf and /etc/raidtab (which is explained in md.txt)
lilo.conf
________________
disk = /dev/md0
bios=0x80
sectors=63
heads=255
cylinders=553
partition=/dev/md1
start=63
boot=/dev/sda
map=/boot/map
prompt
timeout=150
vga=normal
# this CAN'T boot
image=/boot/bzImage.0428
root = /dev/md0
label = LRH0427
read-only
#this boots
image=/boot/vmlinuz
root = /dev/md0
label = LinuxRaid
read-only
#END.
________________
raidtab
________________
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
chunk-size 32
nr-spare-disks 0
persistent-superblock 1
device /dev/sda1
raid-disk 0
device /dev/sdb1
raid-disk 1
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
chunk-size 32
nr-spare-disks 0
persistent-superblock 1
device /dev/sda2
raid-disk 0
device /dev/sdb2
raid-disk 1
________________
I can't find a mistake. If younitice sth please let me know
>Kevin
>Did you run "make modules" and "make
>modulesinstall"?
Yes.
>If its not the kernel, its the way the boot
>loader is configured to boot the new kernel. Is that the same?
I've posted my lilo.conf, if you find sth please let me know :)
And I run lilo, lilo -q, etc , after editing lilo.conf
I'll try to do sth with initrd. May be the problem is here.
I'll continue to search the net
Have a nice weekend :)
-
: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
