Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

NPSF3000

Members
  • Joined

  • Last visited

Everything posted by NPSF3000

  1. Summary: Starting a parity check on Unraid OS 7.0.1 causes an immediate kernel panic due to a crash in the raid6_avx21_gen_syndrome function (AVX2-optimized RAID6 parity code). The parity check thread exits, but the UI misleadingly shows a successful check using old cached data. Confirmed on a Ryzen Threadripper 2920X system with 2 disks (1 parity, 1 data). System Info: Unraid OS: 7.0.1 (kernel 6.6.78-Unraid) CPU: AMD Ryzen Threadripper 2920X (AVX2 supported) Mobo: Gigabyte X399 AORUS PRO-CF Array: 2 disks (1 parity, 1 storage) Cache: 2x 1 TB NVME, mirror. FS: XFS for array, BTRFS cache pool Steps to Reproduce: Boot into Unraid 7.0.1. Go to Main > click "Check Parity". Note that it appears to complete instantly. Check syslog.txt — crash occurs in raid6_avx21_gen_syndrome. Observed Behavior: Kernel panic occurs when AVX2 RAID6 function is invoked. Parity thread unraidd0 exits and never completes. No I/O activity happens. UI displays a false success, recycling old check results. Example UI output: Last checked on Mon 21 Apr 2025 03:06 PM (today) Duration: 15 hours, 9 minutes, 22 seconds. Average speed: 146.7 MB/s Finding 0 errors This result is incorrect — it's recycled from the last valid check from last year (system was offline between checks). Log Excerpt (syslog.txt): Tower kernel: md: recovery thread: check Q ... Tower kernel: general protection fault, maybe for address 0x1 Tower kernel: RIP: raid6_avx21_gen_syndrome+0x80/0x104 Tower kernel: check_parity+0x207/0x354 [md_mod] Tower kernel: unraidd+0xedf/0x1278 [md_mod] Work Around: 1. Open the go file on your Unraid USB boot drive From the Unraid Web UI, click Terminal (top-right), then run: nano /boot/config/go This opens the boot script Unraid runs during startup. 2. Add this line above the line that starts emhttp (usually at the end of the file): modprobe raid6_pq disable_avx2=1 So your go file should look something like: #!/bin/bash modprobe raid6_pq disable_avx2=1 /usr/local/sbin/emhttp 3. Save and exit nano Press Ctrl + O to save the file Press Enter to confirm Press Ctrl + X to exit 4. Reboot server and run check. The UI should show the check being in progress,. Request: Fix or bypass raid6_avx21_gen_syndrome. Detect parity thread crash and prevent false UI success reports, show failed attempts and record in history. Provide UI toggle to disable AVX2 parity calculation for affected CPUs. Logs available upon request. Happy to test future versions or provide diagnostics.
  2. Physically reinstalled the Bluray drive (different sata port etc) and now it seems to work. Went from sr0 | sg3 to sr0 | sg1. root@Tower:~# docker exec MakeMKV lsscsi -g -k ... [2:0:0:0] cd/dvd ASUS BW-16D1HT 3.10 /dev/sr0 /dev/sg1 ... root@Tower:~# docker exec MakeMKV env HOME=/config s6-applyuidgid -u 99 -g 100 -G 19 /opt/makemkv/bin/makemkvcon -r --cache=1 info disc:9999 MSG:1005,0,1,"MakeMKV v1.14.4 linux(x64-release) started","%1 started","MakeMKV v1.14.4 linux(x64-release)" DRV:0,1,999,0,"BD-RE ASUS BW-16D1HT 3.10","","/dev/sr0" DRV:1,256,999,0,"","","" DRV:2,256,999,0,"","","" DRV:3,256,999,0,"","","" DRV:4,256,999,0,"","","" DRV:5,256,999,0,"","","" DRV:6,256,999,0,"","","" DRV:7,256,999,0,"","","" DRV:8,256,999,0,"","","" DRV:9,256,999,0,"","","" DRV:10,256,999,0,"","","" DRV:11,256,999,0,"","","" DRV:12,256,999,0,"","","" DRV:13,256,999,0,"","","" DRV:14,256,999,0,"","","" DRV:15,256,999,0,"","","" MSG:5010,0,0,"Failed to open disc","Failed to open disc" TCOUNT:0 root@Tower:~# ls -l /dev/sr0 /dev/sg1 crw-rw---- 1 root cdrom 21, 1 Sep 2 14:23 /dev/sg1 brw-rw---- 1 root cdrom 11, 0 Sep 2 15:18 /dev/sr0
  3. Hi Djoss, Similar issue to what Tergo247 faced, albeit this is my first time running unraid/makemkv. root@Tower:~# docker exec MakeMKV lsscsi -g -k ... [6:0:0:0] cd/dvd ASUS BW-16D1HT 3.10 /dev/sr0 /dev/sg3 ... root@Tower:~# docker exec MakeMKV env HOME=/config s6-applyuidgid -u 99 -g 100 -G 19 /opt/makemkv/bin/makemkvcon -r --cache=1 info disc:9999 MSG:1005,0,1,"MakeMKV v1.14.4 linux(x64-release) started","%1 started","MakeMKV v1.14.4 linux(x64-release)" MSG:5042,0,0,"The program can't find any usable optical drives.","The program can't find any usable optical drives." DRV:0,256,999,0,"","","" DRV:1,256,999,0,"","","" DRV:2,256,999,0,"","","" DRV:3,256,999,0,"","","" DRV:4,256,999,0,"","","" DRV:5,256,999,0,"","","" DRV:6,256,999,0,"","","" DRV:7,256,999,0,"","","" DRV:8,256,999,0,"","","" DRV:9,256,999,0,"","","" DRV:10,256,999,0,"","","" DRV:11,256,999,0,"","","" DRV:12,256,999,0,"","","" DRV:13,256,999,0,"","","" DRV:14,256,999,0,"","","" DRV:15,256,999,0,"","","" MSG:5010,0,0,"Failed to open disc","Failed to open disc" TCOUNT:0 root@Tower:~# ls -l /dev/sr0 /dev/sg3 crw-rw---- 1 root root 21, 3 Aug 27 19:33 /dev/sg3 brw-rw---- 1 root cdrom 11, 0 Aug 27 19:54 /dev/sr0

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.