schamberlin
Group: Members
Posts: 6
Joined: Jan. 2006 |
|
Posted: Jan. 12 2006,07:11 |
|
Can anyone explain why I always get a "fsck failed, reboot linux" style error on the next boot-up after a power loss?
I'm building a digital picture frame from an old laptop using DSL. I've done an HD install, formatting the disk in a single partition using ext3. My problem is that boot-up after power loss always generates some kind of filesystem error. If the computer is running and you press the power button, it immediately turns off without doing a clean shutdown. On the next bootup, with 100% likelihood I'll see this:
Code Sample | Checking root file system... fsck 1.34-WIP (21-May-2003) /dev/hda1 was not cleanly unmounted, check forced. /dev/hda1: Deleted inode 630431 has zero dtime. FIXED. /dev/hda1: Deleted inode 630431 has zero dtime. FIXED. /dev/hda1: ***** REBOOT LINUX ***** /dev/hda1: 17441/759520 files (0.2% non-contiguous), 103565/1516126 block
fsck failed. Please repair manually and reboot. Please note that the root filesystem is currently mounted read-only. To remount it read-write:
# mount -n -o remount,rw /
|
Then it dumps me to a text-mode command prompt. This is no good, because the whole thing is inside a picture frame and has no keyboard. This happens regardless of what was happening (or not happening) at the time the system was powered off.
I thought the whole point of using ext3 was that it's a journaling filesystem, and is supposed to prevent exactly these kinds of errors? Can you think of any clever ways I can prevent or work-around this?
What about a startup script that does dmesg | grep 'REBOOT LINUX' and automatically reboots the PC if it finds it? Since it always seem to boot up fine on the second boot after a power loss, this might fix the problem without any user intervention.
Thanks!
|