dc: How can I let e2fsck repair a (mounted) SSD (or USB) drive?

[XIII]

The Disk Check script (dc) in amtm reported that the SSD attached to my router was not clean at boot, so I tried to use e2fsck to repair it. However, that refused to do its job because the SSD was mounted and then unmounting failed because the drive was "busy" (all the time). In the end I turned off my router and attached the SSD to a PC running Ubuntu to repair it, but that is a rather clumsy way too achieve this.

What's the proper way (on the router itself) to do this (next time)?

 

[ColinTaylor]

The Disk Check will try to fix minor errors automatically. What did the log show?

In most other cases, if the errors are significant the router will refuse to mount the drive.

If it is still mounted, even with errors I would:
1. Disable JFFS custom scripts and configs in the webUI and reboot the router.
2. After the reboot, eject the USB drive through the webUI.
3. Repair the damaged filesystem using the relevant commands.

 

[XIII]

What did the log show?

This:

Probing 'ext4' on device /dev/sda1
Running disk check with command 'e2fsck -p' on /dev/sda1
ssd: recovering journal
ssd contains a file system with errors, check forced.
ssd: Unattached inode 8130364


ssd: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
       (i.e., without -a or -p options)