Bug 39805
| Summary: | Boot process crashes | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <jlshelby> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2 | ||
| 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: | 2004-09-30 15:38: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
Need Real Name
2001-05-09 05:18:21 UTC
Will you boot into rescue mode, and then run this:
chroot /mnt/sysimage
rpm -qa --qf '%{NAME} %{ARCH}\n' | grep kernel
exit
exit
and let me know what it says?
If I place the harddrive in another system it boots fine. The problem appears to be with the difference in booting the kernel install floppy and the runtime kernel. Says it cant chroot /mnt/sysimage Sorry, I didn't realize you were running 6.2 (I gave instructions for 7.1).
You need to mount your root filesystem with a command like:
mount /dev/hda5 /mnt/sysimage
Note that /dev/hda5 may (probably is) different for you -- the previous
instructions should work once you've done this.
Ahh, much better the result is..... kernel i386 kernel-pcmcia-cs i386 kernel-utils i386 Hrm. Sounds like you need to re-run lilo....... I put the drive in another 486 and it boots fine. That makes it look like bad memory chips..... Can you download the memtest86 program (search on www.freshmeat.net) and test your ramchips ? Switched the memory from the one it does boot in and same problem. Is their a boot time switch I can set to see where the problem is hanging...also it sometimes doesn't give a crc and just reboots itself when loading the kernel. Unfortionatly there is no such switch as this problem hits before the first byte of kernel-code is executed. (eg the kernel is being loaded/uncompressed into ram) Are there any other diagnostics to know why the load/uncompress fails? It loads the rescue kernel and install kernel just fine so I am a little confused at why this doesnt work? The difference between the rescue/install floppy and the harddisk boot is the bootloader: on the harddisk LILO is used, on the floppy syslinux is used. Would it be possible to grab a later lilo and use the rescue floppy to install that ? The difference between the rescue/install floppy and the harddisk boot is the bootloader: on the harddisk LILO is used, on the floppy syslinux is used. Would it be possible to grab a later lilo and use the rescue floppy to install that ? Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |