NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R8000 USB 3.0 not working after updating to Firmware 1.0.3.54
My readyshare drive (external hard drive) plugged into the USB 3.0 port was inaccessible after updating my R8000 firmware to the latest verions 1.0.3.54. The drive wasn't being recognized by the router, by checking the web interface. There was no issue with the drive when plugged into the USB 2.0 port or my laptop. I checked the USB 3.0 port with a couple other external hard drives and usb pen drives. Again with the same results, not recognized in the USB 3.0 port, but working fine in the USB 2.0 port.
Resetting back to factory settings didn't help.
From there I rolled back to firmware version 1.0.3.48, and then like magic the drive in the USB 3.0 port was being recognized.
There seems to be several posts regarding issues with the USB 3.0 port, but the only solutions being offered by support is to try a factory reset. I was very close to contacting support for a hardware replacement since my warranty is close to the end of the one year. My issue isn't hardware, it's with the firmware. I hope there is work being done resolve the issue in a firmware update.
I've posted this "solution" reply serveral times:
My R8000 will not recognize any USB 3 HDD unless I; (1) remove the power from the R8000, (2) remove the USB 3 device from the R8000, (3) fully power up the R8000 without the USB 3 device attached, then finally (4) plug in the USB 3 HDD / device. You will need to do this every time you power down or re-boot the R8000 - a huge PITA with 1.0.3.54!
2 Replies
I've posted this "solution" reply serveral times:
My R8000 will not recognize any USB 3 HDD unless I; (1) remove the power from the R8000, (2) remove the USB 3 device from the R8000, (3) fully power up the R8000 without the USB 3 device attached, then finally (4) plug in the USB 3 HDD / device. You will need to do this every time you power down or re-boot the R8000 - a huge PITA with 1.0.3.54!
Thanks! The work around worked. It's a real pain to have to go through that everytime. Hope they get it fixed.
