Your message dated Fri, 25 Sep 2009 07:57:49 +0200 with message-id <20090925055749.GA22437@stro.at> and subject line Re: initramfs-tools: Unable to detect LVM on Raid for root partition. has caused the Debian Bug report #450762, regarding initramfs-tools: Unable to detect LVM on Raid for root partition. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 450762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450762 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: initramfs-tools: Unable to detect LVM on Raid for root partition.
- From: Daniel Reurich <daniel@centurion.net.nz>
- Date: Sat, 10 Nov 2007 20:56:07 +1300
- Message-id: <20071110075607.3575.95822.reportbug@localhost.localdomain>
Package: initramfs-tools Severity: important mdadm correctly assembles the raid1, but the vgchange -ay $vg fails to find the volume group. I did a little hack to /scripts/local-top/lvm2 that calls vgchange -ay again if it failed the first time succeeds in finding the volume group. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core) Locale: LANG=en_NZ, LC_CTYPE=en_NZ (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
- To: 450762-done@bugs.debian.org
- Subject: Re: initramfs-tools: Unable to detect LVM on Raid for root partition.
- From: maximilian attems <max@stro.at>
- Date: Fri, 25 Sep 2009 07:57:49 +0200
- Message-id: <20090925055749.GA22437@stro.at>
closing as no follow up since report and most likely timing issue. use as recommended in release notes bootarg: "rootdelay=X"
--- End Message ---