FC6 Test3 installer fails

[chiefgeek]

I am having no luck getting the installer for FC5 or FC6 to work with a new computer. With FC5 it fails trying to parse the disk device, for FC6 it fails with what looks like a similar problem.

The board in question is an intel based chipset (ASUS P5BW-LA) with the ICH8 SATA RAID 0/1/10/5 controller configured in RAID0. I think the chipset is Q965 Express Chipset but have not been able to confirm.

I noticed that it takes quite a long time to probe the ata devices and that a warm reboot after the install fails causes bios to lock up at probing devices or probing raid.

Traceback (most recent call first):
  File "/usr/lib/booty/bootloaderInfo.py", line 2048, in getDiskPart
    partNum = int(dev[cut:]) - 1
  File "/usr/lib/booty/bootloaderInfo.py", line 263, in setDevice
    (dev, part) = getDiskPart(device)
  File "/usr/lib/anaconda/bootloader.py", line 86, in bootloaderSetupChoices
    anaconda.id.bootloader.setDevice(choices["mbr"][0])
  File "/usr/lib/anaconda/dispatch.py", line 200, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 123, in gotoNext
    self.moveStep()
  File "/usr/lib/anaconda/gui.py", line 919, in nextClicked
    self.anaconda.dispatch.gotoNext()
ValueError: invalid literal for int(): e

Local variables in innermost frame:
cut: -1
dev: mapper/isw_ebgiieffba_stripe
name: mapper/isw_ebgiieffba_stri
letter: _


/tmp/syslog:
<5>Linux version 2.6.17-1.2630.fc6 (brewbuilder@hs20-bc1-6.build.redhat.com) (gcc version 4.1.1 20060828 (Red Hat 4.1.1-20)) #1 Wed Sep 6 16:26:41 EDT 2006
...
<7>CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000e3bd 00000000 00000001
<7>CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000e3bd 00000000 00000001
<4>monitor/mwait feature present.
<4>using mwait in idle threads.
<6>Intel machine check architecture supported.
<6>Intel machine check reporting enabled on CPU#0.
<4>CPU: Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz stepping 06
<6>Checking 'hlt' instruction... OK.
<6>ACPI: Core revision 20060707
<4>ACPI: setting ELCR to 0200 (from 0c20)
...
<6>ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl RAID mode
<6>ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part 
<6>ata1: SATA max UDMA/133 cmd 0xF88EA100 ctl 0x0 bmdma 0x0 irq 11
<6>ata2: SATA max UDMA/133 cmd 0xF88EA180 ctl 0x0 bmdma 0x0 irq 11
<6>ata3: SATA max UDMA/133 cmd 0xF88EA200 ctl 0x0 bmdma 0x0 irq 11
<6>ata4: SATA max UDMA/133 cmd 0xF88EA280 ctl 0x0 bmdma 0x0 irq 11
<6>ata5: SATA max UDMA/133 cmd 0xF88EA300 ctl 0x0 bmdma 0x0 irq 11
<6>ata6: SATA max UDMA/133 cmd 0xF88EA380 ctl 0x0 bmdma 0x0 irq 11
...
....
<4>=============================================
<4>[ INFO: possible recursive locking detected ]
<4>2.6.17-1.2630.fc6 #1
<4>---------------------------------------------
<4>lvm/682 is trying to acquire lock:
<4> (&md->io_lock){----}, at: [<f8a8c42f>] dm_request+0x18/0xcd [dm_mod]
<4>
<4>but task is already holding lock:
<4> (&md->io_lock){----}, at: [<f8a8c42f>] dm_request+0x18/0xcd [dm_mod]
<4>
<4>other info that might help us debug this:
<4>1 lock held by lvm/682:
<4> #0:  (&md->io_lock){----}, at: [<f8a8c42f>] dm_request+0x18/0xcd [dm_mod]
<4>
<4>stack backtrace:
<4> [<c04037db>] show_trace_log_lvl+0x58/0x171
<4> [<c0403db6>] show_trace+0xd/0x10
<4> [<c0403e53>] dump_stack+0x19/0x1b
<4> [<c042be6f>] __lock_acquire+0x765/0x97c
<4> [<c042c5f7>] lock_acquire+0x4b/0x6c
<4> [<c04296ec>] down_read+0x2d/0x3f
<4> [<f8a8c42f>] dm_request+0x18/0xcd [dm_mod]
<4> [<c04c7ce0>] generic_make_request+0x28e/0x29e
<4> [<f8a8b437>] __map_bio+0xc0/0xee [dm_mod]
<4> [<f8a8bcdd>] __split_bio+0x158/0x3a0 [dm_mod]
<4> [<f8a8c4d6>] dm_request+0xbf/0xcd [dm_mod]
<4> [<c04c7ce0>] generic_make_request+0x28e/0x29e
<4> [<c04c99b2>] submit_bio+0xa1/0xa9
<4> [<c047e9ca>] dio_bio_submit+0x4f/0x61
<4> [<c047f7c3>] __blockdev_direct_IO+0x8fa/0xc52
<4> [<c046657f>] blkdev_direct_IO+0x30/0x35
<4> [<c04449e3>] generic_file_direct_IO+0x88/0xe4
<4> [<c0444bea>] __generic_file_aio_read+0xb7/0x1ad
<4> [<c0445bbc>] generic_file_read+0x87/0x9b
<4> [<c045f6c8>] vfs_read+0xa9/0x15b
...
/tmp/anaconda.log:
21:46:48 INFO    : 2073084 kB are available
21:46:48 INFO    : modules to insert cramfs fat vfat sunrpc lockd fscache nfs_acl nfs loop isofs floppy edd pcspkr squashfs
...
21:46:56 DEBUG   : probing buses
21:46:56 DEBUG   : finished bus probing
21:46:56 DEBUG   : ignoring driverless device Intel Corporation Unknown device 283e
21:46:56 DEBUG   : ignoring driverless device Intel Corporation Unknown device 2812
21:46:56 DEBUG   : ignoring driverless device Intel Corporation Unknown device 244e
21:46:56 DEBUG   : ignoring driverless device Intel Corporation Unknown device 283f
21:46:56 DEBUG   : ignoring driverless device Intel Corporation Unknown device 29a1
21:46:56 DEBUG   : ignoring driverless device Intel Corporation Unknown device 29a0
21:46:56 DEBUG   : ignoring driverless device Intel Corporation Unknown device 284b
21:46:56 DEBUG   : ignoring driverless device Conexant Unknown device 2f20
21:46:56 DEBUG   : ignoring driverless device nVidia Corporation GeForce 7300 LE
21:46:56 DEBUG   : ignoring driverless device Unknown device 4444:0016
21:46:56 DEBUG   : ignoring firewire device Unknown device 11c1:5811 (ohci1394)
...
21:49:59 DEBUG   : ignoring driverless device Intel Corporation 82801H (ICH8 Family) SMBus Controller
21:49:59 DEBUG   : ignoring driverless device Intel Corporation 82801HH (ICH8DH) LPC Interface Controller
21:49:59 DEBUG   : ignoring driverless device Intel Corporation 82801 PCI Bridge
21:49:59 DEBUG   : ignoring driverless device Intel Corporation 82801H (ICH8 Family) PCI Express Port 1
21:49:59 DEBUG   : ignoring driverless device Intel Corporation P965/G965 PCI Express Root Port
21:49:59 DEBUG   : ignoring driverless device Intel Corporation P965/G965 Memory Controller Hub
21:49:59 DEBUG   : ignoring driverless device Intel Corporation 82801H (ICH8 Family) HD Audio Controller
21:49:59 DEBUG   : ignoring driverless device Conexant HSF 56k Data/Fax Modem
21:49:59 DEBUG   : ignoring driverless device nVidia Corporation GeForce 7300 LE
21:49:59 DEBUG   : ignoring driverless device Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder
21:49:59 DEBUG   : ignoring firewire device Agere Systems FW323 (ohci1394)
...
21:52:50 DEBUG   : starting raid <block.device.RaidSet instance at 0xb795da0c> with mknod=True
21:52:51 DEBUG   : done starting dmraids.  Drivelist: ['mapper/isw_ebgiieffba_stripe']
21:52:53 DEBUG   : stopping all dmraids
21:52:53 DEBUG   : stopping raid <block.device.RaidSet instance at 0xb795da0c>
21:52:53 DEBUG   : removing mapper/isw_ebgiieffba_stripe from isys cache
21:52:53 DEBUG   : adding isw_ebgiieffba_stripe to isys cache
21:52:53 DEBUG   : adding isw_ebgiieffba_stripe to isys cache
21:52:53 DEBUG   : removing <block.device.RaidSet instance at 0xb795da0c> from dm cache
21:52:53 WARNING : step complete does not exist
21:52:53 INFO    : moving (1) to step partitionobjinit
21:52:53 INFO    : no initiator set
21:52:53 DEBUG   : starting dmraids
21:52:54 DEBUG   : self.driveList(): ['sda', 'sdb']
21:52:54 DEBUG   : DiskSet.skippedDisks: []
21:52:54 DEBUG   : DiskSet.skippedDisks: []
21:52:54 DEBUG   : starting all dmraids on drives ['sda', 'sdb']
21:52:54 DEBUG   : scanning for dmraid on drives ['sda', 'sdb']
21:52:54 DEBUG   : got raidset <block.device.RaidSet instance at 0xb795da2c> (sda sdb)
21:52:54 DEBUG   :   valid: True found_devs: 2 total_devs: 2
21:52:54 DEBUG   : adding mapper/isw_ebgiieffba_stripe to isys cache
21:52:54 DEBUG   : adding sda to dm cache
21:52:54 DEBUG   : removing sda from isys cache
21:52:54 DEBUG   : adding sdb to dm cache
21:52:54 DEBUG   : removing sdb from isys cache
21:52:54 DEBUG   : starting raid <block.device.RaidSet instance at 0xb795da2c> with mknod=True
21:52:54 DEBUG   : done starting dmraids.  Drivelist: ['mapper/isw_ebgiieffba_stripe']
21:52:55 ERROR   : could not create directory //dev/mapper: File exists
21:52:55 INFO    : moving (1) to step parttype
21:53:20 INFO    : moving (1) to step autopartitionexecute
21:53:20 DEBUG   : stopping all dmraids
21:53:20 DEBUG   : stopping raid <block.device.RaidSet instance at 0xb795da2c>
21:53:20 DEBUG   : removing mapper/isw_ebgiieffba_stripe from isys cache
21:53:20 DEBUG   : adding isw_ebgiieffba_stripe to isys cache
21:53:20 DEBUG   : adding isw_ebgiieffba_stripe to isys cache
21:53:20 DEBUG   : removing <block.device.RaidSet instance at 0xb795da2c> from dm cache
21:53:20 DEBUG   : starting dmraids
21:53:20 DEBUG   : self.driveList(): ['sda', 'sdb']
21:53:20 DEBUG   : DiskSet.skippedDisks: []
21:53:20 DEBUG   : DiskSet.skippedDisks: []
21:53:20 DEBUG   : starting all dmraids on drives ['sda', 'sdb']
21:53:20 DEBUG   : scanning for dmraid on drives ['sda', 'sdb']
21:53:20 DEBUG   : got raidset <block.device.RaidSet instance at 0xb795dfec> (sda sdb)
21:53:20 DEBUG   :   valid: True found_devs: 2 total_devs: 2
21:53:20 DEBUG   : adding mapper/isw_ebgiieffba_stripe to isys cache
21:53:20 DEBUG   : adding sda to dm cache
21:53:20 DEBUG   : removing sda from isys cache
21:53:20 DEBUG   : adding sdb to dm cache
21:53:20 DEBUG   : removing sdb from isys cache
21:53:20 DEBUG   : starting raid <block.device.RaidSet instance at 0xb795dfec> with mknod=True
21:53:20 DEBUG   : done starting dmraids.  Drivelist: ['mapper/isw_ebgiieffba_stripe']
...
21:53:21 INFO    : moving (1) to step partitiondone
21:53:21 INFO    : moving (1) to step bootloadersetup


/tmp/netinfo:
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=dhcp
HOSTNAME=hp
DOMAIN=jeff.com


/tmp/lvmout:
  No volume groups found

[multescugeorge@]

One thing i can think of is to remove all partitions from the hard drive.
I've heard about some block alignment check that was introduced in newer kernels that caused raid partitions created with an earlyer kernel to be un-readable. Perhaps this is similar.
Also it looks like the kernel can't load the drivers for your motherboard, and that looks like a bigger problem.
See if you can boot a kernel, eighter from Fedora4 or 5 "linux rescue" mode, or from some live cd. If they fail with similar "driverless" errors, then it's most likely a kernel problem with your motherboard.

[chiefgeek]

Thanks for the pointers.

I tried fc5 first and it failed with a similar message trying to parse out some disk device for "mbr".

I believe that the kernel that FC6-Test3 does not support the chipset on my mobo.

Is there anyway to get a later kernel, update install image to use newer kernel and give it a try?

[multescugeorge@]

You can try filing a bug report on against the kernel(start at www.kernel.org), also check for known bugs for your chipset.
If the fix exists, then most likely will be included in FC6

[chiefgeek]

Ok. I am now also under the impression that Intel's 965 chipset is not supported by the kernel yet.

I looked on kernel.org and could not figure out if any one is working on it, but more importantly if I do find a newer version of the kernel that works is it possible to update the installer to use that kernel or do I have to wait for the next release?

[multescugeorge@]

In theory, you can re-spinn (that's the technical word for it) the install CD.
IE you update the kernel yourself, it's possible, but it's not very easy. Don't know any detailes about the procedure myself.
It could be possible to install FC6T3 tho, with some clever kernel arguments, but it's more something about luck.
Also, if i understand correctly, you have a RAID thingy going on there. You can try taking them out of raid, perhaps (99% sure) the install will work on single disk.

[skyreacher]

Yes, the chipset is the problem. I also have problems with an Asus P5B Deluxe.

See this thread for further info:
http://forums.fedoraforum.org/forum/...d.php?t=122892

BTW, I'm interested in how installing on the RAID device works (because I want to do the same) - if you can give any hints i'd be thankful.

[skyreacher]

My Asus P5B Deluxe works great with FC6 - even the onboard RAID controller is supported by FC6.