1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

ASUS RT-N16 Bllown USB port

Discussion in 'Tomato Firmware' started by n4mwd, Apr 11, 2013.

  1. n4mwd

    n4mwd Serious Server Member

    I'm not sure what to say here, but it looks like one of my USB ports got blown out some how. I had a 1G USB stick plugged into the bottom port and entware installed on it. Today I decided that I had better make backups of the optware drive so I was busy tarballing it. Right in the middle, it says something like "short write" and the Windows share to the drive simultaneously dropped. The telnet console remained connected. I checked the gui and it was still working. I went to the USB section and there was no USB drive listed. I rebooted, no change. I pulled the stick and put it in another machine and it was fully readable. Put it back in the router and its still not showing up. Then I put it in the top USB port and all is well again. The bottom port seems dead.

    ????????????????????????????????????????

    Are tarballs that hard on these things? What could be causing this?

    I am using Toastman 7501.

    Oh, and when its in the bottom port, "fdisk -l" shows NO drives attached.
     
  2. n4mwd

    n4mwd Serious Server Member

    UPDATE:Tried another memory stick in the bottom USB port and it is ignored as well.
     
  3. Monk E. Boy

    Monk E. Boy Network Guru Member

    I wonder if dmesg would show anything useful? It shows USB hardware & initialization on my Toastman build.
     
  4. n4mwd

    n4mwd Serious Server Member

    I ran dmesg and it has a lot of good stuff, but it seems that the port is bad because it works on port 2 but not port 1 (the bottom one). Also, I noticed that it seemed a bit warm when I pulled it out. I am really suspecting hardware problems here. I wonder how difficult Asus is to deal with. Should I reflash it to the OEM firmware?

    Code:
    <snip>
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    SCSI subsystem initialized
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    PCI: Setting latency timer of device 0000:00:04.1 to 64
    ehci_hcd 0000:00:04.1: EHCI Host Controller
    ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:04.1: irq 5, io mem 0x18004000
    ehci_hcd 0000:00:04.1: USB 0.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 2 ports detected
    vlan1: add 33:33:00:00:00:01 mcast address to master interface
    vlan1: add 01:00:5e:00:00:01 mcast address to master interface
    vlan1: dev_set_allmulti(master, 1)
    vlan1: dev_set_promiscuity(master, 1)
    device eth0 entered promiscuous mode
    device vlan1 entered promiscuous mode
    usb 1-1: new high speed USB device using ehci_hcd and address 2
    device eth1 entered promiscuous mode
    br0: port 2(eth1) entering forwarding state
    br0: port 1(vlan1) entering forwarding state
    vlan2: Setting MAC address to  10 bf 48 e6 7c 7e.
    vlan2: add 33:33:00:00:00:01 mcast address to master interface
    vlan2: add 01:00:5e:00:00:01 mcast address to master interface
    IMQ starting with 3 devices...
    IMQ driver loaded successfully.
            Hooking IMQ after NAT on PREROUTING.
            Hooking IMQ before NAT on POSTROUTING.
    usb 1-1: device not accepting address 2, error -145                  <<<<<<<<<<<
    usb 1-1: new high speed USB device using ehci_hcd and address 3
    usb 1-1: device not accepting address 3, error -145
    usb 1-1: new high speed USB device using ehci_hcd and address 4
    usb 1-1: device descriptor read/64, error -145
    usb 1-1: device descriptor read/64, error -145
    usb 1-1: new high speed USB device using ehci_hcd and address 5
    usb 1-1: device descriptor read/64, error -145
    usb 1-1: device descriptor read/64, error -145
    hub 1-0:1.0: unable to enumerate USB device on port 1
    usb 1-2: new high speed USB device using ehci_hcd and address 6
    usb 1-2: configuration #1 chosen from 1 choice
    scsi0 : SCSI emulation for USB Mass Storage devices
    scsi 0:0:0:0: Direct-Access     USB      DISK 2.0         1219 PQ: 0 ANSI: 0 CCS
    sd 0:0:0:0: [sda] 1957888 512-byte hardware sectors (1002 MB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
    sd 0:0:0:0: [sda] Assuming drive cache: write through
    sd 0:0:0:0: [sda] Assuming drive cache: write through
     sda: sda1
    sd 0:0:0:0: [sda] Attached SCSI removable disk
    EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
    usb 1-2: USB disconnect, address 6
    usb 1-2: new high speed USB device using ehci_hcd and address 7
    usb 1-2: configuration #1 chosen from 1 choice
    scsi1 : SCSI emulation for USB Mass Storage devices
    scsi 1:0:0:0: Direct-Access     USB      DISK 2.0         1219 PQ: 0 ANSI: 0 CCS
    sd 1:0:0:0: [sda] 1957888 512-byte hardware sectors (1002 MB)
    sd 1:0:0:0: [sda] Write Protect is off
    sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00
    sd 1:0:0:0: [sda] Assuming drive cache: write through
    sd 1:0:0:0: [sda] Assuming drive cache: write through
     sda: sda1
    sd 1:0:0:0: [sda] Attached SCSI removable disk
    EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
    usb 1-2: USB disconnect, address 7
    usb 1-2: new high speed USB device using ehci_hcd and address 8
    usb 1-2: configuration #1 chosen from 1 choice
    scsi2 : SCSI emulation for USB Mass Storage devices
    scsi 2:0:0:0: Direct-Access     USB      DISK 2.0         1219 PQ: 0 ANSI: 0 CCS
    sd 2:0:0:0: [sda] 1957888 512-byte hardware sectors (1002 MB)
    sd 2:0:0:0: [sda] Write Protect is off
    sd 2:0:0:0: [sda] Mode Sense: 43 00 00 00
    sd 2:0:0:0: [sda] Assuming drive cache: write through
    sd 2:0:0:0: [sda] Assuming drive cache: write through
     sda: sda1
    sd 2:0:0:0: [sda] Attached SCSI removable disk
    EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
    
     
  5. koitsu

    koitsu Network Guru Member

    I'd suggest opening an RMA with Asus and definitely switch back to the stock Asus firmware before sending it off. It shouldn't require much work, just tell them the bottom USB port no longer works. That's all you should have to do.
     
  6. n4mwd

    n4mwd Serious Server Member

    Have you heard of anybody else with hardware problems with the N16? I surfed a little and found some people having problems with caps drying out on the 500s. Anyhow, looks like I'll be reflashing this thing tomorrow back to the original firmware (which isn't all that bad IMHO).
     
  7. koitsu

    koitsu Network Guru Member

    Hardware goes bad -- it happens. I wouldn't become too OCD over trying to determine if this sort of thing is common or not, honestly. You'll drive yourself mad. :)
     
  8. RMerlin

    RMerlin Network Guru Member

    Try a full power cycle:

    1) Turn the router off
    2) Unplug the power adapter
    3) Turn it on to drain any leftover charge
    4) Turn it off
    5) Plug power back
    6) Turn router on

    I've had PCs where the USB controller would be "crashed" until a complete power cycle was done. Simply rebooting wasn't enough.
     
  9. n4mwd

    n4mwd Serious Server Member

    Did a cold boot this morning and it seems to have fixed it. I will keep an eye on it. However, it did seem kind of strange that it went out just exactly at the same time as I was making that tarball.

    Anyhow, I was wondering if the USB ports on the N16 are fully 2.0 compliant when it comes to power sourcing? I seriously doubt that the little thumb drive overloaded the current, but I do have plans for other devices such as one of those self powered netbook drives.
     
  10. RMerlin

    RMerlin Network Guru Member

    Bus-powered HDDs are always hit-or-miss. Even with an actual PC, I have seen some of these drives fail to get sufficient power through the USB bus. The only way to be sure is to use an external AC adapter.
     
  11. leandroong

    leandroong Addicted to LI Member

    and probably shift to non mechanical drive like CF card or SSD (cheaper version)
     
  12. Monk E. Boy

    Monk E. Boy Network Guru Member

    You could also get a HD based on a 3.5" mechanism that'll be faster, cheaper, and - best of all - they require AC adapters to function.

    Edit: As far as I know the USB ports on an RT-N16 provides the necessary .5A @ 5V for self-powered devices to function, the problem is that self-powered USB HDs typically require .5A as a minimum and sometimes won't work unless they have over .5A.
     

Share This Page