paramehdic

Diagnostics as requested. tower-diagnostics-20240226-2004.zip

After upgrading to 6.12.8 my server randomly shut down and triggered parity check where 26012 errors were found/corrected. I double checked all the drives and nothing appears to be reporting any error or failure. My scheduled parity check just completed with 0 errors (although for some reason the notification still said 26012. Is there anything else I should be checking?

I think this makes the most sense, I will run unbalance for the data it thinks is on the drive, then new config then check for duplicate files after new parity has been calculated.

I removed 2 disks from my array (disk2 and disk3) which went fine following the directions on the Wiki. I then wanted to replace disk4 with a larger disk but mistakenly assigned it as disk2 which essentially was expanding the array again (it also caused many shares to disappear and errors such as full rootfs). I realized my mistake and stopped the rebuild (likely have lost some data but not a major concern) and assigned it has disk4, preclear completed and everything seems to be working fine except the array thinks disk2 is missing and the spare drives I have are not large enough (new drive is 14tb, old were 8tb). As it appears to be emulating data that it thinks was on disk2 will I loose data if I create a new config (like I did to originally shrink the array?) . Little stuck on this one and may end up just ordering another 14tb (which was the plan but the 14tb I ordered was defective and prices have increased so was hoping to avoid buying due non-ideal time). Thanks! Maybe I can just unbalance to transfer the data it thinks is on disk2 to the other drives and then redo the config like I initially did with the shrinking?

My logs didn't appear to be saving and I already rebooted. I have turned on mirror to flash so hopefully if it happens again I will have logs to provide.

Have been having some issues with checksum/md5 with rclone so figured I would do some maintenance. Scrub went fine however balance appears to have caused unraid server to hang (web gui, ssh) but does still respond to ping. Last progress update was 106/123 or close to it (I have since closed the web gui window). Any dockers are also not responding such as Plex Any suggestions prior to hard powering off the server? It has been running now for approx 60 minutes and cache drive is 480gb with 70gb used.

Update from rc4 went fine. Apologies wasn't able to get diagnostic for issue I had with RC5 (array not starting) but it is not an issue with RC6.

Array wont start, reverted to RC4 and working fine again.

Open as in still downloading or also those that may be seeding? Can't believe the answer could have been so easy, although I feel in the past when I had this setup mover was still completing except for files currently downloading.

I had a share that I previously had set to use cache disk only and now want this share to utilize the array. Figured I could change use cache disk to yes and mover would start its magic. However when I invoke mover it runs / completes nearly instantly without moving anything and gives below in the log. I checked and fixed anything pointing to /mnt/cache/Torrents to /mnt/user/Torrents but I still can't seem to get mover running correctly. Jan 23 18:19:38 Tower root: move_object: /mnt/cache/Torrents/incomplete: Directory not empty Jan 23 18:19:38 Tower root: move_object: /mnt/cache/Torrents: Directory not empty Jan 23 18:19:38 Tower root: mover: finished

When will or is there a change that can be made to update this to latest version of Plexpy (now Tautulli? http://tautulli.com/) Thanks,

While I was able to resolve this issue last time it was through reinstalling everything and starting fresh. However it appears the issue has returned, same message in log as before. Anything you suggest? Seems like it was an issue earlier on in this thread but didn't see the resolution other than it appears an update corrected it. Thanks Going back through I completed the below step and it appears to have corrected issue and allowed rtorrent to start again rename /config/rtorrent/rtorrent.rc to /config/rtorrent/rtorrent.rc.old and reboot the container

After most recent update unable to start. Also have received

Enable DHT Network and Peer Exchange (under settings, bittorrent) keep re-enabling is there something I am missing to keep these turned off? (seems to stay off for a period of time but always comes back not sure on interval) Also under Downloads/other the Check Has After Download wont allow it to be turned off (it will let you uncheck but is always back when you check settings)

How can I change the default password and do I need to change .htpasswd or is that not required since this is a docker? Also on topic of docker how do they handle resources? Whatever the server has they can utilize or can more resources be allocated? While rTorrent has fixed my speeds issues I was having with deluge it seems to get very unresponsive with only a handful of torrents active (20) whereas deluge I've had over 100 without any such issues. (both were docker images)