Hello all,

By default, KnoppMyth chooses EXT3 as the filesystem for the root partition - seems like a good idea, so I went with it. But when the system does lock up (I've been trying to get rivatv installed & working), and I do a hard reboot, fsck runs and stops at a prompt that tells me to hit Ctrl-D to reboot. I thought that using a journaling fs like EXT3 meant that fsck would NOT run after a crash, which would allow for a clean boot back into MythTV after a power outage, for example.

Am I all wet about this? Or is something wrong with my setup?

Thanks in advance,

Eric

well journaling file systems at this point do not stop 1000% of corruption, we'll have to wait for rieserfs4 for that. What it usually does is prevent corruption and make fsck run faster at boot, but with a particularly bad freeze you can cause problems.

What you need to do is when it gives you that message run fsck manually like this.

fscd /dev/hda

assuming of course that your hard drive is the primary master on an ide system.

It will run fsck and ask you if you want to fix a ton of stuff. just hit the y key a bunch and it should repair everything.

once it's done reboot.