Hard disk failing? write error: Bad file descriptor
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.
No. You probably have a corrupt block on the disk which is possibly fixable.
"I have checked lost+found on the both the system's partitions and
they are empty."
fsck places orphan files in lost+found. If you have not run fsck then there will be nothing in lost+found.
"Can someone explain what this error might mean and what, if anything I
should do about it?"
You can diagnose and probably fix the error by running fsck. fsck has to be run against a umounted file system so you would probably have to take the server down to run fsck. You have to balance how badly you want to fix the error versus how badly you want to avoid down time.
Thanks for the response. I did do an fsck recently. It failed with an error,
but I was not able to investigate that further at the time (it was raining
in the server room, so that was the least of troubles!).
I'm trying to get permission to take the server down to try fsck again.
If I can't do fsck soon, is that error likely to result in further corruption?
Hi Again,
fsck seemed to do the trick. All has been well
with this machine for some time now.
...Except now we have another error on the same
machine:
Dec 12 12:39:42 igor kernel: aacraid:ID(0:01:0); Error Event [command:0x2a]
Dec 12 12:39:42 igor kernel: aacraid:ID(0:01:0); Hardware Error [k:0x4,c:0x19,q:0x0]
Dec 12 12:39:42 igor kernel: aacraid:ID(0:01:0); Defect List Error
Can anyone explain what these mean?
What should be done about this?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.