Bug 17521
| Summary: | kickstart floppy net-install uses wrong drive geometry on ProLiant ML330 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | John Cagle <john.cagle> | ||||
| Component: | anaconda | Assignee: | Brock Organ <borgan> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 7.1 | ||||||
| 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-11-06 18:23:43 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: | |||||||
| Attachments: |
|
||||||
|
Description
John Cagle
2000-09-15 00:14:17 UTC
Created attachment 3426 [details]
kickstart file
Brock can you reproduce? There are two bug assertions above: 1) LILO writes it's partition information to the wrong location on disk 2) because of 1), the system is not bootable In testing the LILO partition information is located in it's proper place on disk (first 512 bytes of sda1) ... this shows LILO is not writing data to the wrong location (ie 1) is not a bug...) Secondly, without proper boot redirection from the MBR, the system not being bootable is not a bug; placing LILO on the first sector of boot/root partition implicitly requires help from the MBR ... (ie 2) is not a bug ...) Below are listed the octal character dump (od -c) of the first few bytes from sda and sda1 post-install (note: the drive sda was zeroed entirely before this test was run!) Here is the MBR from sda (post-LILO): (od -c dump of first 1k) 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0000660 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 200 001 0000700 001 \0 203 ? 020 \0 \0 \0 340 207 \0 \0 \0 \0 0000720 001 021 005 ? 340 377 \0 210 \0 \0 \0 250 016 001 \0 \0 0000740 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0000760 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 U 252 0001000 Note the first 512 bytes are empty ... zeroed out ... LILO did not affect this area ... Here are the first few bytes of sda1: 0000000 372 353 | l b a L I L O 001 \0 025 004 Z \0 0000020 \0 \0 \0 \0 027 247 006 : 363 H 300 \0 001 364 H 300 0000040 \0 001 362 H 300 \0 001 001 D Z 366 H 300 \0 001 367 0000060 H 300 \0 001 351 < 300 \0 001 352 < 300 \0 001 353 < 0000100 300 \0 001 354 < 300 \0 001 355 < 300 \0 001 356 < 300 0000120 \0 001 357 < 300 \0 001 360 < 300 \0 001 361 < 300 \0 0000140 001 362 < 300 \0 001 363 < 300 \0 001 \0 \0 \0 \0 \0 0000160 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 270 The LILO string appears in it's proper place, showing that LILO indeed wrote the proper information to the proper location (ie boot sector of sda1) instead of a bad location on disk ... I hope this helps, please reopen if there are other issues not being addressed ... thanks for your report! |