Menu
What's new
By:
Filters Better Search

Bad File Descriptor

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

skeal

skeal

Part of the Furniture
Can anyone tell me what this means. I have added the line:
Code: 
umount /tmp/mnt/EXT2
To the unmount script in /jffs. I get this error repeated for about 35 times:
Code: 
Jan 29 12:42:45 syslog: USB partition unmounted from /tmp/mnt/EXT2 fail. (return -1, Bad file descriptor)
Often just before power is interrupted during the reboot or the first line after the power cycle I get this line:
Code: 
Jan 29 12:43:20 syslog: USB partition busy - will unmount ASAP from /tmp/mnt/EXT2
If I leave out the umount command, in the unmount script, the usb gets forced to unmout, and shows that fact in the AMTM disk check log. Any light shed on this would be great, thanks in advance guys!

EDIT: When the umount command is used as stated above, I in fact show a clean unmount in AMTM disk check log. But it takes about 35 tries and about 45 seconds added to the reboot process. The progress meter goes to 100 percent and then hangs for 45 seconds, while it tries to unmount.
 
Last edited:
My guess is that an attempt is made to gracefully unmount but a process is holding on to files. The ASAP unmount is not graceful. That being said, I have seen discussion where a lot of thought had been put into the shutdown of the software likely running on the USB drive, so I don't know.

I'm glad I chose ext4 with journaling on. I am also using the AMTM disk check script.

This happened when I last upgraded the firmware:
Code: 
Jan 27 11:07:19 router ejusb[8667]: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:19 router rc_service: ejusb 8667:notify_rc stop_nasapps
Jan 27 11:07:19 router avahi-daemon[5949]: Files changed, reloading.
Jan 27 11:07:19 router avahi-daemon[5949]: Loading service file /tmp/avahi/services/mt-daap.service.
Jan 27 11:07:19 router iTunes: daemon is stopped
Jan 27 11:07:19 router FTP_Server: daemon is stopped
Jan 27 11:07:19 router Samba_Server: smb daemon is stopped
Jan 27 11:07:19 router avahi-daemon[5949]: Got SIGTERM, quitting.
Jan 27 11:07:19 router avahi-daemon[5949]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.50.1.
Jan 27 11:07:19 router avahi-daemon[5949]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Jan 27 11:07:19 router avahi-daemon[5949]: avahi-daemon 0.7 exiting.
Jan 27 11:07:19 router Timemachine: daemon is stopped
Jan 27 11:07:19 router avahi-daemon[8681]: Found user 'nobody' (UID 65534) and group 'nobody' (GID 65534).
Jan 27 11:07:19 router avahi-daemon[8681]: Successfully dropped root privileges.
Jan 27 11:07:19 router avahi-daemon[8681]: avahi-daemon 0.7 starting up.
Jan 27 11:07:19 router avahi-daemon[8681]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jan 27 11:07:19 router avahi-daemon[8681]: No service file found in /tmp/avahi/services.
Jan 27 11:07:19 router avahi-daemon[8681]: Loading new alias name RT-AX88U.
Jan 27 11:07:19 router avahi-daemon[8681]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.50.1.
Jan 27 11:07:19 router avahi-daemon[8681]: New relevant interface br0.IPv4 for mDNS.
Jan 27 11:07:19 router avahi-daemon[8681]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Jan 27 11:07:19 router avahi-daemon[8681]: New relevant interface lo.IPv4 for mDNS.
Jan 27 11:07:19 router avahi-daemon[8681]: Network interface enumeration completed.
Jan 27 11:07:19 router avahi-daemon[8681]: Registering new address record for 192.168.50.1 on br0.IPv4.
Jan 27 11:07:19 router avahi-daemon[8681]: Registering new address record for 127.0.0.1 on lo.IPv4.
Jan 27 11:07:20 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:20 router avahi-daemon[8681]: Server startup complete. Host name is RT-AX88U-F098.local. Local service cookie is 3659585021.
Jan 27 11:07:20 router avahi-daemon[8681]: Alias name "RT-AX88U" successfully established.
Jan 27 11:07:21 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:22 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:23 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:24 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:25 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:26 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:27 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:28 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:29 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:30 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:31 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:32 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:33 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:34 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:35 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:36 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:37 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:38 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:39 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:40 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:41 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:42 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:43 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:44 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:45 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:46 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:47 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:48 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:49 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:50 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:51 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:52 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:53 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:54 router ejusb: USB partition busy - will unmount ASAP from /tmp/mnt/SamsungT5
Jan 27 11:07:54 router rc_service: httpd 5990:notify_rc stop_upgrade
Jan 27 11:07:54 router usb: USB is ejected
Jan 27 11:07:54 router nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Jan 27 11:07:55 router kernel: IDPfw: Exit IDPfw
Jan 27 11:07:55 router kernel: mod epilog takes 0 jiffies
Jan 27 11:07:55 router kernel: IDPfw: Exit IDPfw
Jan 27 11:07:55 router kernel: Exit chrdev /dev/idpfw with major 191
Jan 27 11:07:55 router kernel: Exit chrdev /dev/idp with major 190
Jan 27 11:07:55 router kernel: Cpuidle Host Clock divider is enabled
Jan 27 11:07:55 router BWDPI: re-enable fc
Jan 27 11:07:57 router networkmap: Error unlocking 0: 9 Bad file descriptor
Jan 27 11:07:57 router avahi-daemon[8681]: Got SIGTERM, quitting.
Jan 27 11:07:57 router avahi-daemon[8681]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.50.1.
Jan 27 11:07:57 router avahi-daemon[8681]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Jan 27 11:07:57 router avahi-daemon[8681]: avahi-daemon 0.7 exiting.
Jan 27 11:07:57 router kernel: klogd: exiting
 
EmeraldDeer said:
My guess is that an attempt is made to gracefully unmount but a process is holding on to files. The ASAP unmount is not graceful. That being said, I have seen discussion where a lot of thought had been put into the shutdown of the software likely running on the USB drive, so I don't know.

I'm glad I chose ext4 with journaling on. I am also using the AMTM disk check script.

This happened when I last upgraded the firmware:
Code: 
Jan 27 11:07:19 router ejusb[8667]: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:19 router rc_service: ejusb 8667:notify_rc stop_nasapps
Jan 27 11:07:19 router avahi-daemon[5949]: Files changed, reloading.
Jan 27 11:07:19 router avahi-daemon[5949]: Loading service file /tmp/avahi/services/mt-daap.service.
Jan 27 11:07:19 router iTunes: daemon is stopped
Jan 27 11:07:19 router FTP_Server: daemon is stopped
Jan 27 11:07:19 router Samba_Server: smb daemon is stopped
Jan 27 11:07:19 router avahi-daemon[5949]: Got SIGTERM, quitting.
Jan 27 11:07:19 router avahi-daemon[5949]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.50.1.
Jan 27 11:07:19 router avahi-daemon[5949]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Jan 27 11:07:19 router avahi-daemon[5949]: avahi-daemon 0.7 exiting.
Jan 27 11:07:19 router Timemachine: daemon is stopped
Jan 27 11:07:19 router avahi-daemon[8681]: Found user 'nobody' (UID 65534) and group 'nobody' (GID 65534).
Jan 27 11:07:19 router avahi-daemon[8681]: Successfully dropped root privileges.
Jan 27 11:07:19 router avahi-daemon[8681]: avahi-daemon 0.7 starting up.
Jan 27 11:07:19 router avahi-daemon[8681]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Jan 27 11:07:19 router avahi-daemon[8681]: No service file found in /tmp/avahi/services.
Jan 27 11:07:19 router avahi-daemon[8681]: Loading new alias name RT-AX88U.
Jan 27 11:07:19 router avahi-daemon[8681]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.50.1.
Jan 27 11:07:19 router avahi-daemon[8681]: New relevant interface br0.IPv4 for mDNS.
Jan 27 11:07:19 router avahi-daemon[8681]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Jan 27 11:07:19 router avahi-daemon[8681]: New relevant interface lo.IPv4 for mDNS.
Jan 27 11:07:19 router avahi-daemon[8681]: Network interface enumeration completed.
Jan 27 11:07:19 router avahi-daemon[8681]: Registering new address record for 192.168.50.1 on br0.IPv4.
Jan 27 11:07:19 router avahi-daemon[8681]: Registering new address record for 127.0.0.1 on lo.IPv4.
Jan 27 11:07:20 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:20 router avahi-daemon[8681]: Server startup complete. Host name is RT-AX88U-F098.local. Local service cookie is 3659585021.
Jan 27 11:07:20 router avahi-daemon[8681]: Alias name "RT-AX88U" successfully established.
Jan 27 11:07:21 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:22 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:23 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:24 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:25 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:26 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:27 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:28 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:29 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:30 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:31 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:32 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:33 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:34 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:35 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:36 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:37 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:38 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:39 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:40 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:41 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:42 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:43 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:44 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:45 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:46 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:47 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:48 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:49 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:50 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:51 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:52 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:53 router ejusb: USB partition unmounted from /tmp/mnt/SamsungT5 fail. (return -1, Bad file descriptor)
Jan 27 11:07:54 router ejusb: USB partition busy - will unmount ASAP from /tmp/mnt/SamsungT5
Jan 27 11:07:54 router rc_service: httpd 5990:notify_rc stop_upgrade
Jan 27 11:07:54 router usb: USB is ejected
Jan 27 11:07:54 router nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Jan 27 11:07:55 router kernel: IDPfw: Exit IDPfw
Jan 27 11:07:55 router kernel: mod epilog takes 0 jiffies
Jan 27 11:07:55 router kernel: IDPfw: Exit IDPfw
Jan 27 11:07:55 router kernel: Exit chrdev /dev/idpfw with major 191
Jan 27 11:07:55 router kernel: Exit chrdev /dev/idp with major 190
Jan 27 11:07:55 router kernel: Cpuidle Host Clock divider is enabled
Jan 27 11:07:55 router BWDPI: re-enable fc
Jan 27 11:07:57 router networkmap: Error unlocking 0: 9 Bad file descriptor
Jan 27 11:07:57 router avahi-daemon[8681]: Got SIGTERM, quitting.
Jan 27 11:07:57 router avahi-daemon[8681]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.50.1.
Jan 27 11:07:57 router avahi-daemon[8681]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Jan 27 11:07:57 router avahi-daemon[8681]: avahi-daemon 0.7 exiting.
Jan 27 11:07:57 router kernel: klogd: exiting
Click to expand...
That's the same results I get when trying to unmount as the last thing to do in a reboot.
 
skeal said:
That's the same results I get when trying to unmount as the last thing to do in a reboot.
Click to expand...
I am not sure this is relevant to your situation, but I just initiated a reboot from the button in the GUI. Not a single error message related to my USB drive.
Code: 
May  5 01:05:17 router amtm: Disk check done on /dev/sda1
May  5 01:05:17 router custom_script: Running /jffs/scripts/pre-mount (args: /dev/sda1 ) - max timeout = 120s
May  5 01:05:17 router usb: USB ext4 fs at /dev/sda1 mounted on /tmp/mnt/SamsungT5.
May  5 01:05:17 router kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: user_xattr
May  5 01:05:17 router custom_script: Running /jffs/scripts/post-mount (args: /tmp/mnt/SamsungT5 ) - max timeout = 120s
May  5 01:05:17 router kernel: Adding 1048572k swap on /tmp/mnt/SamsungT5/myswap.swp.  Priority:-1 extents:10 across:1196028k SS
May  5 01:05:17 router hotplug: USB ext4 fs at /dev/sda1 mounted on /tmp/mnt/SamsungT5
May  5 01:05:17 router amtm: Running disk check 'e2fsck -p' on /dev/sda1
Just an unrelated file descriptor error:
Code: 
Jan 29 19:31:35 router networkmap: Error unlocking 0: 9 Bad file descriptor
I do not know why the last few disk checks no longer report "recovering journal".
Code: 
 Sat May  5 01:05:14 EDT 2018 Starting 'e2fsck -p /dev/sda1'
 SamsungT5: recovering journal
 SamsungT5: Backing up journal inode block information.

 SamsungT5: clean, 649/122093568 files, 8013249/122093568 blocks

 Sat May  5 01:05:14 EDT 2018 Starting 'e2fsck -p /dev/sda1'
 SamsungT5: recovering journal
 SamsungT5: clean, 648/122093568 files, 8013567/122093568 blocks

 Sat May  5 01:05:14 EDT 2018 Starting 'e2fsck -p /dev/sda1'
 SamsungT5: recovering journal
 SamsungT5: clean, 689/122093568 files, 7949056/122093568 blocks

 Sat May  5 01:05:13 EDT 2018 Starting 'e2fsck -p /dev/sda1'
 SamsungT5: recovering journal
 SamsungT5: clean, 700/122093568 files, 7946560/122093568 blocks

 Sat May  5 01:05:14 EDT 2018 Starting 'e2fsck -p /dev/sda1'
 SamsungT5: recovering journal
 SamsungT5: clean, 701/122093568 files, 7949512/122093568 blocks

 Sat May  5 01:05:14 EDT 2018 Starting 'e2fsck -p /dev/sda1'
 SamsungT5: recovering journal
 SamsungT5: clean, 717/122093568 files, 7938889/122093568 blocks

 Sat May  5 01:05:14 EDT 2018 Starting 'e2fsck -p /dev/sda1'
 SamsungT5: recovering journal
 SamsungT5: clean, 1014/122093568 files, 7952149/122093568 blocks

 Sat May  5 01:05:18 EDT 2018 Starting 'e2fsck -p /dev/sda1'
 SamsungT5: clean, 1023/122093568 files, 7955588/122093568 blocks

 Sat May  5 01:05:16 EDT 2018 Starting 'e2fsck -p /dev/sda1'
 SamsungT5: clean, 1023/122093568 files, 7955746/122093568 blocks

 Sat May  5 01:05:17 EDT 2018 Starting 'e2fsck -p /dev/sda1'
 SamsungT5: clean, 1075/122093568 files, 7964947/122093568 blocks
Perhaps there are pragmatic realities to a firmware upgrade which do not allow for graceful unmounting. But a normal reboot is fine.
 
Im having the same issues here,
the rt-ac86 takes up to 5 minutes to reboot because of this issue.
Also tried lazy umount, no effect.
Im in my third usb stick in two weeks trying to figure out why is this happening,
Drives are ext4 formatted with journaling.
Here is a list o files preventing the usb umouting properly according to Lsof.

Code: 
     359467 /tmp/mnt/MYUSB/entware/bin/lsof
lsof       7443               jose  mem       REG                8,1   101072     358722 /tmp/mnt/MYUSB/entware/lib/libpthread-2.27.so
lsof       7443               jose  mem       REG                8,1  1345800     358664 /tmp/mnt/MYUSB/entware/lib/libc-2.27.so
lsof       7443               jose  mem       REG                8,1    83960     358680 /tmp/mnt/MYUSB/entware/lib/libgcc_s.so.1
lsof       7443               jose  mem       REG                8,1   161808     359464 /tmp/mnt/MYUSB/entware/lib/libtirpc.so.3.0.0
lsof       7443               jose  mem       REG                8,1   128760     358660 /tmp/mnt/MYUSB/entware/lib/ld-2.27.so
lsof       7445               jose  txt       REG                8,1   143400     359467 /tmp/mnt/MYUSB/entware/bin/lsof
lsof       7445               jose  mem       REG                8,1   101072     358722 /tmp/mnt/MYUSB/entware/lib/libpthread-2.27.so
lsof       7445               jose  mem       REG                8,1  1345800     358664 /tmp/mnt/MYUSB/entware/lib/libc-2.27.so
lsof       7445               jose  mem       REG                8,1    83960     358680 /tmp/mnt/MYUSB/entware/lib/libgcc_s.so.1
lsof       7445               jose  mem       REG                8,1   161808     359464 /tmp/mnt/MYUSB/entware/lib/libtirpc.so.3.0.0
lsof       7445               jose  mem       REG                8,1   128760     358660 /tmp/mnt/MYUSB/entware/lib/ld-2.27.so
lsof      7964               jose  txt       REG                8,1   143400     359467 /tmp/mnt/MYUSB/entware/bin/lsof
lsof      7964               jose  mem       REG                8,1   101072     358722 /tmp/mnt/MYUSB/entware/lib/libpthread-2.27.so
lsof      7964               jose  mem       REG                8,1  1345800     358664 /tmp/mnt/MYUSB/entware/lib/libc-2.27.so
lsof      7964               jose  mem       REG                8,1    83960     358680 /tmp/mnt/MYUSB/entware/lib/libgcc_s.so.1
lsof      7964               jose  mem       REG                8,1   161808     359464 /tmp/mnt/MYUSB/entware/lib/libtirpc.so.3.0.0
lsof      7964               jose  mem       REG                8,1   128760     358660 /tmp/mnt/MYUSB/entware/lib/ld-2.27.so
lsof      7976               jose  txt       REG                8,1   143400     359467 /tmp/mnt/MYUSB/entware/bin/lsof
lsof      7976               jose  mem       REG                8,1   101072     358722 /tmp/mnt/MYUSB/entware/lib/libpthread-2.27.so
lsof      7976               jose  mem       REG                8,1  1345800     358664 /tmp/mnt/MYUSB/entware/lib/libc-2.27.so
lsof      7976               jose  mem       REG                8,1    83960     358680 /tmp/mnt/MYUSB/entware/lib/libgcc_s.so.1
lsof      7976               jose  mem       REG                8,1   161808     359464 /tmp/mnt/MYUSB/entware/lib/libtirpc.so.3.0.0
lsof      7976               jose  mem       REG                8,1   128760     358660 /tmp/mnt/MYUSB/entware/lib/ld-2.27.so
 
Last edited:
I ended up formatting the usb drive and re-install everything. Problem seems to be fine on my AX88U.
 
skeal said:
I ended up formatting the usb drive and re-install everything. Problem seems to be fine on my AX88U.
Click to expand...
Dam, i really did not want to to that.
@skeal Witch usb port are you using? Usb2 or 3?
 
faria said:
Dam, i really did not want to to that.
@skeal Witch usb port are you using? Usb2 or 3?
Click to expand...
On my AX88U I'm using a old USB3.0 device 16GiG and it is mounted as USB3. Hope that helps, Asus sucks at USB3.0 drive support.
 
skeal said:
On my AX88U I'm using a old USB3.0 device 16GiG and it is mounted as USB3. Hope that helps, Asus sucks at USB3.0 drive support.
Click to expand...
i noticed that, i have 2 usb3 drives and most of the time i plug them in after a reboot they show unmounted,
also if im not mistaken usb3 port takes allot longer to mount a drive.
Im going to try and reinstall every thing this weekend and see how it goes, this time im going to use a Samsung 250gb M.2 SATA ssd that just became available from an ultra-book upgrade.
Thanks.
 
faria said:
i noticed that, i have 2 usb3 drives and most of the time i plug them in after a reboot they show unmounted,
also if im not mistaken usb3 port takes allot longer to mount a drive.
Im going to try and reinstall every thing this weekend and see how it goes, this time im going to use a Samsung 250gb M.2 SATA ssd that just became available from an ultra-book upgrade.
Thanks.
Click to expand...
Depends on what you are going to use the USB drive for. If it is just scripts and swap, just buy a cheap USB stick, These routers don't really act as a file server very well, IMHO
 
skeal said:
Depends on what you are going to use the USB drive for. If it is just scripts and swap, just buy a cheap USB stick, These routers don't really act as a file server very well, IMHO
Click to expand...
Just Entware stuff and daily router backups .
for other stuff I have my Synology Nas.
Currently using a cheep sandisk 8gb card but it gets pretty toasty, since the ssd is doing nothing may as well use it.
 
faria said:
Just Entware stuff and daily router backups .
for other stuff I have my Synology Nas.
Currently using a cheep sandisk 8gb card but it gets pretty toasty, since the ssd is doing nothing may as well use it.
Click to expand...
Personally I would back the router up to the NAS and use the stick for scripts and Entware and a swap. It will go along way to save the possibility of a corrupt drive.
 
Since my last post in this thread I have reset to firmware defaults, reset jffs and repartitioned my USB drive.

For new USB drives, I recommend:
  • Before installing amtm and Entware, partition the drive from the router or in Windows MiniTool Partition Wizard.
  • Make the first partition the Entware partition, 3 GB. Use journaled ext4.
  • Enable full filesystem checks on the Entware filesystem each reboot with tune2fs.
  • Create one or more partitions with the remaining space. Use journaled ext4.
  • Disable full filesystem checks on the non-Entware filesystems with tune2fs. Perform these manually from time to time. Without Entware on them, it should be easy to unmount, e2fsck and mount them without disrupting the functions of the router. If they are large, the Entware swap file may help full checks succeed. Minimize what you do in the jffs and Entware filesystems. Use this filesystem(s) instead.
  • Install amtm and use it to create a swap file in the Entware filesystem. The relatively small filesystem allows for the router to reboot, the full filesystem check to only take a few seconds and for the router to come back online quickly with a supporting swap file.
 
Yeah what he said!! +1 ;):)
 
EmeraldDeer said:
Since my last post in this thread I have reset to firmware defaults, reset jffs and repartitioned my USB drive.

For new USB drives, I recommend:
  • Before installing amtm and Entware, partition the drive from the router or in Windows MiniTool Partition WizardMake the first partition the Entware partition, 3 GB. Use journaled ext4
  • 2: Enable full filesystem checks on the Entware filesystem each reboot with tune2fs.
  • Create one or more partitions with the remaining space. Use journaled ext4.
  • Disable full filesystem checks on the non-Entware filesystems with tune2fs. Perform these manually from time to time. Without Entware on them, it should be easy to unmount, e2fsck and mount them without disrupting the functions of the router. If they are large, the Entware swap file may help full checks succeed. Minimize what you do in the jffs and Entware filesystems. Use this filesystem(s) instead.
  • Install amtm and use it to create a swap file in the Entware filesystem. The relatively small filesystem allows for the router to reboot, the full filesystem check to only take a few seconds and for the router to come back online quickly with a supporting swap file.
Click to expand...
Int step 2 above: Does the OS support GPT with ext4?
 
Thank you for the quick reply. I will let you know the outcome.
 
Jay Culley said:
Int step 2 above: Does the OS support GPT with ext4?
Click to expand...
Yes it does, Well a least on the Rt-ac86u, i started a fresh reinstall with the new Ssd, partition it as advised here with Partition magic then i noticed the ssd was in GPT mode , all working fine so far, no more umount problems.
 
On USB0 I have a lexmark 16 GB drive with Entware installed, with an MBR and ext4 file system. It's been there for 2 years. All is ready to go to attempt to install that ad blocker thing again. The first thing Divergent did was corrupt the NTFS file system on the 1TB drive on USB1. I have spent 2 days, 3 different firmware versions, GPT, MBR, any one of 5 different file systems created with 2 or 3 different tools. It flat out will not work on the 5300 again. Windows 10 does not care, works fine on it. I just had to mess with it, could not leave it alone. After 2 days websites were starting to populate with AD's again, the network was way slower, just a very negative experience.
 
Jay Culley said:
On USB0 I have a lexmark 16 GB drive with Entware installed, with an MBR and ext4 file system. It's been there for 2 years. All is ready to go to attempt to install that ad blocker thing again. The first thing Divergent did was corrupt the NTFS file system on the 1TB drive on USB1. I have spent 2 days, 3 different firmware versions, GPT, MBR, any one of 5 different file systems created with 2 or 3 different tools. It flat out will not work on the 5300 again. Windows 10 does not care, works fine on it. I just had to mess with it, could not leave it alone. After 2 days websites were starting to populate with AD's again, the network was way slower, just a very negative experience.
Click to expand...

Are you talking about Diversion by thelonelycoder?
 
You must log in or register to reply here.

Similar threads

B
Entware Where is Entware started upon reboot?
2
Replies
25
Views
1K
bibikalka
B
I
kernel: __ntfs_error: 58 callbacks suppressed
Replies
2
Views
225
Indi
I
B
AC86U: boot the prior "bootfs_update" mtd as is?
Replies
6
Views
680
sfx2000
sfx2000
B
NFS sharing not working with 3004.388.4 on RT-AX88U
Replies
5
Views
1K
Beherit
B
pmcarrion
Solved No Swap file detected
Replies
13
Views
2K
glens
G
Similar threads
Thread starter Title Forum Replies Date
N (Solved - Bad router) RT-AX88U node causes network instability (3004.388.7) Asuswrt-Merlin 2
K Need help with a bad DHCP issue!!!! Asuswrt-Merlin 6
S No file transfer to USB drive Asuswrt-Merlin 3
D Import long ovpn file Asuswrt-Merlin 3
D File Copied to JFFS Partition Gets Deleted Automatically Asuswrt-Merlin 5
U File Timestamps are 2 hours ahead in FTP server Asuswrt-Merlin 17
C Firmware File? Asuswrt-Merlin 17
C Running dnsmasq with a huge config file like pihole - possible/sensible? Asuswrt-Merlin 10

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 550 (members: 20, guests: 530)
Top