Re: Ack. Help.
Nope. No go.
A little more information might help, so here goes. It's a custom built 2.4.21
kernel, with ext3 support built in. Nothing has changed OS wise (AFAIK) that
would cause this problem.
Just before trying to launch into fsck in the bootup sequence, it gives:
EXT3-fs: invalid journal inode.
When I try to fsck the drive manually, it immediately gives the illegal block
number error.
Maybe it's time for a rebuild anyway...
-Matt
On Friday 09 January 2004 12:32, Rus Foster wrote:
> On Fri, 9 Jan 2004, Matthew Bardeen wrote:
> > After travelling with my laptop (safely in suspended mode), I turn it on
> > only to find the following error when it tries to fsck the drive..
> >
> > fsck.ext3: Illegal block number while checking ext3 journal for /dev/hda2
> >
> > an 'ls -al' of the journal file reveals the following information:
> > b--sr-S--x 26979 1970433896 1953523829 44, 116 Mar 25 1995 .journal
>
> Try booting it in single user read only. Then try a remount of the
> filesystem which should replay the journal. See if that helps
>
> Rgds
>
> rus
Reply to: