USB Drive has mount errors

[mstrom62]

Hello,

I have several Routers and put 8GB USB sticks in them to load Optware etc. I notice when I reboot the router that many time I end up with an error saying one or more folders did not dismount cleanly and it won't mount properly. Any suggestions on how to make sure my USB stick stays mounted properly even if the router is power cycled?

thanks in advance.

Mike

 

[ILMostro]

Yup. Same problem here; unfortunately, no responses/advice

 

[john9527]

For the ARM based routers (AC56U and above) and if these devices are plugged into the USB3 port, make sure that under Wireless > Professional for 2.4GHz that the Reduce USB3 interference is set to Disabled.

 

[ILMostro]

Same result here even after following your advice, @john9527 .

kernel: EXT2-fs (sda5): warning: mounting unchecked fs, running e2fsck is recommended
kernel: EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended

Furthermore, the usb-related scripts are useless as they're always disregarded, even though they were executed.

I did notice some interesting errors:

syslog: module ledtrig-usbdev not found in modules.dep
Jul 31 19:00:25 syslog: module leds-usb not found in modules.dep
Jan  9 20:10:08 kernel: csw_retry 100
Jan  9 20:10:09 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Jan  9 20:10:09 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Jan  9 20:10:09 kernel: usb usb1: No SuperSpeed endpoint companion for config 1  interface 0 altsetting 0 ep 129: using minimum values
Jan  9 20:10:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Jan  9 20:10:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Jan  9 20:10:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Jan  9 20:10:09 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Jan  9 20:10:09 kernel: xhci_hcd 0000:00:0c.0: disable burst on ep 1
Jan  9 20:10:09 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst
Jan  9 20:10:09 kernel: xhci_hcd 0000:00:0c.0: disable burst on ep 2
Jan  9 20:10:09 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst

The weird thing is `lsmod` doesn't show that "xhci_hcd" is used. Then there's also something called "scsi_wait_scan", which is also unused; I wonder if the latter has anything to do w/scheduling fsck during bootup, which always fails. :-/

# lsmod
Module  Size  Used by  Tainted: P  
sr_mod  10842  0
cdrom  30901  1 sr_mod
cdc_mbim  3129  0
qmi_wwan  5780  0
cdc_wdm  7248  2 cdc_mbim,qmi_wwan
cdc_ncm  8750  1 cdc_mbim
rndis_host  4936  0
cdc_ether  3187  1 rndis_host
asix  10832  0
usbnet  11161  6 cdc_mbim,qmi_wwan,cdc_ncm,rndis_host,cdc_ether,asix
mii  3367  2 asix,usbnet
usblp  10317  0
ohci_hcd  17918  0
ehci_hcd  31565  0
xhci_hcd  51124  0
thfsplus  82029  0
tntfs  443780  0
tfat  174489  0
ext2  52768  1
ext4  221662  2
jbd2  48989  1 ext4
crc16  1007  1 ext4
ext3  106401  0
jbd  42367  1 ext3
mbcache  4599  3 ext2,ext4,ext3
usb_storage  34290  3
sg  19823  0
sd_mod  21983  4
scsi_wait_scan  416  0
scsi_mod  108730  4 sr_mod,usb_storage,sg,sd_mod
usbcore  101794 14 cdc_mbim,qmi_wwan,cdc_wdm,cdc_ncm,rndis_host,cdc_ether,asix,usbnet,usblp,ohci_hcd,ehci_hcd,xhci_hcd,usb_storage
nf_nat_sip  5031  0
nf_conntrack_sip  15713  1 nf_nat_sip
nf_nat_h323  4761  0
nf_conntrack_h323  33807  1 nf_nat_h323
nf_nat_rtsp  3202  0
nf_conntrack_rtsp  4067  1 nf_nat_rtsp
nf_nat_ftp  1144  0
nf_conntrack_ftp  4909  1 nf_nat_ftp
ip6table_mangle  934  0
ip6t_LOG  4494  0
ip6table_filter  750  1
jffs2  91266  1
zlib_deflate  19489  1 jffs2
nf_nat_pptp  1602  0
nf_conntrack_pptp  3355  1 nf_nat_pptp
nf_nat_proto_gre  887  1 nf_nat_pptp
nf_conntrack_proto_gre  3296  1 nf_conntrack_pptp
wl  3978047  0
igs  11887  1 wl
emf  15049  2 wl,igs
et  61221  0
ctf  20227  0

 

[john9527]

@ILMostro - you didn't say what size drive you have, but if it's a big drive, remember this is a limited CPU and can take a long time for the disk check.

Two things you can try....
- Manually running the disk check from the index page - click on USB drive icon - Disk Utility
- Disable the auto fsck based on mount count with (substitute the mount point as needed).

tune2fs -c 0 /dev/sda1

Those USB errors are normal....it's just the kernel trying to determine what type of USB hardware is attached.

 

[ILMostro]

It's a 16GB usb3.0 drive. The real issue arises when the usb drive is, presumably, mounted too late for certain scripts and/or configuration options to take effect. This is less evident with the entware setup, as it seems to be working correctly after it mounts.