Bug 40760
Summary: | Installer failed to install Lilo on mbr on system with scsi zip drive | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Will Henry <whenry> |
Component: | anaconda | Assignee: | Brent Fox <bfox> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-07-10 04:31:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Will Henry
2001-05-15 18:16:33 UTC
That's strange, because I have an internal zip in one of my test machines and have not seen this problem. However, mine is on the IDE bus and not the SCSI bus, so that probably makes the difference. After you've got the machine installed and reattached the device, what device does the kernel see the zip drive as? sda, sdb, or sdc? It sees the zip as sda after I successfully install linux and reattach the drive. Since there is no boot disk in the zip drive the system skips it and boots off of the hard drive. One additional bit of information for what it's worth, my system uses software raid for all partitions except the swap and /boot. I suspect the root of the problem is that the system scans the UW SCSI bus first, where the zip is, and then scans the U2 SCSI bus, where the hard drives are. I don't know of any way to change this. However, it seems to me that linux should recognize that the mbr doesn't belong on the zip drive. It doesn't try to put it on the floppy or CDRW so why does it try to put it on the zip? It appears linux thinks the zip is a hard drive. We don't have an internal SCSI zip drive. We have an external SCSI one, but I was not able to reproduce this behavior. It could be because there are two scsi busses in the computer. We don't really have a way of figuring out which SCSI bus should be the primary controller. I think that might be the root of the problem. I've talked to the other developers and here's the situation. The kernel scans the PCI bus in ascending order. The first controller it finds is considered the primary controller, and that's what it installs to. You might try changing the bus order of the controllers in the bios, or changing their order inside the machine. Other than that, we don't really have a way of fixing the problem. |