Share your knowledge at the LQ Wiki.
Go Back > Forums > Linux Forums > Linux - Distributions > Red Hat
User Name
Red Hat This forum is for the discussion of Red Hat Linux.


  Search this Thread
Old 08-20-2004, 09:45 AM   #1
LQ Newbie
Registered: Aug 2004
Posts: 3

Rep: Reputation: 0
ext3-fs warning device ext3_clear_journal


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_abort called.
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!!!
Old 08-20-2004, 06:08 PM   #2
LQ Newbie
Registered: Aug 2004
Posts: 3

Original Poster
Rep: Reputation: 0
Old 08-24-2004, 10:35 AM   #3
LQ Newbie
Registered: Aug 2004
Posts: 3

Original Poster
Rep: Reputation: 0
WTF? No one can help?
Old 10-31-2004, 03:26 PM   #4
Registered: Feb 2004
Distribution: Debian Jessie
Posts: 259

Rep: Reputation: 32
I had a problem with my ext3 journels once... fsck blew them away when running a disk check.

I used tune2fs to re-create the journal so I would imagine you could use tune2fs to remove then re-create your corrupt journal.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Ext3-fs error (device hda1) in start-transaction kt8993 Linux - General 0 02-05-2005 12:09 PM
Ext3 warnings on a loop device andreseso Linux - Hardware 2 12-09-2004 10:47 PM
slave-device-name usage warning when running xterm spevack Slackware 2 04-28-2004 07:04 PM
XMMS problem : ** WARNING **: oss_open(): Failed to open audio device (/dev/dsp): sureshrk19 Slackware 4 04-01-2004 10:17 PM
lilo:***warning :device exceed 1024*** niton Linux - Newbie 2 07-17-2002 10:52 AM > Forums > Linux Forums > Linux - Distributions > Red Hat

All times are GMT -5. The time now is 06:51 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration