On Sun, Aug 29, 2010 at 9:38 AM, Toni Mueller <supp...@oeko.net> wrote:
>
> Hi,
>
> On Sun, 29.08.2010 at 07:18:36 +0200, Dh H <dhh4...@googlemail.com> wrote:
>> Downgrading MDADM helped for me, but not completely.
>> The behaviour at the beginning is still the same, such that it does
>> not find the volume-group.
>> But now I am dropped into a shell instead of getting these
>> /sys/devices/virtual/block/mdX
>> messages.
>
> IOW, you need to manually intervene to get the machine to actually
> boot, but the whole process is now faster than waiting until the
> system "figures it out" on it's own, right?
>
Actually it the system does not figure it out, as it does not find my
root filesystem:
I now get this while booting:
>>>
mdadm: /dev/md0 has been started with 2 drives
mdadm: /dev/md1 has been started with 2 drives
Volume Group "m" not found
skipping volume group m
unable to find LVM volume m/root
Gave up waiting for root device
.... < some unapplicable hints ;) ....
ALERT! /dev/mapper/m-root does not exist. Dropping into shell
Busybox ....
(initramfs)
<<<<
In busybox I have to start the cryptodrive with
cryptsetup luksOpen md1 md1_crypt
and then start the vg/lv with
lvm vgscan
vgchange -a y
when I exit from the shell the system boots as it finds the root
device after the above
BTW: I have upgraded grub from 1.98+20100804-2 to 1.98+20100804-4
before I downgraded mdadm. This did not help on itself. As to wheather
this now creates the the dropping into busybox I cannot judge.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
