imperiects

It was a movie I had wripped from disk. Not a torrent. Edit: the file I transferred via SMB.

I did. I changed to it most free. Stopped/started the array. Manually added a file over SMB. Most disks are 50% or higher. Two disks are below 20%. The file I transferred went to disk1. It should have chosen disk5 or disk7.

Fill up works by getting up to the minimum required space then starts on a new disk. Didn't happen. Most free is suppose to keep them pretty close to even. Still wrote to disk 1 with two disk less than 20%. Data share still writes to disk1 even though it's on the excluded list. Why comment if you're going to ignore most of the information provided?

opened a different thread earlier but it is dead now. I know a bit more now so i am starting this one. Old post. The issue I am having is that the array only writes/downloads to disk1. The minimum space required was 50GB. It is now 75GB. The share itself as well as global shares are set to all disk. Split level was set to default (as needed). It is now set to level 2. Steps so far. 1. Restarted array 2. Rebooted server [(full shut down/ reset cmos because it wont reboot otherwise) a different issue] 2.5 cleared all incomplete torrents from client and array 3 Changed share from Fill-up to high water (added torrent after change) 4 Changed from high water to most free (added torrent after change) 5 Created a new share and pointed Qbit at it. (still only disk1) 6 Added disk1 to exclude list (still writes to it) Help please tower-diagnostics-20220820-1630.zip

deleted everything that was incomplete. Set share to high water. Double checked limit settings. Between share, sonarr, and radarr they are all set to 50GB. Its been running high water for almost 10 minutes. Still writing to disk1 even though disk5 and disk7 are nearly empty.

Not saying they're related. The device being disabled. Then missing upon reboot. Then not spinning up when pulled for testing. Died. That was weeks ago.

I swapped to split level 2 after the issue presented itself. Can swap it back to as needed. The 50GB limit has been there since the share was set up. Quality settings in the arrs is limited. Shouldn't be any single file over 23GB. Some manual adds are in the 40GB range. There are incomplete files. I am freeing up room by transferring the completed files to a different disk (2.7TB ish). I was going to transfer the incomplete folder but it reads 14TB when the drive is only 8TB. I've started the file transfer for completed files a couple hours ago. So downloads can continue and I can try to resolve the issue. I guess I had this issue before. A drive hit 100% (then died >.<) but I didn't think about it hitting max as much as I was concerned about the dead drive.

Yes it was configured like that (split as needed) when the issue began.

it was set to default. Split as needed. It is now set to level 2.

it is set to 50GB.

Yesterday my disk1 one filled up (as configured) but downloads and everything did not continue on a different drive in the array. Global share is set to all disks. Data share is set to fill-up / all disk. I have rebooted the server. Tried different setting (high water/most free). Nothing changed. How can this be resolved? Side note. Trying to transfer my /data/incomplete folder to a different drive begins a 14TB transfer. the drive is only 8TB. Not sure how its reading 14TB tower-diagnostics-20220820-0804.zip

I can fix that. The folder is empty. Edit: I have free memtest86. Ran through two full tests (4 passes per test). No error

I have been troubleshooting issues that led to a bad RAM stick. Since then my server has stopped freezing but one docker shuts itself down. The only error given is below. kernel: traps: qbittorrent-nox[10144] general protection fault ip:152310763cdf sp:7ffce19e6410 error:0 in qbittorrent-nox[15230f7ce000+37d4000] I have been unable to find any specific info for this or how to resolve the issue. Any help is appreciated. tower-diagnostics-20220814-1055.zip

Although I had gone through all RAM (single x4, double x2, triple x2, quad x1) it seems I had messed up something. Found a bad stick. Replaced it and everything seems to be resolved. Been running without issue for several hours now.

When I first built the server (1st time) I messed something up and the default docker image maxed out. So I increased its size while working out the issue. Never changed it back. Edit: this seemed wrong. My original build was changed to 150 while troubleshooting. Current build should be at 20. Might be part of the issue?