lessismore

Alright @JorgeB, seems things are back on track. Appreciate all the help!

Thanks, I started the array and am not seeing the error anymore. Not sure what you meant by check the lost+found, but attached is a list of the files. lost+found directory.txt

I ran it with option -v to repair Then ran a check again with option -nv. Both logs attached. Repair 20230619 option -v.txt Check after Repair 20230619 option -nv.txt tower-diagnostics-20230619-1105.zip

I ran the Filesystem Check with option -nv. It completed in only 49 seconds. Below is a copy and paste of the status output from within the Unraid GUI as well as another diagnostic pack. Check Filesystem Log 20230616 084149.txt tower-diagnostics-20230616-0843.zip

Oops sorry. Here it is: tower-diagnostics-20230615-1057.zip

Thanks JorgeB. I've updated to v6.11.5 then rebooted. I haven't started the array yet. Here are the diagnostics:tower-diagnostics-20230614-1522.zip

Thanks, here is the diagnostics and the two extended SMART reports for the two drives that make up my array. I have two parity drives that I'm running extended SMART test on now. These 4 drives make up my total unraid setup. tower-diagnostics-20230613-1513.ziptower-smart-20230613-1509.ziptower-smart-20230613-1510.zip

Hi, I could use some help with the below syslog errors. It doesn't seem to affecting operation of my Unraid server, but I feel like I better fix it. I am in the process of running SMART extended tests on both of my array disks. I understand that I need to Start my array in Maintenance Mode then through the webgui, do a filesystem check. Is this equivalent to running xfs_repair? The error references "dm-1", how do I identify which disk has the issue? I ran the below commands to identify the "dm-1" KNAME. SYSLOG ERRORS Jun 9 10:58:48 Tower kernel: XFS (dm-1): Metadata CRC error detected at xfs_dir3_block_read_verify+0x7c/0xf1 [xfs], xfs_dir3_block block 0x182ba4640 Jun 9 10:58:48 Tower kernel: XFS (dm-1): Unmount and run xfs_repair Jun 9 10:58:48 Tower kernel: XFS (dm-1): First 128 bytes of corrupted metadata buffer: Jun 9 10:58:48 Tower kernel: 00000000: 39 73 00 a0 57 58 2e 37 bc 03 a3 8d 69 e2 d7 c3 9s..WX.7....i... Jun 9 10:58:48 Tower kernel: 00000010: 7b a5 40 fa d6 72 05 af 72 7e 97 87 88 60 28 10 {[email protected]~...`(. Jun 9 10:58:48 Tower kernel: 00000020: ec 40 a5 a7 6a 38 a5 8b 7a 80 31 fd e4 60 b9 03 [email protected]..`.. Jun 9 10:58:48 Tower kernel: 00000030: 77 e0 6a 20 2a c6 cf 7d 4d 56 9f 9d f6 fa a3 46 w.j *..}MV.....F Jun 9 10:58:48 Tower kernel: 00000040: 30 93 45 ef 67 1b 65 95 36 81 25 ba 93 21 ed 5c 0.E.g.e.6.%..!.\ Jun 9 10:58:48 Tower kernel: 00000050: 6d 33 ab dd 30 72 42 80 74 67 12 10 16 56 ae 33 m3..0rB.tg...V.3 Jun 9 10:58:48 Tower kernel: 00000060: 64 15 29 7c e9 55 e4 13 0d ba 0c c0 66 d7 6d 3d d.)|.U......f.m= Jun 9 10:58:48 Tower kernel: 00000070: 2d b5 0d 0f af d4 45 42 d0 3e ed 53 06 73 d0 ea -.....EB.>.S.s.. Jun 9 10:58:48 Tower kernel: XFS (dm-1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x182ba4640 len 8 error 74 Jun 9 10:58:58 Tower kernel: XFS (dm-1): Metadata corruption detected at xfs_dir3_data_reada_verify+0x53/0x64 [xfs], xfs_dir3_data_reada block 0x182ba4640 Jun 9 10:58:58 Tower kernel: XFS (dm-1): Unmount and run xfs_repair Jun 9 10:58:58 Tower kernel: XFS (dm-1): First 128 bytes of corrupted metadata buffer: Jun 9 10:58:58 Tower kernel: 00000000: 39 73 00 a0 57 58 2e 37 bc 03 a3 8d 69 e2 d7 c3 9s..WX.7....i... Jun 9 10:58:58 Tower kernel: 00000010: 7b a5 40 fa d6 72 05 af 72 7e 97 87 88 60 28 10 {[email protected]~...`(. Jun 9 10:58:58 Tower kernel: 00000020: ec 40 a5 a7 6a 38 a5 8b 7a 80 31 fd e4 60 b9 03 [email protected]..`.. Jun 9 10:58:58 Tower kernel: 00000030: 77 e0 6a 20 2a c6 cf 7d 4d 56 9f 9d f6 fa a3 46 w.j *..}MV.....F Jun 9 10:58:58 Tower kernel: 00000040: 30 93 45 ef 67 1b 65 95 36 81 25 ba 93 21 ed 5c 0.E.g.e.6.%..!.\ Jun 9 10:58:58 Tower kernel: 00000050: 6d 33 ab dd 30 72 42 80 74 67 12 10 16 56 ae 33 m3..0rB.tg...V.3 Jun 9 10:58:58 Tower kernel: 00000060: 64 15 29 7c e9 55 e4 13 0d ba 0c c0 66 d7 6d 3d d.)|.U......f.m= Jun 9 10:58:58 Tower kernel: 00000070: 2d b5 0d 0f af d4 45 42 d0 3e ed 53 06 73 d0 ea -.....EB.>.S.s.. Jun 9 10:58:58 Tower kernel: XFS (dm-1): Metadata CRC error detected at xfs_dir3_block_read_verify+0x7c/0xf1 [xfs], xfs_dir3_block block 0x182ba4640 Jun 9 10:58:58 Tower kernel: XFS (dm-1): Unmount and run xfs_repair Jun 9 10:58:58 Tower kernel: XFS (dm-1): First 128 bytes of corrupted metadata buffer: Jun 9 10:58:58 Tower kernel: 00000000: 39 73 00 a0 57 58 2e 37 bc 03 a3 8d 69 e2 d7 c3 9s..WX.7....i... Jun 9 10:58:58 Tower kernel: 00000010: 7b a5 40 fa d6 72 05 af 72 7e 97 87 88 60 28 10 {[email protected]~...`(. Jun 9 10:58:58 Tower kernel: 00000020: ec 40 a5 a7 6a 38 a5 8b 7a 80 31 fd e4 60 b9 03 [email protected]..`.. Jun 9 10:58:58 Tower kernel: 00000030: 77 e0 6a 20 2a c6 cf 7d 4d 56 9f 9d f6 fa a3 46 w.j *..}MV.....F Jun 9 10:58:58 Tower kernel: 00000040: 30 93 45 ef 67 1b 65 95 36 81 25 ba 93 21 ed 5c 0.E.g.e.6.%..!.\ Jun 9 10:58:58 Tower kernel: 00000050: 6d 33 ab dd 30 72 42 80 74 67 12 10 16 56 ae 33 m3..0rB.tg...V.3 Jun 9 10:58:58 Tower kernel: 00000060: 64 15 29 7c e9 55 e4 13 0d ba 0c c0 66 d7 6d 3d d.)|.U......f.m= Jun 9 10:58:58 Tower kernel: 00000070: 2d b5 0d 0f af d4 45 42 d0 3e ed 53 06 73 d0 ea -.....EB.>.S.s.. Jun 9 10:58:58 Tower kernel: XFS (dm-1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x182ba4640 len 8 error 74 root@Tower:~# lsblk --output NAME,KNAME,TYPE,SIZE,MOUNTPOINT NAME KNAME TYPE SIZE MOUNTPOINT loop0 loop0 loop 116.8M /lib/firmware loop1 loop1 loop 19.4M /lib/modules sda sda disk 14.3G └─sda1 sda1 part 14.3G /boot sdb sdb disk 232.9G └─sdb1 sdb1 part 232.9G sdc sdc disk 5.5T └─sdc1 sdc1 part 5.5T sdd sdd disk 3.6T └─sdd1 sdd1 part 3.6T sde sde disk 3.6T └─sde1 sde1 part 3.6T sdf sdf disk 3.6T └─sdf1 sdf1 part 3.6T md1 md1 md 3.6T └─md1 dm-0 crypt 3.6T md2 md2 md 3.6T └─md2 dm-1 crypt 3.6T PS: I found this related forum post for guidance and also the Unraid Wiki: https://docs.unraid.net/legacy/FAQ/check-disk-filesystems/

Edit: Solved (sort of). I upgraded to Unraid 6.9.0-rc2 and followed the directions here to unblacklist the i915 gpu. I didn't do anything else except for add /dev/dri device passthrough to the Plex container as per lotetreemedia guide below (the /dev/dri directory already exists!). Basically it just works out the gate! Nice to see my cpu hovering below 40% Hi, hopefully I'm not hijacking the thread from anyone. Unraid 6.8.3 Linuxserver/plex:latest J5040 Plex Pass Use hardware acceleration when available is enabled. Onboard GPU is enabled in BIOS I am having issues with enabling hw transcode. I followed the guide here: I may have had tired eyes late at night, but starting from a blank slate (had not previously installed a plex docker container) I followed the above directions and got the (hw) to show up when transcoding. After a reboot (I modified the /boot/config/go as suggested in the guide) it wasn't working any more. Since then I've tried running through the steps again, removing and reinstalling the container, deleting the plex appdata and using different plex containers. It's been really frustrating since I think I had it working the very first time... Here are the steps I took: Linux 4.19.107-Unraid. root@Tower:~# cd /dev/dri -bash: cd: /dev/dri: No such file or directory root@Tower:~# modprobe i915 root@Tower:~# cd /dev/dri root@Tower:/dev/dri# ls by-path/ card0 renderD128 root@Tower:/dev/dri# chmod -R 777 /dev/dri root@Tower:/# docker exec -it plex bash root@Tower:/# cd /dev/dri root@Tower:/dev/dri# ls -la total 0 drwxr-xr-x 2 root root 80 Dec 30 16:32 . drwxr-xr-x 6 root root 360 Dec 30 16:32 .. crwxrwxrwx 1 root videoYn41fhzr 226, 0 Dec 30 16:32 card0 crwxrwxrwx 1 root videoYn41fhzr 226, 128 Dec 30 16:32 renderD128 I then added the /dev/dri Device to the Docker container and started it. As you can see, no hardware decoding and cpu is between 80% and 100%. This is from my plex log Main 10 profile bitstream Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Decoding SPS Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Main 10 profile bitstream Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Decoding VUI Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Decoding PPS Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Format vaapi_vld chosen by get_format(). Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Format vaapi_vld requires hwaccel initialisation. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Considering format 0x30313050 -> p010le. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Picked p010le (0x30313050) as best match for yuv420p10le. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Direct mapping possible. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x1. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x2. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x3. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x4. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x5. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x6. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x7. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x8. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x9. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0xa. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0xb. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0xc. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0xd. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0xe. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0xf. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x10. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x11. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x12. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Created surface 0x13. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Considering format 0x30313050 -> p010le. Dec 30, 2020 12:53:49.611 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Picked p010le (0x30313050) as best match for yuv420p10le. Dec 30, 2020 12:53:49.613 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Decode context initialised: 0x16/0x10000000. Dec 30, 2020 12:53:49.614 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Param buffer (type 0, 604 bytes) is 0. Dec 30, 2020 12:53:49.614 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Slice 0 param buffer (264 bytes) is 0x1. Dec 30, 2020 12:53:49.614 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Slice 0 data buffer (47 bytes) is 0x2. Dec 30, 2020 12:53:49.614 [0x14fa9c7cf700] DEBUG - [Transcode] [FFMPEG] - Decode to surface 0x13. Dec 30, 2020 12:53:49.615 [0x14fa9c7cf700] ERROR - [Transcode] [FFMPEG] - Failed to end picture decode issue: 23 (internal decoding error). Dec 30, 2020 12:53:49.615 [0x14fa9c7cf700] ERROR - [Transcode] [FFMPEG] - hardware accelerator failed to decode picture plexserverlog.txt

I have a Sandisk Ultra Fit too. I couldn't get the flash creator to recognise the USB. I also couldn't do it manually either (I can't recall the exact error, something about permission denied). Turning off Windows Controlled Folder Access helped me progress a bit more, but I couldn't get it working. Instead I did it manually on my Linux nuc.