Pascal Cavy <[EMAIL PROTECTED]> writes: > 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.
/root/drakx/report.bug.gz would help. > I was wondering if it is possible to rebuild my initrd from the 9.1 rescue CD. Theoretically, it should be feasible (and easy). > 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. I don't consider that to be a bug. Many (all?) of our system tools rely very much on /proc being available. I'm not even sure the system will boot without a /proc filesystem mounted. > mount /proc > > mkinitrd /boot/initrd-2.4.21-0.13mdk.img 2.4.21-0.13mdk.img "-v" often helps debugging. > 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. No idea why it's saying that. Maybe strace would help. It works for me (cooker nfs rescue). -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
