Red Hat Bugzilla – Bug 330931
liveinst fails - sg devices confuse anaconda?
Last modified: 2007-11-30 17:12:18 EST
Description of problem:
rawhide-20071011-i686-Live liveinst fails with Anaconda errors reading /dev/sg2,
/dev/sg3, /dev/sg4, /dev/sg5, etc. and then tracebacks.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot rawhide LiveCD
2. Select "Install to Hard Drive"
3. Select keyboard type
4. Click "Cancel" on sg error dialog.
Error opening /dev/sg3: Invalid argument
... traceback ...
No traceback. Unsupported devices should be skipped perhaps.
This is a Dell PowerEdge 2650 server.
Created attachment 226481 [details]
Created attachment 226491 [details]
.xsession-errors from LiveCD fedora user
FATAL: Module md not found.
Probing for video card: ATI Technologies Inc Rage XL
Starting graphical installation...
Created attachment 226511 [details]
Dell PowerEdge 2650 scsi info, dmesg, lspci, sg device info
Same problem with 20071019 i686 live CD. I worked around it by doing "rmmod sg"
before starting liveinst.
What's the output of 'kudzu -p -c HD' on this box?
It appears that the kernel is now exposing the logical disk as /dev/sda (which
is correct), but is now also exposing the underlying physical disks as /dev/sg*
as well. This would be fairly new behavior. It's true - for doing useful
things like firmware upgrades on the drives, having a /dev/sg node for each is
good. But anaconda isn't ready for that...
Author: Mark Haverkamp <firstname.lastname@example.org>
Date: Fri Jan 26 09:23:32 2007 -0800
[SCSI] aacraid: expanded expose physical device code (new)
Received from Mark Salyzyn,
Take the expose_physicals flag and allow the user to select default (physicals
available via /dev/sg), exposed (physicals available via /dev/sd for
experimental reasons) and hidden (physicals blocked from all access). This
expands the functionality of the previous expose_physicals insmod parameter
which was added to support some experimental configurations.
Signed-off-by Mark Haverkamp <email@example.com>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
so it's a module parameter 'expose_physicals', defaulting to value -1 meaning to
expose the disks as /dev/sg*. This can be disabled by passing the module option
'expose_physicals=0'. Or you can fix kudzu.
int expose_physicals = -1;
module_param(expose_physicals, int, S_IRUGO|S_IWUSR);
MODULE_PARM_DESC(expose_physicals, "Expose physical components of the arrays.
-1=protect 0=off, 1=on");
Or we can just filter them in anaconda. Which is the route that's probably the
least risky and least likely to cause other problems.
Created attachment 239551 [details]
output from 'kudzu -p -c HD'
Sorry for the delay, I was away. Here is the kudzu output you requested.
A regular anaconda install on this system worked fine today. I haven't tried a
Live install, since there isn't a new LiveCD to test. However, I think this bug
should be removed from blocking the release, since the regular install worked
fine and there is a good workaround for liveinst. Besides, it sounds like you
fixed the bug already from discussion on fedora-test-list. So, I'll go ahead
and close this.
*** Bug 351221 has been marked as a duplicate of this bug. ***