IK
← Incident Log
RESOLVED CRITICAL Home Lab Β· incident Β· 08-11-26 Β· smb, ct, mounting, storage management, wireguard

Unraid Media Share randomly unmounting from Media CT - Home Lab

What happened

On media-docker CT on node 1 I have multiple stacks to manage my media lifecycle. One of those stacks uses wire guard for secure and private torrenting. Since I use SMB to connect to my Unraid Node for my media. I was encountering some issues with SMB when I was attempting to install directly to the storage pool through the network, so I had to figure out another way to implement my torrent system.

I decided to go use the qBittorrent integrated incomplete install path where I could have my files download locally to my on a local SSD for consist download speeds and auto move to the network when its done.

Initially on my first test this system was flawless, post downloads automatically moved to network media share and automatically feed to my home media service. It was a win situation.

When I woke up, all my torrents stopped and my media container wouldn't boot, which I easily fixed due to the local virtual drive pool being full.

Root cause

The fix

Prevention

Tests/Debugging

Fixing CT Disk Max Capacity

First issue I need to fix is removing all downloaded files that downloaded locally instead of transferring to the network.

Disk Status (CT 100 is Media CT)

image
image

To fix this issue I'm going to go into the CT100 Terminal and removing all the media that defaulted into "installing-temp" (incomplete torrent folder)

Results

I fixed this by switched to NFS for my network mounting and cutting off SMB. Since my CTs are linux based I learned that NFS was the better network protocol to use and mounted directly through my CT instead of using proxmox and I didn't have any more mounting issues.

// related project

Home Lab β†’

// referenced in

↩ Node 2 Overheating, CPU triggering shutdowns.↩ Media Container Fail without Backup - HomeLab