On Mon, 07 Aug 2006, Ivan Sergio Borgonovo wrote: > If you've time and patience... could you explain? > The initial setup with original kernel worked. > Once I installed the debian -smp version it screwed up the order of creation > of md. > I had to change fstab after manually mounting the md.
the previous initramfs-tools mdadm hook had ordering trouble. > This is the description of the problem I made to svlug list trying to get > some help: > http://lists.svlug.org/archives/svlug/2006-July/053261.html > > As you may notice the symptoms were different: > - can't mount / cos order of devices was "changed" > vs. well if you can still reproduce that with latest mdadm please file a bug against it. > - can't mount / cos no md3 sure missing drivers when you use MODULES=list > MODULES=list *worked* for previously manually generated initrd as reported in > the *body* of the bug report. > kernel was not updated after I made last initrd manually with list, nor any > relevant "boot" related package I can remember with the exception of > initramfs-tool. > The list is actually pretty long and was obtained just deleting few entries > (snd_*[*]) from > lsmod | cut -d" " -f1 > I would exclude this as the reason of the problem. If you're still convinced > it can be the problem let me know and I'll test MODULES=most. yes please use MODULES=most > * and no... I don't have a sound blaster with an integrated ide > controller attached to the disk that contain my /. ??? greetings -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
