Bug 554602

I had tried the no mpath boot option, and that didn't help. Inclusion of the "basic video" got past GFX issues with the NV 6600GT display initialization (straight to text mode). Adding the "NoDMRAID" option at boot time seemed to get past the storage hardware initialization issue. OS installation is getting past the storage initialization errors now.

Please try another time, and then when the error has happened switch to tty2 (ctrl + alt + F2), and collect the log files under /tmp (copy them to a usbstick or use scp), and attach them here.

Without logs there is very little we can do.

Thanks you,

Hans

Hans,

OK. Will try tomorrow night.  I was able to complete the install, but needed to add dm_multipath to the blacklist.conf file.  

Strangely the 4 SATA devices were given /dev/sda, /dev/sdf, and /dev/sdg and /dev/sdh names, but the install worked properly when I used the nodmraid boot option during the install.

After the install completed, and the box failed to boot, I did a rescue boot (with nodmraid option) and added "blacklist dm_multipath" to the blacklist.conf file. Then an init 6 brought the system up properly.

I realize this may not help the debugging of dm_multipath, but it at least confirms the source of the problem (IMHO). 

Anecdotally, the NVidia 6600GT card and Noveau driver didn't work. I had to use basic VGA to do a graphical install. 

The Alt-F1 and Alt-F2 CLI sessions also seemed to get confused. I would see display from one "leaking" into the other, and often I'd need to hit Alt-F1 and then Alt-F2 to see the output from (say) df.

Otherwise I'd type in "df" and it would not display any thing on the current screen (Alt-F1) but it would display on alt screen (Alt-F2).

The Fedora 10 DVD booted perfectly and behaved well in all aspects.  Display, Alt-F1/Alt-F2, Storage etc.

In short:

The Fedora 12 DVD did not work with dm_multipath kernel module, with the Noveau Xorg driver, and the Alt-F1/Alt-F2 sessions were intermingled.

Do you have any other folks working on this? Is particular to K8WE/Tyan board?


Thanks!

John Westerdale

Created attachment 383598 [details]
From failed boot from 64 bit F12

Boot Tyan K8WE from F12 DVD that passed the binary check.   Look for 3 more files.

Created attachment 383599 [details]
Program.log from failed install

Program.log from failed install

Created attachment 383600 [details]
Storage log from failed F12 boot from DVD

Storage log from failed F12 boot from DVD

Created attachment 383601 [details]
Syslog file from failed F12 boot from DVD

Syslog file from failed F12 boot from DVD

Added 4 files from the F12/K8WE OS install.  Graphics load failed with a NVIdia 6600GT card, and the DMRAID kernel module seemed to be nutty. 

There were 4 SATA drives, and all booted fine,  SOmehow, USB stick was presented with /dev/sdc... Hmm.. shouldn't it be sda, sdb, sdc and sdd for disks and sde for USB thumbdrive?

Best

John Westerdale

Hi John,

Thanks for providing the logs. I'm afraid a really important one I really need is missing. Can you please try one more time (sorry), once you get the unhandled exception, you should see a traceback and there should be a
/tmp/anacdump.txt file which I need. If that is not there, hit the file a bug button if that is there. Otherwise please write down the exact error message you are seeing (or take a picture).

While you're add it could you also run:
dmraid -vvv -t -ay &> dmraid.log

From tty2, and attach dmraid.log here too, that could save us another install attempt just to get that.

Thanks,

Hans

Created attachment 384493 [details]
Tar file of the /tmp dir from failed install on K8WE of Fedora 12

This is a tar file of the /tmp dir following a failed install

Created attachment 384494 [details]
Output from dmraid -vvv -ta -y >dmraid.log

This is the dmraid log file I was asked to provide!

Hi all,

I reran the install. and collected /tmp as well as screen shots of the debug screen of last rites.  

The DMRAID is also attached separately.

Hi John,

Thanks! Now I finally have all the bits I need to be able to analyse why this is
going wrong :)

First of all you mention that you were surprised to see 8 scsi disks, this is normal, your system has an usb card reader which has one lun per slot, so your usb card reader accounts for 4 of the 8 disks, the other 4 are your regular disks.

Second, the traceback you are seeing is because your 4 disks are configured as a RAID5 set in your BIOS. Or maybe once upon a time were configures as such, and when you disabled the RAID support in the BIOS, you did not first reset the disks back to non RAID disks. So the disks still have BIOS RAID metadata on them, and we recognize them as BIOS RAID and try to active the BIOS RAID set.

This activation fails because of bug 533703, so I'm marking this as a duplicate of that bug.

If you want to use your disks as BIOS RAID disks, you need to choose a different raid level either 0, 1, 10 or 01 (iow you need to recreate the set in the BIOS).

If you have long ago disabled the RAID BIOS, but not first set the disks to non RAID status, then you are sort of hit by:
https://fedoraproject.org/wiki/Common_F11_bugs#dmraid-nodmraid

As described there nodmraid is a valid workaround (but removing the metadata from the disks so you don't hit this again with future installs is preferred)

*** This bug has been marked as a duplicate of bug 533703 ***