Archer BE800: The shared drive “disappears” after a reboot.
I recently purchased an Archer BE800 v1.20 and updated it to firmware version 1.3.2 Build 20251015 rel.10659(5553). Overall, it has worked perfectly for me, but this morning, after scheduling an automatic reboot at 2:00 a.m., I noticed that I could not access my shared network folder. When I logged into the administration panel, I only saw the following message: “No USB storage device found. Insert one into a USB port on your router and try again.”
Of course, I unplugged it and reconnected it several times, with no success. I even tried using other USB cables, but nothing worked. I rebooted the router to see if that was the issue, but that did not help either, nothing at all.
So I tried something else: testing with a different device. The one that was “causing the issue” was an Asus TUF Gaming A2 enclosure paired with a Samsung 990 EVO Plus 4TB SSD (NTFS format, GPT). It had initially worked without any issues, with excellent transfer speeds. I unplugged it and tested another device using the same cable, this time a Samsung T7 Shield 4TB (also NTFS, GPT), and it was detected immediately without any problems. I then tried a SanDisk Extreme PRO 256GB, and again, no issues at all. However, when I reconnected the Asus enclosure, it was still not detected.
I took the Asus enclosure, thinking it might be faulty, and connected it to my PC. I had no trouble accessing it at all. Even though it did not prompt me to do so, I ran an error check using the Windows tool, which reported no errors and that everything was fine. I disconnected it again and brought it back to the router. And here is the strange part: it worked perfectly once again:
I removed it again, disconnected and reconnected it, and once more it was not detected. I tried rebooting the router again, but nothing changed. I repeated the process of taking it back to my PC, and then, voilà, it worked again without any issues.
Based on all of the above, it seems to me that the hardware itself is not faulty, but rather that there is some issue with the router’s firmware that is preventing the drive from being properly recognized after a reboot, or after a drive that was initially working gets disconnected. Hopefully this can be reviewed by the technical team. For now, it works relatively well, but sooner or later the router will reboot again and the issue will likely reappear.
