Ez fura! Nekem mdadm autodetectalja a raid diszkeket, igy pl. ez van a dmesg-ben:
...
[ 3.023797] sda: sda1 sda2 sda3
[ 3.040354] sd 1:0:0:0: [sda] Attached SCSI disk
[ 5.240045] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
[ 5.246459] ata4.00: ATA-7: SAMSUNG HD154UI, 1AG01113, max UDMA7
[ 5.246462] ata4.00: 2930277168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 5.252972] ata4.00: configured for UDMA/100
[ 5.253072] scsi 3:0:0:0: Direct-Access ATA SAMSUNG HD154UI 1AG0 PQ: 0 ANSI: 5
[ 5.253284] sd 3:0:0:0: Attached scsi generic sg1 type 0
[ 5.253600] scsi 4:0:0:0: Direct-Access ATA SAMSUNG HD154UI 1AG0 PQ: 0 ANSI: 5
[ 5.253717] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 5.253925] sd 4:0:0:0: [sdc] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
[ 5.253975] sd 4:0:0:0: [sdc] Write Protect is off
[ 5.253979] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 5.254004] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5.254114] sd 3:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
[ 5.254200] sd 3:0:0:0: [sdb] Write Protect is off
[ 5.254203] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 5.254229] sdc:
[ 5.254313] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5.254435] sdb: sdb1 sdb2 sdb3
[ 5.265850] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 5.267171] sdc1 sdc2 sdc3
[ 5.271174] sd 4:0:0:0: [sdc] Attached SCSI disk
[ 5.580033] ata6: SATA link down (SStatus 0 SControl 300)
[ 5.590851] async_tx: api initialized (async)
[ 5.760025] raid6: int64x1 1498 MB/s
[ 5.930035] raid6: int64x2 1939 MB/s
[ 6.100030] raid6: int64x4 1316 MB/s
[ 6.270026] raid6: int64x8 1323 MB/s
[ 6.440031] raid6: sse2x1 2223 MB/s
[ 6.610027] raid6: sse2x2 3001 MB/s
[ 6.780012] raid6: sse2x4 3188 MB/s
[ 6.780014] raid6: using algorithm sse2x4 (3188 MB/s)
[ 6.795423] xor: automatically using best checksumming function: generic_sse
[ 6.840014] generic_sse: 5926.400 MB/sec
[ 6.840017] xor: using function: generic_sse (5926.400 MB/sec)
[ 6.850768] md: raid6 personality registered for level 6
[ 6.850771] md: raid5 personality registered for level 5
[ 6.850774] md: raid4 personality registered for level 4
[ 6.859735] md: raid10 personality registered for level 10
[ 6.971103] md: bind<sda1>
[ 7.001131] md: bind<sda3>
[ 7.017220] md: bind<sdc1>
[ 7.025693] md: bind<sdc3>
[ 7.055790] md: bind<sdb3>
[ 7.058411] raid5: device sdb3 operational as raid disk 2
[ 7.058416] raid5: device sdc3 operational as raid disk 0
[ 7.058419] raid5: device sda3 operational as raid disk 1
[ 7.058939] raid5: allocated 3230kB for md3
[ 7.059220] 2: w=1 pa=0 pr=3 m=1 a=2 r=3 op1=0 op2=0
[ 7.059223] 0: w=2 pa=0 pr=3 m=1 a=2 r=3 op1=0 op2=0
[ 7.059227] 1: w=3 pa=0 pr=3 m=1 a=2 r=3 op1=0 op2=0
[ 7.059229] raid5: raid level 5 set md3 active with 3 out of 3 devices, algorithm 2
[ 7.059232] RAID5 conf printout:
[ 7.059233] --- rd:3 wd:3
[ 7.059236] disk 0, o:1, dev:sdc3
[ 7.059238] disk 1, o:1, dev:sda3
[ 7.059240] disk 2, o:1, dev:sdb3
[ 7.059280] md3: detected capacity change from 0 to 2999233019904
[ 7.061458] md3: unknown partition table
...
Sima ubuntu-s initrd-s mdadm. Nem is foglalkoztam sose, hogy melyik diszk hanyadik a tombben. Ez most akkor hogyan is van?