FC3 system won't boot off of any newer kernel than install CD kernel, 2.6.9

From: Torbjørn Lindahl (lindahl_at_stud.ntnu.no)
Date: 05/02/05


Date: Mon, 02 May 2005 22:57:04 +0200

A system that I installed with FC3 ran fine with the original FC3 install
kernel, but any newer than that refuses to pass the initrd step right
after kernel is uncompressed during boot.

There are no error messages. The output during boot goes like this:

   Booting 'Fedora Core (2.6.11-1.14_FC3)'

root (hd0,0)
  Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.11-1.14_FC3 ro root=/dev/drivepool/root
    [Linux-bzImage, setup=0x1600, size=0x1974cb]
initrd /initrd-2.6.11-1.14_FC3.img
    [Linux-initrd @ 0x1fed6000, 0x1098d9 bytes]

_

And that is all. It hangs there with no more progress.

The system runs all on Logical Volumes except /boot, which is 100 MB on
/dev/hda1
It was initially installed as LVM1 and converted to LVM2.

The same thing partially happened on FC2. FC2 ran fine on the 2.6.5
install kernel, but

The drive configuration is as follows:

Onboard IDE devices:
hda: 80 gb ide, hda1 100 mb boot, hda2 2 gb swap, hda3 is a physical volume
hdb: cd-rom
hdc: 120 gb, ide, lvm whole disk
hdd: 120 gb, ide, lvm whole disk

2-port IDE controller on PCI-bus
hde: 120 gb, ide, lvm whole disk
hdf: 120 gb, ide, lvm whole disk
hdg: 300 gb, ide, lvm whole disk

4-port Promise SATA controller
sda: 250 gb, sata, lvm whole disk
sdb: 250 gb, sata, lvm whole disk
sdc: 250 gb, sata, lvm whole disk
sdd: 250 gb, sata, lvm whole disk

2-port Sil. Image SATA controller
sde: 250 gb, sata, lvm whole disk
sdf: 250 gb, sata, lvm whole disk

lspci produces the following output:

00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev
02)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 22)
00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 10)
00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 10)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
30)
00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169
Gigabit Ethernet (rev 10)
00:0b.0 Unknown mass storage controller: Promise Technology, Inc. PDC20318
(SATA150 TX4) (rev 02)
00:0d.0 RAID bus controller: Silicon Image, Inc. (formerly CMD Technology
Inc) SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 02)
00:11.0 RAID bus controller: Silicon Image, Inc. (formerly CMD Technology
Inc) PCI0680 Ultra ATA-133 Host Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX
440 AGP 8x] (rev a2)

The grub.conf with the entry that fails boot on the most recent kernel
looks like this:

default=2
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.11-1.14_FC3)
         root (hd0,0)
         kernel /vmlinuz-2.6.11-1.14_FC3 ro root=/dev/drivepool/root
         initrd /initrd-2.6.11-1.14_FC3.img

The working grub item looks like this:

title Fedora Core (2.6.9-1.667)
         root (hd0,0)
         kernel /vmlinuz-2.6.9-1.667 ro root=/dev/drivepool/root rhgb quiet
         initrd /initrd-2.6.9-1.667.img

Is there anything I can do to make the initrd step, or the step right
after, more verbose, to help identify what makes the system freeze?

-- 
Torbjørn Lindahl


Relevant Pages

  • Re: need help booting from SATA in 2.4.32
    ... Willy Tarreau wrote: ... will not recognize this disk. ... So i'm thinking once the drive shows up as /dev/sda, the LVM will be ... Good suggestion on disabling IDE, it does not show up as SATA, it simply ...
    (Linux-Kernel)
  • {Spam?} Re: problems with an SATA drive on nVidia3 controller
    ... We have an amd64 machine with an nVidia3 SATA controller on motherboard. ... preference to the Silicon Image connectors, ... failed drive to run on SATA150 (if it's a SATA300 disk). ...
    (freebsd-stable)
  • Re: SATA problem
    ... the ability to "see" a SATA hard drive is a function of the BIOS ... and SATA controller on the motherboard, not a function of the hard drive ... Once the RAID array has been created, the SATA disk should appear in the ...
    (microsoft.public.windowsxp.general)
  • Re: SATA problem
    ... the ability to "see" a SATA hard drive is a function of the BIOS ... and SATA controller on the motherboard, not a function of the hard drive ... Once the RAID array has been created, the SATA disk should appear in the ...
    (microsoft.public.windowsxp.hardware)
  • Re: Using RAID chipsets in the motherboard.
    ... > 1) All most all of the newer motherboards come with SATA RAID. ... > many knowledge base resources that a HW controller looks just like an IDE ... It is usable as a SATA host. ... "One disk to rule them all, ...
    (Debian-User)