ClearOS - how to avoid getting stuck at a fsck message at boot?
- by Scott Szretter
I have had this happen a couple times - I have a ClearOS Enterprise 5.2 box, and due to a power outage or similar, it ends up showing an error at boot and saying that fsck needs to be run (I think it said with (or without?) the -a parameter).
The problem is, I need this box to be headless, at a remote location (miles away)!
SO, I need to come up with a solution on how to either have it automatically repair itself, without someone to be present with a monitor and keyboard.
Another possibility is to simply avoid the issue all together - maybe there is something that can be changed so it's very unlikely to happen (I am unable to avoid the power outage of course - at least not practically).
Finally, maybe it can be boot off a read only media (cd) or file system or similar? At least the base OS, so that it would always at least boot with enough configuration that might allow remote access, or basic connectivity?