Hi,
I don't know if this problem got treated yet, because I just joined this
list, so here goes:
I just installed the newest raid-patches (19981106-C) into a 2.0.35
kernel, and I also use the newest tools (19981105-0.90).
I gave all my raid-partitions the 0xfd type, but the kernel only finds the
raid-partitions on the first disk, so the autostart does not work.
I'm using three disks (/dev/sda /dev/sdb /dev/sdc) with several extended
partitions in a raid5 configuration.
raidstart --all
works like a charm, but I presume it gets the raid-info from the
/etc/raidtab file.
So I thought there might be something wrong with the raid-superblocks
(wrong version or something), but
mkraid /dev/md2 says
handling MD device /dev/md2
analyzing super-block
disk 0: /dev/sda7, 530113kB, raid superblock at 530048kB
array needs no upgrade
mkraid: aborted
So it needs no update. The weird thing is, it only mentions the first
raiddisk.
cat /proc/mdstat says (after the raidstart --all)
Personalities : [linear] [raid0] [raid1] [raid5] [translucent] [lvm]
read_ahead 128 sectors
md2 : active raid5 sdc7[2] sdb7[1] sda7[0] 0 blocks level 5, 256k chunk,
algorithm 2 [3/3] [UUU]
md5 : active raid5 sdc12[2] sdb12[1] sda12[0] 0 blocks level 5, 256k
chunk, algorithm 2 [3/3] [UUU]
md4 : active raid5 sdc9[2] sdb9[1] sda9[0] 0 blocks level 5, 256k chunk,
algorithm 2 [3/3] [UUU]
md3 : active raid5 sdc8[2] sdb8[1] sda8[0] 0 blocks level 5, 256k chunk,
algorithm 2 [3/3] [UUU]
md1 : active raid5 sdc6[2] sdb6[1] sda6[0] 0 blocks level 5, 256k chunk,
algorithm 2 [3/3] [UUU]
unused devices: <none>
thanks,
kind regards,
Anthony
- - 8<- - - - - 8<- - - - - 8<- - - - - 8<- - - - - 8<- - - - - 8<- - - - - 8<-
Bekemaheerd 113 e-mail: [EMAIL PROTECTED]
9737 PS Groningen home-page: http://www-th.phys.rug.nl/~hams
tel.: +31-50-5491254, +31-50-3637430 ICQ# 13019042
