No subject
Thu Aug 5 15:37:00 UTC 2010
the passphrase.
I stopped the try after approx 18hrs of waiting, cause I thought it is
maybe rebuilding the mirror be4 continueing.
With the same kernel but using (recovery mode) the behaviour is
slightly different:
>>>>
first I get normal boot messages for the first 15 seconds about CPU
started USB started (cannot capture this using xon/xoff)
[ <timestamp>] sd 0:0:0:0 Attached scsi generic sg0 type 0
[ <timestamp>] sd 0:0:0:0 Attached scsi generic sg1 type 0
[ <timestamp>] sd 0:0:0:0 Attached scsi generic sg2 type 5
Begin: Loading essential drivers ... done
Begin: Running /scripts/init-premount.... done
Begin: Mounting root file system ..... Begin: Running
/scripts/local-top ..... Begin: Loading [ <timestamp>] md: raid1
personality registered for level 1
Success: loaded module raid1
done.
Begin: Assembling all MD arrays .... [ <timestamp>] md: md0 stopped.
[ <timestamp>] md: bind <sdb1>
[ <timestamp>] md: bind <sda1>
[ <timestamp>] raid1: raid set md0 active with 2 out of 2 mirrors
[ <timestamp>] md0: detected capacity change from 0 to <boot device size>
mdadm: /dev/md0 has been started with 2 drives
[ <timestamp>] md0: unknown partition table
[ <timestamp>] md: md1 stopped.
[ <timestamp>] md: bind <sdb2>
[ <timestamp>] md: bind <sda2>
[ <timestamp>] raid1: raid set md0 active with 2 out of 2 mirrors
[ <timestamp>] md0: detected capacity change from 0 to <LVM device size>
mdadm: /dev/md1 has been started with 2 drives
[ <timestamp>] md0: unknown partition table
Success: Assembled all arrays
[ <timestamp>] device-mapper: uevent: Version 1.0.3
[ <timestamp>] device-mapper: ioctl 4.15.0-ioctl (2009-04-01)
initialised: dm-devel at redhat.com
Volume Group "m" not found
Skipping Volume group m
Unable to find LVM volume m/root
cryptsetup: vm device name (/dev/disk/by-uuid/<uuid>) does not begin
with /dev/mapper
cryptsetup: evms_activate is not available
Begin: Waiting for encrypted source device ..... done
udevadm settle - timeout of 30 seconds reached, the event queue contains
/sys/devices/virtual/block/md0 (....)
.... + more of the above
Unlocking the disk /dev/disk/by-uuid/<uuid> (md1_crypt)
Enter Passphrase:
<<<<
More information about the Pkg-grub-devel
mailing list