[Bug 73952] Re: no devices found for /dev/md0 at startup

2007-04-13 Thread Pascal Rolle
*** This bug is a duplicate of bug 75681 *** https://bugs.launchpad.net/bugs/75681 I had the same problem. today's update fixed it for me (with 2.6.20-15-386 kernel image) -- no devices found for /dev/md0 at startup https://bugs.launchpad.net/bugs/73952 You received this bug notification bec

[Bug 73952] Re: no devices found for /dev/md0 at startup

2006-11-30 Thread Ben Collins
If you used the via82cxxx in edgy, then your drives were hda2 and hdb2, right? More than likely you need to tell mdadm that you are using sda and sdb now. Check /etc/mdadm/mdadm.conf. I suggest instead of device names, you use the UUID symlinks in /dev/disk/by-uuid/, so instead of /dev/sdb, you w

[Bug 73952] Re: no devices found for /dev/md0 at startup

2006-11-30 Thread Fabio Massimo Di Nitto
can you please add a dmesg output from .17 and .19 ? that will help to understand what's happening. Fabio -- no devices found for /dev/md0 at startup https://launchpad.net/bugs/73952 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 73952] Re: no devices found for /dev/md0 at startup

2006-12-01 Thread Grégoire Cachet
Ben> actually this is sda2 and sdb2 on my system ... And there is nothing in my mdadm.conf to tell about sda and sdb. Fabio> I can't get a dmesg of linux 2.6.19 because it doesn't boot at all. Tell if I can get some interesting informations from the busybox shell, because I don't know how. I incl

[Bug 73952] Re: no devices found for /dev/md0 at startup

2006-12-16 Thread Ben Collins
Please retest against 2.6.20-2 when it is available in the feisty archive. ** Changed in: linux-source-2.6.19 (Ubuntu) Sourcepackagename: linux-source-2.6.19 => linux-source-2.6.20 -- no devices found for /dev/md0 at startup https://launchpad.net/bugs/73952 -- ubuntu-bugs mailing list ubuntu-b

[Bug 73952] Re: no devices found for /dev/md0 at startup

2006-12-17 Thread Grégoire Cachet
Well, I found something interesting ... The kernel starts when I add quiet=n break=mount arguments to the boot command line in grub. Then, I hit Ctrl+D and it boots right. It works for 2.6.19 and 2.6.20. If I remove quiet=n or break=mount, it just breaks like before. I think there is an issue wi

[Bug 73952] Re: no devices found for /dev/md0 at startup

2006-12-17 Thread tbjablin
*** This bug is a duplicate of bug 75681 *** ** This bug has been marked a duplicate of bug 75681 initramfs script: race condition between sata and md -- no devices found for /dev/md0 at startup https://launchpad.net/bugs/73952 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https:

[Bug 73952] Re: no devices found for /dev/md0 at startup

2007-09-21 Thread Launchpad Janitor
*** This bug is a duplicate of bug 75681 *** https://bugs.launchpad.net/bugs/75681 [Expired for linux-source-2.6.20 (Ubuntu) because there has been no activity for 60 days.] -- no devices found for /dev/md0 at startup https://bugs.launchpad.net/bugs/73952 You received this bug notification b

[Bug 73952] Re: no devices found for /dev/md0 at startup

2007-03-08 Thread Sami J. Laine
*** This bug is a duplicate of bug 75681 *** This bug seems to be still active in both linux-image-2.6.20-9-i386 and linux-image-2.6.20-generic. With both images boot failes with RAID1 root. Updating initramfs doesn't seem to have any effect on this. -- no devices found for /dev/md0 at startup

[Bug 73952] Re: no devices found for /dev/md0 at startup

2006-12-23 Thread Jonathan Hseu
*** This bug is a duplicate of bug 75681 *** Confirming that this bug exists and that it still happens on 2.6.20-2 -- no devices found for /dev/md0 at startup https://launchpad.net/bugs/73952 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubu