Tobasama

So just wait again for the next crash and post the syslog after that?

Yes, it crashed during the night. I rebooted it and fetched the syslog.

Like this? syslog

I've disabled c-states globally, set Power Supply Idle Control" to "typical current idle" Also downclocked ram to 2400mhz. Still the same problem. Attached new diagnostics after another reboot. tower-diagnostics-20240315-0744.zip

Recently switched from 12 year old hardware to some newer (but previously used in a workstation). Only added new RAM. Switched a few drives to bigger. The transition went fine. But after a few day it crashes. I reboot it and it's running for a few more days, then crash again. Does anyone looking at the diagnostics have an idea what's wrong? tower-diagnostics-20240130-1629.zip

Tried to do a parity check. First one after adding a few new drives a month ago. I added two 18TB-drives, use one as a parity drive and one in the array. The old parity drive (6TB) is now in the array as well. Everything seemed to work fine, until I started a parity check and it stopped at 14%, with kb/s-speeds and an estimated end in 7000 days. I tried to pause and cancel the parity check without success. Tried to stop the docker image and that looks like it works (it says No in the enable docker image settings), but all apps and plugins keep on running. Tried to reboot the whole system, without success. About half of all new files since the newly added drives are not visible either in unraid or in network shared drive in windows. In Main under Array devices the Parity drive says it's reading data at 1GB/s, been like that for 12 hours. All cpu cores are at 100%, also for 12 hours. Checked log and all it says is Jan 8 09:49:03 Tower kernel: md: disk0 read error, sector=664128888 Jan 8 09:49:03 Tower kernel: md: disk0 read error, sector=2931121040 Jan 8 09:49:03 Tower kernel: md: disk0 read error, sector=4399641472 disk0 is the parity drive. Is there anything I can do besides running a hard power off on the actual machine? And switching the parity drive for a new one? tower-diagnostics-20230109-0938.zip

After som hw issues I did a reinstall. Using pretty much the same hw, same array, same cache drive and same usb-stick. Everything is working except Transmission. Docker containers says it's started but I can't reach the Webui. Its logs keep repeating: [2022-06-08 00:00:25.692] transmission-daemon Error loading config file -- exiting. (/home/buildozer/aports/community/transmission/src/transmission-3.00/daemon/daemon.c:825) I've tried reinstalling it, with and without old image. I've wiped the old transmission folder in appdata. And even tried installing to appdata2 without success. Help please?

I'm stupid. Thought I hade disabled Docker but there you go. I'll see myself out. Thanks.

I'm just saying that I've run Mover twice and the cache drive still contains 61GB of system and appdata. Could I move them manually and if so, how?

Ok, thanks. But what about the system and app data that are on the cache drive?

Hi. Trying to get rid of bottlenecks in my setup, I'm replacing the old ssd I use as cache drive with a new Samsung 870. Reading the guide at https://wiki.unraid.net/Replace_A_Cache_Drive I can't helt but wonder if the guide's correct? It says: I ain't no tech genius but shouldn't "use cache disk: Yes" mean that the shares end up ON the cache drive? Because I've done all according to the guide but when I browse /mnt/cache in the Unraid GUI, the only folders I see on the cache drive are my system and appdata folders (amounting for 61GB). Just feels unintuitive to unassign this drive in this state.