/serval-var (and maybe others) can get mounted read-only

[gardners]

Boot scripts should detect this, and (re)run fsck.ext3 on the file system to fix it, and maybe report an error if it can't be fixed.

[gardners]

... can also happen due to error some time after boot, where it remounts read-only. we should detect and try to fix it, or at least show a "memory stick faulty. please replace"

[gardners]

The re-mount read-only problem has been seen due to USB bus errors causing the kernel to get upset and switch the mount to read-only to protect against corruption.

LBARD has been extended to detect when this happens, and to try to fix it, and if that doesn't work, to mount a temporary RAM disk, so that at least basic operations can continue without USB.