Power came back on, NAS were setup to automatically wake up, they did, however, neither are showing a light for the LAN. I have 2 F5-221 units both are behaving this way.
They both have two CAT5 network cables attached for redundant connections, both are able to mount their drives using Samba, but I cannot access the Web UI. I get a ERR_CONNECTION_REFUSED response. I triple checked everything is setup, I can see the devices on the network and I can access their file systems, but I can't access their UI.
I need to be able to access the UI as one of the units has a bad hard drive and the beeping is annoying. I can't turn off the beeping any other way.
Has anyone else experienced this?
Edit: I purchased these in November of 2020, so they are only 5 months old.
Edit 2: I can ping the devices:
Code: Select all
PING nas-terramaster-6tb.local (192.168.1.125) 56(84) bytes of data.
64 bytes from nas-terramaster-6tb.local (192.168.1.125): icmp_seq=1 ttl=64 time=0.724 ms
64 bytes from nas-terramaster-6tb.local (192.168.1.125): icmp_seq=2 ttl=64 time=0.518 ms
64 bytes from nas-terramaster-6tb.local (192.168.1.125): icmp_seq=3 ttl=64 time=0.312 ms
64 bytes from nas-terramaster-6tb.local (192.168.1.125): icmp_seq=4 ttl=64 time=0.572 ms
64 bytes from nas-terramaster-6tb.local (192.168.1.125): icmp_seq=5 ttl=64 time=0.576 ms
64 bytes from nas-terramaster-6tb.local (192.168.1.125): icmp_seq=6 ttl=64 time=0.563 ms
64 bytes from nas-terramaster-6tb.local (192.168.1.125): icmp_seq=7 ttl=64 time=0.541 ms
64 bytes from nas-terramaster-6tb.local (192.168.1.125): icmp_seq=8 ttl=64 time=0.595 ms
64 bytes from nas-terramaster-6tb.local (192.168.1.125): icmp_seq=9 ttl=64 time=0.631 ms
^C
--- nas-terramaster-6tb.local ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8168ms
rtt min/avg/max/mdev = 0.312/0.559/0.724/0.103 ms
Code: Select all
traceroute to nas-terramaster-6tb.local (192.168.1.125), 30 hops max, 60 byte packets
1 nas-terramaster-6tb.local (192.168.1.125) 0.659 ms 0.628 ms 0.617 ms