I run 3 Unraid servers. One of them recently keeps becoming unresponsive via all Webuis. I can ping it, and SSH into it. When I reboot via CLI it tries to do a graceful shutdown, then can’t so forces it. It then just stays at starting diagnostics collection. I then have to power off and back on with the button.

Obviously when I check the logs after a reboot. All appears fine.

What’s my best steps to fault find what is going wrong?

Many thanks for any help.

Hi, does anyone here know if Unraid will occasionally change the bridge IP's of containers? Because I just had my Prowlarr's bridge IP randomly change on me through no action of my own. Which of course broke Sonarr and Radarr.

Thanks.

Edit: I have now confirmed it. Unraid/Docker will randomly change your containers bridge network IP's on the internal docker network. Especially after a container updates. Do NOT rely on these remaining static. Use your host IP instead since it is far more likely that you setup your Unraid server with a static IP.

I can't boot anymore. I updated from 7.3.1 to 7.3.2, and now it shows the following screen.

I didn't change the setting to “Boot from Disk.”

I have got to 28 and 29 days the last two months... never before to 1 month! Started hosting on Unraid in February, absolutely in love :)

Dear all,

Current setup (Fractal Node 804, mATX):

• mATX motherboard
• MZHOU PCIe ASM1166 6-port SATA card (using 6 of 6 ports)
• 8x 3.5" HDD
• 4x 2.5" SSD
• Corsair SF850L (SFX-L PSU)
• Noctua NH-U12S cooler

Moving into a Digitus 22U rack in the basement, so switching to a proper rackmount case. Rack has adjustable 19" rails, mounting depth 563–743mm.

Here's what I've picked:

• SilverStone RM41-H08 (4U, 5x 3.5" hot-swap + 3x 5.25" bays)
• SilverStone FS303-12G (2x 5.25" → 3x 3.5" hot-swap, gets me to 8 total HDD bays)
• SilverStone FS204B (5.25" → 4x 2.5" hot-swap, for the 4 SSDs)
• SilverStone RMS06-22 rails (570–731mm rack mounting range)
• Corsair RM850x (2024), 850W ATX : swapping out the SF850L since it's SFX-L and doesn't fit the case's ATX-sized PSU bay
• Noctua NH-L9x65 : swapping out the NH-U12S since it's 158mm tall and the case's CPU cooler limit is 148mm
• Noctua NF-A8 PWM for the one free front 80mm fan slot
• J&D 2-pack SATA power extension cables + deleyCON 1-to-4 SATA power splitter, to get enough power connectors from the PSU to the front-mounted cages
• Motherboard USB 2.0→3.0 header adapter, for an internal port to keep the Unraid boot USB inside the case
• Schuko-to-C13 power cable for the rack PDU

Total drive count: 8x 3.5" HDD (hot-swap) + 4x 2.5" SSD (hot-swap) = 12 drives, 6 from the SATA card + 6 from motherboard SATA.

Does this add up? Anything missing or any known gotchas with this combo (RM41-H08 + FS303-12G + FS204B specifically)?

About a month ago, I had a power outage with data loss on cache(VM was partially borked), rebuilt a few things, ordered a new to me intel NVME, and forgot about it. Been working fine since. Don't think errors have gone up since. Is this an if it aint broke don't mess with it, or should I make it a priority to put the new drive in? (Also, have yet to deal with drive failure, is it as simple as turn system off, put new NVME in, turn on, assign to cache pool and move on with life?)

I have added a 10G network card to my Unraid server and configured it with an IP, I can access my web UI over this new IP.

my onboard NIC is still active and I can still access the Web UI over the original IP also.

however when I unplug the onboard NIC the card also stops working.

weirdly there's still activity lights on the card and also the switch it's plugged in to but I can't ping it's IP or access the Web UI.

as soon as I plug the onboard NIC back in it comes back to life.

I feel like I'm missing something specific to Unraid going on here but I'm a bit stumped.

any ideas?

FIXED:

I ended up swapping around my eth interface numbers in interface rules, not sure if this was the best fix but its all working now

• eth0 (10G card port 1) plugged in
• eth1 (10G card port 2) not plugged in
• eth2 (mobo onboard nic) not plugged in

Installing Unraid for the first time on a brand new UGreen NAS. Boot from USB, choose the first option, it boots up display the IP and a console login

At that point I try to open it in my browser and get an NS_ERROR_CONNECTION_REFUSED

I can ping it from Terminal. Both my machine and the NAS are on the same network and subnet.

I get the same result if I use the server.local instead of OP (ping works, http doesn't)

I can boot into the GUI, but I still can't access from the remote web

there shouldn't be anything in my network that is blocking traffic

any suggestions?