Public bug reported: 32 bit Edgy beta.
bootchart: http://librarian.launchpad.net/4918059/edgy-20061021-1.png One 160gb drive Partitions: * 1gig swap * 20gig root (ext3) * 20gig /home (ext3) * rest a data (no OS files) partition (vfat) Two 250gb drives * one partion, in RAID1 array with mdadm (just used for data (no OS files), ext3) I think I have an unconventional setup with my RAID array. I first created this array in Dapper. When I moved to Edgy, I did a fresh install from CD. After I had Edgy installed, I couldn't get my array to be assembled on boot, so after every boot, I would have to run this to get access to my data: sudo mknod -m 0660 /dev/md0 b 9 0 && sudo mdadm --assemble /dev/md0 --scan && sudo mount /dev/md0 /raid-data/ mdadm.conf: DEVICE partitions ARRAY /dev/md0 level=raid1 num-devices=2 UUID=3dcc3d57:4499d301:a27ac102:cf8ea623 Every time I boot, grub loaded & booted to the splash. The progress bar would fill up maybe 5 millimeters then not go any further for about 5 seconds. After 5 seconds, it would go to a blank screen with a flashing underline in the top left corner. It would stay at this point for roughly 4 minutes. Once this blank screen disappeared, the system continues to boot to the login screen. Pressing Ctrl+C or Ctrl+D has no effect. If you look at the bootchart above, mdadm and a subprocess md seem to be running A LOT. Because I am not a developer, I cannot give any technical information on this bug, apart from that a 5 minute boot time is very annoying. ** Affects: mdadm (Ubuntu) Importance: Undecided Status: Unconfirmed -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
