PDA

View Full Version : FC6 installation does not boot on newer (X38BT) hardware


vugo
18th July 2008, 03:31 AM
I recently decided to repurpose an older system (Intel 975XBX), and transferred its PATA Linux drive into my new system (Intel X38BT). The installation is FC6, and the last system update was to kernel 2.6.22.14-72.fc6. It boots perfectly fine on my old system. However, I got the following message when I tried to boot it in the new system:

___

Reading all physical volumes. This may take a while...
No volume groups found
Volume group "VolGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: could not find filesystem '/dev/root'
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
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

___

I initially suspected an LVM issue, but I came across the following threads:
http://fedoraforum.org/forum/showthread.php?t=192719
http://fedoraforum.org/forum/showthread.php?t=192425

and figured that the kernel is fairly old, so it must not have correct drivers for the IDE controller on the new board (a Marvell 88SE61XX, based on the BIOS boot messages).

Both, an FC9 LiveCD, as well as rescue-mode FC9 installation CD are able to boot on the new system. (An FC6 installation CD does NOT boot, citing driver problems [I forget the exact message]).

So I downloaded kernel 2.6.26 and built it with relevant ATA/PATA config options I found under /boot of the LiveCD image:

CONFIG_ATA=m
CONFIG_ATA_ACPI=y
CONFIG_ATA_PIIX=m
CONFIG_ATA_GENERIC=m
CONFIG_PATA_ACPI=m
CONFIG_PATA_MARVELL=m

When I try to boot this new kernel (initially with the vanilla initrd created by "make install"), I get the following:

____

PCI: Failed to allocate mem resource #6:20000@a0000000 for 0000:01:00.0
mount: could not find filesystem '/dev/root'
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
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

____

So the only difference is that the LVM messages are gone, but I am getting the PCI device error. Can PCI device enumeration/naming change everytime you boot? When I boot the FC9 rescue CD, /sys/class/block/sda is linked to device 0000:00:1c.4/0000:03:00.0, which is not the same name as the one in the error above.

Anyway, I then tried various flavors of initrd, as suggested in
http://fedoraforum.org/forum/showthread.php?t=192425:

including --preload libata --preload pata_marvell --preload ata_piix, to no avail. I still get the same message as above.

Loaded ata/pata modules when booted on the rescue CD are as follows:

____

lsmod | grep ata

ata_generic 8964 0
ata_piix 20228 0
pata_acpi 8192 0
pata_marvell 8064 0
libata 126816 5 ahci,ata_generic,ata_piix,pata_acpi,pata_marvell
scsi_mod 121204 7 sg,sr_mod,sd_mod,libata,iscsi_tcp,libiscsi,scsi_tr ansport_iscsi

____

What else can I try? There has to be a way, since the rescue CD is able to mount the drive without any problems.

ppesci
18th July 2008, 08:48 AM
Vugo:

FC6 is no longer supported. You can try F8 or F9 that are more advanced. I think both will work well in your hardware.

Welcome to this forum.

HTH

tsorvoja
18th July 2008, 09:02 AM
Install F9. FC6 is really out-dated and has one nasty root access bug in kernel...

vugo
18th July 2008, 04:48 PM
Well, my base installation is FC6, but I am running the latest released kernel (2.6.26) within it- which is even newer than the current FC9 kernel. Regardless of the base installation, I keep thinking I ought to be able to get it to work with the right set of drivers/kernel config.

ppesci
18th July 2008, 05:47 PM
Ok vugo:

I thinf you are right, then maybe some needed module is not included in your kernel compilation

This is the output of the comand : grep ATA /boot/config-2.6.25.9-40.fc8

CONFIG_ATA_ACPI=y
CONFIG_SATA_AHCI=m
CONFIG_SATA_SVW=m
CONFIG_ATA_PIIX=m
CONFIG_SATA_MV=m
CONFIG_SATA_NV=m
CONFIG_SATA_QSTOR=m
CONFIG_SATA_PROMISE=m
CONFIG_SATA_SX4=m
CONFIG_SATA_SIL=m
CONFIG_SATA_SIL24=m
CONFIG_SATA_SIS=m
CONFIG_SATA_ULI=m
CONFIG_SATA_VIA=m
CONFIG_SATA_VITESSE=m
CONFIG_SATA_INIC162X=m
CONFIG_PATA_ACPI=m
CONFIG_PATA_ALI=m
CONFIG_PATA_AMD=m
CONFIG_PATA_ARTOP=m
CONFIG_PATA_ATIIXP=m
CONFIG_PATA_CMD640_PCI=m
CONFIG_PATA_CMD64X=m
CONFIG_PATA_CS5520=m
CONFIG_PATA_CS5530=m
CONFIG_PATA_CS5535=m
CONFIG_PATA_CS5536=m
CONFIG_PATA_CYPRESS=m
CONFIG_PATA_EFAR=m
CONFIG_ATA_GENERIC=m
CONFIG_PATA_HPT366=m
CONFIG_PATA_HPT37X=m
CONFIG_PATA_HPT3X2N=m
CONFIG_PATA_HPT3X3=m
CONFIG_PATA_HPT3X3_DMA=y
# CONFIG_PATA_ISAPNP is not set
CONFIG_PATA_IT821X=m
CONFIG_PATA_IT8213=m
CONFIG_PATA_JMICRON=m
# CONFIG_PATA_LEGACY is not set
CONFIG_PATA_TRIFLEX=m
CONFIG_PATA_MARVELL=m
CONFIG_PATA_MPIIX=m
CONFIG_PATA_OLDPIIX=m
CONFIG_PATA_NETCELL=m
CONFIG_PATA_NINJA32=m
CONFIG_PATA_NS87410=m
CONFIG_PATA_NS87415=m
CONFIG_PATA_OPTI=m
CONFIG_PATA_OPTIDMA=m
CONFIG_PATA_PCMCIA=m
CONFIG_PATA_PDC_OLD=m
CONFIG_PATA_QDI=m
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
CONFIG_PATA_SERVERWORKS=m
CONFIG_PATA_PDC2027X=m
CONFIG_PATA_SIL680=m
CONFIG_PATA_SIS=m
CONFIG_PATA_VIA=m
CONFIG_PATA_WINBOND=m
# CONFIG_PATA_WINBOND_VLB is not set
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_INFINIBAND_IPOIB_DEBUG_DATA=y
# CONFIG_ATARI_PARTITION is not set
CONFIG_DEBUG_RODATA=y


You can check for something missing, but anyway, my advice is to upgrade.

HTH

Trat Photos - Tipasa - Kherson