Setup:
- 2.0.36 with no patches
- raidtools-0.50beta10
- md compiled in
- raid5.o in /lib/modules/2.0.36/block
# cat /etc/raidtab
raiddev /dev/md0
raid-level 5
nr-raid-disks 3
nr-spare-disks 0
chunk-size 256
device /dev/sdb1
raid-disk 0
device /dev/sda1
raid-disk 1
device /dev/sdc1
raid-disk 2
# cat /proc/mdstat
Personalities :
read_ahead not set
md0 : inactive sdb1 sda1 sdc1 13325823 blocks
md1 : inactive
md2 : inactive
md3 : inactive
With kerneld running in debug mode I get the following message:
# raidrun -a
169:job (0804b3f8) scheduled, type request_module ('md-personality-4')
169:job (0804b3f8) stored, pid=1200
169:finish_jobs
169:SIGCHLD: job=0x804b3f8, pid=1200, status=1
169:finish_jobs
169:job (0804b3f8) unlinked
Naturally everything works if I run "modprobe raid5". I've tried every
resource to find an answer as to why when running raidadd kerneld
doesn't load raid5 automatically. Where am I going wrong?
