NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Seagate USB 5 TB drive recognized after 2 hrs 45 mins
I had this Seagate 5TB drive hooked up to my DD-WRT enabled Buffalo AC1750 with no issues/trouble whatsoever. This past weekend I purchased the Nighthawk R9000 as the hardware specs were awesome...a...
Well sure enough the drive is now available at boot. I did the following:
- booted
- enabled telnet (via http://[router ip]/default.htm)
- telnet'd in...killed the e2fsck process
- disabled plex
- disabled all samba shares setup
- telnet back in and umount the USB drive (for me it was umount /mnt/sda1)
- ran: e2fsck /mnt/sda1 (you may want to consider: e2fsck -y /mnt/sda1)
Please note I had to enter "y" a bunch and it took over 2.5 hrs to complete (thus my noted wait time before the drive was seen). I also noted "e2fsck -p" was what was being run. Therefore, doing the above but running "e2fsck -y /mnt/sda1" or "e2fsck -y /mnt/sdb1" should fix your issues. I'm betting most drives will work...
Now when the router boots, the drive is seen and plex starts up with no issues.
And yes, this drive works regardless of denoted as been supported.
I just telnet'd into the box after boot. Notice e2fsck was running. Seems like when it reboots the drive does not cleanly unmount (is my bet). For whatever reason e2fsk takes about 2 hrs 45 mins to run through 3.5 TB worth of disk...
I should also mention that I killed e2fsck and suddenly the drive appeared and was mounted. I killed e2fsck within 10 mins of reboot and then saw the drive mounted >:(
Well sure enough the drive is now available at boot. I did the following:
- booted
- enabled telnet (via http://[router ip]/default.htm)
- telnet'd in...killed the e2fsck process
- disabled plex
- disabled all samba shares setup
- telnet back in and umount the USB drive (for me it was umount /mnt/sda1)
- ran: e2fsck /mnt/sda1 (you may want to consider: e2fsck -y /mnt/sda1)
Please note I had to enter "y" a bunch and it took over 2.5 hrs to complete (thus my noted wait time before the drive was seen). I also noted "e2fsck -p" was what was being run. Therefore, doing the above but running "e2fsck -y /mnt/sda1" or "e2fsck -y /mnt/sdb1" should fix your issues. I'm betting most drives will work...
Now when the router boots, the drive is seen and plex starts up with no issues.
And yes, this drive works regardless of denoted as been supported.