Matt Elias

So far so good after 22 days uptime.

I don't recall changing that, is it the default? I've changed it to ipvlan now, thanks.

Here's the generated diagnostics right after booting up again. tower-diagnostics-20240708-0828.zip

I went away for the weekend, when I came back my Unraid server was unresponsive. I powered it down by holding in the power button until it turned off. Then plugged the usb drive into my desktop. Here is the newest diagnosticstower-diagnostics-20240703-1258.zip and the syslogfile in my usb logs folder. Can I immediately boot it back up?

Okay, so then I wait now until it happens again, and hopefully I can retrieve the logs. Thanks everyone for the help.

tower-diagnostics-20240627-1018.zip This is now via the web GUI after a hard reboot.

I am reading through the diagnostics link, I have enabled syslog now. Reading the last paragraph in this screenshot leads me to believe that any helpful diagnostic data is lost after I reboot, which I have to do to get local or remote access to Unraid after it locks up.

Here's my main log after reboot. main log.txt

I have no access to any logs without doing a hard reset. I read that the diagnostic logs are reset at boot.

Twice now I have lost all network access to my Unraid web interface, ssh & all VMs/Containers. The network switch shows the interface is physically connected when plugged in (and unconnected when I unplug the ethernet cable) but the only way I can recover is with a hard reset, which of course causes the array to run a parity check. I'm very new to Unraid, I can't find any error or warning other then the array parity check after booting back up. This has happened now twice within 4 days. How can/should I dig into the cause?

I have registered with Seafile previously, but how to login with docker so that it can pull from their Pro repo? I can't find how to do that with the unRaid GUI. Is it cli only?

Care to elaborate? How do I register?

Now, does anyone know how to upgrade to PRO edition?

Okay, I tried again after removing prev containers and deleting all mariadb & seafile directories from my appdata. This time I created the mariadb container first, then seafile and now it's working after following these instructions as closely as possible.

Which instructions? I only see some instructions in the seafile-mc template but they conflict with the technique that @emrepolat7 shows in his screenshots I can't seem to figure it out. I get lost at Step 4, "a new database container that has nothing on it", what does that mean? Trying to follow @emrepolat7's screenshots I get the "502 Bad Gateway" error.

Thanks for the pointers. It appears after disabling "global c-states", it's stayed online through the weekend! I could not find a setting for "Power Supply Idle Control" but it seems to be working now. Regarding DRAM speed, I just left it as is for now.

I think I'm having this same issue with my B450M Pro4, R5 1400, Unraid 6.10.3 trial. Where is the "Power Supply Idle Control" setting in the bios? (I can't find it)

I setup a Ryzen 5 1400 with 32GB of RAM, 1TB NVMe and 10TB platter for Proxmox or a dedicated SeaFile server but then I came across Unraid and decided I want to try it. Any major reason to avoid running it on a Ryzen 5 1400?