Production issue : Input/output error and Bus Error
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It sounds like a HW error to me - I'd guess the disk is dying. (?)
Have you got a /var/log/dmesg or /var/log/boot.log file ?
Basically there should be a log that lists what happened for HW checks during boot - not sure what its called in RHEL4.
Totally different file, with (in general) totally different information.
dmesg holds the boot, hardware detection, driver installation, and system IPL results. Generally, once the system is completely up and running it is not written again until the next boot.
Messages is updated with kernel signal and informational messaged during operation.
It does make sense to check on what was detected during initial setup. It is good information in itself, but it also gives extra meaning to some of the information found in later logs.
I agree with the chrism01, and want to add that you might want to pick a time for a full diagnostic analysis (testing) of your entire hardware platform starting with the testing built into the BIOS. Not because hardware is the problem, but to rule that out as a factor. No amount of fixing software will repair a hardware failure, so it is good to know what hardware you can trust!
Even before that, though, I would check that .logout file. It may be doing something that will provide a clue.
I would also check the 'last' report, it rarely has detail useful for this kind of issue, but rare does not mean never. Also the security log records, in case that there is something interesting in the record of the account startup.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.