[Voyage-linux] Re: check/repair fs
Raimund Berger
(spam-protected)
Wed Jun 24 01:07:56 HKT 2009
"Robert Rawlins - Think Blue"
<robert.rawlins-EBmHtJ59PSbN/KKgT+RXvNBc4/FLrbF6 at public.gmane.org>
writes:
> Hello Raimund,
>
> Thanks for all your input so far, I greatly appreciate it! I tried to mount
> the partition a second time however it won't let me, just complains that
> it's busy.
>
> voyage:~# mount -t ext2 -r /dev/disk/by-label/ROOT_FS /mnt
> mount: /dev/disk/by-label/ROOT_FS already mounted or /mnt busy
> mount: according to mtab, /dev/disk/by-label/ROOT_FS is mounted on /
Hm. Works here. Not sure what could prevent that on your system.
> I'm also not keen to run the e2fsck just yet as I get a horrible warning at
> the start telling me not to do this on a mounted FS. Is there any way to
> have fsck run on the next reboot before the fs is mounted and make any
> repairs it needs to?
The usual way would be to touch /forcefsck I guess, but I never tried
that with a voyage installation. From what I glance from the init
scripts it should work as well though.
Meaning you'd
$ remountrw
$ /forcefsck
$ reboot
and then the script /etc/rcS.d/S30checkfs.sh should perform a check on
the root file system upon reboot.
Also, if that doesn't help and you really can't manage to get a proper
look at the actual disk file system, there's always the possibility to
draw an image of the raw disk/partition with 'dd' over the
network. That's what I do occasionally to make a full backup of my 512MB
router flash card. Although, admittedly, it'd be quite a fuss with 2GB
over the internet.
Still, it might be a measure of last resort because then you could
inspect the file system locally on your workstation by means of that
image, find out what's wrong and take appropriate action.
Regards, R.
More information about the Voyage-linux
mailing list