Am Donnerstag, den 26.08.2010, 11:07 +0200 schrieb Toni Mueller: > After several (5?) minutes where the machine didn't do anything I was > able to see, the screen was suddenly flushed with a large number of > messages like: > > /sys/devices/virtual/block/md0 (10715) > /sys/devices/virtual/block/md1 (10716) > /sys/devices/virtual/block/md0 (10717) > /sys/devices/virtual/block/md1 (10718) > /sys/devices/virtual/block/md0 (10719) > /sys/devices/virtual/block/md1 (10720) > /sys/devices/virtual/block/md0 (10721) > Unlocking the disk /dev/md1 (md1_crypt) > Enter the passphrase:
Am Samstag, den 28.08.2010, 23:58 +0200 schrieb Andreas v. Heydwolff: > Then I tried to boot, GRUB came up, the mds were started, and > > /sys/devices/virtual/block/md0 (numbers in the high 5000s here) > > scrolled by for all 3 arrays. The passphrase was entered and the machine > just remained stuck with the single server case hdd activity light on all the > time, both with a regular boot and a rescue mode boot, so I never got > past the passphrase promt. Am Sonntag, den 29.08.2010, 02:35 +0200 schrieb Agustin Martin: > May this be related to #583917, mdadm: long delay (6-200 minutes) > during boot (root device detection) after upgrade on RAID/LVM/LUKS > setup? Am Samstag, den 04.09.2010, 04:22 +0100 schrieb Darren: > upgrading to mdadm 3.1.4-1+8efb9d1 from sid solved my boot problems. > That is for both, the VM I set up for testing, as well as my base PC. > Both are booting fine now. This *might* indeed be a duplicate of #594418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594418 Best regards Alexander Kurtz
signature.asc
Description: This is a digitally signed message part
