rtgurley

I ran the Live Memory Tester and got the results below. Am I screwed? [26.11.2025 11:10:04 CST] /usr/bin/memtester 10G 1 ============================================================================================= memtester version 4.6.0 (64-bit) adapted for use on Unraid installations Copyright (C) 2001-2020 Charles Cazabon Copyright (C) 2024 desertwitch (modifications for Unraid) THIS PROGRAM IS PROVIDED AS IS AND WITHOUT ANY WARRANTIES It is licensed under GNU General Public License Version 2 pagesize is 4096 pagesizemask is 0xfffffffffffff000 want 10240MB (10737418240 bytes) got 10240MB (10737418240 bytes), trying mlock ...locked. Loop 1/1: Stuck Address : Testing... failed Random Value : Testing... failed Compare XOR : Testing... ok Compare SUB : Testing... ok Compare MUL : Testing... ok Compare DIV : Testing... ok Compare OR : Testing... ok Compare AND : Testing... ok Sequential Increment : Testing... ok Solid Bits : Testing... failed Block Sequential : Testing... failed Checkerboard : Testing... failed Bit Spread : Testing... failed Bit Flip : Testing... failed Walking Ones : Testing... failed Walking Zeroes : Testing... failed 8-bit Writes : Testing... failed 16-bit Writes : Testing... failed Done. ============================================================================================= [26.11.2025 11:13:29 CST] The operation has finished with errors. [26.11.2025 11:13:29 CST] Code: 6 - Error during Stuck Address Test + Other Test(s).

My son was watching Plex and paused it for a bit, when he went to restart it, nothing was online. I could access the GUI, but not everything was loading on the screen. I did a hard reboot of the machine, but the Array won't start. It is stuck trying to mount the cache drive which has all my docker info. I don't even know what to look for at this point. gurley-diagnostics-20251125-1917.zip

I had to be patient. It took about 20 minutes for it to complete. Afterwards I was able to mount it properly.

I finally got my Parity disk upgraded (copied from old Parity) and Disk 1 (old Parity) rebuilt. Then I see that Disk 2 is unmountable with a red X, CRC errors are appearing. I shut down my machine and reseat the cables, but the drive still won't mount after reboot. It is now getting stuck as Mounting and just sits there, unRAID will not respond to a restart or shutdown command. After rebooting the machine I: removed the device from the array, clearing and formatting the drive, add drive back to array, start array - same result as above Currently running xfs_repair -L through the GUI to see if it can be fixed, it seems to be taking much longer than any previous xfs_repair that I have performed Do I just have another bad drive? Or is something bigger at play here? gurley-diagnostics-20240523-1258.zip

I had a situation that required me to repurpose the parity drive as a data drive and upgrade the size of the parity drive. I followed these instructions https://docs.unraid.net/unraid-os/manual/storage-management/#parity-swap and waited ~26 hours for the Copy to complete (Step 14). Step 15 says that I can now Start the array and a rebuild for my new data disk will start. I elected to do a graceful shutdown of my machine so I could add a couple of SSDs and create a second pool. When I restarted, it took me back to Step 13 Did I screw up by being a little impatient? Am I doomed to an endless loop of Copying the parity data? gurley-diagnostics-20240522-1036.zip

Somebody on reddit shared this document with me. So far I am about 74% (18 hours) into copying data from old parity to new parity. This seems faster than having to redownload data and rebuild parity.

I know that the proper setup for unRAID is to have the parity drive be at least as large as all other drives otherwise you lose access to some of the space on the larger disks in the array. My current setup is: Parity 14TB Array - 3 x 8TB, 3 x 12TB, 3 x 14TB Here is what I ran into this weekend. I noticed my parity check was going painfully slow so I used the DiskSpeed docker to test my disks. 2 of my 8TB drives are reading very slow speeds. I decided that it was time to upgrade them with some 16TB plus use a spare 14TB spare I had on hand. The plan WAS to: pull an 8TB from array, replace with spare 14TB and let rebuild pull 14TB parity, replace with 16TB and let parity rebuild pull 8TB from array, replace with 14TB and let rebuild keep extra 16TB as a spare Long story short the spare 14TB can't be read by 3 different computers, and the 8TB rebuild would take over a week. Currently I am running with my 8TB emulated. My plan now is to put my new 16TB in the array and only use 14 TB (size of parity), then put the other 16TB in parity. If I do that will I get my 2 TB back automatically when the parity drive is installed? Is there a better solution to this? I originally posted this in Reddit and 2 people have said that unRAID won't even let me use a 16TB drive in the array if parity is only 14TB. I was always under the impression that if the parity drive was smaller it could be used, it would just limit the size of the drive to match the size of the parity drive.

Server crashed again at about 14:45 today. Is it possible that the mother board is flaking out on me. Should I try to get log files from there? syslog-172.25.106.62.log

I appreciate the help. I haven't touched that setting ever, how would macvlan get enabled suddenly? Or, what else would change that would make it make a difference? The only physical change I made was adding a 2.5Gbps NIC because the onboard NIC stopped responding.

Server crahed yesterday at 10:05 pm. Here is the syslog. syslog-172.25.106.62.log

For the last few weeks I have been dealing with an unRAID machine that keeps freezing up. I have been running this machine for over 4 years, but for some reason it has been freezing occasionally. I connected a monitor to it so I could try to figure something out. The only thing that I can tell is what time it stops responding. My only recourse is to hard boot it and kick off another parity check. I am not sure where to start looking in the diagnostics file. I am assuming this is hardware related because I was running 6.12.4 just fine for a few months, any my 4 year old hardware might be starting to fail. gurley-diagnostics-20231030-1738.zip

This is what my setup looks like for both Radarr and Sonarr. Would you recommend changing the downloads folder to be /mnt/cache/Downloads (not necessarily to fix this issue)? I have various shares created based on types of TV show or movie. Should they just be put in subfolders under the TV Share or Movie Share?

Running 6.11.1 but the issue has been ongoing for a while. I have many shares set up to not use the cache pool. I want Sonarr/radarr to immediately move the files from the downloads folder (Cache only) to the array. Many times I see that some folders (TV/Classic TV/Movies) are being created on the cache drive and filling it up. The only way to move the files off is to manually do it with UNBalance. Then I use the 'rm' command to delete the folder from /mnt/cache, but it doesn't prevent the system from recreating the folder and filling up the drive again. Do I need to change permissions somewhere to prevent Sonarr/Radarr from creating the folders over and over? gurley-diagnostics-20221014-1123.zip

Thanks for creating this for the community. Over the last couple of days I have noticed that the file processing has been very slow. When I clicked into one of the workers tonight I saw this message "No Plugin requested to run commands for this file" What would cause this, and how can I correct it. I haven't added or removed any plugins, and they are all up to date.

UnRaid version 6.8.3 Woke up this morning to a corrupt docker image file. Deleted it and restarted docker, then reinstalled my apps and all good to go except for one. binhex-nzbget docker refuses to start - when trying to manually start it I get a pop-up that says "Execution Error - Server Error" Log file shows the following Oct 9 11:00:01 gurley speedtest: Internet bandwidth test started Oct 9 11:00:16 gurley speedtest: Host: Sparklight (Dallas, TX) [28.07 km] Oct 9 11:00:16 gurley speedtest: Ping (Lowest): 11.267 ms | Download (Max): 502.76 Mbit/s | Upload (Max): 159.67 Mbit/s Oct 9 11:00:16 gurley speedtest: Internet bandwidth test completed Oct 9 11:00:32 gurley crond[1976]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 9 11:06:46 gurley kernel: docker0: port 5(vethe9cf8bb) entered blocking state Oct 9 11:06:46 gurley kernel: docker0: port 5(vethe9cf8bb) entered disabled state Oct 9 11:06:46 gurley kernel: device vethe9cf8bb entered promiscuous mode Oct 9 11:06:46 gurley kernel: IPv6: ADDRCONF(NETDEV_UP): vethe9cf8bb: link is not ready Oct 9 11:06:46 gurley kernel: docker0: port 5(vethe9cf8bb) entered blocking state Oct 9 11:06:46 gurley kernel: docker0: port 5(vethe9cf8bb) entered forwarding state Oct 9 11:06:46 gurley kernel: docker0: port 5(vethe9cf8bb) entered disabled state Oct 9 11:06:47 gurley kernel: docker0: port 5(vethe9cf8bb) entered disabled state Oct 9 11:06:47 gurley kernel: device vethe9cf8bb left promiscuous mode Oct 9 11:06:47 gurley kernel: docker0: port 5(vethe9cf8bb) entered disabled state The log file for the container itself is blank. I have rebooted the machine, as well as removing the container and reinstalling. What are my next steps? PS I clicked on the Support link and it brought me to this forum. Let me know if I need to find a different forum.