Bug 80628
Summary: | After a few days, system won't boot - unable to mount /proc | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Mike McMullen <mlm> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.0 | CC: | alan, borst, damonp, mlm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | athlon | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-30 15:40:20 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
Mike McMullen
2002-12-29 02:11:54 UTC
I have this same problem on RH9 Athlon XP (no RAID) (brand new hw). mounting proc /etc/rc.sysinit:line 90: 39 segmentation fault LC_ALL = C grep - q /initrd /proc/mount If I go in to rescue and chroot, grep (and most other) cmd line utils segfault same. I've installed twice (swapping hd's in between tries). While setting up, machine was booted and rebooted at least 7 or 8 times configuring and setting up. Once configuration was complete, walked away from the box, then it dies several days later. Does memtest86 (www.memtest86.com) show any problem on either of these systems ? Does a current errata kernel help ? I have upgraded a few systems (RH7.3 to start) immediately after install to all of the most recent errata and fixes. After the system is rebooted 2-3 times, this error shows up, but it doesn't show up on all of them. I have not attempted to use memtest86, but will run it in the near future. I found no errors with memtest86 running all of the tests. I also ran PowerMax (it's a Maxtor HD) to test the HD. No problems there either. Is there any better HD test or maybe a disk controller test? Thanks damonp It doesnt feel like a disk controller error. The ram test is important because that is a common problem but you seem to have passed that ok. The next thing I'd like to do is try and eliminate power management and bios events from the equation. If you can turn off APM/ACP power management in the bios of a problem box, and also if it has it turn off USB legacy keyboard support, save the CMOS settings then boot Linux and see if it dies in a few more days time I have had the same problem some weeks ago. I had RH8.0 running on a server for some months (almost from the release o rh8.0). I had a small script running from crond each minute. One day I ssh'd to the server and I could see hundreds of executables used by the script in <defunct> state, because almost no command was able to be executed. I tried to "more /var/log/.." but ->segfault. Root fs was ext3. PC was PIII, IDE. I rebooted, and the first error was "Cannot mount /proc"... many other errors, and when I received the prompt for password (for system maintenance) it didn't accept the password. I restarted the password from a boot CDROM, and when rebooted, I entered the password, but every command gave segfault (including "mount", which was what was causing the first error) I made a backup of the currupt fs to another partition, reinstalled RH8.0 in the same partition after mke2fs, and everything worked fine until... until I tried to execute "vi" from the corrupt partition. It corrupted everything in my new partition again, so I had to reinstall once again. It acted like a virus, as if my old system executables were tainted. Any idea of the cause? Eduardo Gimeno 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/ |