On Wed, 2007-06-27 at 08:48 -0700, Andrew Burgess wrote:
Odd
Maybe you have an initrd which is loading md as a module, then
running raidautorun or similar?
..
I suspect that the last comment is the clue, after pivotroot I bet it
runs another init, not from the boot/initrd images,
Odd
Maybe you have an initrd which is loading md as a module, then
running raidautorun or similar?
..
I suspect that the last comment is the clue, after pivotroot I bet it
runs another init, not from the boot/initrd images, but from the init.d
in the root filesystem.
One quick way to
When I try and disable auto detection, with kernel boot parameters, it
goes ahead and auto assembles and runs anyway. The md= parameters seem
to be noticed, but don't seem to have any other effect (beyond resulting
in a dmesg).
Here is the result
$ dmesg | egrep 'raid|md:'
Kernel
On Tuesday June 26, [EMAIL PROTECTED] wrote:
When I try and disable auto detection, with kernel boot parameters, it
goes ahead and auto assembles and runs anyway. The md= parameters seem
to be noticed, but don't seem to have any other effect (beyond resulting
in a dmesg).
Odd
Maybe you
On Tue, 2007-06-26 at 16:38 +1000, Neil Brown wrote:
On Tuesday June 26, [EMAIL PROTECTED] wrote:
When I try and disable auto detection, with kernel boot parameters, it
goes ahead and auto assembles and runs anyway. The md= parameters seem
to be noticed, but don't seem to have any other
Ian Dall wrote:
On Tue, 2007-06-26 at 16:38 +1000, Neil Brown wrote:
On Tuesday June 26, [EMAIL PROTECTED] wrote:
When I try and disable auto detection, with kernel boot parameters, it
goes ahead and auto assembles and runs anyway. The md= parameters seem
to be noticed, but don't seem
