Other Help Topics :: fsck fails, any way to automate

Basically the box looks good, thanks for all the help so far. Naturally another snag. These box's won't have monitors, keyboards, etc. as they will be displaying data on a monitor via a flash page.

So when they need to move, etc. they just power down, the filesystem complains on re-start, runs the fsck, then drops out and say's you must fix manually (which they won't be able to do).

The solution it seems, will be to put the OS and most of the stuff into a ramdrive. There is a text file that changes with data, so that will have to stay on the disk, but the OS can be put into the ram drive (which I have never done).

Does this sound like something possible? I know the live boot works that way, or is there a way to simply force x,y,z check/repair without a keyboard attached?

Thanks as always....
lr

Quote

So when they need to move, etc. they just power down

I still don't understand why so many people do this. It is a bad idea for anything other than embedded read-only devices.

You might try using the toram boot option. This loads the KNOPPIX file into ram and unmounts the boot device (if it's not still in use). This still won't allow for a simple poweroff, though, if you need to save data.
I can't think of any way to safely shut down a desktop system that way.

Acpid. It is in recent DSL versions, and you can bind an action to power events, aka pressing the power button (shortly, not the 5-sec instant kill) for a clean shutdown.

original here.