On Tue, 08 Jun 2010 13:25:13 +0200 "Jean-Luc Coulon (f5ibh)" <jean-luc.cou...@wanadoo.fr> wrote:
> I've a system with lvm2 over raid1 and some filesystems encrypted. > When I updated mdadm from 3.1.1-1 to 3.1.2-1 the system failed to boot kernel > 2.6.34 (from experimental). > I tried 3.1.2-2 when it was released, I got the same problem. > > The system boot from grub and the wait for the password. > > When I enter the password, there is a huge / endless disk activity but the > boot > process seems to be frozen. > > The system is still living : if I plug/unplug an usb disk, it is reported on > the > console. > > I've then rebooted with 2.6.33 without any problem. > > Reverting to 3.1.1-1 solved also the problem. I wonder if it could be commit b179246f4f519082158279b2f45e5fd51842cc42 causing this. Can you report the contents of /etc/mdadm/mdadm.conf ?? Can you boot of a live CDROM and see if mdadm -As works, or spins or does something else bad? I'd love to know the cause of this before I release 3.1.3, but there is so little hard information to go on, it is hard to make progress. Thanks, NeilBrown -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
