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!
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.
Depends on the type of hardware. For hards drives there's smartctl if the drive is S.M.A.R.T. capable. You might be able to run stress tests (e.g. Prime95) to determine if a component is bad. In general, however, the kernel doesn't have any ways of determining hardware health, it just sees the symptoms when things go wrong.
Thanks guys, but my system doesn't have the smartctl command, plus, i already looked into the dmesg, it doesn't show anything wrong...
Funny thing is the problem looks like an I/O error. which is tied to a particular disk section.. but the dmesg has no errors at all on this.
Try booting into single user mode (or off a Knoppix disk, which is the safest way) and run badblocks on your hard drive. if there is a bad sector, it should detect it. Don't run badblocks while your system is fully booted up and file systems are mounted read/write.
You should also fsck the partition in question (fsck /dev/whatever) after finishing the badblocks scan,