Hi I have used rootdelay=9, as described in the release-notes. Frankly, I am not familiar with grub2, and as I specified it from the grub boot menu, there is a slight chance that I made some mistakes.
I did some research and found that I can wirte GRUB_CMDLINE_LINUX="rootdelay=9" in the file /etc/default/grub. I will try with this setting and larger values later. On Sun, 27 Mar 2011 17:21:45 +0100 Miguel Figueiredo <el...@debianpt.org> wrote: > A Sabado 26 Marco 2011 09:11:03 MIZUHARA Bun voce escreveu: > > Package: installation-reports > > Severity: normal > > > > It seems that I am having the same problem as Herbert had. > > Specifying "rootdelay" did not help, but after countless installation > > retries, > > I managed to figure out a recovery process from the shell prompt on > > initramfs. > > > > (initramfs) sh scripts/local-top/mdadm > > ... messages from mdadm ... > > (initramfs) sh scripts/local-top/lvm2 > > ... messages from lvm ... > > (initramfs) exit > > > > These commands bring the machine back into normal boot sequence. > > I suspect the problem lies in the module insertion order. > > [...] > > What values of rootdelay have you used? > > -- > Melhores cumprimentos/Best regards, > > Miguel Figueiredo > http://www.DebianPT.org -- 水原 文 <mizuh...@acm.org> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
