running fsck after crash sometimes requires human intervention

Bug #1212020 reported by Florin Andrei on 2013-08-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Raspbian
Undecided
Unassigned

Bug Description

Sometimes when fsck is run with errors after a crash or hard reset, it requires user input.

The Raspberry Pi is used a lot as a pseudo-embedded controller. Such a thing must be able to handle a crash on its own, and must not require any human intervention.

Currently, the only way to achieve headless unclean fsck is by hacking the OS core scripts, which is ugly, error-prone, and changes could be over-written during an upgrade. Examples:

http://raspberrypi.stackexchange.com/questions/7853/how-can-i-harden-raspbian-to-boot-unattended-after-unexpected-shutdown

http://raspberrypi.stackexchange.com/questions/5002/make-fsck-run-without-intervention-after-non-clean-shutdown

Please incorporate a change in the OS to allow setting a flag in a config file, that will change the behavior of fsck to run without user intervention.

peter green (plugwash) wrote :

The files mentioned in your links are conffiles so they shouldn't get overwritten on updates without asking. For the first one the change is to /etc/default/rcS which is definately a configuration file so your first request is invalid. For the second request I can see the argument that despite being marked as a conffile it's not really a configuration file but I can also see the argument that enabling dangerous fsck options should not be done lightly.

In any case none of this is Pi or raspbian specific and as such i'm not messing with it on a raspbian level, that would just confuse people. If you really think it should be changed take it up with debian (but don't be surprised if you get a response like the one I gave above).

Changed in raspbian:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers