On Fri, 9 Jan 2004, Matthew Bardeen wrote: > 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.
For a last ditch attempt you could try deleteing the .journal. Rus -- e: [EMAIL PROTECTED] t: 1-888-327-6330 www.jvds.com - Root on your own box www.vpscolo.com - Your next hosting company -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
