Re: Problems with 2.4.9 auto-detecting raid arrays.
Funny how posting to a list, after trying to solve it yourself
for a day or so, can result in solving your own problem, an
hour later.
After posting, I spent some time perusing ./drivers/md/md.c, and
realized that the kernel requires some boot parameters to tell it
which disks to probe for the persistent super block info. This
would probably be a good thing to get added to the HOWTO.
So, to use my problem below, I appended the following to my
boot prompt:
SILO: linux md=0,/dev/sda1,/dev/sde1
And I was rewarded with:
md: raid0 personality registered
md: raid1 personality registered
md: raid5 personality registered
raid5: measuring checksumming speed
VIS : 104.800 MB/sec
raid5: using function: VIS (104.800 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
md: Loading md0: /dev/sda1
(read) sda1's sb offset: 64704 [events: 00000006]
md: bind<sda1,1>
(read) sde1's sb offset: 64704 [events: 00000006]
md: bind<sde1,2>
md: sde1's event counter: 00000006
md: sda1's event counter: 00000006
md0: max total readahead window set to 248k
md0: 1 data-disks, max readahead per data-disk: 248k
raid1: device sde1 operational as mirror 1
raid1: device sda1 operational as mirror 0
raid1: raid set md0 active with 2 out of 2 mirrors
md: updating md0 RAID superblock on device
md: sde1 [events: 00000007](write) sde1's sb offset: 64704
md: sda1 [events: 00000007](write) sda1's sb offset: 64704
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 2048 buckets, 32Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
---> Note, the root filesystem only got mounted here!
Hope this helps someone else.
Cheers,
k
On Mon, Oct 08, 2001 at 09:22:34PM -0400, keith@ajmani.org wrote:
> Hello:
>
> I'm running potato on an Ultra5, upgraded to 2.4.9. I have an ISP
> Qlogic SCSI controller, and two external MultiPacks with 4x4GB SCSI
> drives in them.
>
> I'm able to create and use RAID-1 arrays, no problems. The problem
> is, I would like to boot of RAID. However, its seems that the
> kernel fails to auto-detect them at boot-time, despite:
>
> - compiling in RAID support, and RAID1 and RAID0
> - setting the partition types of the two mirrored partitions to 0xFD
> (doesn't work as 0x83 either)
>
> The raid array does get detected and started OK after mounting the
> root partition and running /etc/init.d/raid2. However, I would
> like it to happen before that point, obviously, and this is
> supposed to work. (See the snippets from 'dmesg' below)
>
> The linux-raid mailing list appears to be dead, so this list is
> my only resource.
>
> If anyone has had any sucess with sparc-raid-kernel-detection,
> please let me know.
>
> I saw an earlier thread where Ben Collins commented that the
> IOCTLs might not be fully there to support RAID, could this
> be related.
>
> Any help is appreciated.
>
> Thanks,
>
> Keith
>
> Some details:
>
> /etc/raidtab:
> raiddev /dev/md0
> raid-level 1
> nr-raid-disks 2
> nr-spare-disks 0
> chunk-size 32
> persistent-superblock 1
> device /dev/sda1
> raid-disk 0
> device /dev/sde1
> raid-disk 1
>
> dmesg: shortened to relevant bits with "...", and some [comments]
> ...
> SCSI subsystem driver Revision: 1.00
> qlogicisp : new isp1020 revision ID (5)
> scsi0 : QLogic ISP1020 SCSI on PCI bus 03 device 20 irq 6969600 MEM base 0x1ff02808000
> ...
> Attached scsi disk sda at scsi0, channel 0, id 1, lun 0
> ...
> Attached scsi disk sde at scsi0, channel 0, id 9, lun 0
> SCSI device sda: 8385121 512-byte hdwr sectors (4293 MB)
> sda: sda1 sda2 sda3 sda8
> ...
> SCSI device sde: 8385121 512-byte hdwr sectors (4293 MB)
> sde: sde1 sde2 sde3 sde8
> md: raid0 personality registered
> md: raid1 personality registered
> md: raid5 personality registered
> raid5: measuring checksumming speed
> VIS : 104.800 MB/sec
> raid5: using function: VIS (104.800 MB/sec)
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: Autodetecting RAID arrays.
> md: autorun ...
> ---> [This is where it should have detected the array, /dev/md0]
> md: ... autorun DONE.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 2048 buckets, 32Kbytes
> TCP: Hash tables configured (established 16384 bind 16384)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> VFS: Mounted root (ext2 filesystem) readonly.
> ---> [Here the kernel mounts the boot disk, scsi/ext2]
> Adding Swap: 261344k swap-space (priority -1)
> (read) sda1's sb offset: 64704 [events: 00000002]
> (read) sde1's sb offset: 64704 [events: 00000002]
> md: autorun ...
> md: considering sde1 ...
> md: adding sde1 ...
> md: adding sda1 ...
> md: created md0
> md: bind<sda1,1>
> md: bind<sde1,2>
> md: running: <sde1><sda1>
> ---> [Here it finds the array!]
> md: now!
> md: sde1's event counter: 00000002
> md: sda1's event counter: 00000002
> md0: max total readahead window set to 248k
> md0: 1 data-disks, max readahead per data-disk: 248k
> raid1: device sde1 operational as mirror 1
> raid1: device sda1 operational as mirror 0
> raid1: raid set md0 active with 2 out of 2 mirrors
> md: updating md0 RAID superblock on device
> md: sde1 [events: 00000003](write) sde1's sb offset: 64704
> md: sda1 [events: 00000003](write) sda1's sb offset: 64704
> md: ... autorun DONE.
>
> /usr/src/linux/.config: (relevant bits)
> (compiled with egcs-64)
> #
> # Multi-device support (RAID and LVM)
> #
> CONFIG_MD=y
> CONFIG_BLK_DEV_MD=y
> CONFIG_MD_LINEAR=m
> CONFIG_MD_RAID0=y
> CONFIG_MD_RAID1=y
> CONFIG_MD_RAID5=y
> CONFIG_BLK_DEV_LVM=m
> CONFIG_BLK_DEV_RAM=m
> CONFIG_BLK_DEV_RAM_SIZE=4096
>
>
> --
> To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: