Joentje

After some testing over time, after the suggestion of @itimpi, I checked the power. Here are some details about my setup: Intel Core i3-9100 Fujitsu D3644-B 2x Kingston KSM26ED8/16ME 6x Seagate 2.5" 5TB drives Mini-box picoPSU 90 Leicke ULL Power Supply 120 W I guess that combined with everything running, power requirements have increased over time. The parity check would spin up all drives, which would eventually "kill" the server because I didn't have enough power. I have now replaced the power supply with the following: Mini-Box picoPSU-160-XT LEICKE ULL 156W The server has been running smoothly for some days/weeks now, including during parity checks. All, thanks for the help!

So when I start the parity check, it will freeze after a few seconds but you cannot refresh the page. After this is starting up again. The syslog will show this: Currently I have VM enabled and Docker engine enabled, but without running containers. Parity check still running fine till now, needs some hours to finish.

Just want to say what I currently have done. I have swapped the motherboard, CPU and mem. I have two Unraid servers with the same hardware. Disks are not replaced. After starting up, I still have the same behaviour. So not sure if it is hardware related. On the other server I did not have this issue. How do I know if it is a crash or not? It's shutdown immediately, no reboot page. Can it be the startup is done because it did go down, because the behaviour or setting is to start after having power? This is BIOS setting iirc. I still need to test different containers up/down.

Can this maybe be related? Aug 28 09:23:34 london root: Error response from daemon: error while removing network: network br0 id a2ef645d11f0be732eac145067de6e1189b88ecc338abf00eb194ccd8209552b has active endpoints Aug 28 09:23:34 london root: Error response from daemon: network with name br0 already exists Aug 28 09:23:34 london root: Error response from daemon: endpoint with name Adguardhome already exists in network br0 Aug 28 09:34:31 london root: Fix Common Problems: Error: Macvlan and Bridging found

Hi all, For some time now, I've had an issue with my Unraid server restarting when the parity check starts. It usually happens within the first 1% or so. What I've tried to do: • Removed UPS, thinking it might be a power-related issue, but the problem persisted even after disabling the UPS (docker/VM enabled). • Disabled docker, left VM enabled, and the parity check ran smoothly. • Disabled VM, left docker enabled, and the parity check failed again. • Disabled both docker and VM, and the parity check ran smoothly. So, it seems like it might be Docker-related, but I'm not sure why. I'm a bit out of options, so I thought maybe someone else might have a good idea. Thanks! london-diagnostics-20240828-0832.zip

Finished a memtest, it passed. Seems to be no issue with the memory. I tried to run the memtest86 from Unraid, but seems to be freezed. So I created a usb with memtest86, that runs fine.

I have indeed disabled auto-start of the array. But after like 10 min or so, when the rebuild is running, the Unraid server will reboot. Are there other logs that I can use for diagnostics?

The wierd thing is, I didn't reboot. It's seems, when it fails (somehow). I need to login again in the Unraid UI. New diagnostics attached. diagnostics-20210723-2014.zip

Hi everyone, I have 2 partity drives and 3 'normal' drives. All Seagate 2.5inch 5tb drives. My nr1 drives stopped working. Indicated with a red cross. I replaced the drive with a new one, and started the rebuild. But after couple minutes/hours it stops rebuilding without a message. All containers/vms stops. After some time a get the message: Parity sync / Data rebuild finished (0 errors) Duration: 4 hours, 19 minutes, 36 seconds. Average speed: nan B/s This can not be true. Hopefully you can help diagnostics-20210723-1918.zip