EXT2-fs in Kernel Log

[Soapm]

This is the only entry I keep getting in my kernal log. Do I need to do anything? Should I run this commane, e2fsck and if so, what options?

Sep 28 02:25:58 (none) kernel: EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
Sep 28 02:43:37 (none) kernel: EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

[PlainBill]

That is normal when mounting /var.

PlainBill

[Jamie]

That is normal when mounting /var.

PlainBillActually, no. The startup scripts automatically run e2fsck on /var.

It's normal when mounting a "dirty" /. The startup scripts do not normally run e2fsck on /, since on an unhacked tivo, it is readonly and should never be dirty.

Something like e2fsck -p /dev/hda4 ought to do it, but use the root device specified in your bootpage in place of /dev/hda4. Make sure root is mounted readonly before you run e2fsck on it.

[Narf54321]

Actually, I just ran into a similar issue myself. A brand-new virgin image on a new drive. I believe it is more to do with the current date on the PC (MFSLive CD) being over 180-days than the Tivo's system software filedates.

I'm not convinced its a real problem.

[Jamie]

Actually, I just ran into a similar issue myself. A brand-new virgin image on a new drive. I believe it is more to do with the current date on the PC (MFSLive CD) being over 180-days than the Tivo's system software filedates.

I'm not convinced its a real problem.e2fsck gives a different message for that. The above quoted message specifically means the file system is dirty, not that it just hasn't had e2fsck run for a while.

It's not really a problem, but dirty e2fsck file systems can have space lost to orphan inodes.

[Soapm]

Something like e2fsck -p /dev/hda4 ought to do it, but use the root device specified in your bootpage in place of /dev/hda4. Make sure root is mounted readonly before you run e2fsck on it.

I ran this command, is this good? What exactly did it do?

FamRoom-bash# e2fsck -p /dev/hda4
/dev/hda4 is mounted. Do you really want to continue (y/n)? yes

/dev/hda4 has reached maximal mount count, check forced.
Deleted inode 10254 has zero dtime.
Set dtime? yes

Deleted inode 10258 has zero dtime.
Set dtime? yes

Deleted inode 10259 has zero dtime.
Set dtime? yes

Deleted inode 10260 has zero dtime.
Set dtime? yes

Deleted inode 16427 has zero dtime.
Set dtime? yes

Deleted inode 16428 has zero dtime.
Set dtime? yes

Deleted inode 16431 has zero dtime.
Set dtime? yes

Deleted inode 18479 has zero dtime.
Set dtime? yes

Deleted inode 18488 has zero dtime.
Set dtime? yes

Deleted inode 20507 has zero dtime.
Set dtime? yes

Deleted inode 20509 has zero dtime.
Set dtime? yes

Deleted inode 20510 has zero dtime.
Set dtime? yes

Deleted inode 20571 has zero dtime.
Set dtime? yes

Deleted inode 28696 has zero dtime.
Set dtime? yes

Deleted inode 28701 has zero dtime.
Set dtime? yes

Deleted inode 34834 has zero dtime.
Set dtime? yes

Deleted inode 36921 has zero dtime.
Set dtime? yes

Deleted inode 36923 has zero dtime.
Set dtime? yes

Deleted inode 45057 has zero dtime.
Set dtime? yes

Deleted inode 45058 has zero dtime.
Set dtime? yes

Deleted inode 47105 has zero dtime.
Set dtime? yes

Deleted inode 47106 has zero dtime.
Set dtime? yes

Deleted inode 63513 has zero dtime.
Set dtime? yes

Deleted inode 63514 has zero dtime.
Set dtime? yes

Fix summary information? yes

/dev/hda4: 3280/65536 files (0.9% non-contiguous), 78392/262144 blocks