skel2raw

Yes, it wakes up. But after it comes back it suddenly shuts down after not too long. But when I start Unraid again it does not say unclean shutdown.

Hi guys, Atower-diagnostics-20260623-2203.zipfter running for several weeks without any issues at all my unraid server now randomly goes into sleep mode or even shuts down completely. This sometimes happens after a couple of hours but most of the times within the first hour of running. I thought maybe it is a UPS issue but even after I disabled UPS the problem continues. Any ideas what might make my server behave this way and how I can solve the issue? Thanks!

I know, but even though I placed the old templates into the folder it wouldn't install the old configs. Bottomline is I ended up setting my entire server up from scratch. At least now I do not have any errors and crashes anymore. I guess over time some updates just messed up my unraid configuration.

Yes

Thanks! So I finally made a fresh install and now I have no crashes anymore. However one issue: Though I copied the templates-user folder and the templates actually do contain all settings, the dockers have to be configured manually again to run. The settings in the templates somehow are not working. Any ideas why this happens?

Done. So with a stock USB I have logs, but after I copy the old config folder there is again no syslog. Maybe the best thing is to do a fresh install. What's the best solution to backup my configurations incl. dockers? Reconfiguring everything from the beginning is going to be a lot of work.

tower-diagnostics-20260403-2027.zip here you go

It is booting in normal mode, just not in safe mode

I have connected the server to a monitor and selected boot into safe mode with GUI without plugins. But during the boot up it hangs at some point and does not boot into Unraid.

Unfortunately I cannot even boot in safe mode. Gui shows it is stopping the array and shutting down but nothing further happens and the system hangs. Ultimately I have to power off and power on the system again for Unraid to boot up

Nope, still empty

tower-diagnostics-20260403-1718.zip I have assigned a new folder "Logging" for the syslog and attached a new diagnostics. Any further ideas?

It's empty, no files inside

I tried various settings but it still won't show up.

Still no log

Syslog is enabled but after the last crash Unraid does not log anything at all anymore. Log is simply empty. Any idea how to fix this?

So I have let run memtest86 pro now for an entire night and it finished the 4 rounds of tests without any errors. Any other ideas? 😅

Okay, so I have recreated the pool. But my server crashed again after about 1 day of running. Any idea what I should do next? tower-diagnostics-20260328-2009.zip

Can I do the move from the cache pool with unbalanced or should I use the mover?

So I found the files and deleted them. But 2 uncorrectables remain. The syslog only shows this info and no file: Mar 25 18:02:57 Tower kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 55138320384 on dev /dev/nvme0n1p1 physical 50843353088 Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6891, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6890, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6889, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6888, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6887, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6886, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6885, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6884, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6883, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6882, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6881, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6876, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6875, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6874, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6873, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme0n1p1, physical 50843353088, root 6722, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:02:57 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 18, gen 0 Mar 25 18:03:06 Tower kernel: BTRFS error (device nvme0n1p1): unable to fixup (regular) error at logical 55138320384 on dev /dev/nvme2n1p1 physical 50822381568 Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6891, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6890, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6889, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6888, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6887, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6886, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6885, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6884, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6883, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6882, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6881, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6876, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6875, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6874, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6873, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS warning (device nvme0n1p1): checksum error at logical 55138320384 on dev /dev/nvme2n1p1, physical 50822381568, root 6722, inode 2598, offset 0, length 4096, links 1 (path: usr/bin/psl) Mar 25 18:03:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme2n1p1 errs: wr 0, rd 0, flush 0, corrupt 18, gen 0

Indeed there seems to be a serious issue with my my btrfs cache pool (the other pool is zfs) UUID: a05f72c2-5645-449e-a3d9-c21a00744f10 Scrub started: Tue Mar 24 21:32:20 2026 Status: finished Duration: 0:00:41 Total to scrub: 206.43GiB Rate: 5.03GiB/s Error summary: csum=12 Corrected: 0 Uncorrectable: 12 Unverified: 0Pool device status shows this: Id Path Write errors Read errors Flush errors Corruption errors Generation errors -- -------------- ------------ ----------- ------------ ----------------- ----------------- 1 /dev/nvme1n1p1 0 0 0 343 0 2 /dev/nvme2n1p1 0 0 0 343 0The other pool shows no errors. Does this mean at least one drive is bad? If so, does at least one of the drives need to be replaced?

I did a partial test with live memory tester and there have been no issues found. Might the data corruption not just be a result of too many system crashes?

Hi guys, My Unraid setup was running for many months without any issues. At some point my server began randomly crashing without me chaning anything at all. The only thing that I did was installing docker and Unraid updates once they became available. Now, since a couple of days my server is barely able to run a couple of hours without crashing. Unfortunately I do not understand well enough what the diagnostics and syslog are exactly putting out to find the cause of the issue. Can you please help me in finding out what is causing the crashes? My server is running with the latest Unraid version. Thank you guys! tower-diagnostics-20260323-2140.zip

I have now changed my cache drive from zfs to btrfs and the issue has resolved itself. Now my server is shutting down properly. The weired thing is that my other cache pool I use for downloads is not causing any issues.