Bug 61027
| Summary: | System fails to boot after install (Hampton beta1) | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Issue Tracker <tao> |
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | dcm |
| 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: | 2003-03-18 14:58:59 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
Issue Tracker
2002-03-12 14:37:04 UTC
What drives are in this system? Also, does the same thing happen with Hampton beta 2? (Hampton beta 1 and beta 2 are drastically different installer code bases) Can I close this out since we have moved away from the Beta 1 installer? We should drop this unless its a problem with the later Hampton betas. Is this a problem with beta 3? We really need some sort of response on this, or we will be forced to close it. Attempted install of beta 2. Did it (a) once on the third virtual disk of a 18.2 gig divided into 3, and (b) did it the second time on a 4 gig. In both cases, I was able to complete the install. For both tests I used the same server. In (a), I had a GRUB loader on the first disk and configured it with all the necessary information to boot the 3rd and attempted booting it several times without success. Each time it would try to load the kernel image, it would say it was corrupt. In (b) I wanted to eliminate any wierdness induced by the 3-disk split scenario so I used a single 4 gig SCSI. Again, the install completed w/o error, but when I attempted to boot, not even the GRUB loader would load. Are you booting from a SCSI drive attached to a SCSI controller, or from a hardware RAID device? Is one of these machines available in our Raleigh office so we can work on it? Really need to get some feedback on this tao. We are getting really close to freeze and need to know if this is still an issue or not. Updates: With beta 4 the first boot of the OS fails differently than with beta 3. With beta 4 the install completes to the embedded array controller w/o error. On reboot the cursor flashes in the upper left corner of the screen and the system will not boot. Boot CD#1 using "linux rescue" on the command line. Allow the system to mount / on /mnt/sysimage. Then chroot /mnt/sysimage. The /etc/lilo.conf shows: boot=/dev/cciss/c0d0 Should be: boot=/dev/ida/c0d0 After modifying the file and executing /sbin/lilo the system boots from the embedded array controller as expected. Configuration: DL760 P46(10/08/2002) 2 x 700Mhz Xeon, 12GB RAM Boot controller: ROC Boot disk: 9GB RAID0 (8.5GB useable space) slot 1: 10/100 NIC 82557/8/9 Slot 10: SA5312 fw1.86, 1 logical volume 560GB, RAID5 cciss version:2.4.5 (modified by Redhat) cpqarray:2.4.5 kernel version: 2.4.18-0.13bigmem #1 SMP /etc/redhat-release: Red Hat Linux release 7.2.93 (Skipjack) This is the ever-fun "can't determine x86 boot order" bug, then. Milan has the code to allow this to be specified (dupe of lots of other bugs from Compaq like this) |