--- On Tue, 2/17/09, martin f krafft <madd...@debian.org> wrote:
> Can you please make a copy of the current
> /boot/initrd.img-2.6.26-1-686 and put it somewhere where I
> can
> download it? Uploading to ftp://ftp.madduck.net/incoming/
> would
> work, too.
The simplest for me would be to email it, it's about 5.1MB. (firewalls and all)
> Can you then please rebuild the 2.6.26 initramfs like this:
>
> update-initramfs -ctk 2.6.26-1-686
>
> You can later use -u instead of -c to update it. Now try a
> boot.
Tried it, the system drops into BusyBox on boot with seemingly the same
messages that were already described:
....
md: no devices found for /dev/md1
md: no devices found for /dev/md2
md: no devices found for /dev/md3
Also tried to create a new etch image with
# update-initramfs -ctk 2.6.18-6-686
but the system doesn't boot with this image, fails to assemble the mdadm drives
but it does print the initrd section
--- initrd.img-2.6.18-6-686:
25153 blocks
etc/mdadm
etc/mdadm/mdadm.conf
lib/modules/2.6.18-6-686/kernel/drivers/md/md-mod.ko
lib/modules/2.6.18-6-686/kernel/drivers/md/raid0.ko
lib/modules/2.6.18-6-686/kernel/drivers/md/raid1.ko
lib/modules/2.6.18-6-686/kernel/drivers/md/xor.ko
lib/modules/2.6.18-6-686/kernel/drivers/md/raid456.ko
lib/modules/2.6.18-6-686/kernel/drivers/md/linear.ko
lib/modules/2.6.18-6-686/kernel/drivers/md/multipath.ko
lib/modules/2.6.18-6-686/kernel/drivers/md/raid10.ko
sbin/mdadm
scripts/local-top/mdadm
> If that does not work, please also make this
> /boot/initrd.img-2.6.26-1-686 available (under a different
> name).
I can email it as well if you wish, in a separate message, it's about 6.3MB.
Thanks
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
