Shomesomesho

Unfortunately that would prevent being able to download to a cache pool during an increment.

https://old.reddit.com/r/unRAID/comments/1byaqxn/scripts_to_pause_torrents_during_parity/ Seeding torrents from the array slows down a parity operation. I'd rather pause the seeding than slow down the parity operation. I don't want to close the torrent client completely, as that stops downloads to the cache. And without pause being recognized as a stop/end, and using the Increments feature of Parity Check Tuning plugin means the torrent docker would remain shut down for days until the parity operation is finished.

Is there a way to modify this script to consider a paused parity operation as stopped/finished?

Like many others, I have the Arr suite and use Qbittorent with a share setup for my media using the trash-guide for hard links. https://trash-guides.info/Hardlinks/How-to-setup-for/Unraid/ So my share is data, and my folder structures are /data/media/ & /data/torrents/ However, I used Mover Tuning's "Ignore files listed inside of a text file" option to ignore /mnt/download_cache/data/torrents which is obviously my cache disk that I download torrents to. The Unraid GUI is still showing space being occupied by the files in /download_cache/data/torrents that I hardlinked using any of the various Arr programs, but also shows space occupied by the files on the array in /data/media/ Are my hardlinks broken because of /data/torrents/ being kept off the array? I'm sorry if this is confusing. I did my best to explain it, but it's confusing to me.

System hasn't had a similar crash since. Going to say this was the problem. Thank you for your help!

Apologies if the title isn't an accurate description. It's the best I could word it. I created a Windows 11 VM yesterday but it seems like when the VM is running, it will (seemingly) randomly get these x86/split lock detection errors which bring down my network interface. It can be found in the log at timestamps: Jan 4 15:43:51 & Jan 4 15:50:26 I found other topics (#1 , #2) discussing this, but wasn't able to find any solutions. Anyone got any suggestions? Thanks. unraid-diagnostics-20240104-1622.zip

Thank you. For whatever reason a reboot of my piihole fixed it.

Hey, hoping someone can help me. I've had this container running fine previously. Sometime overnight something seems to have broken and I'm struggling to figure out where the problem is. It seems like the container can no longer connect to my VPN. I've confirmed that my VPN account is good and I can connect on other machines using the VPN's client. Please find my supervisord log attached, and thanks for any help. supervisord.log

3 Days, 14 hours uptime since just swapping the HBA out of the PCIe 5.0 into the PCIe 4.0. Don't want to get hopeful too soon, but this seems to have been the problem. Can anyone explain why the 5.0 slot would have an issue with my HBA? Should I have set the 5.0 slot in the bios to 3.0 link speed? Should I be setting the 4.0 to 3.0 link speeds?

Memtest passed with no errors. I swapped the HBA to a different port and it's been up for 24 hours so far. If it crashes again, I'll remove 3 sticks of ram and test each individually.

I'll try moving it to a different slot. The card has a fan mounted directly on the heatsink, but I've not found a way to monitor temps. Ah, sorry. I meant are these the things logged when Unraid first boots, illustrating that this was the point that the server rebooted? Thank you for all your help.

Thank you @JorgeB I will try that. I realize this isn't an Unraid specific question, but how long/how many passes would you advise memtest run? Edit: I'm also seeing these messages in my log file: Dec 11 01:11:11 Unraid kernel: mpt3sas_cm1: SAS host is non-operational !!!! Dec 11 01:11:12 Unraid kernel: mpt3sas_cm0 fault info from func: mpt3sas_base_make_ioc_ready Dec 11 01:11:12 Unraid kernel: mpt3sas_cm0: fault_state(0x2667)! Dec 11 01:11:12 Unraid kernel: mpt3sas_cm0: sending diag reset !! Dec 11 01:11:12 Unraid kernel: mpt3sas_cm1 fault info from func: mpt3sas_base_make_ioc_ready Dec 11 01:11:12 Unraid kernel: mpt3sas_cm1: fault_state(0x2667)! Dec 11 01:11:12 Unraid kernel: mpt3sas_cm1: sending diag reset !! And then right after the above messages: Dec 11 01:13:36 Unraid kernel: Linux version 6.1.49-Unraid (root@Develop-612) (gcc (GCC) 12.2.0, GNU ld version 2.40-slack151) #1 SMP PREEMPT_DYNAMIC Wed Aug 30 09:42:35 PDT 2023 Dec 11 01:13:36 Unraid kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot Dec 11 01:13:36 Unraid kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks Dec 11 01:13:36 Unraid kernel: BIOS-provided physical RAM map: Was this the reboot/crash point?

Hello everyone, I'm hoping to get some help with my random reboot problem. I just built this system in November and I’ve been struggling to solve this on my own. My server seems to crash or reboot itself after anywhere from 5 – 72 hours of uptime. I have the array set to not start itself on boot, so I will come back to my server and see it just sitting, waiting for me to start the array, with notifications about unclean shutdowns. It seems more likely to occur when I’m doing tasks with a lot of disk activity like a Parity Sync or running Mover (with many TBs to move) The server is plugged into an APC UPS with fresh batteries which report good health and I have NUT setup with a shutdown method. So far, I’ve done to following: Changed the CPU from an i5 13500 to an i7 13700k (upgrade unrelated to this issue). Removed an old disk with questionable SMART data, without alleviation. Replaced the TIM on my HBA. Reseated the RAM. I'm currently running memtest, but do not have results yet. I mirrored the syslog to flash and will attach it. System Specs: Intel Core i5-13500 > Intel Core i7-13700K. ASRock Z690 Extreme ATX LGA1700 Motherboard G.Skill Ripjaws V 64 GB (4 x 16 GB) DDR4-3200 CL16 Memory Appdata Storage: Western Digital Black SN850X 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive Download Cache: 2x SAMSUNG 870 QVO 2.5" 1x SAMSUNG 850 EVO 2.5” PSU: SeaSonic FOCUS Plus Platinum 750 W 80+ Platinum HBA: LSI 9300-16i SAS in IT Mode. Please let me know if I’ve missed anything important or if more info is needed. Thank you. syslog