EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

[jayazusa]

I have SD-DVR80 that is receiving the following error on bootup.


EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

I have tried running a e2fsck -y /dev/hda7 it fails

I would appriciate any help possible here. Does this mean the drive is failing and if so since I have a dual drive system what drive is failing the master or slave? Both drives are brand new Samsung SpinPoint 160 GB.

Thanks in advance,

Jay

Followup this is what I get after I run e2fsck -y /dev/hda7


TivoMaster:/var/tmp$ e2fsck -y /dev/hda7
e2fsck 1.06, 7-Oct-96 for EXT2 FS 0.5b, 95/08/09
e2fsck: Bad magic number in super-block while trying to open /dev/hda7

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

[Jamie]

I have tried running a e2fsck -y /dev/hda7 it failsAre you sure /dev/hda7 is your root partition (not hda4)? What does bootpage -p /dev/hda tell you?

[brywalker]

Interesting. I have the same error in my kernel log, but everything works fine. This is on my HDVR-2 with 4.01b.

[Jamie]

Interesting. I have the same error in my kernel log, but everything works fine. This is on my HDVR-2 with 4.01b.That error indicates your tivo was shutdown uncleanly (is there any other kind of shutdown?) while the root file system was mounted rw. It's a good idea to run e2fsck on the root file system when that happens. Here's (http://www.dealdatabase.com/forum/showthread.php?p=202641#post202641) another thread where it is discussed.

[brywalker]

Excellent info Jamie! Just ran it and it fixed the 1.1% that was messed up.

Forgive my ignorance, but is this somewhat the equivalence to a FATxx chkdisk?

[7.1]

Excellent info Jamie! Just ran it and it fixed the 1.1% that was messed up.

Forgive my ignorance, but is this somewhat the equivalence to a FATxx chkdisk?Roughly. If a system crashes or is shutdown while a file system is being modified, it's possible that the metadata in the file system is left in an inconsistent state. For example, a block might be allocated to a file, but also on the free list, or left allocated to two files, or in limbo: neither allocated or free. Newer file systems (ext3, reiser, ntfs, MFS, ...) have transaction logs that are used to prevent this sort of problem. vfat and ext2 do not, so they rely on separate programs to check and repair file system inconsistencies.

[jayazusa]

Are you sure /dev/hda7 is your root partition (not hda4)? What does bootpage -p /dev/hda tell you?

My bad I did assume my boot page was hda7 but it truely is hda4
I ran this at my prompt:

TivoMaster:/var/tmp$ bootpage -p /dev/hda
it returns:

root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false
so than I ran:

e2fsck -y /dev/hda4
and it returned:

Free inodes count wrong (31111, counted=31112). FIXED...

1656/32768 files (1.2% non-contiguous), 97198/131072 blocks

I guess thais is what hapens if you follow guides without understanding all the commands. I do now understand bootpage and will add that to my upgrade process.

Jamie, is it recomended to run the e2fsck on bootup in your rc.sysinit.author after a long wait? or on some type of cron job?

Thanks again,

Jay

[Jamie]

Jamie, is it recomended to run the e2fsck on bootup in your rc.sysinit.author after a long wait? or on some type of cron job?If your root file system is always mounted readonly, there is little need to run e2fsck at bootup. But, otherwise, it's a good idea. Just make sure it is mounted readonly when running e2fsck.