deoner

FIXEDStatus: Solved The Fix: Replaced a faulty Ethernet cable between the 16-port switch (where the server is connected) and the MikroTik router. The Discovery: The server was connected to a 16-port switch. Everything seemed fine, but I noticed the link between this switch and the main MikroTik router had dropped to 100Mbps and was likely producing massive CRC errors. Even though the server's local connection was Gigabit, the "bottlenecked" and faulty uplink to the router caused the system to choke. Technical Summary for others: If your server freezes under load, check the entire chain of cables. A faulty uplink cable between switches can cause "Backpressure" and an "Interrupt Storm" on Core 0 of your Unraid server. The NIC driver struggles to handle the congestion and packet loss, leading to a complete UI lockup while the CPU is busy managing the network chaos. Key Optimizations that stayed: ipvlan instead of macvlan. Realtek r8125 OOT Driver. Direct Cache Paths (/mnt/cache/) to bypass FUSE. CPU Pinning (keeping Cores 0 & 1 for the OS).

I am experiencing a complete system management lockup (WebUI and SSH unresponsive) during high-speed downloads via SABnzbd/NZBGet. The system remains in this "flatline" state for the duration of the download, though the downloads often complete in the background. This setup was stable for over 20TB of traffic and recently started failing consistently. I have tested downloading directly to RAM by mapping /tmp to the container. The freeze still occurs immediately. This rules out my ZFS pool and NVMe SSDs as the cause. The issue is strictly related to high-speed network throughput and how the system handles the load. System Specs: CPU: Intel i5-12400 Motherboard: Biostar B760MX2-E PRO D4 (BIOS C-States still on Auto) RAM: 48GB NIC: Onboard Realtek RTL8125 2.5GbE Storage: ZFS Stripe (Samsung 970 512GB + Corsair MP510 256GB) Unraid Version: 7.2.2 What I have already tried: RAM Download Test: Mapped /tmp to /ramdownload in Docker. Freeze happens regardless of disk I/O. Drivers: Installed the "Realtek RTL8125" out-of-tree driver plugin (verified loaded via lsmod). Networking: Switched from macvlan to ipvlan. Docker Config: Moved all paths to /mnt/cache/ (bypass FUSE) and pinned CPUs to keep Cores 0 & 1 free. App Switch: Same behavior on both SABnzbd and NZBGet. Observations: It seems like a massive "Interrupt Storm" is hitting Core 0, making the management layer (nginx/ssh) unresponsive, even though the actual download process (on pinned cores) continues to work. root@SERVERDEONER2:~# zpool status -v cache pool: cache state: ONLINE config: NAME STATE READ WRITE CKSUM cache ONLINE 0 0 0 nvme0n1p1 ONLINE 0 0 0 nvme-Force_MP510_19428205000127695377 ONLINE 0 0 0 errors: No known data errors root@SERVERDEONER2:~# root@SERVERDEONER2:~# mount | grep cache cache on /mnt/cache type zfs (rw,relatime,xattr,posixacl,casesensitive) cache/system on /mnt/cache/system type zfs (rw,relatime,xattr,posixacl,casesensitive) cache/domains on /mnt/cache/domains type zfs (rw,relatime,xattr,posixacl,casesensitive) cache/isos on /mnt/cache/isos type zfs (rw,relatime,xattr,posixacl,casesensitive) cache/appdata on /mnt/cache/appdata type zfs (rw,relatime,xattr,posixacl,casesensitive) cache/data on /mnt/cache/data type zfs (rw,relatime,xattr,posixacl,casesensitive) cache/domains/HomeAssistant on /mnt/cache/domains/HomeAssistant type zfs (rw,relatime,xattr,posixacl,casesensitive) /mnt/cache/system/docker/docker.img on /var/lib/docker type btrfs (rw,noatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/) /mnt/cache/system/docker/docker.img on /var/lib/docker/btrfs type btrfs (rw,noatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/) /mnt/cache/system/libvirt/libvirt.img on /etc/libvirt type btrfs (rw,noatime,ssd,discard=async,space_cache=v2,subvolid=5,subvol=/) root@SERVERDEONER2:~# root@SERVERDEONER2:~# modinfo r8125 | grep version version: 9.016.01-NAPI-RSS srcversion: BA104C0510886D056381E52 root@SERVERDEONER2:~# serverdeoner2-diagnostics-20260123-1200.zip

anyone got a fix for this? i have the same issue

Hello, I'm planning to migrate my ~100TB Windows Server 2019 (with DrivePool) to Unraid and would appreciate some feedback on my migration strategy. I used Claude AI to create a migration plan, but I'd like to get it reviewed by the community to make sure I'm not missing anything or if there are any outdated practices. My setup goals: No parity drive - mostly media files that are easily replaceable 512GB M.2 SSD - cache drive for Sabnzbd extraction and Docker databases 4TB WD Purple - dedicated to Frigate (security camera footage) 2x 8TB WD Red - documents and photos with file duplication/mirroring Remaining drives (~9 drives) - simple media storage for Plex (no protection) Does this approach make sense, or are there better practices I should consider? Any feedback appreciated! Your Drive Setup Summary Total: ~106TB raw capacity Unraid target configuration: 🟣 WD Purple (4TB) - Frigate only 🔴 2x WD Red (8TB) - Documents/photos with duplication 📦 9x Mixed drives - Media storage (no protection) 💾 SSD 512GB - Cache drive for databases/Docker Migration Strategy: "Rolling Consolidation" Since you have no parity, this is actually easier! We'll consolidate data onto larger drives first, then build Unraid array. Phase 1: Preparation (Still in Windows) Goal: Consolidate all data onto 8-9 drives, leaving 4-5 drives empty Step 1: Calculate your actual data Move all data TO these drives (keep full): 1. ✅ 12TB WD (Drive 1) 2. ✅ 10TB WD (Drive 2) 3. ✅ 18TB WD (Drive 5) 4. ✅ 8TB SMR (Drive 3) 5. ✅ 8TB SMR (Drive 4) 6. ✅ 8TB SMR (Drive 6) 7. ✅ 8TB SMR (Drive 7) 8. ✅ 8TB SMR (Drive 8) Leave EMPTY (or minimal data): - ⬜ 8TB SMR (Drive 9) - ⬜ 8TB WD Red (Drive 10) - ⬜ 4TB WD Purple (Drive 11) - ⬜ 8TB WD Red (Drive 12) - ⬜ 512GB SSD (Drive 13) **In DrivePool, use "File Placement" rules:** ``` - Move data to fills drives 1-8 completely - Empty drives 9, 10, 11, 12, 13 ## **Phase 2: Create Initial Unraid Array** **Shutdown Windows → Boot Unraid USB** **Initial Unraid array (NO PARITY):** ``` Array Configuration: ├─ Cache: 512GB SSD (XFS) ├─ Disk 1: 8TB SMR (Drive 9) - WILL BE FORMATTED ├─ Disk 2: 8TB Red (Drive 10) - WILL BE FORMATTED ├─ Disk 3: 4TB Purple (Drive 11) - WILL BE FORMATTED └─ Disk 4: 8TB Red (Drive 12) - WILL BE FORMATTED Total: 32TB usable (all formatted XFS) Unassigned (keep NTFS, read-only): Drive 1-8 (all your data is here) Format and start array - This gives you 32TB to work with. Phase 3: Copy Data Stage 1 Install plugins: bash # In Unraid Community Applications → Install: - Unassigned Devices - Dynamix File Manager (optional) - MC (Midnight Commander) via Nerd Tools Mount old drives: Go to: Main → Unassigned Devices Mount drives 1-8 as read-only They appear as: /mnt/disks/WD120EDJAZ/, etc. Copy data: bash # For each NTFS drive cd /mnt/disks/[DRIVE_NAME]/PoolPart.xxx/ # Copy to Unraid user shares rsync -avh --progress --ignore-existing ./ /mnt/user/media/ # For SMR drives (slower), use: rsync -avh --progress --no-compress --ignore-existing ./ /mnt/user/media/ ``` **Strategy:** - Copy from Drive 3 (8TB SMR) first → takes ~24 hours - Verify copy completed - Once Drive 3 is empty, stop array --- ## **Phase 4: Expand Array (Repeat)** **Add Drive 3 to array:** 1. Stop Unraid array 2. Go to Main → Array Devices 3. Assign Drive 3 (8TB SMR) to next available slot 4. Start array → formats Drive 3 as XFS 5. Now you have 40TB usable **Repeat copy process:** - Copy from Drive 4 → Add Drive 4 to array - Copy from Drive 6 → Add Drive 6 to array - Continue until all drives added --- ## **Phase 5: Final Unraid Configuration** Once all data copied and all drives in array: **Create shares with specific allocations:** **1. Frigate Share (Purple drive only):** ``` Share: frigate Included disks: disk3 (Purple 4TB) Excluded disks: All others ``` **2. Documents Share (Both Reds with duplication):** ``` Share: documents Included disks: disk2, disk4 (both 8TB Reds) Allocation method: High-water Minimum free space: 10GB # Enable duplication at share level (not drive level) # Use Unraid's "User Share Copy" plugin or manually rsync ``` **3. Media Share (Everything else):** ``` Share: media Included disks: disk1, disk5-13 (all others) Allocation method: Most-free Split level: Automatically split Order of Drive Addition (Optimized) Copy priority (fastest first): Drive 9 (8TB SMR) → already empty, format first Drive 10 (8TB Red) → already empty, format first Drive 11 (4TB Purple) → already empty, format first Drive 12 (8TB Red) → already empty, format first Then copy from and add: Drive 3 (8TB SMR) → 24h copy Drive 4 (8TB SMR) → 24h copy Drive 6 (8TB SMR) → 24h copy Drive 7 (8TB SMR) → 24h copy Drive 8 (8TB SMR) → 24h copy Drive 2 (10TB WD) → 30h copy Drive 1 (12TB WD) → 36h copy Drive 5 (18TB WD) → 48h copy (LAST - biggest) Keep SSD (Drive 13) for cache throughout.