e2fsck on attached EXT3 USB drive

[RocketJSquirrel]

I have a Seagate 2TB USB hard drive formatted with EXT3 attached to my RT-N66U.

The router has started showing a warning at boot time that I should run e2fsck more often than "never".

Dec 31 16:00:13 kernel: EXT3-fs: Unrecognized mount option "umask=0000" or missing value
Dec 31 16:00:13 hotplug[639]: USB /dev/sda1(ext3) failed to mount at the first try!
Dec 31 16:00:13 kernel: EXT3-fs: starting recovery.
Dec 31 16:00:16 kernel: kjournald starting. Commit interval 5 seconds
Dec 31 16:00:16 kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
Dec 31 16:00:16 kernel: EXT3 FS on sda1, internal journal
Dec 31 16:00:16 kernel: EXT3-fs: recovery complete.
Dec 31 16:00:16 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Dec 31 16:00:16 hotplug[639]: USB ext3 fs at /dev/sda1 mounted on /tmp/mnt/USB_Storage

But I cannot seem to unmount the drive. umount refuses:

# umount /dev/sda1
umount: can't umount /tmp/mnt/USB_Storage: Device or resource busy

The drive is typically mounted from 2 Win7 PCs as a backup drive. I still get the same complaint from umount even after doing a "net use /delete" on both PCs.

Questions:

1. Should I be running e2fsck periodically on the attached USB drive?

2. If I should be doing so, how can I get the router to unmount the drive so I can run e2fsck?

 

[ryzhov_al]

1. Should I be running e2fsck periodically on the attached USB drive?

Yes, due to...

Dec 31 16:00:13 kernel: EXT3-fs: starting recovery.

2. If I should be doing so, how can I get the router to unmount the drive so I can run e2fsck?

Samba holds files often. You may try to...

$ killall smbd

...before unmount.

 

[shantanugoel]

You can run e2fsck using the pre-mount user script in jffs. It was added specifically for this usecase

 

[ryzhov_al]

You can run e2fsck using the pre-mount user script in jffs. It was added specifically for this usecase

On Merlin's mod only, AFAIK.

 

[RMerlin]

On Merlin's mod only, AFAIK.

Yes, tho I think there might be some Tomato leftover in the original firmware that could do the same thing - I just don't remember the name.

 

[RocketJSquirrel]

Thanks for the advice. I killed the smbd and minidlna processes, and that allowed me to unmount the drive.

But then I got another problem. e2fsck is unhappy.

# e2fsck -v /dev/sda1
e2fsck 1.38 (30-Jun-2005)
USB_Storage has been mounted 120 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Error allocating icount link information: Communication error on send
e2fsck:

This happens every time. Any ideas how to get around this?