FC5 Test 3 kernel panic

[Joffer]

I've installed FC5 Test 3 on a AMD64 X2 3800+ with two 80GB SATA disks in RAID1 through nvidia bios. It worked fine on Test2, and it is recognized during installation and everything is fine until I reboot after the installation. Then I get a msg about it not being able to find nvidia_aedjfifb, and then it does not find my VolGroup00 etc.. and then the kernel panics..

any tips?

[hiberphoptik]

well.. i would blame LVM but thats only because every time i fix a friends linux install it seems the problems are related to them selecting autoformat/partition and using LVM

if you are bored and out of options try reinstalling it and manually partitioning without using LVM

[Joffer]

It did not help to partition without LVM either.

Anyone installed FC5 Test 3 on a BIOS made RAID? In my case it's a RAID1 from a Nvidia C51 chip (kinda nforce4 with integrated graphics.. nForce430 is perhaps the chipset name.. )

Anyone at all installed where the installer uses /dev/mapper/XXXXXX as device?

[risidoro]

Same problem here.
I installed Fedora Core 5 test 3 on /dev/mapper/via_ecfiejdch3, a 20gb partition on my Via vt8237 fakeRAID 0 controller.

I installed it two times:

- the first one without specifying any boot option: installation went fine but grub didn't install at all (on the next reboot i couldn'd see any menu or whatsoever, just windows XP)

- the second (and last) one i put "linux dmraid" at the installation cd's boot prompt: this time, on the next reboot, i was able to see grub graphical menu but i got (and i'm still getting) kernel panic errors when i try to boot linux (XP is ok).

I don't remember the exact problem but it complained about not being able to find /dev/boot or something similar. It seems others are having this very same problem: See here (http://www.redhat.com/archives/fedora-devel-list/2006-February/msg01007.html)

BTW: i didn't use any LVM at all. Just two partitions: ext3 and swap, both on my raidset.

PLS, find a solution (i'm a poor linux noob)!!!

Bye

[LLS]

Some recent reading in Linux magizine discusses a problem with raid devices excluding (raid 1) "mirroring", that explains booting is not possible on some raid devices because of the way the data is spread across multiple partitions makes it unavailable during boot resulting in kernel panic. Solution being to set up seperate partitions for boot and then configure that raid 1. Then create the raid 0, 4/5 or 6 on the remaining disks. It sounds feasable in the article.

[Joffer]

Same problem here.
I installed Fedora Core 5 test 3 on /dev/mapper/via_ecfiejdch3, a 20gb partition on my Via vt8237 fakeRAID 0 controller.

I installed it two times:

- the first one without specifying any boot option: installation went fine but grub didn't install at all (on the next reboot i couldn'd see any menu or whatsoever, just windows XP)

- the second (and last) one i put "linux dmraid" at the installation cd's boot prompt: this time, on the next reboot, i was able to see grub graphical menu but i got (and i'm still getting) kernel panic errors when i try to boot linux (XP is ok).

I don't remember the exact problem but it complained about not being able to find /dev/boot or something similar. It seems others are having this very same problem: See here (http://www.redhat.com/archives/fedora-devel-list/2006-February/msg01007.html)

BTW: i didn't use any LVM at all. Just two partitions: ext3 and swap, both on my raidset.

PLS, find a solution (i'm a poor linux noob)!!!

Bye


Sounds just like my problem. I'm trying to get FC4 to work now.. but had to ditch the nvidia bios raid ("fakeraid") and use software raid instead. Now I just need to get my nvidia nic to work (forcedeth).... It would have been so much better if I could have had test3 work and then just update to final with the packages released..

[RahulSundaram]

I've installed FC5 Test 3 on a AMD64 X2 3800+ with two 80GB SATA disks in RAID1 through nvidia bios. It worked fine on Test2, and it is recognized during installation and everything is fine until I reboot after the installation. Then I get a msg about it not being able to find nvidia_aedjfifb, and then it does not find my VolGroup00 etc.. and then the kernel panics..

any tips?

can you post to fedora-test list and file a bug report?

[Joffer]

I'm sorry. I don't have time at the moment (I'm not on the list either..). I had to install FC4 to get the computer up and running. I did however manage to take a picture of the screen with the kernel-panic, and dump a few logs/system settings (from within a chroot using the dvd as rescue media):

Screenshot: http://www.joffer.net/webshare/files/20060225-FC5-test3-kernel_panic.jpg
Logs: http://www.joffer.net/webshare/files/20060225-FC5-test3-kernel_panic.tar

What I did:
I did a clean FC5 test3 install, removed all partitions, and let the installer configure the partition settings, did not install any extra packages (no office etc) and chose "customize later", and hit next. It installed fine, and booted.. well.. into the kernel panic.

Perhaps you could post it for me or something.

[glen]

i have the exact same problem with my setup, ASUS A8N-CSM which has the nforce4 430 chipset. the drives will work/boot/etc fine in normal sata mode, but when you combine them into the 430's raid (RAID1 in my case) the machine won't boot. i've been trying a bunch of different grub config's etc, but nothing seems to work

any resolution on this yet?

[snowfly]

We also are having the exact same problem here.

Install process worked fine (mostly default settings), but on first reboot, we get the kernel panic messages.

Installing on a nvidia geforce GA-K8N51GMF-9 board, with NVidia nforce Raid (nvidia mcp51 serial ata controller).
With AMD athlon 64 X2 Dual Core 3800+
And two 232.88gb SATA II drives.

I might try and post bug to redhat/fedora bugzilla.
Hmmmm....

[snowfly]

Ok see the following bugs, they may relate. And I've posted my problem to one of them.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183966
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182232
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182326

[risidoro]

Hi, i've finally found a solution on how to install fc5 test3 on a fakeraid array!!! :)

This is what i've done:
- boot Fedora DVD
- at the boot prompt use: 'linux dmraid'
- install as usual
- when installation completes it asks you to reboot, then, on reboot, it gives you the kernel panic error!!!
- insert Fedora DVD again and reboot
- on the boot prompt use: 'linux rescue' to start in rescue mode
- activate your network card when required (you'll need an Internet connection)
- chroot in your fedora partition: 'chroot /mnt/sysimage'
- mount selinux: 'mount -t selinuxfs none /selinux'
- update mkinitrd: 'yum update mkinitrd'
- now you should have version 5.0.29 (instead of 5.0.26); check with: 'mkinitrd --version'
- create a new initrd image, to do this, at the prompt:
---- mv /boot/initrd-2.6.15-1.1955_FC5.img /boot/initrd-2.6.15-1.1955_FC5.OLD
---- mkinitrd /boot/initrd-2.6.15-1.1955_FC5.img 2.6.15-1.1955_FC5
- reboot
- ENJOY your new Fedora!!!

Let me know if you encounter any problem!
Have fun!!!

Bye Bye,
Isidoro

[snowfly]

Hi, i've finally found a solution on how to install fc5 test3 on a fakeraid array!!! :)

This is what i've done:
- boot Fedora DVD
- at the boot prompt use: 'linux dmraid'
- install as usual
- when installation completes it asks you to reboot, then, on reboot, it gives you the kernel panic error!!!
- insert Fedora DVD again and reboot
- on the boot prompt use: 'linux rescue' to start in rescue mode
- activate your network card when required (you'll need an Internet connection)
- chroot in your fedora partition: 'chroot /mnt/sysimage'
- mount selinux: 'mount -t selinuxfs none /selinux'
- update mkinitrd: 'yum update mkinitrd'
- now you should have version 5.0.29 (instead of 5.0.26); check with: 'mkinitrd --version'
- create a new initrd image, to do this, at the prompt:
---- mv /boot/initrd-2.6.15-1.1955_FC5.img /boot/initrd-2.6.15-1.1955_FC5.OLD
---- mkinitrd /boot/initrd-2.6.15-1.1955_FC5.img 2.6.15-1.1955_FC5
- reboot
- ENJOY your new Fedora!!!

Let me know if you encounter any problem!
Have fun!!!

Bye Bye,
Isidoro

Excellent!!! It works.
Thanks for that, now we can get our 2 brand new servers running.
:)

[Eddd]

Excellent!!! It works.
Thanks for that, now we can get our 2 brand new servers running.
:)
I don't know how good of an idea it is to install experimental software on servers.

[RahulSundaram]

I'm sorry. I don't have time at the moment (I'm not on the list either..). I had to install FC4 to get the computer up and running. I did however manage to take a picture of the screen with the kernel-panic, and dump a few logs/system settings (from within a chroot using the dvd as rescue media):

Screenshot: http://www.joffer.net/webshare/files/20060225-FC5-test3-kernel_panic.jpg
Logs: http://www.joffer.net/webshare/files/20060225-FC5-test3-kernel_panic.tar

What I did:
I did a clean FC5 test3 install, removed all partitions, and let the installer configure the partition settings, did not install any extra packages (no office etc) and chose "customize later", and hit next. It installed fine, and booted.. well.. into the kernel panic.

Perhaps you could post it for me or something.

Bug reports by proxy are generally a bad idea since it represents a discussion in which the developer might ask more information on the issue and I wouldnt be able to provide it for you. While using test/development releases it is important that you use http://bugzilla.redhat.com to report problems and discuss issues in the fedora-test list

http://fedoraproject.org/wiki/Testing