Bug#526525: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0
On Sat, May 9, 2009 at 12:35 AM, martin f krafft <madduck@debian.org> wrote:
> retitle 526525 amd64 kernel cannot find bnx2 PCI device base address
Um. BNX2 is the network card? WTF does it have to do with being able
to mount and boot off RAID in 64-bit mode only?
> also sprach Tony Godshall <togo@of.net> [2009.05.09.0117 +0200]:
>> > If you cannot boot, append break=mount to the kernel line, and at
>> > the initramfs prompt, type
>> >
>> > rm /etc/mdadm/mdadm.conf
>> > /scripts/local-top/mdadm
>> > <ctrl-d>
>> >
>> > and then fix the initramfs.
>>
>> I'm not interested in deleting mdadm.conf or taking any other steps
>> that might break the existing functionality.
>
> I considered it a necessary step in my analysis, but if you prefer
> to do things your way, it's your system. Note that I would have
> never proposed anything that made permanent changes without adequate
> warning.
rm /etc/mdadm.conf ? Maybe mv. Anyhow, I'm giving more info below
and am open to suggestions on how to acquire more.
>> I'm not reporting this bug because I must have an amd64 kernel-
>> like I said, the 686 and 686bigmem kernels are working.
>> I initiated this bug to help get the amd64 version of the kernel
>> (or mdadm?) fixed. I'm interested in steps that will help fix the
>> packages, not manually work around its flaws.
>
> Then please provide all the necessary infos. mdadm works perfectly
> fine with amd64 kernels. I think your problem is that the kernel
> doesn't initialise the drives you're using properly, so mdadm
> doesn't find them when trying to assemble.
>
> You will have to make sure the kernel sees your drives. From what
> you've allowed me to see, I can conclude that this is not a RAID
> problem.
Please find below my mdadm.conf.
I assume the dmesg output would be useful but I'm not sure how to
capture that in the initramfs environment.
Let me know what else comprises the "necessary infos" I have failed to provide.
# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=4
UUID=1cdfc35d:237af2b8:58db9480:16165906
# This file was auto-generated on Mon, 27 Apr 2009 02:47:01 -0700
# by mkconf $Id$
Best Regards.
Please keep in touch.
This is unedited.
P-)
> --
> .''`. martin f. krafft <madduck@d.o> Related projects:
> : :' : proud Debian developer http://debiansystem.info
> `. `'` http://people.debian.org/~madduck http://vcs-pkg.org
> `- Debian - when you have better things to do than fixing systems
>
> fashions have done more harm than revolutions.
> -- victor hugo
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkoFMkEACgkQIgvIgzMMSnUk5ACfcRDawcJVFhpm2RqdxehK64Mv
> +10An3TllsHOk1io8ho4e8nW4CxlUGZL
> =jHa4
> -----END PGP SIGNATURE-----
>
>
Reply to: