# dmesg ** Attachment added: "dmesg.txt" http://librarian.launchpad.net/7605453/dmesg.txt
** Description changed: Hi, - I have installed Feisty (alternate CD). I created an md0 device (raid1). - I was surprised that there is still not something like a progress bar - for the resync of the partitions of my previously created md0 device. In - case of a small partition it doesn't matter so much, but in case of a - 300 Gb one could run into trouble after a reboot. Maybe it would be a - nice idea to regard the resync of md devices during installation. ;o) + I have installed Kubuntu-Desktop Feisty (alternate CD). I created an md0 + device (raid1). I was surprised that there is still not something like a + progress bar for the resync of the partitions of my previously created + md0 device. In case of a small partition it doesn't matter so much, but + in case of a 300 Gb one could run into trouble after a reboot. Maybe it + would be a nice idea to regard the resync of md devices during + installation. ;o) Then I have created a volume group for LVM. When I told the installer to create that logical volume I got a blue screen and the installer seemed to hang. On another console I have made this screenshot: http://www.asapos.de/pub/feisty/root-on-lvm-on-raid/IMG_0131.JPG There you see that it hangs for three upto four minutes. After that you get an error message: partman-lvm: Rendezvous with udev timed out for 'vgsys-root'; stat failed: No such file or directory partman-lvm: Logical volume "root" created As you can see in the screenshot this keeps on going for all my logical volumes. At the end I was able to boot cleanly into my system with lilo. But now I want to test the raid functionality. At first disconnected the second SATA drive. And started my PC again. The system hangs up for several minutes: http://www.asapos.de/pub/feisty /root-on-lvm-on-raid/IMG_0140.JPG After a while I got dropped into the busybox: http://www.asapos.de/pub/feisty/root-on-lvm-on-raid/IMG_0141.JPG With "mdadm --assemble --scan" I could reactivate my md device: http://www.asapos.de/pub/feisty/root-on-lvm-on-raid/IMG_0142.JPG and by pressing CTRL-D I could reboot into my system. At least I found my self in a full functioning system. I turned the machine off and connected the other drive again. Started it up and I did a resync of my md0 device. The next test is to disconnect the first drive of my two SATA disks. And started my Pc again. The system hangs up for several minutes: http://www.asapos.de/pub/feisty /root-on-lvm-on-raid/IMG_0143.JPG After a while I got dropped into the busybox and ith "mdadm --assemble --scan" I could reactivate my md device: http://www.asapos.de/pub/feisty /root-on-lvm-on-raid/IMG_0144.JPG and by pressing CTRL-D I could reboot into my system. At least I found again my self in a full functioning system. Again I halted the machine and reconnected the first SATA drive to my controller and powered the machine on again. In the middle of the bootprocess it got completely stuck and I wasn't dropped into a busybox: http://www.asapos.de/pub/feisty/root-on-lvm-on- raid/IMG_0145.JPG I turned the PC off again and booted up completely and I could do my resync again. Normally one should not be dropped into the busybox only because of a drive failure of one md device. If you guys need any further information or testing let me know. This problem is reproducible... Thanks a lot for any hint... -- root on lvm on raid (mdadm) on feisty https://bugs.launchpad.net/bugs/113627 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
