Re: initrd is too fast for md

2010-11-17 Thread Ivan Jager
On Thu, Nov 11, 2010 at 11:47:49PM +0100, Ferenc Wagner scribbled: > Michal Ludvig writes: > > > In my case scsi_wait_scan.ko didn't wait for all SCSI disks to be > > discovered, debian initramfs moved on prematurely and failed > > miserably. Recompiling the kernel without CONFIG_SCSI_SCAN_ASYNC

Re: initrd is too fast for md

2010-11-11 Thread Ferenc Wagner
Michal Ludvig writes: > In my case scsi_wait_scan.ko didn't wait for all SCSI disks to be > discovered, debian initramfs moved on prematurely and failed > miserably. Recompiling the kernel without CONFIG_SCSI_SCAN_ASYNC fixed > the problem for me. Actually, you don't need to recompile the kernel

Re: initrd is too fast for md

2010-11-10 Thread Michal Ludvig
Hi Ivan, On 11/10/2010 05:51 PM, Ivan Jager wrote: I recently installed testing on a Sun V240 but couldn't set up md/lvm during the install. I tried to submit an insallation report, but it doesn't seem to have made it yet. I'll try and figure out what happened to it. Anyways, I've been trying

Re: initrd is too fast for md

2010-11-10 Thread Ferenc Wagner
Ivan Jager writes: > The problem is that /scripts/local-top is running and trynig to set up > md before the hard drives are detected and show up in /dev. Add rootdelay=5 or similar to your kernel command line. This is documented in the installation guide. Yes, this is a workaround. Usually the

initrd is too fast for md

2010-11-09 Thread Ivan Jager
I recently installed testing on a Sun V240 but couldn't set up md/lvm during the install. I tried to submit an insallation report, but it doesn't seem to have made it yet. I'll try and figure out what happened to it. Anyways, I've been trying to switch the system over to lvm on raid1, but I'm not