Red HatThis forum is for the discussion of Red Hat 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.
I'm having trouble booting my RH9.0 Linux. What happened was, my mounted secondary HDD suddenly failed to response, so I tried to shutdown my Linux. It failed and showed no response, so I just press the RESET button.
When I tried booting again, I get a problem SIMILIAR to the following :
kjournald starting. Commit interval 5 seconds
EXT3-fs warning (device hdb1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
EXT3-fs warning (device hdb1): ext3_clear_journal_err: Marking fs in need of filesystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on hdb1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
attempt to access beyond end of device
hdb1: rw=0, want=274989144, limit=268413957
EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=17187087, block=34373642
Aborting journal on device hdb1.
EXT3-fs abort (device hdb1): ext3_journal_start: Detected aborted journal
Remounting filesystem read-only
Now, I can't boot into my Linux because of this crap. Anyone know a fix to this? I'm terribly desperate to fix this cause my Linux HDD has my thesis project (I did back some stuff up but those aren't the most recent ones!) and many other stuff in it!!!