On 21/05/10 09:39, Per Jessen wrote:
Hans de Faber wrote:
Hans should be able to boot into rescue, mount the filesystems, chroot and then run mkinitrd. I think he might need to amend /etc/sysconfig/kernel:INITRD_MODULES.
Good morning I am online again. I think this is the right way to go. Is there somewhere a example how to do this ?
Probably, but it's not too difficult -
boot a rescue system run fsck on the filesystems you need (root,boot,usr,whatever) mount root on /mnt mount boot on /mnt/boot mount usr on /mnt/usr mount var on /mnt/var (you get the idea). mount -o bind /proc /mnt/proc mount -o bind /dev /mnt/dev mount -o bind /sys /mnt/sys chroot /mnt make sure that /etc/sysconfig/kernel:INITRD_MODULES contains 'ext4' run mkinitrd update your bootloader (e.g. run lilo) exit from chroot umount /mnt/proc /mnt/dev /mnt/sys umount /mnt/usr /mnt/boot /mnt/var /mnt reboot
Linux (opensuse) is a very flexible OS you can put everything were you want and changing is easy. Grub is also very flexible you can boot always and everything. Except for the hardcoded data in initrd this kills the flexibility.
This construction looks to me like the sentence "Every color is beautifull if it is black"
No, there is nothing wrong with the initrd - changing your root filesystem is not a minor change, it's not realistic to expect it to 'just work'.
This was the last step in the process. Without any problem I can now boot my ext4 root. I don't do this everyday but it was easyer than I thought. Thanks to everybody. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org