Re: aboot vs. linux-image-2.6.24
Hi,
[del]
>scsi 0:0:3:0: Direct-Access COMPAQ BF01865222 B014 PQ: 0
>ANSI: 3
> target0:0:3: tagged command queuing enabled, command queue depth 16.
> target0:0:3: Beginning Domain Validation
> target0:0:3: asynchronous
> target0:0:3: wide asynchronous
> target0:0:3: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
> target0:0:3: Domain Validation skipping write tests
> target0:0:3: Ending Domain Validation
>Begin: Loading MD modules ...
>Success: loaded module raid456.
>Done.
>Begin: Assembling all MD arrays ...
>mdadm: No devices listed in conf file were found.
>
>I notice the above line - I thought MD arrays were supposed to self-
>assemble these days, and didn't need configuration files any more?
True, but you can provide one, which is more safe, i.e. if you have more
than one array on one host.
>Failure: failed to assemble all arrays.
>Done.
>Done.
>Begin: Waiting for root file system... ...
>Driver 'sd' needs updating - please use bus_type methods
>sd 0:0:0:0: [sda] 35565080 512-byte hardware sectors (18209 MB)
>sd 0:0:0:0: [sda] Write Protect is off
>sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, supports
>DPO and FUA
>sd 0:0:0:0: [sda] 35565080 512-byte hardware sectors (18209 MB)
>sd 0:0:0:0: [sda] Write Protect is off
>sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, supports
>DPO and FUA
> sda: sda1 sda2 sda3 sda4
>sd 0:0:0:0: [sda] Attached SCSI disk
[del]
I assume that you pasted the log as it was - but then the sequence is
a bit strange. The RAID-module should load *after* all SCSI-drivers
have been loaded, including sd. Maybe the older kernel had sd build-in
so that wasn't a problem?
HTH,
Uli
--
Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de | Listening to:
Stormweg 24 |Der Weisse Raum (Der Dritte Mann), Caligari
24539 Neumuenster, Germany|(Opération S), Sacred Decay (The Estranged)
Reply to: