Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
I have the following problem.We had a server running Fedora Core 6 with a Celeron Conroe CPU 1.8 Ghz.We decided to swop out the CPU with a Intel(R) Core(TM)2 CPU 1.80GHz,same harddrive,same motherboard,etc.
The machine booted up fine,but as soon as a try to open a file it gives the following error.
Code:
vim /var/log/messages
-bash: /usr/bin/vim: Input/output error
even something like df gives problems
Code:
df -h
-bash: df: command not found
I mean.df is certainly a registered command on the box.
My question is.Is this related to the CPU that was changed,or has the harddrive crashed?It looks to me like a harddrive error,and i'd just like to know,if i must rebuild the server on new harddrive,or if swopping the old CPU back will help.
If it is CPU related,what steps do i need to go through then to swop the CPU.
It does not appear related to the CPU swap. There appears to be a bad sector on your drive. You may be able to map the bad sector out, by reformatting the drive with the "-c -c" option, but this will take a long time. For example:
Code:
mke2fs -c -c -j -m0 /dev/sdx
If you have a spare drive, you can swap it in, then install the bad drive on another machine and run the mke2fs command there. For more information on mke2fs, see 'man mke2fs'.
Thanks for the reply.I did build it with a new harddrive,got the same error after a copule of hours uptime.Just a different sector in the error message.I'm running the server now with the first CPU again,Currently fine,but i'll have to monitor it today to be sure.
So basically,its not the harddrive.What's my other options.Sata Controller maybe?Currently i think it must be related to the CPU although the error message does not imply that.
Sorry, you have two bad hard drives. They are delicate mechanical devices, and easily damaged. Vibration, heat, shock, electrostatic discharge will all damage a hard drive.
Other issues, like a failing controller or excessive heat will not cause a consistent sector error.
Sorry, you have two bad hard drives. They are delicate mechanical devices, and easily damaged. Vibration, heat, shock, electrostatic discharge will all damage a hard drive.
HardDrive is fine for about 3 days now,with the original CPU.(The same hardrive gave sector errors with new CPU),so i still believe its not the hard drive.Anyway,i'm going to get a new system and use the CPU thats giving problems and see if it still gives issues.
Very weird that a faulty CPU can cause I/O error messages like the above,but to me it certainly looks like this is the case.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.