Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
A few days ago a user reported strange ticking noises coming from the hard disk while the whole system was idle but unresponsive. It was resetted and upon reboot the usual fsck check after an unclean unmount failed and gave me a minimal console with / mounted as read-only. I prompted me to run fsck manually because it had found errors.
All I did was type
and answer yes to everything.
After that few small files ended up linked to /lost+found. (Is there a log fsck leaves behind in those cases?)
The ticking noises are gone, all data seems to be intact, a few following fsck checks have been succesful, BUT if I try to cat any of the files that appear in the /lost+found directory, the disk starts the ticking noises again and everything seems a bit unresponsive.
I managed to reboot (shutdown -r now) in that moment to stop the ticking.
The last time I had bad sectors was in a 42 MB disk running DOS 5 and Windows 3.1 so I'm not familiar with this topic on Linux.
This an ext4 partition and it is the only partition (no separate /boot or /home).
I heard about smartctl (which is not installed on this system yet), but I fear it will try to read those files in /lost+found and die or increase the damage.
Is there a way to check for bad sectors? Or to mark them so they don't get used anymore? Should I forget about the files in /lost+found and continue using the disk as if nothing had happened?
smartctrl/smartmontools does not read the storage area of the drive at all. It reads the drives internal error log.
Get the vendors drive test software. It will test the disk in a way the manufacturer approves of (it may need to destroy all the data in he process). The manufacturer will take the result as proof of a warranty claim, if the drive is still in warranty.
If the drive has bad sectors that the operating system can detect, its because its run out of spares.
Drives are made with spare sectors, which are swapped in throughout the useful life of the drive as original sectors show signs of failing. When all spares are used, the drive is end of life.