Pascal Cavy wrote:
After migration from MDK 7.2 to MDK 9.1, the installer left a new system
without an initrd for 2.4.21-0.13mdk, thus I cannot boot it anymore.
I was wondering if it is possible to rebuild my initrd from the 9.1 rescue CD.
I tried the following but to no avail (maybe because of using the freshly
installed system by means of a chroot on /mnt) :
boot rescue cd1
mount all FS on /mnt
go to console
chroot /mnt
First I was to mount /proc because mkinitrd _does not check_ that /proc is
available and thus we end in a loop at the step it scans for /proc/mounts FS.
mount /proc
mkinitrd /boot/initrd-2.4.21-0.13mdk.img 2.4.21-0.13mdk.img
which leads to an error like :
+ dd if=/dev/zero of=/tmp/initrd.img.LiQwlh bs=1k count=420
+ '[' -n '' ']'
+ mke2fs -q -m 0 -F -N 45 -s 1 /tmp/initrd.img.LiQwlh
mke2fs 1.32 (09-Nov-2002)
mke2fs: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
+ mkdir -p /tmp/initrd.mnt.sSf2Ug
+ mount -t ext2 /tmp/initrd.img.LiQwlh /tmp/initrd.mnt.sSf2Ug -o loop
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
or too many mounted file systems
+ echo 'Can'\''t get a loopback device'
Can't get a loopback device
+ exit 1
+ rm -rf /tmp/initrd.3Syylf /tmp/initrd.mnt.sSf2Ug /tmp/initrd.img.LiQwlh
has anyone a key of how to do this under rescue ?
The following seem possibly related:
http://qa.mandrakesoft.com/show_bug.cgi?id=3614
https://qa.mandrakesoft.com/show_bug.cgi?id=1614
http://www.mail-archive.com/[EMAIL PROTECTED]/msg90067.html
