Bug#446724: SAME SITUATION - initramfs-tools: creates broken initramfs image as reported on Bug #445688
On Mon, 15 Oct 2007, Miguel Martins Feitosa Filho wrote:
>
> I have the same situation described by Beojan in one of my boxes but
> not the other two - all three are debian testing.
> His solution - yaird - also worked for me.
that is a local workaround that is highly discouraged,
as yaird is no longer developed and broken beyond..
> A call to
> egrep -r modprobe /usr/share/initramfs-tools/scripts/init-premount/
> shows some modprobe commands, all are without options such as:
>
> tatarana:/etc/default# egrep -r modprobe
> /usr/share/initramfs-tools/scripts/init-premount/ | head -2
> /usr/share/initramfs-tools/scripts/init-premount/ps3:modprobe
> ps3_storage
> /usr/share/initramfs-tools/scripts/init-premount/ps3:modprobe gelic_net
that is fine, that comes from stock debian.
> Since apt installed kernel 2.6.21-2 on my system I get the
> "Waiting for root filesystem" at boot time error.
>
> What is amazing is that my other two boxes have also up to date kernels
> and
> never had this problem.
sorry this not an initramfs-tools error, nor an kernel error
there is _no_ guarante that device name stay stable.
but the cause because you passed the wrong root arg
with pata_sis your root switched from /dev/hda to /dev/sda
so you need to fix your grub boot args + your fstab,
or better even switch to use UUID
-> http://michael-prokop.at/blog/2006/08/11/stable-root-device-aka-uuid/
> -- /proc/cmdline
> root=/dev/hda1 ro
> pata_sis 13636 0
best regards
--
maks
Reply to: