[arch-general] Forced to run fsck manually on unattended system

[edd_smith]

Hi,

I run a series of remote boxes running Arch. These boxes are unnattended and
are very difficult to access. Due to the nature of their power supply they
are often powered down without any warning. A UPS is not an option.

I have noticed that over time the boxes are showing file system errors and
getting stuck during the boot phase requiring manual intervention (Either
press Control-D to continue - resulting in failure or log in to the start up
shell using the root password and run fsck manually). I simply answer yes to
every prompt from fsck and the errors are resolved, the box reboots and runs
fine.

I need to be able to force an 'fsck -y'  type command at every boot as
visiting these boxes manually isn't an option. I have already moved the
partitions to ext2 as this seemed to show a mild improvement and also set 0
1 flags in /etc/fstab but still I'm seeing the freezing on boot.

First of all should I be re-partitioning my drives to something which can
handle these kinds of sudden power outages or removing the swap space or
something?

Secondly can I have arch run a completely unprompted startup whereby fsck
will do its best to repair the system without requiring intervention - for
me a blank disk is no worse than a frozen system.

Thanks in advance,

Edward Smith



--
View this message in context: http://archlinux.2023198.n4.nabble.com/Forced-to-run-fsck-manually-on-unattended-system-tp4684861.html
Sent from the arch general mailing list archive at Nabble.com.