[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#381844: itramfs-tools doesn't produce working ramdisk on amd64 with MODULES=list



On Mon, 21 Aug 2006 22:55:14 +0200
maximilian attems <maks@sternwelten.at> wrote:

> hello ivan,

> i have lots of output from your side,
> but no conclusions about what is happening.

> also this bug report is heavy to parse,
> as many stuff is customized on your own LIST usage,
> where as you report the bug against the default image.

> also you seem to contradict the findings of initramfs.
> when initramfs-tools drops you into the rescue shell
> it says that the root device is not there, but you say
> that it is there.

What happened was:
a) wrong order of md so /home got mounted in spite of / (somehow fixed, it seems it was a mdadm problem but I can't reproduce it)
b) devices didn't mount but once left into the busybox shell I was able to mount them manually
so every time I was drop in busybox ALL the modules needed WERE there I never had the need to modprobe ANY module manually
*This exclude it was a module related problem*
What I had to do was just
mkdir /z; mount /dev/mdN /z
or
mkdir /z; mount /dev/md/N /z
as you may notice device name was different depending on initramfs-tools version

> so i really that debug output from an default initramfs
> with MODULES=most and the output of the following commands
> after your are dropped into shell
> ls -l /dev
> cat /proc/mdstat

> if you trouble are cured in between due to newer mdadm
> hooks i'd also be happy to know about.

Upgrade to 0.74 didn't solve the problem.
Commenting out /etc/udev/rules.d/z60_mdadm.rules partially fixed the problem since I got trapped in another bug

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383555

I did report to you and cc to bugs.debian.org on 19 Aug. My message didn't reach the list. Since I didn't receive any bounce... (or maybe it got filtered too by anti spam or whatever) I thought at least you received news.
If you didn't receive that mail I can resend it to you so you can track down what the cause of the problem really *was*.

I just did an update/upgrade and these notable packages got in:
busybox
udev
initramfs-tools

I *can* boot with stock kernel and stock initrd.
Even 383555 seems fixed.

I'd consider the problem solved.



TY




Reply to: