>> *However*, I *still* get errors in dmesg logs... this time saying:
>>
>> request_module[md-personality-3]: Root fs not mounted
>> do_md_run() returned -22
>
>Strange... Is that before or after the initrd is unloaded, and the RAID
>set is mounted?
I don't know how to tell, but this these are the log lines just preceding
the lines mentioned above:
RAMDISK: Compressed image found at block 0
autodetecting RAID arrays
(read) hda5's sb offset: 136448 [events: 0000000a]
(read) hda6's sb offset: 7670912 [events: 0000000a]
(read) hdc1's sb offset: 131392 [events: 0000000a]
(read) hdc5's sb offset: 7717632 [events: 0000000a]
autorun ...
considering hdc5 ...
adding hdc5 ...
adding hda6 ...
created md1
bind<hda6,1>
bind<hdc5,2>
running: <hdc5><hda6>
now!
hdc5's event counter: 0000000a
hda6's event counter: 0000000a
request_module[md-personality-3]: Root fs not mounted
>
>> Partition check:
>> hda: hda1 hda2 <hda5 hda6>
>> hdc: hdc1 hdc2 <hdc5>
>...
>> Oops! md1 not running, giving up!
>> Bad md_map in ll_rw_block
>
>Could you send the output of :
>fdisk -l /dev/hda
>fdisk -l /dev/hdc
>
>along with /etc/raidtab? I'm mostly curious about the partition id's and
>sizes....
Here you go (obviously this is with the functioning 2.2.12-20 kernel in
use). I hope that you understand what these mean, because although I
understand the individual lines, I don't understand what they mean with
respect to my problem wholistically.
[root@metroid log]# /sbin/fdisk -l /dev/hda
Disk /dev/hda: 255 heads, 63 sectors, 977 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 5 40131 83 Linux
/dev/hda2 6 977 7807590 5 Extended
/dev/hda5 6 22 136521 fd Linux raid autodetect
/dev/hda6 23 977 7671006 fd Linux raid autodetect
[root@metroid log]# /sbin/fdisk -l /dev/hdc
Disk /dev/hdc: 16 heads, 63 sectors, 15574 cylinders
Units = cylinders of 1008 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 * 1 261 131512+ fd Linux raid autodetect
/dev/hdc2 262 15574 7717752 5 Extended
/dev/hdc5 262 15574 7717720+ fd Linux raid autodetect
[root@metroid log]# cat /etc/raidtab
raiddev /dev/md0
raid-level 0
nr-raid-disks 2
chunk-size 64k
persistent-superblock 1
#nr-spare-disks 0
device /dev/hdc1
raid-disk 0
device /dev/hda5
raid-disk 1
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
chunk-size 64k
persistent-superblock 1
#nr-spare-disks 0
device /dev/hda6
raid-disk 0
device /dev/hdc5
raid-disk 1
[root@metroid log]#
>Don't know, that's what I remember from the HOWTO's I read some time
>ago. I believe the point to be that lilo won't know about RAID at boot
>time, and it might get the blocks wrong, which is why you see "Loading
>Linux ......." and lilo stops.
Wasn't this the purpose behind having initrd? For example, on SCSI-based
systems where the drives cannot be detected before the SCSI driver is
loaded initrd use is a must. This situation is similar, isn't it?
Lee Howard
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
