that guy

Uhhh... This? UUID: 8c2cf7ae-792d-4e0b-88bb-544a2c6d33e9 Scrub started: Tue Jan 3 11:29:40 2023 Status: finished Duration: 0:03:12 Total to scrub: 918.92GiB Rate: 4.79GiB/s Error summary: verify=310 csum=90910 Corrected: 91220 Uncorrectable: 0 Unverified: 0 Is that all I needed to do? Is that something that I should run on a schedule? I saw the run on schedule just past the manual option, and it's disabled.

My syslog is full of this: Jan 3 08:46:43 Watchtower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 144866576 off 16384 csum 0x8941f998 expected csum 0xf230cf28 mirror 1 Jan 3 08:46:43 Watchtower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 74575594, rd 127015, flush 2688585, corrupt 795283, gen 0 Jan 3 08:46:43 Watchtower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 144866576 off 49152 csum 0x8941f998 expected csum 0xb9fd18fc mirror 1 Jan 3 08:46:43 Watchtower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 74575594, rd 127015, flush 2688585, corrupt 795284, gen 0 Jan 3 08:46:43 Watchtower kernel: repair_io_failure: 4 callbacks suppressed Jan 3 08:46:43 Watchtower kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 144866576 off 16384 (dev /dev/nvme0n1p1 sector 44269288) Jan 3 08:46:43 Watchtower kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 144866576 off 49152 (dev /dev/nvme0n1p1 sector 44269352) Jan 3 08:46:43 Watchtower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 144866576 off 327680 csum 0x8941f998 expected csum 0x0ccf29d1 mirror 1 Jan 3 08:46:43 Watchtower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 74575594, rd 127015, flush 2688585, corrupt 795285, gen 0 Jan 3 08:46:43 Watchtower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 144866576 off 331776 csum 0x8941f998 expected csum 0xf904b254 mirror 1 Jan 3 08:46:43 Watchtower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 74575594, rd 127015, flush 2688585, corrupt 795286, gen 0 Jan 3 08:46:43 Watchtower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 144866576 off 335872 csum 0x8941f998 expected csum 0x5437483e mirror 1 Jan 3 08:46:43 Watchtower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 74575594, rd 127015, flush 2688585, corrupt 795287, gen 0 Jan 3 08:46:43 Watchtower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 144866576 off 339968 csum 0x8941f998 expected csum 0x4f0074a8 mirror 1 Jan 3 08:46:43 Watchtower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 74575594, rd 127015, flush 2688585, corrupt 795288, gen 0 Jan 3 08:46:43 Watchtower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 144866576 off 344064 csum 0x8941f998 expected csum 0x77433822 mirror 1 Jan 3 08:46:43 Watchtower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 74575594, rd 127015, flush 2688585, corrupt 795289, gen 0 Jan 3 08:46:43 Watchtower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 144866576 off 348160 csum 0x8941f998 expected csum 0x3f262c36 mirror 1 Jan 3 08:46:43 Watchtower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 74575594, rd 127015, flush 2688585, corrupt 795290, gen 0 Jan 3 08:46:43 Watchtower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 144866576 off 352256 csum 0x8941f998 expected csum 0x0f648a88 mirror 1 Jan 3 08:46:43 Watchtower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 74575594, rd 127015, flush 2688585, corrupt 795291, gen 0 Jan 3 08:46:43 Watchtower kernel: BTRFS warning (device nvme1n1p1): csum failed root 5 ino 144866576 off 356352 csum 0x8941f998 expected csum 0xd92f4cd2 mirror 1 Jan 3 08:46:43 Watchtower kernel: BTRFS error (device nvme1n1p1): bdev /dev/nvme0n1p1 errs: wr 74575594, rd 127015, flush 2688585, corrupt 795292, gen 0 Jan 3 08:46:43 Watchtower kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 144866576 off 327680 (dev /dev/nvme0n1p1 sector 44269896) Jan 3 08:46:43 Watchtower kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 144866576 off 335872 (dev /dev/nvme0n1p1 sector 44269912) Jan 3 08:46:43 Watchtower kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 144866576 off 331776 (dev /dev/nvme0n1p1 sector 44269904) Jan 3 08:46:43 Watchtower kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 144866576 off 339968 (dev /dev/nvme0n1p1 sector 44269920) Jan 3 08:46:43 Watchtower kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 144866576 off 368640 (dev /dev/nvme0n1p1 sector 44269976) Jan 3 08:46:43 Watchtower kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 144866576 off 401408 (dev /dev/nvme0n1p1 sector 44270040) Jan 3 08:46:43 Watchtower kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 144866576 off 344064 (dev /dev/nvme0n1p1 sector 44269928) Jan 3 08:46:43 Watchtower kernel: BTRFS info (device nvme1n1p1): read error corrected: ino 144866576 off 372736 (dev /dev/nvme0n1p1 sector 44269984) I haven't had any system issues yet, save Plex stopping last night but a system restart fixed that. I've got no smart errors on any drive, cache or array. I ran memtest for 8.5 hours last night, and it passed. All my google searches say either memtest or failing drive, neither of which seem to be the case. I will mention that, according to the device attributes in UnRaid, the drive has a bunch of writes: Data units written 1,365,844,436 [699 TB] which I think is over WD specs for lifetime data writes. Could that be the issue? It's also pretty full, but there is 4GB of free space. I'm kinda at a loss on what to do at this point. Thanks! watchtower-diagnostics-20230103-1106.zip

I'm having issues with this container since I upgraded my server last week. It hasn't work since, and I'm not sure why. It was just a cpu/mobo upgrade, nothing else changed, and all my other containers work fine. This is what the logs say: 2021-06-13 10:46:10,237 DEBG 'start-script' stdout output: 2021-06-13 10:46:10 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2021-06-13 10:46:10 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication 2021-06-13 10:46:10 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication 2021-06-13 10:46:10 TCP/UDP: Preserving recently used remote address: [AF_INET]206.217.216.23:1912 2021-06-13 10:46:10 Socket Buffers: R=[212992->786432] S=[212992->786432] 2021-06-13 10:46:10 UDP link local: (not bound) 2021-06-13 10:46:10 UDP link remote: [AF_INET]206.217.216.23:1912 2021-06-13 10:46:40,170 DEBG 'start-script' stdout output: 2021-06-13 10:46:40 [UNDEF] Inactivity timeout (--ping-restart), restarting 2021-06-13 10:46:40 SIGHUP[soft,ping-restart] received, process restarting 2021-06-13 10:46:40,171 DEBG 'start-script' stdout output: 2021-06-13 10:46:40 DEPRECATED OPTION: ncp-disable. Disabling cipher negotiation is a deprecated debug feature that will be removed in OpenVPN 2.6 2021-06-13 10:46:40,171 DEBG 'start-script' stdout output: 2021-06-13 10:46:40 WARNING: file 'credentials.conf' is group or others accessible 2021-06-13 10:46:40 OpenVPN 2.5.2 [git:makepkg/23ae78e657052748+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 21 2021 2021-06-13 10:46:40 library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10 2021-06-13 10:46:40 Restart pause, 5 second(s) 2021-06-13 10:46:40,170 DEBG 'start-script' stdout output: 2021-06-13 10:46:40 [UNDEF] Inactivity timeout (--ping-restart), restarting 2021-06-13 10:46:40 SIGHUP[soft,ping-restart] received, process restarting 2021-06-13 10:46:40,171 DEBG 'start-script' stdout output: 2021-06-13 10:46:40 DEPRECATED OPTION: ncp-disable. Disabling cipher negotiation is a deprecated debug feature that will be removed in OpenVPN 2.6 2021-06-13 10:46:40,171 DEBG 'start-script' stdout output: 2021-06-13 10:46:40 WARNING: file 'credentials.conf' is group or others accessible 2021-06-13 10:46:40 OpenVPN 2.5.2 [git:makepkg/23ae78e657052748+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 21 2021 2021-06-13 10:46:40 library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10 2021-06-13 10:46:40 Restart pause, 5 second(s)

Amazing, that did the trick! Could've sworn I had tried that, but oh well. Out of curiosity, what's the difference between using extra parameters vs adding a device? Thanks for all your help with this!

Sorry, still new to this unraid stuff! I guess this is what I'm looking for: [cont-init.d] 95-check-qsv.sh: executing... [cont-init.d] 95-check-qsv.sh: Processor: Intel® Core(TM) i3-8100 CPU @ 3.60GHz [cont-init.d] 95-check-qsv.sh: Intel Quick Sync Video not supported: device directory /dev/dri not exposed to the container. [cont-init.d] 95-check-qsv.sh: exited 0. So it's not seeing the device, right? Did I make a typo somewhere in my Extra Parameters or something?

I don't have any lines like that in my log... appdata\HandBrake\log\hb\conversion.log, right? It's attached, if that helps at all... Thanks for the help so far, by the way!

This is all I see in the logs, simply stating it's not supported. Intel says it is though... Is there something else I should be looking for? Cannot load libnvidia-encode.so.1 Cannot load libnvidia-encode.so.1 Cannot load libnvidia-encode.so.1 Cannot load libnvidia-encode.so.1 [17:31:32] hb_init: starting libhb thread [17:31:32] thread 15392a12fb10 started ("libhb") HandBrake 1.2.2 (2019050500) - Linux x86_64 - https://handbrake.fr 4 CPUs detected Opening /watch/Die Hard.mkv... [17:31:32] CPU: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz [17:31:32] - Intel microarchitecture Kaby Lake [17:31:32] - logical processor count: 4 [17:31:32] Intel Quick Sync Video support: no

I'm having issues getting the H.264 (Intel QSV) option to show up in Handbrake. I think I've done everything correctly, but I've obviously missed something, as it's not working. My processor supports it: https://ark.intel.com/content/www/us/en/ark/products/126688/intel-core-i3-8100-processor-6m-cache-3-60-ghz.html I've enabled the iGPU in my system bios. The driver seems to be loading properly - this is the readout from the terminal: root@tower:/dev/dri# ls -l total 0 drwxrwxrwx 2 root root 80 Jul 13 16:58 by-path/ crw-rw---- 1 root video 226, 0 Jul 13 16:58 card0 crwxrwxrwx 1 root video 226, 128 Jul 13 16:58 renderD128 I added the required lines (I think) to my /boot/config/go file # Load the i915 driver. modprobe i915 chmod -R 777 /dev/dri I've entered --device=/dev/dri:/dev/dri under Extra Parameters in the container page. I've tried both the regular and dev branches. I don't see anything in the logs indicating any errors... I'm not sure what I've missed. Help?