Mark12

No one else is having issues with the postfix-relay container? I just turned it off for now, PeerTube works fine, just no mails...

It is attached in the post above yours?

What I get is this: Filesystem Size Used Avail Use% Mounted on rootfs 16G 222M 16G 2% / If I do ls -lah /mnt/user the command prompt freezes. No output. I have included the output from right after the restart after it froze. It crapped out within an our of starting the Postfix-Relay docker container... tower-diagnostics-20250505-0827.zip

I will get back to this once it locks up again. Really can't let it cr*p out right now or the WAF (wife acceptance factor) will be below 0.

Most of them are to /mnt/user/appdata .

Nothing. It just locks up. Same if I do cd /mnt/user . Nothing happens and the command prompt is frozen.

This is exactly what I did. I enabled syslog, mirrored to flash and ran diagnostics immediately after the reboot. I cannot run the diagnostics once the system locks up, it never finishes.

Ok, this is my last attempt for Unraid. If we cannot get this fixed I am going back to OMV, it is just costing to much time. After upgrading to Unraid 7 my system has not once been stable. What have I done so far: Set all power options to performance in the BIOS. Disabled UASP for the USB-C drive. Checked the drives via SMART Re-installed the docker containers. Switched from a mini-pc with a USB-C drive to a fully integrated nas <<--- this cost me a lot of money and did not change anything. Checked the disks again. Enabled UASP Set all power options to performance My Unraid server still craps out on me. But this time I am able to reproduce it within minutes! As soon as I start my PeerTube containers (PeerTube, PostfixRelay, PostgreSQL17 and Redis) my user shares dissapear and everything stops working. I cannot collect logs, when I go to the docker page the webpage times out, I cannot reboot the machine from the GUI. I have attached the diagnostics logs from right after the restart. Hopefully you can find something in them so we can fix this issue. tower-diagnostics-20250413-0849.zip

Got it fixed! What I did: Moved the disks back to the old hardware (pc with usb-c storages). Made an extra backup... Moved ALL data from my array to the pool (pool is as large and is my main storage as it is all SSD). Removed all directories from the array and cache. Removed the disks from the array and cache. Put the disks in the new PC (all sata). Create new config, under tools. Assign the previous disks (except for cache, that was a different one). Start the array. This time it works as I hoped!

Well, I have transferred the files back to the USB-C enclosure and tried to see what happened: exact same issue. This is a brand new machine, what kind of hardware issue could I be looking at? Is it possible this is because I just plugged in the USB drive in the new machine, not do a fresh install?

Now that would really suck big time... But it actually sounds like a probability, so I will try.

Sorry: you may ignore the above 2 posts. I just moved to a different setup to solve this issue. I had a different thread open for issues with that and posted in this thread by accident:

Posted this in the wrong thread: tower-diagnostics-20250405-1433.zip

It is already enabled. How do I post those logs? Do you mean the diagnostics? Attached those. tower-diagnostics-20250405-1433.zip