Bad installed kernel problem!
 

Here's my situation. I'm running SuSE 8.2 Pro and decided to try the YAST Online Update (YOU). I downloaded all recommended patches, including a kernel optimized for AMD processors (mine is a 2000+ XP AMD). After rebooting I received the following error (some of the final verbose comments):

Using /lib/modules/2.4.20-4GB-athlon/kernel/fs/reiserfs/reiserfs-o
kmod: failed to exec /sbin/modprobe -s -k block -major-3, errno=2
VFS: Cannot open root device "hda2" or 03:02
Please append a correct "root=" boot option
You may want to retry boot with pci=noacpi or acpi=oldboot on the command line
If one helps please report with the following lines to acpi@suse.de
DMI: (hardware vendor info)
Kernel panic: VFS: Unable to mount root fs on 03:02

It wouldn't even let me log on. So, I posted a thread here. Someone responded and said my root partition was formatted as 'reiserfs', and that the new kernel doesn't have support for 'reiserfs'. Essentially, I think I have to reinstall the old kernel, but I don't know how to do that. I was able to boot into KDE from the boot CD (#1). I went into YAST, found the old kernel under install/uninstall, and tried that way, but the system can't read my CD drive. Is there a way around this with LILO/GRUB? Should I just reinstall the entire OS? Please help....

(need to buy 'Linux in a Nutshell')

"I was able to boot into KDE from the boot CD (#1)."

I interpret this to mean that you used the rescue CD to boot your existing system then started YaST.

Instead of reinstalling the kernel that way try using the SuSE install CD to do a partial install and tell it to install the kernel and only the kernel.

If you are using lilo, then use the SuSE rescue CD to boot into your old system and run lilo. If you are using grub you might be able to skip this step.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Yes, I used the rescue CD to boot into the system and YAST. That's a good idea to do a partial install...I'll try that. Even if I could start Lilo/Grub I wouldn't know what commands to do. I'm one of those 'newbies'. Thanks for now.

NO! I refuse to take the easy way out! I really wannna debug this problem to learn more about Linux.

I did some searching, and found that modules can be added by editing the /etc/sysconfig/kernel file. I added 'reiserfs' such as:

INITRD_MODULES="reiserfs"

It says to add the module to the ramdisk, call the script "mk_initrd". I found the original file (/dev/initrd), but wherever I execute "mk_initrd", I get the following:

/using "/dev/root" as rot device (mounted on "/" as "ext2")
no kernel image "vmlinuz"
no kernel image "vmlinuz.shipped"

I can't make a new initrd file. Think I'm on the right track?

"Think I'm on the right track?"

No. You are into the details of how to compile a kernel from source. I doubt very much that you could accomplish that from a rescue CD.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Thank you very much for the straightforward answer, just what I'm looking for. Seeing that you're a guru, I'll take your word for it. So what are my options? Are you saying I'm screwed and have to completely reinstall my OS...or just do a manual installation for the old kernel?

Couple of questions - is /dev/hda2 the correct root partition?, did you use reiserfs on that partition?

Next, /dev/initrd is not the ramdisk image, it is a device file. The initrd image can be found by looking in your grub.conf or lilo.conf file. It is usually in your /boot directory. You can add a module to it by mounting it as a file system. If you want to try, post back.

" Are you saying I'm screwed and have to completely reinstall my OS...or just do a manual installation for the old kernel?"

Sorry that my reply was so abrupt.

I think that reinstalling the entire OS is probably overkill. I would first try reinstalling the old kernel. If you successfully reinstall the old kernel and you still have problems then you could either reinstall the entire OS or get into the details of repairing initrd, etc.

I think that your original idea of using the rescue CD to boot your system and using YaST was a good one. I am unsure why YaST did not work correctly. Doing a partial install from the install CD also should work.

The things that you are trying to do with the initrd, etc. are what people do after they have compiled a new kernel and it almost works. They fool around with initrd and perhaps change a few things in make xconfig and recompile the kernel again. If SuSE did not compile the new kernel in such a way that it will work on your hardware then it would be very difficult for you to fix a kernel "post compile" from a rescue CD.

If SuSE's new kernel has features that you want then I suggest that you first get your old kernel working. Then install the new kernel as a dual boot system until you get the new kernel working correctly. That is the best time to try out your ideas on initrd and musrum's suggestions on fixing initrd.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites