What's new

USB Drive Mounts but won't remount on reboot

  • 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!

taelvin

Occasional Visitor
AC680+ Merlin .43 USB Drive Remount Failure after reboot

note: following applies to a RT-AC680 running latest Merlin FW

Good Evening,

I did a fresh FAT32 reformat of my new USB 3 64Gb drive using windows so that it could have no name for the partition/volume. I Put the files back on. Plugged it back in and the router recognized it and then I hit reboot with the webUI and now after four reboots it still is not automounting the USB drive. LED is dark and status in webUI is empty.

SSH in "mount" command after USB failed to remount after a reboot:
Code:
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=127720k,nr_inodes=31930,mode=755)
proc on /proc type proc (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/mtdblock5 on /jffs type jffs2 (rw,noatime)
usbfs on /proc/bus/usb type usbfs (rw,relatime)

I rebooted with USB drive pulled, then re-inserted it, and it lit up and recognized it in the WEBUI and on the front LED. Now SSH and mount command shows what I thought was an error in that last line but some threads on Unix forums say it is just telling you that if there was an error it would remount in read-only in the last line:

Code:
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=127720k,nr_inodes=31930,mode=755)
proc on /proc type proc (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/mtdblock5 on /jffs type jffs2 (rw,noatime)
usbfs on /proc/bus/usb type usbfs (rw,relatime)
/dev/sda1 on /tmp/mnt/sda1 type vfat (rw,nodev,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=utf8,shortname=winnt,flush,errors=remount-ro)

That being said I saw some other useful commands in other posts on this forum and decided to get them to help troubleshoot.

System Log shows this after inserting the drive:

Code:
Dec 31 19:00:41 kernel: usb 1-1: new SuperSpeed USB device using xhci_hcd and address 2
Dec 31 19:00:41 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Dec 31 19:00:41 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Dec 31 19:00:41 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Dec 31 19:00:41 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
Dec 31 19:00:41 kernel: force burst = 0.
Dec 31 19:00:41 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst
Dec 31 19:00:41 kernel: scsi0 : usb-storage 1-1:1.0
Dec 31 19:00:42 kernel: scsi 0:0:0:0: Direct-Access              Patriot Memory   PMAP PQ: 0 ANSI: 6
Dec 31 19:00:42 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Dec 31 19:00:42 kernel: sd 0:0:0:0: [sda] 123535360 512-byte logical blocks: (63.2 GB/58.9 GiB)
Dec 31 19:00:42 kernel: sd 0:0:0:0: [sda] Write Protect is off
Dec 31 19:00:42 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 31 19:00:42 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 31 19:00:42 kernel:  sda: sda1
Dec 31 19:00:42 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 31 19:00:42 kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Dec 31 19:00:42 rc_service: asus_sd 629:notify_rc restart_xhcimode 2
Dec 31 19:00:44 iTunes: daemon is stopped
Dec 31 19:00:44 FTP Server: daemon is stopped
Dec 31 19:00:44 Samba Server: smb daemon is stopped
Dec 31 19:00:44 kernel: gro disabled
Dec 31 19:00:44 Timemachine: daemon is stopped
Dec 31 19:00:44 kernel: xhci_hcd 0000:00:0c.0: remove, state 1
Dec 31 19:00:44 kernel: usb usb1: USB disconnect, address 1
Dec 31 19:00:44 kernel: usb 1-1: USB disconnect, address 2
Dec 31 19:00:44 kernel: xhci_hcd 0000:00:0c.0: USB bus 1 deregistered
Dec 31 19:00:44 kernel: ehci_hcd 0000:00:0b.1: remove, state 1
Dec 31 19:00:44 kernel: usb usb2: USB disconnect, address 1
Dec 31 19:00:44 kernel: ehci_hcd 0000:00:0b.1: USB bus 2 deregistered
Dec 31 19:00:44 kernel: ohci_hcd 0000:00:0b.0: remove, state 1
Dec 31 19:00:44 kernel: usb usb3: USB disconnect, address 1
Dec 31 19:00:44 kernel: ohci_hcd 0000:00:0b.0: USB bus 3 deregistered
Dec 31 19:00:44 rc_service: hotplug 651:notify_rc restart_nasapps
Dec 31 19:00:44 rc_service: waitting "restart_xhcimode 2" via  ...
Dec 31 19:00:45 kernel: xhci_hcd 0000:00:0c.0: xHCI Host Controller
Dec 31 19:00:45 kernel: xhci_hcd 0000:00:0c.0: new USB bus registered, assigned bus number 1
Dec 31 19:00:45 kernel: xhci_hcd 0000:00:0c.0: irq 112, io mem 0x18023000
Dec 31 19:00:45 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Dec 31 19:00:45 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Dec 31 19:00:45 kernel: usb usb1: No SuperSpeed endpoint companion for config 1  interface 0 altsetting 0 ep 129: using minimum values
Dec 31 19:00:45 kernel: hub 1-0:1.0: USB hub found
Dec 31 19:00:45 kernel: hub 1-0:1.0: 1 port detected
Dec 31 19:00:45 kernel: [xhci-hub] usb2mode:[2]
Dec 31 19:00:45 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Dec 31 19:00:45 kernel: ehci_hcd 0000:00:0b.1: EHCI Host Controller
Dec 31 19:00:45 kernel: ehci_hcd 0000:00:0b.1: new USB bus registered, assigned bus number 2
Dec 31 19:00:45 kernel: ehci_hcd 0000:00:0b.1: irq 111, io mem 0x18021000
Dec 31 19:00:45 kernel: ehci_hcd 0000:00:0b.1: USB 0.0 started, EHCI 1.00
Dec 31 19:00:45 kernel: hub 2-0:1.0: USB hub found
Dec 31 19:00:45 kernel: hub 2-0:1.0: 2 ports detected
Dec 31 19:00:45 kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Dec 31 19:00:45 kernel: ohci_hcd 0000:00:0b.0: OHCI Host Controller
Dec 31 19:00:45 kernel: ohci_hcd 0000:00:0b.0: new USB bus registered, assigned bus number 3
Dec 31 19:00:45 kernel: ohci_hcd 0000:00:0b.0: irq 111, io mem 0x18022000
Dec 31 19:00:46 kernel: hub 3-0:1.0: USB hub found
Dec 31 19:00:46 kernel: hub 3-0:1.0: 2 ports detected
Dec 31 19:00:46 kernel: usb 2-1: new high speed USB device using ehci_hcd and address 2
Dec 31 19:00:46 kernel: scsi1 : usb-storage 2-1:1.0
Dec 31 19:00:46 iTunes: daemon is stopped
Dec 31 19:00:46 FTP Server: daemon is stopped
Dec 31 19:00:46 Samba Server: smb daemon is stopped
Dec 31 19:00:46 kernel: gro disabled
Dec 31 19:00:47 Timemachine: daemon is stopped
Dec 31 19:00:47 kernel: scsi 1:0:0:0: Direct-Access              Patriot Memory   PMAP PQ: 0 ANSI: 6
Dec 31 19:00:47 kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
Dec 31 19:00:47 kernel: sd 1:0:0:0: [sda] 123535360 512-byte logical blocks: (63.2 GB/58.9 GiB)
Dec 31 19:00:47 kernel: sd 1:0:0:0: [sda] Write Protect is off
Dec 31 19:00:47 kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Dec 31 19:00:47 kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Dec 31 19:00:47 kernel:  sda: sda1
Dec 31 19:00:47 kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Dec 31 19:00:47 kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk
Dec 31 19:00:49 kernel: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Dec 31 19:00:49 hotplug[740]: USB vfat fs at /dev/sda1 mounted on /tmp/mnt/sda1
Dec 31 19:00:53 rc_service: hotplug 740:notify_rc restart_nasapps
Dec 31 19:00:53 iTunes: daemon is stopped
Dec 31 19:00:53 FTP Server: daemon is stopped
Dec 31 19:00:53 Samba Server: smb daemon is stopped
Dec 31 19:00:53 kernel: gro disabled
Dec 31 19:00:53 Timemachine: daemon is stopped
Dec 31 19:00:53 kernel: gro enabled with interval 2
Dec 31 19:00:55 Samba Server: daemon is started

fdisk -l shows something intriguing with the mtdblock but that isn't the USB, I think it is the JFFS partition.

Code:
Disk /dev/mtdblock0: 0 MB, 524288 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 1 MB, 1572864 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/mtdblock2: 31 MB, 31457280 bytes
255 heads, 63 sectors/track, 3 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock2 doesn't contain a valid partition table

Disk /dev/mtdblock3: 29 MB, 29726720 bytes
255 heads, 63 sectors/track, 3 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock3 doesn't contain a valid partition table

Disk /dev/mtdblock4: 100 MB, 100663296 bytes
255 heads, 63 sectors/track, 12 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock4 doesn't contain a valid partition table

Disk /dev/mtdblock5: 33 MB, 33554432 bytes
255 heads, 63 sectors/track, 4 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock5 doesn't contain a valid partition table

Disk /dev/sda: 63.2 GB, 63250104320 bytes
255 heads, 63 sectors/track, 7689 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1   *           1        7690    61766656   c Win95 FAT32 (LBA)

df -kh command shows this before a reboot:

Code:
Filesystem                Size      Used Available Use% Mounted on
/dev/root                27.0M     27.0M         0 100% /
devtmpfs                124.7M         0    124.7M   0% /dev
tmpfs                   124.8M      4.5M    120.4M   4% /tmp
/dev/mtdblock5           32.0M      1.1M     30.9M   4% /jffs
/dev/sda1                58.9G     46.7G     12.2G  79% /tmp/mnt/sda1
 
Last edited:
POST REBOOT CODE

This is an abridged system log after the reboot.

Code:
Dec 31 19:00:13 kernel: Registering the dns_resolver key type
Dec 31 19:00:13 kernel: Northstar brcmnand NAND Flash Controller driver, Version 0.1 (c) Broadcom Inc. 2012
Dec 31 19:00:13 kernel: NAND device: Manufacturer ID: 0x01, Chip ID: 0xf1 (AMD NAND 128MiB 3,3V 8-bit)
Dec 31 19:00:13 kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Dec 31 19:00:13 kernel:  2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Dec 31 19:00:13 kernel: Available 7 bytes at (off,len):
Dec 31 19:00:13 kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0) 
Dec 31 19:00:13 kernel: Scanning device for bad blocks
Dec 31 19:00:13 kernel: Bad eraseblock 953 at 0x000007720000
Dec 31 19:00:13 kernel: Options: NO_AUTOINCR,NO_READRDY,BBT_SCAN2NDPAGE,
Dec 31 19:00:13 kernel: Creating 2 MTD partitions on "brcmnand":
Dec 31 19:00:13 kernel: 0x000002000000-0x000008000000 : "brcmnand"
Dec 31 19:00:13 kernel: 0x000004000000-0x000006000000 : "jffs2"
Dec 31 19:00:13 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
Dec 31 19:00:13 kernel: devtmpfs: mounted
Dec 31 19:00:13 kernel: Freeing init memory: 212K
Dec 31 19:00:13 kernel: ctf: module license 'Proprietary' taints kernel.
Dec 31 19:00:13 kernel: Disabling lock debugging due to kernel taint
Dec 31 19:00:13 kernel: et_module_init: passivemode set to 0x0
Dec 31 19:00:13 kernel: et_module_init: txworkq set to 0x1
Dec 31 19:00:13 kernel: et_module_init: et_txq_thresh set to 0x400
Dec 31 19:00:13 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.14.86 (r456083)
Dec 31 19:00:13 kernel: wl_module_init: passivemode set to 0x0
Dec 31 19:00:13 kernel: wl_module_init: txworkq set to 0x1
Dec 31 19:00:13 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
Dec 31 19:00:13 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.86 (r456083)
Dec 31 19:00:13 kernel: JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
Dec 31 19:00:13 kernel: usbcore: registered new interface driver usbfs
Dec 31 19:00:13 kernel: usbcore: registered new interface driver hub
Dec 31 19:00:13 kernel: usbcore: registered new device driver usb
Dec 31 19:00:13 kernel: SCSI subsystem initialized
Dec 31 19:00:13 kernel: Initializing USB Mass Storage driver...
Dec 31 19:00:13 kernel: usbcore: registered new interface driver usb-storage
Dec 31 19:00:13 kernel: USB Mass Storage support registered.
Dec 31 19:00:13 kernel: jnl: driver (lke_8.9.0, Apr  9 2014 16:56:06, LBD=ON) loaded at bf5fe000
Dec 31 19:00:13 kernel: ufsd:: trace mask set to 0000000f
Dec 31 19:00:13 kernel: ufsd: driver (lke_8.9.0 lke_8.9.0_r225078_b43, LBD=ON, delalloc, acl, ioctl, ugm, sd(1), wb, tr) loaded at bf60b000
Dec 31 19:00:13 kernel: NTFS support included
Dec 31 19:00:13 kernel: Hfs+/HfsJ support included
Dec 31 19:00:13 kernel: optimized: speed
Dec 31 19:00:13 kernel: Build_for__ASUS_PRODUCTS_003_lke_8.9.0_r225078_b43
Dec 31 19:00:13 kernel: xhci_hcd 0000:00:0c.0: xHCI Host Controller
Dec 31 19:00:13 kernel: xhci_hcd 0000:00:0c.0: new USB bus registered, assigned bus number 1
Dec 31 19:00:13 kernel: xhci_hcd 0000:00:0c.0: irq 112, io mem 0x18023000
Dec 31 19:00:13 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Dec 31 19:00:13 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Dec 31 19:00:13 kernel: usb usb1: No SuperSpeed endpoint companion for config 1  interface 0 altsetting 0 ep 129: using minimum values
Dec 31 19:00:13 kernel: hub 1-0:1.0: USB hub found
Dec 31 19:00:13 kernel: hub 1-0:1.0: 1 port detected
Dec 31 19:00:13 kernel: [xhci-hub] usb2mode:[0]
Dec 31 19:00:13 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Dec 31 19:00:13 kernel: ehci_hcd 0000:00:0b.1: EHCI Host Controller
Dec 31 19:00:13 kernel: ehci_hcd 0000:00:0b.1: new USB bus registered, assigned bus number 2
Dec 31 19:00:13 kernel: ehci_hcd 0000:00:0b.1: irq 111, io mem 0x18021000
Dec 31 19:00:13 kernel: ehci_hcd 0000:00:0b.1: USB 0.0 started, EHCI 1.00
Dec 31 19:00:13 kernel: hub 2-0:1.0: USB hub found
Dec 31 19:00:13 kernel: hub 2-0:1.0: 2 ports detected
Dec 31 19:00:13 kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Dec 31 19:00:13 kernel: ohci_hcd 0000:00:0b.0: OHCI Host Controller
Dec 31 19:00:13 kernel: ohci_hcd 0000:00:0b.0: new USB bus registered, assigned bus number 3
Dec 31 19:00:13 kernel: ohci_hcd 0000:00:0b.0: irq 111, io mem 0x18022000
Dec 31 19:00:13 kernel: hub 3-0:1.0: USB hub found
Dec 31 19:00:13 kernel: hub 3-0:1.0: 2 ports detected
Dec 31 19:00:13 kernel: usbcore: registered new interface driver usblp
Dec 31 19:00:14 kernel: usbcore: registered new interface driver asix
Dec 31 19:00:14 kernel: usbcore: registered new interface driver cdc_ether
Dec 31 19:00:14 kernel: usbcore: registered new interface driver rndis_host
Dec 31 19:00:14 kernel: hub 2-0:1.0: unable to enumerate USB device on port 1
Dec 31 19:00:14 kernel: cdc_ncm: 14-Mar-2012
Dec 31 19:00:14 kernel: usbcore: registered new interface driver cdc_ncm
Dec 31 19:00:14 kernel: usbcore: registered new interface driver cdc_wdm
Dec 31 19:00:14 kernel: usbcore: registered new interface driver qmi_wwan
Dec 31 19:00:14 kernel: cdc_mbim: loaded
Dec 31 19:00:14 kernel: usbcore: registered new interface driver cdc_mbim
Dec 31 19:00:14 syslog: module proxyarp not found in modules.dep
Dec 31 19:00:14 kernel: device vlan1 entered promiscuous mode
Dec 31 19:00:14 kernel: device eth0 entered promiscuous mode
Dec 31 19:00:14 kernel: device eth1 entered promiscuous mode
Dec 31 19:00:14 kernel: device eth2 entered promiscuous mode
Dec 31 19:00:14 kernel: br0: topology change detected, propagating
Dec 31 19:00:14 kernel: br0: port 3(eth2) entering forwarding state
Dec 31 19:00:14 kernel: br0: port 3(eth2) entering forwarding state
Dec 31 19:00:14 kernel: br0: topology change detected, propagating
Dec 31 19:00:14 kernel: br0: port 2(eth1) entering forwarding state
Dec 31 19:00:14 kernel: br0: port 2(eth1) entering forwarding state
Dec 31 19:00:14 kernel: br0: topology change detected, propagating
Dec 31 19:00:14 kernel: br0: port 1(vlan1) entering forwarding state
Dec 31 19:00:14 kernel: br0: port 1(vlan1) entering forwarding state
Dec 31 19:00:15 stop_nat_rules: apply the redirect_rules!
Dec 31 19:00:15 dnsmasq[505]: started, version 2.69 cachesize 1500
Dec 31 19:00:15 dnsmasq[505]: warning: interface tun22 does not currently exist
Dec 31 19:00:15 dnsmasq[505]: warning: interface tun21 does not currently exist
Dec 31 19:00:15 dnsmasq[505]: asynchronous logging enabled, queue limit is 5 messages
Dec 31 19:00:15 dnsmasq-dhcp[505]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Dec 31 19:00:15 dnsmasq[505]: read /etc/hosts - 5 addresses
Dec 31 19:00:15 WAN Connection: Ethernet link down.
Dec 31 19:00:15 dropbear[508]: Running in background
Dec 31 19:00:15 RT-AC68U: start httpd
Dec 31 19:00:15 RT-AC68U: start httpd - SSL
Dec 31 19:00:15 crond[522]: crond: crond (busybox 1.20.2) started, log level 8
Dec 31 19:00:15 disk monitor: be idle
Dec 31 19:00:15 kernel: gro enabled with interval 2
Dec 31 19:00:16 syslog: Generating SSL certificate...
Dec 31 19:00:16 syslog: Generating SSL certificate...

fdisk -l (you can see drive is now gone)

Code:
Disk /dev/mtdblock0: 0 MB, 524288 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 1 MB, 1572864 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/mtdblock2: 31 MB, 31457280 bytes
255 heads, 63 sectors/track, 3 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock2 doesn't contain a valid partition table

Disk /dev/mtdblock3: 29 MB, 29726720 bytes
255 heads, 63 sectors/track, 3 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock3 doesn't contain a valid partition table

Disk /dev/mtdblock4: 100 MB, 100663296 bytes
255 heads, 63 sectors/track, 12 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock4 doesn't contain a valid partition table

Disk /dev/mtdblock5: 33 MB, 33554432 bytes
255 heads, 63 sectors/track, 4 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock5 doesn't contain a valid partition table

Mount Command

Code:
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=127720k,nr_inodes=31930,mode=755)
proc on /proc type proc (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/mtdblock5 on /jffs type jffs2 (rw,noatime)
usbfs on /proc/bus/usb type usbfs (rw,relatime)

df -kh command
Code:
Filesystem                Size      Used Available Use% Mounted on
/dev/root                27.0M     27.0M         0 100% /
devtmpfs                124.7M         0    124.7M   0% /dev
tmpfs                   124.8M      4.5M    120.4M   4% /tmp
/dev/mtdblock5           32.0M      1.1M     30.9M   4% /jffs

Only weird thing I can see (not a programmer person) is the mtdblock output from the fdisk -l command.

Just to be sure I did pull the USB 3 Drive and ran MACOSX Diskutil diagnostics on it (I didn't know the fschk command for FAT32) and it didn't find anything wrong with the partition or file structure.
 
Last edited:
So I did a FW update and flashed to 374.42_2 and did a Factory Reset. I wanted to see what the behavior would be like on it for the mounted drives.

Without having done anything except formatted the JFFS partition and did two reboots the fdisk -l command showed the same partition message.

Code:
Disk /dev/mtdblock0: 0 MB, 524288 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 1 MB, 1572864 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/mtdblock2: 31 MB, 31457280 bytes
255 heads, 63 sectors/track, 3 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock2 doesn't contain a valid partition table

Disk /dev/mtdblock3: 29 MB, 29726720 bytes
255 heads, 63 sectors/track, 3 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock3 doesn't contain a valid partition table

Disk /dev/mtdblock4: 100 MB, 100663296 bytes
255 heads, 63 sectors/track, 12 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock4 doesn't contain a valid partition table

Disk /dev/mtdblock5: 33 MB, 33554432 bytes
255 heads, 63 sectors/track, 4 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock5 doesn't contain a valid partition table

I then upgraded back to 374.43_2 and Factory Reset and it showed the same. So I am assuming that this is actually normal for the mtdblock's that host the JFFS2 and system files to not have valid partitions?

Can anyone confirm that?
 
if you intend to keep the drive in the router, i'd format it as ext4. might help with this.

everything else is normal
 
Only problem with ext4 is that MACOSX doesn't support read/write by default which would make it difficult for me to maintain. There is a private software made that enables MACOSX to read/write and format ext4 but it is $40 :-/

What I don't understand is it has no problem mounting the drive if I plug it in after a reboot. But if you reboot it again the drive disappears from "mount" command. Might this be an issue with it mounting the drive as a /tmp/mnt/ ?

I noticed in one forum thread someone proposed having the drive associate with its UUID. But when I try the # blkid command it doesn't seem to do anything. Which is probably because I don't have a strong command of how to access the JFFS programs and use them save for following the steps I have seen posted by authors.

The thread I am referencing:

http://forums.smallnetbuilder.com/showthread.php?t=10166
 
if you intend to keep the drive in the router, i'd format it as ext4. might help with this.

I use EXT2 as journalling is not required. Also saved writes on a finite-life flash drive.
 
afaik, even ext4 without journaling or writeback enabled offers improvements over ext2. that said, i've only ever killed one flash memory card in my life by over-writing to it, which was like a 1st generation class 6 microsd by a-data that had an overused swap file and only lasted like 6 months. i've got older cards that once served the same purpose that still work :p
 
I then upgraded back to 374.43_2 and Factory Reset and it showed the same. So I am assuming that this is actually normal for the mtdblock's that host the JFFS2 and system files to not have valid partitions?

Can anyone confirm that?
Yes that's normal. The mtdblock's aren't disks so they won't have a partition table. In fact I'm surprised that fdisk even attempts to look at them! It should know that they're not disks.

Regarding your USB problem, it looks like the disk isn't being detected at all at boot time. I'd guess that it's probably just a timing issue between the router and the disk. After you reboot the router with the disk attached, type the following command and see if it detects and mounts the disk. If it does then you just need to issue that command from a script at boot time after a suitable delay (like 30 seconds).
Code:
/sbin/hotplug2

http://forums.smallnetbuilder.com/showpost.php?p=113976&postcount=9
 
Last edited:
That command issues the following:

Code:
:/tmp/home/root# /sbin/hotplug2
[sighandler]: No more events to be processed, quitting.
[cleanup]: Waiting for children.
[cleanup]: All children terminated.

But the drive doesn't show up on web UI or subsequent "mount" command
 
I tried both these commands and got the following :(

Code:
/tmp/home/root# ipkg install blkid
-sh: ipkg: not found
tmp/home/root# opkg install blkid
-sh: opkg: not found
If you have ac68u install download master and remove after, for 66u install entware
 
That command issues the following:

Code:
:/tmp/home/root# /sbin/hotplug2
[sighandler]: No more events to be processed, quitting.
[cleanup]: Waiting for children.
[cleanup]: All children terminated.

But the drive doesn't show up on web UI or subsequent "mount" command
No idea then. It looks like the same problem GoNz0 had here: http://forums.smallnetbuilder.com/showthread.php?t=15920

It might be worth asking him if he found a solution.
 
1. try your disk on the USB2 port
Your UseCase is streaming music from it...USB2 will just do.

2. try with another disk
As this is not normal behaviour you need to rule out that the ASIUS is the cause of these problems....it should work with another disk.
I am using this: http://www.amazon.com/dp/B009D79VH4/?tag=snbforums-20 with a class10/UHS-I flash-card from samsung.
 
No idea then. It looks like the same problem GoNz0 had here: http://forums.smallnetbuilder.com/showthread.php?t=15920

It might be worth asking him if he found a solution.

PM'd him and he said he gave up and ended up getting a 3TB NAS. I don't blame him LoL. Completely puzzling as to how it can detect it just fine when you manually insert it after a reboot but not if it stays in during a reboot and then doesn't respond to the hotplug2 command.
 
I tried to take it to Asus but never got a reply so I gave up. It wasn't something Merlin wanted to take up, not really his problem.
 
I have a very similar problem where after reboot my partitions disappear. I've tried ext2 and ext3.

Code:
admin@LH-RTR:/tmp/mnt# fdisk -l

Disk /dev/sda: 2013 MB, 2013265920 bytes
62 heads, 62 sectors/track, 1022 cylinders
Units = cylinders of 3844 * 512 = 1968128 bytes

Disk /dev/sda doesn't contain a valid partition table
admin@LH-RTR:/tmp/mnt# /sbin/hotplug2
[sighandler]: No more events to be processed, quitting.
[cleanup]: Waiting for children.
[cleanup]: All children terminated.

So for some reason it does not like the partition table on reboot. Any ideas?
 
Small update, I installed DD-WRT and also have the same issue, apart from one bonus. disabling and enabling USB core support sparts it into life after a reboot.

Saves me having to contort round the back of the TV to get to the router to unplug/plug the USB cable to get it to come alive.
 
I have the same problem: When the router (AC68 with Firmware:376.49_4) booted up earlier without USB 3.0 HDD attached (Sharkoon Rapidcase with external power supply), all is fine, the HDD is recognized upon attachment.
But when I hit reboot on the webUI, after reboot it is not automounting the USB drive. LED is dark and status in webUI is empty. It doesen’t count how many times I reboot the router with HDD attached, it won't recognise again. I must boot up the router without the HDD, then later connect it.

Quotes from the system log:
Jan 1 01:00:12 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Jan 1 01:00:12 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Jan 2 00:49:46 kernel: xhci_hcd 0000:00:0c.0: Timeout while waiting for a slot
Jan 2 00:49:46 kernel: hub 1-0:1.0: couldn't allocate port 1 usb_device

Does anybody have idea what could be the problem?
 
Last edited:
I had my Toshiba 3tb replaced under warranty due to the click of death, I forgot all about this then attached it again and it works fine, I assumed Asus had updated the USB code.
 

Latest threads

Sign Up For SNBForums Daily Digest

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