So I recently installed NZBGet and everything seems to work fine while I watch it download, but if I ever leave it unattended it seems to lock up my entire unraid system and nothing but a power cycle will correct it. I'm not too sure what I am looking at, but I have attached the I've attached the syslog, from the syslog server as I can't access anything once it locks up, if this is not correct, please let me know.

 

My assumption at this point is the mover is trying to move files that are currently being accessed by NZBGet?

 

Any pointers to fix this (or anything else that seems off) would be greatly appreciated

syslog-192.168.4.100.log

The logs reveal two potential issues causing your Unraid system to crash:
 

BTRFS Checksum Errors:

There are multiple warnings and errors indicating BTRFS checksum failures on the cache drive (nvme1n1p1), which is likely where NZBGet is storing and processing files. These errors suggest data corruption on the cache drive and could be the source of system instability.

 

File Operations Conflicts:

Errors related to NZBGet accessing files (move_object: File exists) indicate that files being moved or accessed may conflict with other processes, such as the mover, causing excessive I/O or locking issues.

 

Steps to Resolve the Issues

1. Address the BTRFS Errors

The checksum errors on the cache drive need immediate attention to ensure data integrity and system stability.

Check and Repair BTRFS:

Run a BTRFS filesystem check and repair on the cache drive:

btrfs scrub start /mnt/cache

This will verify and attempt to repair data integrity issues.

After the scrub completes, check the status:

btrfs scrub status /mnt/cache

 

If the scrub reports unrepairable errors, you may need to back up data from the cache and reformat it:

Backup important data from /mnt/cache.

Reformat the cache drive to a clean BTRFS or XFS filesystem in the Unraid GUI.

 

*run smart test/check...

Monitor the Drive's Health:

Run a SMART test on the cache drive to check for hardware issues

smartctl -a /dev/nvme1n1

*Check settigns and permission...
2. Prevent File Access Conflicts

NZBGet and the mover may be accessing the same files, causing conflicts.

Configure NZBGet to Use a Temporary Directory:

Set NZBGet to use a separate temporary directory for incomplete downloads (on the cache drive):

Go to NZBGet’s settings and configure Temporary Download Folder to a location like /mnt/cache/incomplete.

Ensure the Completed Download Folder is on the cache drive but separate from the mover target.

Adjust Mover Settings:

Schedule the mover to run during off-peak times when NZBGet is not actively downloading.

Go to Settings > Scheduler > Mover Settings and configure the frequency appropriately.

Disable Mover for Specific Shares:

For the share used by NZBGet, set Use Cache to Only in the share settings. This ensures files remain on the cache drive until manually moved.

 

3. Test NZBGet with Reduced Load

High I/O activity from NZBGet could be overwhelming the cache drive. Limit NZBGet’s concurrent downloads and connections:

In NZBGet settings, reduce Download Queue size and limit Maximum Connections to a lower value (e.g., 10).

 

4. Debug and Monitor System

If crashes persist, enable better logging and monitoring:

Enable Persistent Syslogs:

Go to Settings > Syslog Server and set up remote logging or store logs on a separate drive.

Resource Monitoring:

Use the Dynamix System Stats or Netdata plugins to monitor CPU, RAM, and disk usage during NZBGet operations.

 

5. Reassess Cache Configuration

If the cache drive continues to be problematic:

Consider switching to an XFS cache drive for better stability (especially with single drives).

Upgrade or replace the cache drive if SMART tests indicate hardware degradation.