Home / server / Questions / 574548
Accepted
ethrbunny
Asked: 2014-02-11 12:00:12 +0800 CST

Doing a remote fsck - possible?

  • 772

We've been deploying fanless PCs for a research study. Some of these are having HD issues as their OS runs from an SD card. I'm seeing cases where I need to fsck a folder or two.

I've tried using shutdown -rF now but it doesn't seem to be doing the trick. There are notes in the syslog that say stuff was fixed but it doesn't appear to be. Also the order of events in the syslog makes it sound like the OS was fully up when the fsck was done (IE fs was mounted). Certainly not a good thing.

Any suggestions on other ways to fix this without having to do service calls and replace the units?

OS: debian 6.x

Note: I did see this. Gave me the notion for the shutdown command but it doesn't seem to be working properly (or I'm not using it properly).

debian

1 Answers

  1. Best Answer

    Also the order of events in the syslog makes it sound like the OS was fully up when the fsck was done

    The root filesystem usually needs to be mounted to run fsck. The rootfs is usually mounted read-only, and then re-mounted read-write after the fsck is complete. Of course the automatic fsck can't always fix all the problems. Sometimes you need to manually run it to fix things.

    Any suggestions on other ways to fix this without having to do service calls and replace the units?

    Assuming you have SSH acccess to this box, you should be able to stop all services that write to the filesystems, and then remount any filesystems as read-only, while leaving your SSH server running(1). If you can get everything remounted read-only then should be able to safely run a manual fsck.

    • (1) sshd doesn't normally write to the filesystem directly. It writes via syslog, and syslog can be stopped while a system is running.

    And the standard disclaimers, test stopping services and remounting on a box you have physical access to first. If possibly make sure you have someone in place you can call and have power-cycle the box just in case you stop the wrong services and kill your remote access.

    • 5