md autodetect doesn't work with 2.6.[34]
My md devices doesn't get automatically started with kernels
2.6.[34]-1-686. They do get started with 2.4.25-1-686.
This is the relevant (hope so anyway;-) part of boot messages from the
md module is inserted and the first device started from 2.4.25:
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
136 [events: 0000000f]
137 md: bind<ide/host0/bus1/target1/lun0/part1,1>
138 md: ide/host0/bus1/target1/lun0/part1's event counter:
0000000f
139 md: raid1 personality registered as nr 3
140 md0: max total readahead window set to 124k
141 md0: 1 data-disks, max readahead per data-disk: 124k
142 raid1: device ide/host0/bus1/target1/lun0/part1 operational as
mirror 0
143 raid1: md0, not all disks are operational -- trying to recover
array
144 raid1: raid set md0 active with 1 out of 2 mirrors
145 md: updating md0 RAID superblock on device
146 md: ide/host0/bus1/target1/lun0/part1 [events:
00000010]<6>(write) ide/host0/bus1/target1/lun0/part1's sb offset:
128384
147 md: recovery thread got woken up ...
148 md0: no spare disk to reconstruct array! -- continuing in
degraded mode
149 md: recovery thread finished ...
150 [events: 00000011]
151 md: bind<ide/host0/bus0/target0/lun0/part6,1>
152 [events: 00000011]
With 2.6.[34] I just get the message that the module is loaded:
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
--
Daniel Lundin
Department of Molecular Biology & Functional Genomics
Arrhenius Laboratories for Natural Sciences
Stockholm University, SE-106 91 Stockholm, Sweden
tel. +46 8 16 41 95, mobile: +46 708 123 922
Email: daniel.lundin@molbio.su.se
Reply to: