I like to run a system unattended for every day 'kiosk' use.
However, the system may be powered off anytime without someone doing a proper shutdown before. By default, Ubuntu is not expected to be shut down by power loss. After rebooting after a power loss, fsck may be run to check the file system, and fsck may tell the system to reboot after it has finished. So even if no configuration data gets corrupted, the machine may not boot well after power loss. So I tested some workarounds:
1) change the root mount fsck priority to
0 (last field in
fstab root entry)
that prevents running
fsck after every power loss. However, the the system may boot with root mounted read-only then, which is not expected by many services and results in a console login prompt instead the graphical login.
errors=continue. This gives a bad feeling that further data loss may occur by an incosistent filesystem. However, with
fsck enabled again, it should increase the system's boot propability after power loss. So I dropped 1).
3) Reconfigure grub2 to use a normal default option timeout after a failed boot. For that, i've added
Hoever, it is hard to know if these hacks make the system power loss proof. Any ideas? Any more one can do?