I have "successfully" installed FC5 (just downloaded last night) and when I tried to boot into it, I get a kernel panic.

My system is:
AMD 2400, 2 HDs and 1 DVD-R drive

ide0 has 1 HD with winXP loaded
ide1 has dvd-R (as primary) and HD (as secondary) with FC5 loaded

I used grub on the MBR for booting.

When I boot, I get normal stuff until I notice:

Trying to resumer from LABEL=SWAP-hdd3
No suspend signature on swap, not resuming
..
..
It sets up root device and filesystem
unmounts old dev,proc and sys
then
kernel panic - not syncing:Attempted to kill init!

Does anyone have any suggestions? Thanks

-mark

Hello,

Does this problem happen every time you boot? The first time I installed FC5 I had same problem, but when I rebooted, it was fine. It didn't happen at all the other two times I installed FC5.

Yes, every time.

Where did you locate your swap partition. On the first or second hard drive? How is the second hard drive partitioned?

There are usually a few error messages displayed before the "Not syncing" message. Usually they relate to trying to boot using a read-only partition, and not being able to create, e.g., tty[0-4].

If there were any such messages, can you tell us what they said?

Review your GRUB settings (displayed when you type "e" on the boot menu item) to be sure that the kernel line specifies the correct root partition. If you used the default installation settings, it should look something like this:where the red section is more typically VolGroup00/LogVol100, but I prefer my own names for the logical volumes I use.

Note that the boot partition "(hd1,1)" is hdb1, and that both the swap and root (i.e., "/") file systems are inside the logical volume.

If you used the manual partitioning option, your root line should be something like root=/dev/hdb2.

Also, check your BIOS for the suspend/resume settings. They may need changing.

I didn't see any error messages prior to the swap error, but i will check again and post a correction if I see any.

root partition was set correctly in grub. it is using labels and i verified that the label was correct in fstab. I even tried to hard code it in and got same results...

My disk set up is as follows:

hdd1 - /boot
hdd2 - /
hdd3 swap

all primary partitions

Now that i write this I seem to remember something about swap needing to be first...does this sound familiar to anyone?

No, "swap" is a partition type, not a label, and it can be anywhere. In fact, I think that Linux may automatically "pool" all the swap partitions it detects into a "single" swap. I'm not sure about that, but I do have one distribution installed on hdh that uses a swap partition on hdb with no problem.

You say that But your first post claimed only two hard drives and one DVD, which would normally imply that only /dev/hda, /dev/hdb and /dev/hdc would exist. Was your (repeated) reference to hdd a typo, or do you somehow actually have more drives then you first claimed?

What happens if you delete the swap partition? (You don't actually need it to boot, and -- if you can boot without it -- you can recreate it and, hopefully, re-boot.)

Is your swap partition type correct? It should be type 0x82.

Did you check you BIOS settings for "suspend" and "resume?" Specifically, what disk area(s) -- if any -- are they set to use?

My first hard drive (/dev/hda) has my windows partitions. My second drive (/dev/hdd) has my linux partitions as noted above. hdd1, hdd2, hdd3 - 3 partitions.

As for the rest, i have decided to try a different distro. I installed FC5 about 5 times yesterday with different configurations, and every time it never booted for one resaon or the other.

Thanks for your help...

I am having the same problem booting after I install Fedora 5. When I boot up, I get the following output:


.
.
.
Scanning logical volumes
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
Activating logical volumes
2 logical volume(s) in volume group "VolGroup00" now active
Trying to resume from /dev/VolGroup00/LogVol01
No suspend signature on swap, not resuming.
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesustems.
Setting up new foor fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to ew root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: No such file or directory
[<c011a32e>] panic+0x3e/0x170 [<c011cede>] do_exit+0x71/0x6c8
[<c011d5b9>] sys_exit_group+0x0/0xd [<c0102bc1>] syscall_call+0x7/0xb

There are no errors before this.

I've tried multiple entries for 'swap' in my /etc/fstab and I get the same output above. I've used the rescue CD and successfully used my swap file (by 'swapon /dev/VolGroup00/LogVol01'). Before I installed Fedora 5, I was running Red Hat 2.4 without problems. If more information is needed, I'll gladly provide it. Can someone please help me?


Thanks,
Master-Xi

well this is something that may work (i am not 100% sure still new but there is nothing to loose). this will make a new kernal with something added. go into linux rescue and mount you drives. then enter.
mkinitrd --preload=ehci-hcd --preload=usb-storage --preload=scsi_mod --preload=sd_mod /boot/[initrdname]-usb.img Your kernal (uname -r) then restart and go into the edit in grub and edit the initrd part where it had your kernal. hit enter and then b for boot. if that does not work at least i gave it my best.

I tried your suggest brianmay, but it is a bash script that assumes /dev/VolGroup00/LogVol00 is bound to /, not /mnt/sysimage. So I am getting loads of errors. I gave my 80% trying to fix the script, but it still didn't work. Do you have any other suggestions? Thanks for your previous input.

After almost giving up on Fedora 5, I finally got the fix to this problem.

The suspend signature on swap error, "Trying to resume from LABEL=SWAP-hdd3. No suspend signature on swap, not resuming", can be ignored. It gives this error because when the volumes are activated (look at the output previous to this error), it resumes the swap partition in that step. Therefore, it's trying to resume something that isn't suspended.

The error that causes all the trouble is "mount: could not find filesystem '/dev/root'". Appartently, in the init script within initrd-2.6.15-1.2054_FC5.img, the command 'mount /sysroot' is trying to mount /dev/root to /sysroot. Fedora 5 does not use /dev/root like in the previous versions of Fedora. Instead, it uses '/dev/VolGroup00/LogVol00' or '/dev/hda1' (or whereever '/' is located) to mount to /sysroot. For some reason, when init calls 'mount /sysroot', it's trying to mount /dev/root to /sysroot, instead of /dev/VolGroup00/LogVol00 to /sysroot. This messes up everything after this step in the init process. When it does a switchroot at the end, it fails. After killing init, it causes the kernel panic.

Here's the fix:

1) Boot with the rescue CD
2) Type 'chroot /mnt/sysimage' (wherever it mounts the Fedora 5 partition)
3) 'cd /boot'
4) 'mkdir newinit'
5) 'cd newinit'
6) 'gunzip -c ../initrd-2.6.15-1.2054_FC5.img | cpio -idmv'
7) 'vi init'
8) Find 'mount /sysroot' (near the end of the file)
9) Delete or comment this out
10) Replace with 'mount -o defaults --ro -t ext3 /dev/VolGroup00/LogVol00 /sysroot' where /dev/VolGroup00/LogVol00 is the mount point for /
11) ':wq' out of vi
12) 'find . | cpio --quiet -c -o >../newinitrd'
13) 'cd ..' - you are now in /boot
14) 'mv initrd-2.6.15-1.2054_FC5.img initrd-2.6.15-1.2054_FC5.bak' - backup current initrd img file (just in case)
15) 'gzip -9 < newinitrd > initrd-2.6.15-1.2054_FC5.img'
16) Reboot the computer without the CD

* Steps 4-6,12,13,15 were taken from another site, but I couldn't post the URL. I'll try in my next post.

This should fix it. I'm glad I can finally run Fedora 5 on my box.

MarkCole, I'm not sure if you were experiencing the exact same problems I was with mounting root. However, I hope this helps anyone else experiencing the same problems I had.

Andy

Steps 4-6,12,13,15 were taken from https://www.redhat.com/archives/fedo.../msg07843.html

I'm having the same problem as described here. I tried about everything I can think of. I was previously running FC2 before upgrading to FC5. Does anyone have any other suggestions?

After trying the above my error changes slightly. It becomes "no fstab.sys, mounting defaults". Then I receive the kernel panic.

Thanks,
Brian