Error When Booting: Resize Inode Not Valid

Error When Booting: Resize Inode Not Valid

[Dan Berger]

Hello. I have recently switched to Linux to prevent any big errors...
but I guess I just have bad luck :)

Distro: Fedora Core 3
Kernel: 2.6.10-1.FC3_770
File system: ext3
Mobo: Gigabyte GA7VAXP+

This morning I went to reboot my machine normally after an 8 day
uptime. At boot, when it checked the root partition's integrity, I got
the error "Resize inode not valid" and I was dropped to the repair fs
console.

I ran fsck.ext3 numerous times, always answering yes to recreating the
resize inode... but to no avail. I even tried doing this from FC3's
rescue CD.

Interestingly enough, I can mount and unmount root and the rest of the
partitions when in the rescue CD.

I should mention that the last 2 bytes of the 512 byte MBR is aa 55
and the PBR of my root partition is entirely null. There is no aa 55
at the end.

I also checked out /var/log/dmesg and /var/log/messages and they both
ave nothing out of the ordinary.

Here is the Grub conf:
default=0
timeout=5
hiddenmenu
title Fedora Core (2.6.10-1.770_FC3)
root (hd0,0)
kernel /vmlinuz-2.6.10-1.770_FC3 ro root=LABEL=/1
initrd /initrd-2.6.10-1.770_FC3.img

Any light that you can shed on this troubling subject would be highly
appreciated,

Respectfully yours,

Dan J. Berger

Re: Error When Booting: Resize Inode Not Valid

[Theodore Ts'o]

On Tue, Apr 12, 2005 at 08:17:46AM -0400, Dan Berger wrote:
> Hello. I have recently switched to Linux to prevent any big errors...
> but I guess I just have bad luck :)
> 
> Distro: Fedora Core 3
> Kernel: 2.6.10-1.FC3_770
> File system: ext3
> Mobo: Gigabyte GA7VAXP+
> 
> This morning I went to reboot my machine normally after an 8 day
> uptime. At boot, when it checked the root partition's integrity, I got
> the error "Resize inode not valid" and I was dropped to the repair fs
> console.
> 
> I ran fsck.ext3 numerous times, always answering yes to recreating the
> resize inode... but to no avail. I even tried doing this from FC3's
> rescue CD.

It looks like there is a bug in FC3's e2fsck program which is failing
to fix the filesystem corruption.  (FC3's e2fsck had resize2fs support
more-or-less hacked in, and it didn't support big endian systems, and
it had a whole host of other problems.)

I would recommend upgrading to the latest version of e2fsck (1.37)
which should be able to fix it.  If not, please see the REPORTING BUGS
section of the e2fsck man page to see the sort of information I would
need to see in order to fix it.

Unfortunately, FC3 doesn't have a prebuilt version of the latest
e2fspros, so you would have to build it yourself.  

						- Ted

Re: Error When Booting: Resize Inode Not Valid

[Dan Berger]

Ted, thank you so much for responding. I sincerely appreciate it.

I went ahead and upgraded my e2fsprogs package (1.37 is actually
available on the fc3 dev repo) and reran fsck.ext3. I once again
answered yes to the question: "Recreate resize inode?"

Unfortunately, on the next reboot, I was once again given the same
error "Resize inode not valid" and dropped to the repair filesystem.

I hope you or someone else can shed some more light on this. I really
believe this is something that can be fixed without any extraordinary
measures (IE start over)

Thanks again for your kind and prompt response

Sincerely,

Dan Berger

On Apr 12, 2005 10:07 AM, Theodore Ts'o <tytso@mit.edu> wrote:
> On Tue, Apr 12, 2005 at 08:17:46AM -0400, Dan Berger wrote:
> > Hello. I have recently switched to Linux to prevent any big errors...
> > but I guess I just have bad luck :)
> >
> > Distro: Fedora Core 3
> > Kernel: 2.6.10-1.FC3_770
> > File system: ext3
> > Mobo: Gigabyte GA7VAXP+
> >
> > This morning I went to reboot my machine normally after an 8 day
> > uptime. At boot, when it checked the root partition's integrity, I got
> > the error "Resize inode not valid" and I was dropped to the repair fs
> > console.
> >
> > I ran fsck.ext3 numerous times, always answering yes to recreating the
> > resize inode... but to no avail. I even tried doing this from FC3's
> > rescue CD.
> 
> It looks like there is a bug in FC3's e2fsck program which is failing
> to fix the filesystem corruption.  (FC3's e2fsck had resize2fs support
> more-or-less hacked in, and it didn't support big endian systems, and
> it had a whole host of other problems.)
> 
> I would recommend upgrading to the latest version of e2fsck (1.37)
> which should be able to fix it.  If not, please see the REPORTING BUGS
> section of the e2fsck man page to see the sort of information I would
> need to see in order to fix it.
> 
> Unfortunately, FC3 doesn't have a prebuilt version of the latest
> e2fspros, so you would have to build it yourself.
> 
>                                                 - Ted
>