Here is some more information from me, as I had not much time this morning: regardless of the passphrase I enter, any is accepted (also wrong ones!!!) and the behaviour after that is the same. Some I captured both standard and (recovery mode) below (please note that the below was copied using an eye to finger scanner)
standard 2.6.32-5-amd64 starts with >>>> 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 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: <<<<- >From that time on the drive LED keeps flickering, even before entering 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-de...@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: <<<< -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
