Kernel Panic when setting up RAID 5
 

Hi,

I am setting RAID 5 on slackware-current using instruction on ftp://ftp.slackware.com/pub/slackwar...EADME_RAID.TXT

When I am up to reboot part, kernel panic happens. Error said: Kernel panic - not syncing - VFS: unable to mount root fs on the unknown block(0,0) (I am using huge kernel)

I am having 4 hard drives, setup for RAID 5 is as follows

/dev/sda1: 100Mb /boot (parition type: FD) (/dev/md0)
/dev/sda2: 512Mb swap (parition type: FD) (/dev/md1)
/dev/sda3: balance / (parition type: FD) (/dev/md2)

The same setup for /dev/sdb, /dev/sdc, /dev/sdd

/etc/lilo.conf is followed instruction
append parameter
root=/dev/md2
boot=/dev/md0
raid-extra-boot=mbr-only

Not sure what I have missed

If anyone is able to help... Thanks

The boot partition cannot be on a RAID5.
Maybe you overlooked that. The boot partition can be at RAID1. What they try to say here that you should put boot on RAID1, the other partitions on RAID5.

jlinkels

Thanks for your quick response, I think I made /dev/md0 (which is boot parition) raid 1 anyways

mdadm --create /dev/md0 --level 1 --raid-devices 4 /dev/sd[abcd]1

(--level 1: is RAID 1, isnt it)

But kernel panic still happens, I actually have no clue how to solve it

What is the content of your mdadm.conf? Not sure if you applies to the huge kernel, but with generic, you have to rebuild initrd to get RAID support.

This is my /etc/mdadm.conf (http://postimg.org/image/s8m0i0iqb/).

Actually, what mkinitrd command did you run to create the initrd?

What are the contents of /boot/initrd-tree/etc/mdadm.conf?

Thanks Richard for the clue, I have successfully installed RAID 5 but using generic kernel. Just follow instruction on ftp://ftp.slackware.com/pub/slackwar...EADME_RAID.TXT

Extra step that I've done

Generate /boot/initrd.gz
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -c > /etc/mkinitrd.conf
# mdadm -Es > /boot/initrd-tree/etc/mdadm.conf
# mkinitrd -F
# lilo

Reboot

Thanks everyone