Red Hat Bugzilla – Bug 445985
Anaconda finds a multipath controller where none exists
Last modified: 2009-07-14 12:09:39 EDT
Description of problem: I have the Fedora 9 Beta installed and am attempting to
install the Preview. However, the preview doesn't see all of my hard drives
during the installation. I have seven drives:
- (2) 14GB drives, mirrored in the BIOS; I have F9 Beta installed on these
- (2) SATA drives connected to the motherboard
- (2) IDE drives connected to a Maxtor PCI card
- (1) IDE drive connected to a Promise PCI card
- the motherboard is an ASUS K8N-E Deluxe with the latest (but not Beta) firmware
All of the IDE drives are bus masters on their own cables and are identified by
the BIOS at boot time. I installed Beta with just the two mirrored drives, so I
don't know what it sees at install time, but when I run the Beta (and run fdisk)
all seven drives are identified. (See attachment).
When I boot the Preview DVD and get to the drive configuration page I select
manual configuration. Preview sees MAPPER (the mirror), SDE (SATA), SDF (IDE)
and SDG (SATA). It appears to be missing the two drives on the Maxtor
controller, and very oddly it skips SDC and SDD.
The Ubuntu 8.04 installer sees all seven drives (but doesn't show that SDA and
SDB are mirrored). It identifies them as SDA-SDF plus /dev/hda and shows the
correct size for each.
Version-Release number of selected component (if applicable):
I tried it twice and got the same results both times.
Steps to Reproduce:
I would expect it to see all of the drives.
Created attachment 305044 [details]
Fdisk taken under the installed Beta
I tried moving the IDE interface card to a different PCI slot, but that didn't
help. However, I was able to get the chip IDs. The two cards have:
- Promise PDC2067 (HDs are recognized at install time)
- SILO68OACL144 (HDs are recognized after installation, but not at install time)
Can you get the output of /tmp/syslog and lshal when the installer is running?
I'm sure I can if you give me instructions. I assume I need to break into the
installer and copy those files to a Flash drive? However, I don't know how to
get to a shell from the installer.
ctrl-alt-f2 will drop you to a shell once you're in the graphical installer.
Created attachment 305314 [details]
Output from lshal + /tmp/syslog
I have attached the output from lshal and /tmp/syslog.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
The problem appears NOT to be that the installer doesn't support one of my drive
interfaces, but rather that it doesn't like something about the drive itself.
It shows a mapped drive of 200GB (the size of my drives); I don't understand why
it does that. However, seeing that gave me the idea to format the drives and
see if that fixed the problem. I booted from a Fedora 9 Live USB drive, ran
mkfs on each drive in turn, and on two of them (sdc1 and sde1) it said 'This
drive appears to be in use' and refused to format it. All of the others
formatted just fine. I removed what I believed to be sdc1 from the system;
after I did that I was able to format all of the remaining drives. I will try
installing again and see if it now sees four 200GB drives rather than three.
Could the installer think that I have mirrored two of the drives? That would
give me one 200GB 'mapper' drive, and only three remaining 200GB drives.
However, these drives have never been mirrored. Three of them were once a
single LV, but never part of an mdadm mirror.
Yes, with sdc removed and the other drives (including sde1 which was 'in use'
yesterday) reformatted, the installer sees four 200GB drives as it should. The
next step is to reinstall sdc and see if the installer then sees all five drives.
If you need more information please let me know ASAP; I don't want my attempts
to diagnose and fix the problem to destroy the evidence you need.
With sdc1 reinstalled I get no joy - four drives (the two SATA drives plus one
of the 190780 MB IDE drives, plus a 190780 MB device-mapper drive.
What other tests would you like me to run?
I finally figured out what is going wrong and how to work around it, although I
still have no clue why. Anaconda thinks two of my drives are a single drive,
reachable via a multipath controller. My humble server has never had a
multipath controller! What is even more puzzling is that the two drives
involved are a SATA and an IDE drive, and are not even the same size.
The workaround of course is to add 'nompath' as a kernel option. (Now as soon
as the blasted repository is fixed so I no longer get 'Unable to read group
information..." I think I can actually install!)
If you need more diagnostic information to determine the root cause please let
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.