Tzundoku

Swapped drives and at the same day the latest stable release dropped so I went with the update as well- no issues so far so either could be the fix. Thanks for your time!

Any chance the issue could be related to something else? I.e. the mobo? I was using a Samsung 870 evo with months of uptime prior to replacing it with the one that is currently going offline. A month or so ago that drive started displaying similar I/O errors whenever I initialized a windows vm (vfio binded ssd which was working fine until last month as well). Thought the 870 evo cache had the issue, hence the replacement.

Should I post diagnostics immediately after powercycling or is the above adequate? Thanks tower-diagnostics-20240325-1636.zip

Thanks for the prompt reply JorgeB. I powercycled as directed but also included the following lines to the syslinux config after going through a couple of other posts: nvme_core.default_ps_max_latency_us=0 pcie_aspm=off Initially everything was working fine, then while watching a movie through Jellyfin shares went out again. Diagnostics taken immediately after. tower-diagnostics-20240325-1615.zip

Hello! I attempted to access some docker services today and realized that the cache drive was "out". The device appears as "Active, normal operation" but there's several errors in its log and most shares are missing. After a clean reboot there was a notification that an unclean shutdown was detected and currently there's a parity check running. Shares are still missing after the reboot. The cache drive is new (~10 days) and was operating with no issues for the past week. Here's the cache drive log: Mar 24 15:56:05 Tower kernel: nvme0n1: p1 Mar 24 15:57:28 Tower emhttpd: Samsung_SSD_990_PRO_with_Heatsink_1TB_S73JNJ0W605701A (nvme0n1) 512 1953525168 Mar 24 15:57:28 Tower emhttpd: import 30 cache device: (nvme0n1) Samsung_SSD_990_PRO_with_Heatsink_1TB_S73JNJ0W605701A Mar 24 15:57:32 Tower emhttpd: read SMART /dev/nvme0n1 Mar 24 15:57:47 Tower emhttpd: shcmd (57): mount -t xfs -o noatime,nouuid /dev/nvme0n1p1 /mnt/cache Mar 24 15:57:47 Tower kernel: XFS (nvme0n1p1): Mounting V5 Filesystem Mar 24 15:57:48 Tower kernel: XFS (nvme0n1p1): Starting recovery (logdev: internal) Mar 24 15:57:48 Tower kernel: XFS (nvme0n1p1): Ending recovery (logdev: internal) Mar 24 16:01:55 Tower kernel: nvme0n1: I/O Cmd(0x2) @ LBA 516769048, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Mar 24 16:01:55 Tower kernel: I/O error, dev nvme0n1, sector 516769048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Mar 24 16:01:55 Tower kernel: nvme0n1: detected capacity change from 1953525168 to 0 Mar 24 16:01:55 Tower kernel: nvme0n1p1: writeback error on inode 1086305362, offset 1630208, sector 989418728 Mar 24 16:01:55 Tower kernel: nvme0n1p1: writeback error on inode 1076556609, offset 0, sector 979578768 Mar 24 16:01:55 Tower kernel: XFS (nvme0n1p1): log I/O error -5 Mar 24 16:01:55 Tower kernel: XFS (nvme0n1p1): Filesystem has been shut down due to log error (0x2). Mar 24 16:01:55 Tower kernel: XFS (nvme0n1p1): Please unmount the filesystem and rectify the problem(s). Mar 24 16:01:55 Tower kernel: XFS (nvme0n1p1): metadata I/O error in "xfs_imap_to_bp+0x50/0x70 [xfs]" at daddr 0x587d2230 len 32 error 5 Mar 24 16:01:55 Tower kernel: nvme0n1p1: writeback error on inode 555942864, offset 0, sector 507454752 Mar 24 16:01:55 Tower kernel: nvme0n1p1: writeback error on inode 536871051, offset 73728, sector 498262064 Mar 24 16:01:55 Tower kernel: nvme0n1p1: writeback error on inode 556136556, offset 86016, sector 507648792 Mar 24 16:01:55 Tower kernel: nvme0n1p1: writeback error on inode 1076717193, offset 0, sector 979739088 Mar 24 16:01:55 Tower kernel: nvme0n1p1: writeback error on inode 536871051, offset 77824, sector 498262072 Mar 24 16:01:55 Tower kernel: nvme0n1p1: writeback error on inode 1626563962, offset 4128768, sector 1508843144 Any ideas? Thanks! tower-diagnostics-20240324-1802.zip

Static IP was already set on the mikrotik router, went and configured it within Unraids network settings as well and then rebooted the router- issue is still there. Attempted to connect via tailscale (plugin) IP, no luck either, had to force reboot.

As the title suggests, I'm losing access to Unraid (unable to ping through router or other LAN devices) if I update/powercycle my router or whenever there is a power outage. I believe its a NIC issue as if I have my Windows VM on at the time (which has a dedicated usb network adapter and a bridged IP from Unraids NIC) the usb adapter (192.168.88.8) retains internet/LAN access while the Virtio interface (192.168.88.7) is down. The issue resolves if I powercycle the server- no luck if I attempt to disable and then re-enable the network port on my (mikrotik) router. Diagnostics and syslog (post-powercycle) are attached. Let me know if there's any other info I can provide. Appreciate your time! tower-diagnostics-20230817-1154.zip tower-syslog-20230817-0858.zip

Welp, phone upload didn't go through, thanks.

As the title suggests, my server hangs (UI and services are completely inaccessible) at random, but usually around array starting. I worked around this in the past by manually starting the array with parity check/docker/vms disabled at first but thats irrelevant since 6.10.3 as it hangs at random. Diagnostics attached, let me know if there's any other info I may provide. Thanks! tower-diagnostics-20220620-1441.zip

Thanks for the reply Squid. I managed to run this .xml template (ignore the description) according to the repositories dockerfile. Only difference is I assigned (P)UID to 99 and (P)GID to 100 instead of the 1337 shown in the dockerfile, if that's relevant. WebUI remains inaccessible. Also added a "WebUI" port to the template pointing to 29316. I'm unsure if I'm currently supposed to configure the .xml according to the example-config.yaml, and which of the parameters are supposed to be configured as environmental variables, volumes, or paths. Thoughts?

Apologies if this is the wrong place to ask this. This is my first attempt at porting a container/creating a template. I'm trying to host a matrix.org bot deployer (maubot) which isn't available as an Unraid template or on Dockerhub, however the docker image can be pulled from gitlab as per the instructions. I had success ("startup actions complete, running forever") with pulling and running the container, updating the .yaml configuration (most probably in an inappropriate manner) and assigning a couple of variables (volume, network..) through portainer (first attempt at learning how to use it). The container runs and can ping/get pinged by other containers on its network, yet when attempting to access the webui as per the instructions I'm unable to connect. I'm currently looking into creating an appropriate template for the container so I can easily edit/play around with the variables. However.. I have no idea what the required environmental variables are and I haven't figured out a way to look them up through the gitlab container link mentioned previously. Edit: I'm guessing the required variables are located in the example-config.yaml. I converted the .yaml to .xml but I'm currently unsure on how to map the variables into the Unraid template/xml. So... any ideas? Thanks for your time!

I thought I had to! I have my ip proxied through cloudflare, unsure if that counts. I just tried adding a CNAME that points valheim.mydomain.com to mydomain.duckns.com, doesn't seem to work though. Just tried accessing through IP and that didn't work either though, so my issue is probably related to my mikrotik router settings not playing well with the containers' fixed IP assigned through unraid (although I can ping the container, its not showing up on my routers IP leases so possible issue there with forwarding traffic). Thanks for the reply!

Hey, thanks for this! I'm having moments of brain lags and can't think through on how to properly configure subdomain redirection on a dynamic IP using cloudflare and duckdns. I'm supposed to add an A record in cloudflare which redirects valheim.mydomain.com to my external IP. Not sure how to properly configure this so it follows duckns?

That worked!

Thanks a bunch. Tried as per the guide, came up with this: I might have misled you as I got confused over what I was seeing: the drive I noticed was btrfs wasn't the nvme cache, the actual nvme cache (similar model to the btrfs one) wasn't appearing in any of my devices (since it dropped offline apparently) and I didn't realize I was looking at the wrong drive. The nvme cache is currently showing (after powering off and taking the server off power for a while), but it appears as a new device if I attempt to set it to the cache pool. The above filesystem status corresponds to the correct nvme drive.