FC4: kernel panic after installation - partition problem?

[npgall]

Hi,

I am getting a kernel panic after installing FC4. I installed with the 'everything' option in the packages screen. Installation finishes without errors, but after the reboot when install finishes, the kernel panics.

I got the following messages before kernel panic:

...
Uncompressing Linux... Ok, booting the kernel.
ide0: I/O resource 0x1F0-0x1F7 not free.
ide0: ports already in use, skipping probe
Red Hat nash version 4.2.15 starting
  Reading all physical volumes.  This may take a while...
  No volume groups found
  Unable to find volume group "VolGroup00"
ERROR: /bin/lvm exited abnormally with value 5 ! (pid 454)
mount: error 6 mounting ext3
ERROR opening /dev/console!!!!: 2
error dup2'ing fd of 0 to 0
error dup2'ing fd of 0 to 1
error dup2'ing fd of 0 to 2
switchroot: mount failed: 22
Kernel panic - not syncing: Attempted to kill init!

This is a Dell Precision M20 laptop.
It should be identical to the Dell Latitude D610 laptop except for the graphics card.

CPU 2.0GHz Pentium M (model 760)
Intel 915PM chipset
1GB RAM (2 x 512MB 533MHz)
ATi Mobility FireGL V3100 (64MB) graphics
DVD RW
60GB 7200rpm hard disk (not sure if this is SATA or regular IDE)


This laptop had Windows XP Pro factory installed, and when I was installing FC4 I chose the automatic partition option, and to delete/overwrite all existing partitions on the hard disk.

I got the above kernel panic after I rebooted several times, each time it was identical. I ran the media check as part of the installation and the disc (DVD) was fine.

The strange thing is, I figured the installer had not set up the partitions properly so I tried to install again. The installer did not find any existing partitions on the hard disk this time and I selected 'minimal' in the packages screen and let install finish. When it finished I clicked reboot and it booted fine this time.
I logged in and copied the /var/log/messages file to a usb disk. There were some errors similar to what I had in the kernel panics the first time:

Jun 15 00:13:37 localhost kernel: RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Jun 15 00:13:37 localhost kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Jun 15 00:13:37 localhost kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Jun 15 00:13:37 localhost kernel: ide0: I/O resource 0x1F0-0x1F7 not free.
Jun 15 00:13:37 localhost kernel: ide0: ports already in use, skipping probe
...some other stuff...
Jun 15 00:13:37 localhost kernel: SCSI subsystem initialized
Jun 15 00:13:37 localhost kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 7
Jun 15 00:13:37 localhost kernel: PCI: setting IRQ 7 as level-triggered
Jun 15 00:13:37 localhost kernel: ACPI: PCI Interrupt 0000:00:1f.2[B] -> Link [LNKB] -> GSI 7 (level, low) -> IRQ 7
Jun 15 00:13:37 localhost kernel: ata: 0x170 IDE port busy
Jun 15 00:13:37 localhost kernel: ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xBFA0 irq 14
Jun 15 00:13:37 localhost kernel: ata1: dev 0 ATA, max UDMA/100, 117210240 sectors: lba48
Jun 15 00:13:37 localhost kernel: ata1: dev 0 configured for UDMA/100
Jun 15 00:13:37 localhost kernel: scsi0 : ata_piix
Jun 15 00:13:37 localhost kernel:   Vendor: ATA       Model: HTS726060M9AT00   Rev: MH4O
Jun 15 00:13:37 localhost kernel:   Type:   Direct-Access                      ANSI SCSI revision: 05
Jun 15 00:13:37 localhost kernel: SCSI device sda: 117210240 512-byte hdwr sectors (60012 MB)
Jun 15 00:13:37 localhost kernel: SCSI device sda: drive cache: write back
Jun 15 00:13:37 localhost kernel: SCSI device sda: 117210240 512-byte hdwr sectors (60012 MB)
Jun 15 00:13:37 localhost kernel: SCSI device sda: drive cache: write back
Jun 15 00:13:37 localhost kernel:  sda: sda1 sda2
Jun 15 00:13:37 localhost kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Jun 15 00:13:37 localhost kernel: device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
Jun 15 00:13:37 localhost kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
Jun 15 00:13:37 localhost kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
Jun 15 00:13:37 localhost kernel: ide: failed opcode was: unknown
...some other stuff...
Jun 15 00:13:37 localhost kernel: md: Autodetecting RAID arrays.
Jun 15 00:13:37 localhost kernel: md: autorun ...
Jun 15 00:13:37 localhost kernel: md: ... autorun DONE.
Jun 15 00:13:37 localhost kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
Jun 15 00:13:37 localhost kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
Jun 15 00:13:37 localhost kernel: ide: failed opcode was: unknown
Jun 15 00:13:37 localhost kernel: hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
Jun 15 00:13:37 localhost kernel: hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
Jun 15 00:13:37 localhost kernel: ide: failed opcode was: unknown

Appologies for the excessive detail. I moved to Linux a few months ago so I'm still a relative newbie unfortunately. I figure the above may be useful to people who understand it better. I still have the complete messages boot log if any Red Hat/Fedora people need to see it, but I did not see any errors in the rest of it.

Any pointers would be appreciated.

[pzeigler]

I get the same thing on my Dell C600. Let me know if you get this resolved.

Philip

[nkoplm]

im having a very simmilar problem too. (im pretty sure its the same problem, but i can only go from memory at to what the output was when the kernel paniced (paniked?... sp?).)

Dell latitude D610
Pentium M processor at 1.86Ghz
512Mb ram
64mb Radeon x300 M
not sure what my hard drive is, ide or what not (i dont know much about hard drive harware) but i can say its an 80Gb FUJITSU MHV2080AH

[zombie]

Same problem with two dimension 8400 and one optiplex (sorry I don't remember the number), BTW I did a reiserfs selinux=0 installation, the 2 dimension have a sata hard disk.
I wasn't able to figured out why, by I installed a second time fc4 with same options and averything went fine. In my understanding something has gone bad during partition format.
So reinstall and good luck!

[pzeigler]

I did 2 re-installs with the same problem. Did a third install and this time selected that I want to review changes to the automatic partition and it worked!

Philip

[npgall]

Ok I got FC4 to install. I reinstalled again and chose to delete all partitions as before and it worked this time. Perhaps the installer cannot delete Windows/NTFS partitions properly, but can delete Linux partitions? Strange.

I still get these errors at boot:

ide0: I/O resource 0x1F0-0x1F7 not free.
ide0: ports already in use, skipping probe

Any idea what these errors mean?

[gilboa]

The original problem seem to relate the kernel failing to auto-detect the LVM volume.
This seem to suggest an installer problem. Sadly enough you cannot open a bug report as you can no longer reproduce the bug...

BTW, by the kernel log your 60GB is SATA based.

[bit.shaker]

Hello everybody,

First my (rather long) story :
this is definately a partitioning problem. I encountered similar problems during installation. To be true speaking, Anaconda said it crashed, put out a debug message and said, i should copy it to floppy and send to fedora/bugzilla/whoever, afterwards ... only problem : I don't have any floppies lying around these days anymore

Did a reboot, did everything again, so far no problems, except for getting the same message as gilboa (aka kernel panic...)

booted into rescue mode (type : "linux rescue" <- without "). could mount my shiny xfs partition, xfs_check didn't find anything. fdisk said there were some unallocated sectors, after prompting it to verify partition table, just don't want to bother with re-partitioning and risking to lose my /home partition ... so took a look into /etc/fstab and /boot/grub/grub.conf

Solution (did not do any LVM, though):
edit your /etc/fstab : find root device and in the first row rename LABEL=/ --> /dev/your device
mine looks this way now:

#
This file is edited by fstab-sync - see 'man fstab-sync' for details
#LABEL=/ / xfs defaults 1 1
/dev/hdb6 / xfs defaults 1 1
# my root device is /dev/hdb6, insert yours

LABEL=/boot1 /boot ext3 defaults 1 2
/dev/devpts /dev/pts devpts gid=5,mode=620 0 0
/dev/shm /dev/shm tmpfs defaults 0 0
LABEL=/home /home ext3 defaults 1 2
/dev/proc /proc proc defaults 0 0
/dev/sys /sys sysfs defaults 0 0
LABEL=SWAP-hdb5 swap swap defaults 0 0
/dev/sda1 /media/usbdisk vfat pamconsole,exec,noauto,managed 0 0
/dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0
/dev/hdd /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0
/dev/hdc /media/cdrom auto pamconsole,exec,noauto,managed 0 0

edit your /boot/grub/grub.conf: change part root=LABEL=/ to root=/dev/your device

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/hdb6
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=3
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.11-1.1369_FC4)
root (hd1,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/hdb6 rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4.img

To all who posted before: Did you do a "custom" install, with which I mean, either using any other filesystem then ext2/3 and/or not using the default installation options desktop/server (what was the third thing??? ) ??? Maybe that is the key to finding a general solution to this problem, because there wasn't this kind of thing in any fc4test1-3 installs. maybe anaconda is really broken???

m2c,
bit.shaker

[wstahw]

I still have the same problem with my dell precision m70 laptop.
After upgrading FC3 to FC4, I got the exact same message:

ide0: I/O resource 0x1F0-0x1F7 not free
ide0: ports already in use, skipping probe
Red Hat nash version 4.2.15 starting
    Reading all physical volumes.  This may take a while ...
    No volume groups found
    Unable to find volume group "VolGroup00"
    ...
Kernel panic - not syncing: Attempted to kill init!

Booting in rescue mode works and the linux partition is mounted
as VolGroup00/LogVol00. So, for some reason in rescue mode the volume group
is found and handled well, while in normal mode it is not.
What should I change (while in rescue mode) to make normal mode work?
Any hints?

[bit.shaker]

hi,
first of all, to correct myself, it seems more like a bug in the creation of the config files, then a real partitioning tool bug. it basically appears that anaconda, or whatever misses assigning the correct LABELs for each partition.

@wstahw:

Booting in rescue mode works and the linux partition is mounted
as VolGroup00/LogVol00. So, for some reason in rescue mode the volume group
is found and handled well, while in normal mode it is not.
What should I change (while in rescue mode) to make normal mode work?
Any hints?

I don't know that much about LVMs, but as far as I know once in rescue mode, check if it's really mounted or atleast mountable without any errors, so you have access to all files on volgroup00/LogVol00. if this works, the data and partition should be ok,
then type "ls /dev/lvm* " (<-- again without "). there should appear some device nodes reflecting the volume groups you have. idealistically you could then apply the method that worked for me, that is: rename the parts in grub.conf/fstab with the complete path of your device nodes, like /dev/lvm/VolGroup00/LogVol00 ... (or as apropiate, because it could look different for you, also: if there are multiple partitions in your LV, be certain, which one is the root partition /).

If you don't mind reading a bit about LVM: http://www.tldp.org/HOWTO/LVM-HOWTO/

Maybe that works, but not sure. Could very well be a completely different variation of the problem I mentioned I had in my previous post.

m2c,
bit.shaker

[loodpool]

I still have the same problem with my dell precision m70 laptop.
After upgrading FC3 to FC4, I got the exact same message:

ide0: I/O resource 0x1F0-0x1F7 not free
ide0: ports already in use, skipping probe
Red Hat nash version 4.2.15 starting
    Reading all physical volumes.  This may take a while ...
    No volume groups found
    Unable to find volume group "VolGroup00"
    ...
Kernel panic - not syncing: Attempted to kill init!

Booting in rescue mode works and the linux partition is mounted
as VolGroup00/LogVol00. So, for some reason in rescue mode the volume group
is found and handled well, while in normal mode it is not.
What should I change (while in rescue mode) to make normal mode work?
Any hints?

I got the same problem after upgrading from fc3 to fc4 with reiserfs partitions

[npgall]

Ok well it looks like the workaround for this issue is to reinstall FC4 and it works the second time.

Gilboa- yes it is a shame I can't reproduce this bug now to file a report. If anyone else here can reproduce the bug- please file a bug report because obviously it needs to get fixed.

Is there a way we can submit a bug report without immediate reproducability? I guess it could be reproduced in my case by trying to install FC4 on any Dell M20 laptop with Windows XP preinstalled? I think we have sufficient details to give useful information to anaconda developers. How can I/we do this?

[wstahw]

I fixed my update problems by doing a full installation instead.
All is well now, but I need to reinstall quite a lot of data :-(
And unfortunately, now the nvidia driver is not working properly.

[gilboa]

Ok well it looks like the workaround for this issue is to reinstall FC4 and it works the second time.

Gilboa- yes it is a shame I can't reproduce this bug now to file a report. If anyone else here can reproduce the bug- please file a bug report because obviously it needs to get fixed.

Is there a way we can submit a bug report without immediate reproducability? I guess it could be reproduced in my case by trying to install FC4 on any Dell M20 laptop with Windows XP preinstalled? I think we have sufficient details to give useful information to anaconda developers. How can I/we do this?

You can try and report it. Try an be as specific as you can.
With a little bit of luck, someone with the same problem will see you bug report and add the missing pieces.

Speaking of which, I had a kernel oops (due to nVidia drivers crapping out) and in the following reboot, the LVM on my FC4/64 refused to mount. (I couldn't see the error code.)
I decided to connect the machine to a serial console and try again, but the problem refuses to reproduce.

Cheers,

[alyunes]

I had the same problem. I opted for Reiserfs/SELinux enabled during installation.