Hey all.

I just installed FC6 over my old FC5 installation on my desktop (I did *not* upgrade--I formatted both the root and boot partitions). Installation went without incident; however, upon trying to boot FC6, I receive the following block of error messages:

...at which point it obviously hard-locks. Some things to note:

1. This is a dual-boot machine with Ubuntu. When I boot Ubuntu, I can then mount Fedora's root which does appear to contain a complete Fedora installation.

2. Both Fedora and Ubuntu get their own respective /boot partitions (/dev/sda1 and /dev/sda2). Both also get their own LVM-contained root filesystems as well (/dev/SystemMain/FedoraRoot and /dev/SystemMain/UbuntuRoot).

3. Grub has the kernel finding the root fs through the "root=LABEL=[fslabel]" clause. In my case, it's "root=LABEL=FedoraRoot". I checked the filesystem label of the root fs by running 'e2label /dev/SystemMain/FedoraRoot', which returned no label. I then set the label to "FedoraRoot" and tried to boot into Fedora. Still go the same error.

4. I have tried modifying the "root=[blah]" clause to find the root fs by means other than the fs label. Some variations I have tried are...
* root=/dev/SystemMain/FedoraRoot
* root=/dev/mapper/SystemMain-FedoraRoot

In either case, I still receive the same message. All I know is that the kernel is being found, the root fs does exist and is not corrupt, the kernel is being passed the proper argument to find root; yet the root fs cannot be mounted. I'm stumped.

Think it's an initrd issue? Any help is greatly appreciated!

I'm thinking it could be an issue with your /etc/fstab file, as it looks to me like its just failing to mount the root partition. The line for your root partition should read something like...

/dev/hda4 / ext3 noatime 1 2

(obviously with /dev/hda4 replaced with whatever the right partition is and ext3 changed if you're using a different filesystem)

I made sure that fstab was pointing at the correct filesystem. It was originally referencing the filesystem by the label, but I've changed it to point directly at the LVM partition. So it is looking for "/dev/mapper/SystemMain-FedoraRoot".

I booted up from the recovery CD, chroot'ed into /mnt/sysimage, and recreated the initrd. I tried booting with the new initrd and *still* get the exact same error message.

Still stumped...

I had similar problem while ago, and the reason was that the label of the RedHat partition was different that the one in "grub.conf". I recommend booing up your Ubuntu kernel. At the prompt check out RedHat partition name by issuing 'e2label /dev/hdx#' command, where 'hdx#' is RedHat partiion, and make sure that the line in 'grub.conf' containg LABEL=root=xxxx (in my case LABEL=root=/) matches the label name.

GL.

I have the same problem (with Fedora 7).
Did you solve the problem and if so, how please?

I solved the problem finally.
Actually my problem was that for some reason, mkinitrd didn't find any volume group when launched from the chrooted rescue CD environment.
I edited the script and replaced the line :
by and regenerated the initrd file.
Checked the vgchange line in the init script and rebooted fine.

I have the same problem. Re-making the image file didn't help. I would like to try your method but couldn't understand it completely. How can I know what "myrootvolumegroup" is? I run "vgdisplay", the result is "vgdisplay -- no volume groups found".

Sorry I'm new at Linux. Thank you very much!

Are you using your LVM with another system?

Sorry that I am new to Linux so I don't quite understand the terminology. Here is what I got from vg. Maybe my node is not using LVM?

>vgdisplay
vgdisplay -- ERROR: "/etc/lvmtab" doesn't exist; please run vgscan

>vgscan
vgscan -- LVM driver/module not loaded?

Here is some detailed thread I posted about the image file.

Thanks in advance for your help.

my thread

I have the same problem!
The original system was upgraded from FC3 to F7, and it was very slow, so I had to move hard disk to a faster machine, and got exactly the same panic screen.
Do I have to reconfig kernel?
or
Could this be hardware dependent?
The original system is custom built machine
CPU - Celeron 700Mhz, 768MB memory
IDE bus - disk is set to single disk
The new system is Dell GX260
CPU - P4 2GHz, 512 MB memory
IDE bus - disk is set to single disk also.

I think this is hardware related, so I re-install FC7 instead,
Everything looks great except squirrelmail does not work.

Hopfully some one can give me some idea,

Here is the avc info regarding dovecot when I used squirrelmail:

avc: denied { create } for comm="dovecot-auth" egid=0 euid=0 exe="/usr/libexec/dovecot/dovecot-auth" exit=-13 fsgid=0 fsuid=0 gid=0 items=0 pid=3343 scontext=system_u:system_r:dovecot_auth_t:s0 sgid=0 subj=system_u:system_r:dovecot_auth_t:s0 suid=0 tclass=netlink_audit_socket tcontext=system_u:system_r:dovecot_auth_t:s0 tty=(none) uid=0

Dear all,

I faced the same problem with kernel 2.6.27.4 on Gigabyte notebook (SATA harddisk). In my case I had not enabled scsi & ahci to be built as modules. So here is what I had to do:
- Enable SCSI & AHCI in config ("make menuconfig"), build & re-create initrd ("mkinitrd -f /boot/initrd-2.6.27.4.img 2.6.27.4")
- Get the LV label by running "e2label /dev/sda5" (My root partition is on sda5); It was "/12".
- Edit grub.conf to add "root=LABEL=/12" & reboot

So you may confirm if you are loading the proper disk drivers and entry in grub.conf is right. I had to try different combinations for "root=" param before I got it working

Bhaskara.

I was having the same problem after installing Fedora 9 as a dual boot with Ubuntu. The problem was solved when I entered the root in the traditional format (i.e. non-UUID way). So instead of:

kernel /boot/vmlinuz root=UUID=...

I entered:

kernel /boot/vmlinuz root=/dev/sda3

Don't know the reason why this worked, but it solved the problem for me!

-Mukul

i got the following error
root(hd0,6)
filesystem type is ext2fs, partition type 0x83 kernel/vmlinuz-2.6.15-1.2054-fc5amp ro root=/dev/volgroup00/logvol00 rhgb quiet ..........
ext3-fs:dm-0:couldn't mount because unsupported optional features(20002000)
mount:error mounting /dev/root on /sysroot as ext3:invalid argument
setuproot: moving /dev failed: no such file or directory
setuproot: error mounting /proc: no such file or directory
setuproot: error mounting /sys: no such file or directory
kernel panic - not syncing: Attempted to kill init!



please anyone help in getting the solution for this problem

try:
tune2fs -O^dir_index /dev/volgroup00/logvol00