osker246

This is working perfectly so far. I'm rebuilding parity right now but all my data is copied over on the drives I'm retaining. I honestly don't know why I was thinking this whole process was super complicated. Thank you so much for the help!

Awesome! Thank you so much for the response and alternative suggestions. I would of never considered those options beforehand. However at this point I'm looking to slim down the server to a minimum by removing the 4TB drives. They're power on hours have reached 8 years and its only a matter of time until they give out on me and I'm having to work on it again. Based on reading your post and based on what I know the proper steps include: 1) Change all my shares inclusion settings to write new data only to disk 5 & 6. 2) unbalance all 4x4TB drives (disk 1-4) 3) Initiate new configuration and unassign Parity 1 & 2 and assigning the new 20TB drive to be parity 1. 4) Let parity rebuild occur while I keep my old parity drives off to the side. 5) Parity rebuild completes and I Preclear the old 12TB parity drives in unassigned devices and then add them to array when ready. 5) Follow The "Clear Drive Then Remove Drive" Method to remove one 4TB drive at a time. 6) Repeat step 5 3-more additional times until the 4TB disks are removed. Sound about right? My wife and kids would kill me if I lose the media on there and I'm in too deep to start over again. 😟 Thanks again!

I'm currently running version 6.12.13 and I've reached the point where I'm going to retire some older 4xHGST 4TB drives that I have in my system. Ultimately I want to replace the existing dual 12TB parity drives with a single 20TB parity drive. Then transfer the existing 12TB parity drives be be data drives. I'm having a difficult time wrapping my head around the sequence of doing this and making sure I'm not going to run into issues. My initial plan to minimize the number of parity rebuilds is: 1) Reconfigure the drives, unassign Parity 1 & 2 and assigning the new 20TB drive to be parity 1. 2) Let parity rebuild occur while I keep my old parity drives off to the side in the event that something may happen. 3) Once parity sync occurs I'll format and add my old 12TB drives to the array. (No sync is required when adding drives, right?) 4) Use Unbalance to move data off one HGST 4TB drive at a time to the new 12TB data drives. 5) Follow The "Clear Drive Then Remove Drive" Method to remove each drive thats been emptied. 6) Repeat steps 4 and 5 x3 to remove the remaining drives. Is this correct? I'm having doubts this is the correct approach and I'd hate to lose everything. I'd appreciate it if others could chime in and give me a bit of guidance.

Here is my volume mappings and download shares. I'm not quite sure where or what the the docker run command is. Care to elaborate where I can find this information? I should also say that I did a reinstall on the unRAID OS, wiped the cache drive, and did a fresh install of all containers and plugins and the issue is still persisting.

I posted this on /r/unraid but I figure I might try and get some help here too. I need some helping figuring out how to stop NZBGet from making my server completely unresponsive when it is working. I can't load unRAID's GUI nor can I access any docker containers when it is downloading. Shortly after a download is initiated, the cpu usage spikes to 100% and I am locked out until NZBGet completes its tasks. I've tried restricting NZBGet to 4Gb of memory and 1 of the 4 cores via --cpuset-cpus=0 --memory=4G. According to "docker stats" the memory is restricted correctly, but it still utilized all 4 of the available cores. Does anybody have an idea how to stop this issue? Also, NZBGet downloads and unpacks to the cache SSD drive and not the array. M/B: ASRock - H97M-ITX/ac CPU: Intel® Core™ i5-4460 CPU @ 3.20GHz

Custom cron.

It happens when I run it in the background. It's just strange that it only occurs when using the plug-in. Sent from my XT1575 using Tapatalk

I have been having an issue where I use rsync, via User Scripts, to perform backups to a remote server and that would make the webGUI unresponsive until the task was completed. Strange thing is I can run the rsync task via shell and I do not have any issues not being able to use the webGUI. Any idea why this is occurring?

Okay so I think something else may be the cause of this and I cannot figure it out. I'm not running any rsync jobs and the server webinterface is completely unresponsive. What is going on?

I recently setup 2 unRAID servers at remote locations for backup purposes and had them connected via openvpn server/client on the router level. After server1 initiates rsync, the server GUI of the server 1 does not respond shortly after. I can still shell into the server and access the docker containers GUI, just not the server GUI. I've tried performing the file transfer from server1 to server2 via MC and the same result happens. Why is this happening? Is there a more efficient way of conducting the sync/copy process? Server1 specs MB: Asrock-h97m-ITX/ac CPU: i5- 4460 RAM: 16GB

Same experience. I got fed up and wiped the container and started from scratch and it fixed it for a few weeks. The issue popped up again just the other day so I had to start from scratch again. Sent from my XT1575 using Tapatalk

Hello, I have been having some issues since I had recently updated both UNRAID and deluge. Initially, I could not get deluge to work with PIA after updating, I changed VPN_PORT to 1198 from 1194 as suggested earlier in the thread. This took care of the problem of not being able to access the webUI of deluge with the VPN on. But after updating I have not been able to connect to deluge with transdrone (android torrent app). After tinkering around for a bit I believe it due deluge no longer opening port 8112 on my router. Although, the port opens perfectly fine with the VPN disabled. I don't understand why this worked before the update, and after updating is ceases to work. I'm no expert when it comes to networking, I'd consider myself to know the basics. So where would I start with solving this issue? Thank you.