veri745

My unraid USB has been in use for several years now. I've just been upgrading my parity drive and swapping in another larger drive. I went to reboot and my server didn't come back up. Plugged in a monitor and I see this error message about `/boot` failing to mount. I tried a couple other USB ports with the same error. I plugged my USB into my Windows machine and it mounts just fine. Advice on how to fix?

No joy after all, same error last night: May 6 02:40:05 Tower kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 May 6 02:40:05 Tower kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? May 6 02:40:05 Tower kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug May 6 02:40:06 Tower kernel: nvme 0000:09:00.0: enabling device (0000 -> 0002) May 6 02:40:06 Tower kernel: nvme nvme0: Removing after probe failure status: -19 May 6 02:40:06 Tower kernel: nvme0n1: detected capacity change from 976773168 to 0 May 6 02:40:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### May 6 02:40:06 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x1455f8f0 len 0 err no 10 May 6 02:40:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 May 6 02:40:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 May 6 02:40:06 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x5f0bac0 len 0 err no 10 May 6 02:40:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 4, rd 1, flush 0, corrupt 0, gen 0 May 6 02:40:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 5, rd 1, flush 0, corrupt 0, gen 0 May 6 02:40:06 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x14dbad78 len 0 err no 10 May 6 02:40:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 6, rd 1, flush 0, corrupt 0, gen 0 May 6 02:40:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 7, rd 1, flush 0, corrupt 0, gen 0 May 6 02:40:06 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x799ede0 len 0 err no 10 May 6 02:40:06 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x14f257e8 len 0 err no 10 May 6 02:40:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 8, rd 1, flush 0, corrupt 0, gen 0 May 6 02:40:06 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x14dbad58 len 0 err no 10 May 6 02:40:06 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 9, rd 1, flush 0, corrupt 0, gen 0 May 6 02:40:06 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x14f257c8 len 0 err no 10 May 6 02:40:06 Tower kernel: I/O error, dev loop2, sector 6879848 op 0x1:(WRITE) flags 0x8800 phys_seg 8 prio class 0 May 6 02:40:06 Tower kernel: BTRFS warning (device loop2): direct IO failed ino 10754 rw 1,34817 sector 0x68fa68 len 0 err no 10 May 6 02:40:06 Tower kernel: I/O error, dev loop2, sector 206432 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0 May 6 02:40:06 Tower kernel: I/O error, dev loop2, sector 2303584 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0 May 6 02:40:06 Tower kernel: I/O error, dev loop2, sector 206400 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0 May 6 02:40:06 Tower kernel: I/O error, dev loop2, sector 2303552 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0 May 6 02:40:06 Tower kernel: BTRFS: error (device nvme0n1p1: state A) in btrfs_create_new_inode:6442: errno=-5 IO failure May 6 02:40:06 Tower kernel: BTRFS info (device nvme0n1p1: state EA): forced readonly May 6 02:40:06 Tower kernel: BTRFS warning (device nvme0n1p1: state EA): Skipping commit of aborted transaction. May 6 02:40:06 Tower kernel: I/O error, dev loop2, sector 8740264 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0 May 6 02:40:06 Tower kernel: BTRFS warning (device nvme0n1p1: state EA): direct IO failed ino 425294 rw 0,0 sector 0x1137f180 len 4096 err no 10

Never had any issue. I have a dedicated share that I mapped to /temp in the docker config and it works fine. All the space in the image size for me appears to be actual assets, in /usr/lib as well as /app/Tdarr_Server and /app/Tdarr_Node . I guess it's just big

Not sure if this is what did it, but the issue has not reoccurred yet.

I got a new 16TB drive and started a preclear on it. It's 8% of the way through the pre-read cycle and the "udma crc error count" SMART attribute has been climbing steadily, up to 85 at this point. It's on a SATA port where I just installed a new SATA cable, but I'm guessing it's a poor connection for some reason. Should I let the pre-clear continue, or kill it and try to fix? There's another drive doing a pre-clear at the same time with no issues.

Anyone know why my Tdarr and Tdarr_node containers would be multiple gigs each? Name Container Writable Log tdarr 5.58 GB 1.50 GB 11.7 MB tdarr_node 3.73 GB 531 MB 11.5 MB This is from docker -> "Container Size" I got a warning after installing and using Tdarr for a bit that my docker vdisk was almost full *edit* I verified that my transcode cache for all of my libraries is properly mapped to a `transcode_cache` share on my cache drive, not in the image

I found all my docker containers unresponsive this morning. It appears my NVMe cache drive encountered some errors and went into read-only mode. What steps should I take to investigate/resolve the issue? Apr 27 00:00:01 Tower Plugin Auto Update: Checking for available plugin updates Apr 27 00:00:01 Tower Docker Auto Update: Community Applications Docker Autoupdate running Apr 27 00:00:01 Tower Docker Auto Update: Checking for available updates Apr 27 00:00:06 Tower Plugin Auto Update: community.applications.plg version 2023.04.26b does not meet age requirements to update - 1 days old Apr 27 00:00:06 Tower Plugin Auto Update: compose.manager.plg version 2023.04.27 does not meet age requirements to update - 0 days old Apr 27 00:00:07 Tower Plugin Auto Update: Checking for language updates Apr 27 00:00:07 Tower Plugin Auto Update: Community Applications Plugin Auto Update finished Apr 27 00:00:28 Tower Docker Auto Update: No updates will be installed Apr 27 00:19:08 Tower emhttpd: spinning down /dev/sdd Apr 27 00:19:08 Tower emhttpd: spinning down /dev/sde Apr 27 00:19:37 Tower emhttpd: spinning down /dev/sdb Apr 27 00:19:51 Tower emhttpd: spinning down /dev/sdf Apr 27 00:23:53 Tower emhttpd: read SMART /dev/sdg Apr 27 00:23:53 Tower emhttpd: read SMART /dev/sde Apr 27 00:36:07 Tower emhttpd: read SMART /dev/sdb Apr 27 00:40:07 Tower emhttpd: read SMART /dev/sdf Apr 27 00:55:24 Tower emhttpd: spinning down /dev/sde Apr 27 01:09:05 Tower emhttpd: spinning down /dev/sdb Apr 27 01:13:05 Tower emhttpd: spinning down /dev/sdg Apr 27 01:13:05 Tower emhttpd: spinning down /dev/sdf Apr 27 02:07:29 Tower emhttpd: read SMART /dev/sdb Apr 27 02:07:48 Tower emhttpd: read SMART /dev/sde Apr 27 02:08:24 Tower emhttpd: read SMART /dev/sdd Apr 27 02:38:25 Tower emhttpd: spinning down /dev/sdb Apr 27 03:14:24 Tower kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 Apr 27 03:14:24 Tower kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? Apr 27 03:14:24 Tower kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug Apr 27 03:14:24 Tower kernel: nvme0n1: I/O Cmd(0x2) @ LBA 639968960, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Apr 27 03:14:24 Tower kernel: I/O error, dev nvme0n1, sector 639968960 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Apr 27 03:14:24 Tower kernel: nvme0n1: I/O Cmd(0x2) @ LBA 639968976, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Apr 27 03:14:24 Tower kernel: I/O error, dev nvme0n1, sector 639968976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Apr 27 03:14:24 Tower kernel: nvme 0000:09:00.0: enabling device (0000 -> 0002) Apr 27 03:14:24 Tower kernel: nvme nvme0: Removing after probe failure status: -19 Apr 27 03:14:24 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0 Apr 27 03:14:24 Tower kernel: nvme0n1: detected capacity change from 976773168 to 0 Apr 27 03:14:24 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0 Apr 27 03:14:24 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0 Apr 27 03:14:24 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 2, rd 2, flush 0, corrupt 0, gen 0 Apr 27 03:14:24 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 3, rd 2, flush 0, corrupt 0, gen 0 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0xe028bc8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x8b0868 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 4, rd 2, flush 0, corrupt 0, gen 0 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x9c4af0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: I/O error, dev loop2, sector 9709456 op 0x1:(WRITE) flags 0x8800 phys_seg 10 prio class 0 Apr 27 03:14:24 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 5, rd 2, flush 0, corrupt 0, gen 0 Apr 27 03:14:24 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 6, rd 2, flush 0, corrupt 0, gen 0 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x9c5350 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Apr 27 03:14:24 Tower kernel: BTRFS warning (device loop2): direct IO failed ino 9757 rw 1,34817 sector 0x942790 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 7, rd 2, flush 0, corrupt 0, gen 0 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 1,34817 sector 0x871130 len 0 err no 10 Apr 27 03:14:24 Tower kernel: I/O error, dev loop2, sector 894240 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0 Apr 27 03:14:24 Tower kernel: I/O error, dev loop2, sector 2991392 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0 Apr 27 03:14:24 Tower kernel: I/O error, dev loop2, sector 897600 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0 Apr 27 03:14:24 Tower kernel: I/O error, dev loop2, sector 2994752 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 0 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdc21160 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00b1a0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00b1a8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00b1b0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00b1b8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00b1c0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00b1c8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00b1d0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00b1d8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a508 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a510 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a518 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a520 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a528 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a530 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a538 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a540 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a548 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a550 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a558 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x524a560 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f6d8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f6e0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f6e8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f6f0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f6f8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f700 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f708 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f710 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f718 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f720 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xe00f728 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd564b8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd564c0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd564c8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd564d0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd564d8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd564e0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd564e8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd564f0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd564f8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd56500 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd56508 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd56510 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xdd56518 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x95b1fd0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x95b1fd8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x95b1fe0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x95b1fe8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x95b1ff0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x95b1ff8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x95b2000 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x95b2008 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x95b2010 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5238150 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5238158 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5238160 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5238168 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5238170 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5238178 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5238180 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5238188 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5238190 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5238198 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x52381a0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x52381a8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5239868 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5239870 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5239878 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5239880 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5239888 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5239890 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5239898 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5236c60 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5236c68 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5236c70 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5236c78 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5236c80 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5236c88 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5236c90 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5236c98 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0x5236ca0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef1b8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef1c0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef1c8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef1d0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef1d8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef1e0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef1e8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef1f0 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef1f8 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef200 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xddef208 len 0 err no 10 Apr 27 03:14:24 Tower kernel: BTRFS warning (device nvme0n1p1): direct IO failed ino 425294 rw 0,0 sector 0xde00880 len 0 err no 10 Apr 27 03:14:24 Tower kernel: I/O error, dev loop2, sector 8742272 op 0x0:(READ) flags 0x0 phys_seg 9 prio class 0 Apr 27 03:14:24 Tower kernel: I/O error, dev loop2, sector 9336344 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0 Apr 27 03:14:24 Tower kernel: I/O error, dev loop2, sector 10100888 op 0x0:(READ) flags 0x0 phys_seg 12 prio class 0 Apr 27 03:14:24 Tower kernel: BTRFS: error (device loop2: state A) in btrfs_run_delayed_refs:2157: errno=-5 IO failure Apr 27 03:14:24 Tower kernel: BTRFS info (device loop2: state EA): forced readonly Apr 27 03:14:24 Tower kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1982: errno=-5 IO failure Apr 27 03:14:24 Tower kernel: BTRFS: error (device nvme0n1p1) in btrfs_commit_transaction:2418: errno=-5 IO failure (Error while writing out transaction) Apr 27 03:14:24 Tower kernel: BTRFS info (device nvme0n1p1: state E): forced readonly Apr 27 03:14:24 Tower kernel: BTRFS: error (device nvme0n1p1: state EA) in cleanup_transaction:1982: errno=-5 IO failure Apr 27 03:14:24 Tower rsyslogd: file '/mnt/user/syslog/syslog-192.168.1.200.log'[10] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: Read-only file system [v8.2102.0 try https://www.rsyslog.com/e/2027 ] ### [PREVIOUS LINE REPEATED 3 TIMES] ### tower-diagnostics-20230427-0726.zip

Is there a way to get my PIA credentials out of plaintext VPN_PASSWORD and VPN_USERNAME fields in the docker template and into the credentials.conf file directly? It works if I change my template from "PIA" to "custom", but I'm not what I'm losing in that case.

Yeah, my log continues on: 2022-04-19 21:06:24 TUN/TAP device tun0 opened 2022-04-19 21:06:24 net_iface_mtu_set: mtu 1500 for tun0 2022-04-19 21:06:24 net_iface_up: set tun0 up 2022-04-19 21:06:24 net_addr_v4_add: www.xxx.yyy.zzz/24 dev tun0 2022-04-19 21:06:24 /root/openvpnup.sh tun0 1500 1553 www.xxx.yyy.zzz 255.255.255.0 init 2022-04-19 21:06:24 Initialization Sequence Completed [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... [info] Successfully retrieved external IP address www.xxx.yyy.zzz [info] Script started to assign incoming port [info] Port forwarding is enabled [info] Checking endpoint 'xxx.xxx.xxx' is port forward enabled... ... [info] Successfully assigned and bound incoming port '24061' [info] qBittorrent incoming port 6881 and VPN incoming port 24061 different, marking for reconfigure [info] Attempting to start qBittorrent... [info] qBittorrent process started Are you sure all necessary ports are mapped properly from your router -> server -> container?

I see that the default qBittorrent releases are back to using libtorrent v1.2, with alternative releases with libtorrent v2. Wouldn't it enhance stability to use the default releases for the unraid image instead? *edit*. The reason I comment is because I have had my version pinned at 4.3.9 since issues with libtorrent v2 cropped up.

No issues so far after moving all drives off of the Marvell controller

This card has an "approved" chipset, but seems really inexpensive. Decent option? https://www.amazon.com/Expansion-Controller-Adapter-Profile-Non-Raid/dp/B09KY3HB8Z/ref=sr_1_6?crid=D0AKVB0XY7UT

Right, I meant that xfs_repair detected a filesystem error after the disk got disabled I had extra ports free on the motherboard, so I moved the two suspect disks to different ports. I will see if that resolves the issue over the next month or two and consider replacing my SATA controller card Thanks

As stated, I'm not aware of any USB -> SATA adapters, but I don't know why you'd want one. USB 3.0 is almost as fast as SATA 3 You could connect such a device to an internal USB header (or multiple)

You can use the built-in sqlite executable. I bookmarked this reddit thread:

By 60gb ssd OS drive, do you mean you're going to dedicate that drive to a VM? Otherwise Unraid doesn't need an OS drive, just a usb flash. 14TB parity drive is 10TB of wasted space if you only have 4TB and smaller drives connected, unless that's what you already have, or you are imminently going to put in another larger data drive 1TB cache is plenty, and yes, you can install later

First step would be post your diagnostics file

A few weeks ago my array went into an error state, and one of the disks went red due to some filesystem corruption It's a relatively new disk, so I ran SMART diagnostics, ran the xfs_repair tool, ran memtest for several hours, and rebuilt the disk back onto itself Since then, I've had several occasions where disk read errors have cropped back up. It's always drives 2 and 4, they always have the same number of read errors, and so far it has resolved itself after a reboot. I am wondering if I experienced some data corruption as part of the initial issue, and the parity was someone incorrect and rebuilt the corrupt data back onto the drive. Attaching my diagnostics from before rebooting (ending 2045, no SMART for the two disks with read errors), and after (ending 2050) tower-diagnostics-20230322-2050.zip tower-diagnostics-20230322-2045.zip

I've been following this thread on Plex's forums for a while now, in hopes that eventually my AMD APU could do gpu transcoding in plex, and it looks like there was some recent progress on getting that working: https://forums.plex.tv/t/got-hw-transcoding-to-work-with-libva-vaapi-on-ryzen-apu-ryzen-7-4700u/676546/310 I was wondering if there was an easy way to integrate the changes to get the amdgpu drivers working into this image, or if there is a guide somewhere for a straightforward way to port my plex library over to a new container

I can report that my Plex container also stopped functioning due to permission errors after upgrading from 6.9 to 6.10. Using the new file explorer plugin, I was able to see that permissions for the "appdata" folder were showing "UNKNOWN" as the owner. Setting ownership of the folder to 'nobody' resolved my issue.

So "Fix Common Problems" didn't report anything after an extended scan, but upon further investigation I noticed that /mnt/user/appdata/binhex-plex/ was showing the owner as `UNKNOWN` I recursively set the owner to `nobody`, and that resolved the issue.

I am getting an looping error after upgrading to Unraid 6.10.2 from 6.9.3 2022-06-01 12:31:09,328 INFO spawned: 'plexmediaserver' with pid 70 2022-06-01 12:31:09,350 DEBG 'plexmediaserver' stderr output: PMS: failure detected. Read/write access is required for path: /config/Plex Media Server 2022-06-01 12:31:09,351 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22716828494304 for <Subprocess at 22716828488832 with name plexmediaserver in state STARTING> (stdout)> 2022-06-01 12:31:09,351 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22716828494352 for <Subprocess at 22716828488832 with name plexmediaserver in state STARTING> (stderr)> 2022-06-01 12:31:09,351 INFO exited: plexmediaserver (exit status 1; not expected) 2022-06-01 12:31:09,351 DEBG received SIGCHLD indicating a child quit Anyone seen this or have an idea how to address it? I've tried restarting the docker image several times

Anyone know if the latest docker image release addresses the RSS feed issue?

Same. working for me with the previous version