Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
Distribution: Red Hat Fedora Core 1&2, Knoppix 3.6
fsck error (read from fs resulted in short read)
When booting Fedora Core 2 with kernel 2.6.10, when fsck runs (usually after the mount limit has been reached) errors like this appear.
Error reading block 168236 (Attempt to read block from filesystem resulted in short read) while reading indirect blocks of inode 82369.
after which the init scripts would drop me to single-user mode to run fsck manually. After fsck was run again, the error would occur once or twice (with different numbers).
There was also a short read error during the inode scan. After fsck finishes, I run it again and all appears to be well, until the mount limit is reached and fsck runs again.
I have also noticed that hdc kernel errors have been occuring, but these seem to be occuring independently of the short read error from fsck. Usually when I see the kernel errors I reboot ASAP using Ctrl-Alt-Del.
I have no idea what is causing the error, whether it is a software bug or hardware malfunction.