Bug 17608
| Summary: | During installation lilo.conf incorrect when / is software raid1, leaving system unbootable | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Christopher Johnson <ckjohnson> |
| Component: | anaconda | Assignee: | Erik Troan <ewt> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-10-03 20:49:48 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
Christopher Johnson
2000-09-18 16:38:42 UTC
This seems to work in 7.0. Please reopen if it doesn't. 7.0 does indeed boot under those conditions (guess the bootloader was improved). But lilo.conf still incorrectly references boot=/dev/sda instead of boot=/dev/md0 As installed if sda fails there will be no bootloader on sdb and in spite of the raid configuration it will not boot without a boot floppy. By using boot=/dev/md0 lilo writes the boot record on sda and sdb to it can boot with either drive. |