Khanan

Nic Down message coincide with the restart on the 21st to upgrade to 7.2.3, ISP outage and restart of the the router on the 22nd, and a reboot of the router on the 23rd to fix a lingering issue. Are you saying everytime I restart my router, sshd and nginix is going to stop and and not come back up again? This seems less than ideal. Thanks fore your time looking at this.

For the last several months, every time I go to the WebGUI to login, it has been unavailable. Everything else still running. Can get to shares and apps running in a docker. I have been hard powering the machine to get it up and running so I can login when needed. I recently got fed up with this and decided that I would enable SSH so that I could ssh to it and restart it cleanly. SSH is not responsive when the WebGUI is not responsive so no real help there. Then 7.2.3 was released so I updated hoping that there was a hidden bug fix. Today, I finally bit the bullet and climbed under the desk and plugged in a monitor and mouse when this happened again. I was able to login to the console and found that both the ngnix daemon and sshd were not running. I was able to start them and the GUI and SSH are accessible. Dec 23 07:52:05 zelda rc.nginx: Updating Nginx server daemon... Dec 23 07:52:05 zelda rc.nginx: Reloading Nginx server daemon... Dec 23 07:52:05 zelda rc.nginx: Checking configuration for correct syntax and then trying to open files referenced in configuration... Dec 23 07:52:05 zelda rc.nginx: /usr/sbin/nginx -t -c /etc/nginx/nginx.conf Dec 23 07:52:05 zelda rc.nginx: Reloading Nginx server daemon configuration... Dec 23 07:52:05 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: bind() to 0.0.0.0:80 failed (98: Address already in use) Dec 23 07:52:05 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: bind() to 0.0.0.0:443 failed (98: Address already in use) Dec 23 07:52:05 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: bind() to 0.0.0.0:80 failed (98: Address already in use) Dec 23 07:52:05 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: bind() to 0.0.0.0:443 failed (98: Address already in use) Dec 23 07:52:06 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: bind() to 0.0.0.0:80 failed (98: Address already in use) Dec 23 07:52:06 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: bind() to 0.0.0.0:443 failed (98: Address already in use) Dec 23 07:52:06 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: bind() to 0.0.0.0:80 failed (98: Address already in use) Dec 23 07:52:06 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: bind() to 0.0.0.0:443 failed (98: Address already in use) Dec 23 07:52:07 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: bind() to 0.0.0.0:80 failed (98: Address already in use) Dec 23 07:52:07 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: bind() to 0.0.0.0:443 failed (98: Address already in use) Dec 23 07:52:07 zelda nginx: 2025/12/23 07:52:05 [emerg] 781001#781001: still could not bind() Dec 23 07:52:08 zelda rc.nginx: Restarting Nginx server daemon... .... Dec 23 07:53:13 zelda rc.nginx: Restarting Nginx server daemon... Dec 23 07:53:13 zelda nginx: 2025/12/23 07:53:13 [emerg] 364257#364257: bind() to 169.254.144.100:80 failed (99: Cannot assign requested address) ..... Dec 22 14:13:17 zelda rc.sshd: Updating SSH server daemon... Dec 22 14:13:17 zelda sshd[777510]: Received signal 15; terminating. Dec 22 14:13:17 zelda sshd[779552]: error: Bind to port 22 on 169.XXX.XXX.100 failed: Cannot assign requested address. Dec 22 14:13:17 zelda sshd[779552]: fatal: Cannot bind any address.zelda-diagnostics-20251223-0905.zip I have attached diagnostics. I'm stumped as to why it is attempting to reload the configuration. And why it is failing but will start when I run the start manually. Dec 23 08:55:47 zelda rc.nginx: Starting Nginx server daemon... Dec 23 08:55:57 zelda rc.nginx: Nginx server daemon... Started. Dec 23 08:57:02 zelda rc.sshd: Restarting SSH server daemon... Dec 23 08:57:24 zelda rc.sshd: Starting SSH server daemon...

This may not apply specifically to this DuckDNS docker by linuxserver but this is the issue. When I try to install I get the following. "...Unable to find image 'lscr.io/linuxserver/duckdns:latest' locally docker: Error response from daemon: Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)...." I am able to nslookup lscr.io from the terminal. I am unable to ping it (this may not mean much as a lot of things are unpingable). This also happened when trying to install the linuxserver plex container. I ended up just installing another plex container. Am I missing something? Is there an extra step that I am not reading in the docs to use linuxserver's repository that I am missing? I can download other containers and install them without issue. Still new to unraid but really loving it over my very old ReadyNas NV+ and a 10 year old desktop running Plex.zelda-diagnostics-20241101-1329.zip Diagnostic is attached from right after the failure. Any help would be extremely appreciated.

For Duplicacy, what license do I need if any to use this docker? Thanks,

Plugging into a molex connection for power fixed the issue. Thank you so much for the help and quick replies.

Thank you both Wody and JorgeB. This makes very good sense and I'm ashamed I didn't think of firmware updates on the card after all the firmware I have had to install to fix issues on fiber HBAs. I guess I was just thinking it was working with the SATA so I kept troubleshooting other stuff. I found JorgeB's article on how to flash and will be following that. Thank you for that as well.

Diagnostics attached. I don't know that it will help as the BIOS isn't seeing the drives so I don't know how Unraid would. This is why I posted this in Hardware rather than Support as it seems to be a hardware issue. A little more background: The SAS drives were harvested from a working NetApp cluster when it was being retired. I know I have to reformat them to 512 but sg3_utils can't see the drives either. I don't see how all 5 drives went bad, that would be some VERY bad luck. Then again, I don't see how two new cables are bad either as that would be some bad luck as well. So I'm chalking this up to I've never used a SAS PCIe card and cables and figure I have configured something wrong. I have changed almost every setting I can in the card to no avail. The SATA drives work, the SAS aren't even detected. zelda-diagnostics-20241012-0858.zip

Built my first Unraid server this week. I had five 6TB hard drives laying around plus the four 3TB SATA drives out of my readyNas. Purchased an LSI 9300 16i The SATA drives work fine. The SAS drives aren't recognized even in the BIOS as being connected. I can feel them spin up. I have tried them with all four connections on the card. SATA works in each, SAS doesn't. Hard to believe that all 5 drives or both cables are bad, so I'm stumped. Is there some magic sauce? These are the cables I ordered. Sonilco Storage Configurations Cable Mini SAS HDD SFF-8643 to 4 SFF-8482 with 15-pin Power Port Cord (2 Cables, 0.5 Meter / 1.6 Feet) https://a.co/d/2hqmvMk Thank for any thoughts you may have.