https://bugzilla.novell.com/show_bug.cgi?id=384275 User vodicka.petr@email.cz added comment https://bugzilla.novell.com/show_bug.cgi?id=384275#c3 --- Comment #3 from Petr Vodicka <vodicka.petr@email.cz> 2008-05-05 04:50:58 MST --- Thank you for your response. 'repair installed system' is not working in this case. I tried that with no luck. It checked system and nothing wrong was found. After that I tried to delete vmlinuz and initrd from /boot directory to make sure, that a lot is wrong and no success in repair again. I am not sure, if it show just "everything is ok" or "I am unable to repair", but I am sure, that it was not working. I repaired system already with editing initrd ramdisk manually, but when I was building new kernel because of DVB-T hardware, I accidentally rebuild initrd with wrong modules which I realized after next reboot (I have forgot that I was playing with /etc/sysconfig/kernel recently). I had to resurect system again, so I booted to 'rescue system' (boot from DVD to console, but not to system installed on disk) and I tried to mount root filesystem and chroot there and run mkinitrd, but chroot was not working (bash not found - even it was in /'chrotdir'/bin/bash, where it should be). So last chance before manually edit initrd ramdisk again was to copy kernel rpm from install DVD and "rpm -i --force kernel-xxxxx.rpm" to system and luckilly it was working. So I found 2 ways how to rebuild initrd, but I think, that some cleaner way should exist. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.