Bug#549083: Not working with 3.0.3-2

Hello, Am Montag, den 09. November schrieb martin f krafft: > unmerge 549083 > retitle 549083 initramfs hook introduces single quotes into homehost name > reopen 549083 > notfixed 549083 > tags 549083 patch > thanks > > also sprach Neil Brown [2009.11.09.0534 +0100]: > > [ -n "${MD_HOMEHOST:-}

Bug#549083: Not working with 3.0.3-2

unmerge 549083 retitle 549083 initramfs hook introduces single quotes into homehost name reopen 549083 notfixed 549083 tags 549083 patch thanks also sprach Neil Brown [2009.11.09.0534 +0100]: > [ -n "${MD_HOMEHOST:-}" ] && extra_args="--homehost='$MD_HOMEHOST'" > if $MDADM --assemble --scan -

Bug#549083: Not working with 3.0.3-2

On Sunday November 8, berbe...@fmi.uni-passau.de wrote: > hello, > > Am Sonntag, den 08. November schrieb M G Berberich: > > still not working with mdadm 3.0.3-2. During boot it failes with: > > > > Begin: Assemble all MD arrays ... Failure: failed to assemble all arrays > > > > and then can

Bug#549083: Not working with 3.0.3-2

hello, Am Sonntag, den 08. November schrieb M G Berberich: > still not working with mdadm 3.0.3-2. During boot it failes with: > > Begin: Assemble all MD arrays ... Failure: failed to assemble all arrays > > and then can't mount the root-fs. Downgrading to mdadm 2.6.7.2-3 makes > it work aga

Bug#549083: not working for me since 3.0-3.1

Hello, my machine with root on raid won't boot since 3.0-3.1 and also still not with 3.0.3-1. I manually choose my older 2.6.29 kernel in grub now as a workaround. I tried re-generating the initrd for 2.6.30-2 to make sure it is using the new mdadm/udev but this didn't help. The initrd can be

Bug#549083: Not working with 3.0.3-1

also sprach M G Berberich [2009.10.29.2129 +]: > I have a simple RAID1 setup, no crypto. And it's not working since > upgrading to mdadm 3. At boot it failes to assemble the arrays. You will need to provide a lot more information. For instance, start with uploading /boot/initrd.img-$(uname-rn

Bug#549083: Not working with 3.0.3-1

Hello, I have a simple RAID1 setup, no crypto. And it's not working since upgrading to mdadm 3. At boot it failes to assemble the arrays. mdadm 3.0.3-1 is still not working. During boot it failes with: Begin: Assemble all MD arrays ... Failure: failed to assemble all arrays and then can't m

Bug#549083:

As reported in #538843 it is the same for me. I do not have encrypted partitions so I don't think it is related to encryption but more the recent change mades in mdadm about volume_id's -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Tr

Bug#549083: mdadm: Since 3.0-3.1, created initrd doesnt allow the system to boot

Package: mdadm Version: 3.0-3.1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I apologize if the problem is related to udev instead of mdadm. In this case, both packages have been updated as the same time and I've had already the problem with udev breaking mdadm few days