keiser

Super weird! I started having this today with only a few of my proxy hosts, maybe 3 and the rest worked fine. Was pulling my hair out trying to figure out what was going on. I could find no change in NginxProxyManager container that would warrant a new behavior, hadn't updated, made no changes. In case anyone comes here getting: *269 connect() failed (113: No route to host) while connecting to upstream or something similar, I eventually disabled Docker and re-enabled it and it went away. I assume it had something to do with Docker networking being twitchy after I had some unrelated problems a few days ago with my Docker image filling up... then my Plex container had a stuck network connection to br0. This must have stemmed from that.

Wowza lots of corrected errors. Glad no uncorrectable. Nothing has hit syslog since scrub finished, so that's nice. UUID: 56161ede-d5a6-4158-8562-5b225651bee7 Scrub started: Fri Aug 26 10:48:37 2022 Status: finished Duration: 0:12:08 Total to scrub: 394.92GiB Rate: 555.45MiB/s Error summary: verify=21115 csum=29539922 Corrected: 29561037 Uncorrectable: 0 Unverified: 0 Hmm I tried using the old libvirt but got: Libvirt Service failed to start. When I go to turn on VMs here's the syslogs, interesting to see: /mnt/user/system/libvirt/libvirt.img is in-use, cannot mount Aug 26 12:28:25 KeiserUnraid ool www[14975]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply' Aug 26 12:28:25 KeiserUnraid emhttpd: Starting services... Aug 26 12:28:25 KeiserUnraid emhttpd: shcmd (1060): chmod 0777 '/mnt/user/media' Aug 26 12:28:25 KeiserUnraid emhttpd: shcmd (1061): chown 'keiser.admin':'Domain Users' '/mnt/user/media' Aug 26 12:28:25 KeiserUnraid root: chown: invalid user: 'keiser.admin:Domain Users' Aug 26 12:28:25 KeiserUnraid emhttpd: shcmd (1061): exit status: 1 Aug 26 12:28:25 KeiserUnraid emhttpd: shcmd (1062): /etc/rc.d/rc.samba restart Aug 26 12:28:25 KeiserUnraid nmbd[17539]: [2022/08/26 12:28:25.655012, 0] ../../source3/nmbd/nmbd.c:59(terminate) Aug 26 12:28:25 KeiserUnraid nmbd[17539]: Got SIGTERM: going down... Aug 26 12:28:27 KeiserUnraid root: Starting Samba: /usr/sbin/smbd -D Aug 26 12:28:27 KeiserUnraid root: /usr/sbin/nmbd -D Aug 26 12:28:27 KeiserUnraid smbd[20310]: [2022/08/26 12:28:27.810026, 0] ../../source3/auth/auth_util.c:1405(make_new_session_info_guest) Aug 26 12:28:27 KeiserUnraid smbd[20310]: create_local_token failed: NT_STATUS_INVALID_PARAMETER_MIX Aug 26 12:28:27 KeiserUnraid smbd[20310]: [2022/08/26 12:28:27.810059, 0] ../../source3/smbd/server.c:2042(main) Aug 26 12:28:27 KeiserUnraid smbd[20310]: ERROR: failed to setup guest info. Aug 26 12:28:27 KeiserUnraid root: /usr/sbin/wsdd Aug 26 12:28:27 KeiserUnraid nmbd[20315]: [2022/08/26 12:28:27.818340, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Aug 26 12:28:27 KeiserUnraid nmbd[20315]: daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections Aug 26 12:28:27 KeiserUnraid root: /usr/sbin/winbindd -D Aug 26 12:28:27 KeiserUnraid winbindd[20325]: [2022/08/26 12:28:27.842505, 0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache) Aug 26 12:28:27 KeiserUnraid winbindd[20325]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Aug 26 12:28:27 KeiserUnraid winbindd[20325]: [2022/08/26 12:28:27.842683, 0] ../../source3/winbindd/winbindd_util.c:1283(init_domain_list) Aug 26 12:28:27 KeiserUnraid winbindd[20325]: Could not fetch our SID - did we join? Aug 26 12:28:27 KeiserUnraid winbindd[20325]: [2022/08/26 12:28:27.842695, 0] ../../source3/winbindd/winbindd.c:1455(winbindd_register_handlers) Aug 26 12:28:27 KeiserUnraid winbindd[20325]: unable to initialize domain list Aug 26 12:28:42 KeiserUnraid emhttpd: shcmd (1081): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 Aug 26 12:28:43 KeiserUnraid root: /mnt/user/system/libvirt/libvirt.img is in-use, cannot mount Aug 26 12:28:43 KeiserUnraid emhttpd: shcmd (1081): exit status: 1 Aug 26 12:28:51 KeiserUnraid nmbd[20315]: [2022/08/26 12:28:51.221565, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Aug 26 12:28:51 KeiserUnraid nmbd[20315]: ***** Aug 26 12:28:51 KeiserUnraid nmbd[20315]: Aug 26 12:28:51 KeiserUnraid nmbd[20315]: Samba name server KEISERUNRAID is now a local master browser for workgroup KEISER on subnet 172.17.0.1 Aug 26 12:28:51 KeiserUnraid nmbd[20315]: Aug 26 12:28:51 KeiserUnraid nmbd[20315]: ***** Aug 26 12:28:51 KeiserUnraid nmbd[20315]: [2022/08/26 12:28:51.221628, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Aug 26 12:28:51 KeiserUnraid nmbd[20315]: ***** Aug 26 12:28:51 KeiserUnraid nmbd[20315]: Aug 26 12:28:51 KeiserUnraid nmbd[20315]: Samba name server KEISERUNRAID is now a local master browser for workgroup KEISER on subnet 10.126.40.20 Aug 26 12:28:51 KeiserUnraid nmbd[20315]: Aug 26 12:28:51 KeiserUnraid nmbd[20315]: *****

Funny you ask that. I just happened to notice something weird that I have a system directory inside my system directory with duplicate docker/libvirt from June 19. I might have increased my docker image file from 20 to 40 GB at that date. I should be able to just copy over it and call it a day right? Do I need to do that with array up and then restart array? What is the process there. root@KeiserUnraid:/mnt/cache/system# ls -alhR .: total 16K drwxrwxrwx 1 1689780724 1689780737 38 Jun 19 05:15 ./ drwxrwxrwx 1 1689780724 1689780737 48 Jun 19 03:07 ../ drwxrwxrwx 1 root root 48 Aug 26 08:34 docker/ drwxrwxrwx 1 root root 22 Aug 26 09:02 libvirt/ drwxrwxrwx 1 1689780724 1689780737 26 May 31 2020 system/ ./docker: total 80G drwxrwxrwx 1 root root 48 Aug 26 08:34 ./ drwxrwxrwx 1 1689780724 1689780737 38 Jun 19 05:15 ../ -rw-rw-rw- 1 nobody users 40G Aug 26 10:44 docker.img -rw-rw-rw- 1 root root 40G Aug 26 08:37 docker.img.bak ./libvirt: total 1.0G drwxrwxrwx 1 root root 22 Aug 26 09:02 ./ drwxrwxrwx 1 1689780724 1689780737 38 Jun 19 05:15 ../ -rw-rw-rw- 1 nobody users 1.0G Aug 26 08:09 libvirt.img ./system: total 0 drwxrwxrwx 1 1689780724 1689780737 26 May 31 2020 ./ drwxrwxrwx 1 1689780724 1689780737 38 Jun 19 05:15 ../ drwxrwxrwx 1 root root 20 May 31 2020 docker/ drwxrwxrwx 1 root root 22 May 31 2020 libvirt/ ./system/docker: total 20G drwxrwxrwx 1 root root 20 May 31 2020 ./ drwxrwxrwx 1 1689780724 1689780737 26 May 31 2020 ../ -rw-rw-rw- 1 nobody users 20G Jun 19 05:15 docker.img ./system/libvirt: total 1.0G drwxrwxrwx 1 root root 22 May 31 2020 ./ drwxrwxrwx 1 1689780724 1689780737 26 May 31 2020 ../ -rw-rw-rw- 1 nobody users 1.0G Jun 19 05:15 libvirt.img And thanks I'll start on the BTRFS scrub. Appreciate the help.

Found this: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Looks like I can just do scrub from the GUI, is that best first action?

Forgot to leave my Diagnostics file, it's attached. keiserunraid-diagnostics-20220826-0956.zip

Hi Team, Please help! Woke up in the morning and found applications misbehaving (noticed because BitWarden was refusing to MFA) and turns out the whole server was down, was unable to ping it so obviously all Docker containers were nonfunctional. I did connect a portable monitor to the HDMI however had no signal and no keyboard/mouse near it to test waking it up with some input. 10 Gb interface link actually appeared to be up based on lights. Ended up hitting the power button once, maybe I should have waited a much longer time for a graceful shutdown, but I may have been impatient. Hard powered it. On power on the portable monitor showed normal boot. Pings started replying and GUI is responsive. I started up the array, however some Docker containers wouldn't start (error 403). Permission issue? Sounds like a full Docker image? Checked on Docker image, it should be fine with plenty of space. I stopped the array and restarted the array. Same issue. About this time I also found my VM (a Windows AD domain controller) was simply missing out of the tab (No Virtual Machines installed). The virtual disk appears to still be there. Definitely not a Docker image issue if it's affecting the VM. Unfortunately local syslog server was not enabled. Just learned about that this morning so it is now enabled and will save to my flash drive. Checking out the syslog since boot shows some BTRFS errors on my cache drive (surprise surprise) where all of my Docker appdata folders and VM vdisk live. Below is an excerpt from syslog and attached is a diagnostics file I generated from Tools. I do have two 1 TB NVMe cache drives in a pool. Are there some BTRFS commands I can run to smooth out recovery of this? Also interestingly, since I've been investigating this more of my Docker containers have started coming online and working, but still a few down. Any of these a good idea? btrfs restore btrfs check —repair /dev/<device_name> btrfs scrub start -Bf /dev/<device_name> Aug 26 10:09:07 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 9835389 off 89989120 csum 0x8941f998 expected csum 0x5f786859 mirror 2 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 47998, gen 0 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 9835389 off 89989120 (dev /dev/nvme0n1p1 sector 365393176) Aug 26 10:09:07 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 9835389 off 59179008 csum 0x8941f998 expected csum 0x4258f56e mirror 2 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 47999, gen 0 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 9835389 off 59183104 csum 0x8941f998 expected csum 0x69b8d6a4 mirror 2 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 48000, gen 0 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 9835389 off 59187200 csum 0x8941f998 expected csum 0x30be874b mirror 2 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 48001, gen 0 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 9835389 off 59191296 csum 0x8941f998 expected csum 0x06d5e54f mirror 2 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 48002, gen 0 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 9835389 off 59195392 csum 0x8941f998 expected csum 0xdc1dc499 mirror 2 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 9835389 off 59240448 csum 0x8941f998 expected csum 0x07f830f0 mirror 2 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 48003, gen 0 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 48004, gen 0 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 9835389 off 59199488 csum 0x8941f998 expected csum 0x3f12127c mirror 2 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 48005, gen 0 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 9835389 off 59203584 csum 0x8941f998 expected csum 0x9bc7d736 mirror 2 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 48006, gen 0 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 9835389 off 59207680 csum 0x8941f998 expected csum 0x34147c17 mirror 2 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 48007, gen 0 Aug 26 10:09:07 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 9835389 off 59191296 (dev /dev/nvme0n1p1 sector 365082704) Aug 26 10:09:07 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 9835389 off 59179008 (dev /dev/nvme0n1p1 sector 365333000) Aug 26 10:09:07 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 9835389 off 59183104 (dev /dev/nvme0n1p1 sector 365333008) Aug 26 10:09:07 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 9835389 off 59195392 (dev /dev/nvme0n1p1 sector 365333032) Aug 26 10:09:07 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 9835389 off 59240448 (dev /dev/nvme0n1p1 sector 365333120) Aug 26 10:09:07 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 9835389 off 59199488 (dev /dev/nvme0n1p1 sector 365333040) Aug 26 10:09:07 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 9835389 off 59207680 (dev /dev/nvme0n1p1 sector 365333056) Aug 26 10:09:07 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 9835389 off 59203584 (dev /dev/nvme0n1p1 sector 365333048) Aug 26 10:09:07 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 9835389 off 59211776 (dev /dev/nvme0n1p1 sector 365333064) Aug 26 10:09:07 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3966877696 wanted 4374590 found 156857 Aug 26 10:09:26 KeiserUnraid kernel: eth0: renamed from veth085e6eb Aug 26 10:09:31 KeiserUnraid kernel: eth0: renamed from veth3f409f6 Aug 26 10:09:31 KeiserUnraid kernel: veth3f409f6: renamed from eth0 Aug 26 10:09:47 KeiserUnraid kernel: btrfs_print_data_csum_error: 6203 callbacks suppressed Aug 26 10:09:47 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 4953896 off 0 csum 0x1e9b9d82 expected csum 0x575f298c mirror 2 Aug 26 10:09:47 KeiserUnraid kernel: btrfs_dev_stat_print_on_error: 6254 callbacks suppressed Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 54420, gen 0 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 4953896 off 4096 csum 0xc23d2ddb expected csum 0xeaff33f3 mirror 2 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 54421, gen 0 Aug 26 10:09:47 KeiserUnraid kernel: repair_io_failure: 6367 callbacks suppressed Aug 26 10:09:47 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 4953896 off 0 (dev /dev/nvme0n1p1 sector 241304) Aug 26 10:09:47 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 4953896 off 4096 (dev /dev/nvme0n1p1 sector 241312) Aug 26 10:09:47 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 4954813 off 73728 csum 0x22cea58f expected csum 0x63c62605 mirror 2 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 54422, gen 0 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 4954813 off 77824 csum 0x8d0b74a2 expected csum 0x9c3d6959 mirror 2 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 54423, gen 0 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 4954813 off 65536 csum 0x510fcf3b expected csum 0x3ec38ce4 mirror 2 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 54424, gen 0 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 4954813 off 69632 csum 0x9d50c2f8 expected csum 0x8698cd4a mirror 2 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 54425, gen 0 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 4954813 off 73728 (dev /dev/nvme0n1p1 sector 824544) Aug 26 10:09:47 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 4954813 off 77824 (dev /dev/nvme0n1p1 sector 824552) Aug 26 10:09:47 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 4954813 off 114688 csum 0xef959b6a expected csum 0xbb19ab3e mirror 2 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 54426, gen 0 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 4954813 off 90112 csum 0xaff8bbba expected csum 0xa4f860ed mirror 2 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 54427, gen 0 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 4954813 off 118784 csum 0x0410962a expected csum 0x201ee439 mirror 2 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 54428, gen 0 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 4954813 off 81920 csum 0x1fd5e356 expected csum 0xd7ff56c7 mirror 2 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1929853063, rd 1603059662, flush 20523883, corrupt 54429, gen 0 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 4954813 off 65536 (dev /dev/nvme0n1p1 sector 1788864) Aug 26 10:09:47 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 4954813 off 69632 (dev /dev/nvme0n1p1 sector 1788872) Aug 26 10:09:47 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 4954813 off 81920 (dev /dev/nvme0n1p1 sector 1345720) Aug 26 10:09:47 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 4954813 off 86016 (dev /dev/nvme0n1p1 sector 1345728) Aug 26 10:09:47 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 4954813 off 114688 (dev /dev/nvme0n1p1 sector 1057128) Aug 26 10:09:47 KeiserUnraid kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 4954813 off 90112 (dev /dev/nvme0n1p1 sector 1057080) Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 4211916800 wanted 4378370 found 157230 Aug 26 10:09:47 KeiserUnraid kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 1503985664 wanted 4432432 found 149241

Hi folks, I've found countless threads asking about adding a SECOND drive to a cache/pool, however my initial setup was 4 HDDs in an array with no cache or pool. I've only just added two 1TB NVMe SSDs as a cache for the first time. I run plenty of Docker apps so I have a pre-existing appdata share. I have a VM (domain controller) as well so I also have a pre-existing domains share. I added the two SSDs without problem. Set them up in the cache pool. I went into Shares and edited each of my data shares Use Cache Pool: to Yes. My intention is for all data shares to use this pool as a cache, then copy the data to the array later. I also set appdata, domains, and system shares to Cache: Only. My intention is for all Docker apps and my DC VM to run directly off the cache pool for performance. Per the docs, this SHOULD copy files for these shares to the cache, however from what I understand this will only work if the files are not in use. How likely is it the mover will do anything at all if my Docker apps and VM are running overnight? Should I instead shut everything down and manually copy from the array to the cache, then fire it all back up? Thanks for reading!

Hey thanks for this, I just got this setup as I've been pretty unhappy with Photoprism's mobile app not getting updated/working with some new backend changes and only being accessible from a constantly broken Testflight link. Also I don't feel warm and fuzzy it will keep getting updated when it specifically states it's just a hobby. Some notes: Steps 1,4,9 you call the network 'private' but later use it as 'privnet'. Personally I just called it 'photonix'. For the postgres container I suggest changing the data storage path because it's just something like /mnt/disk1/appdata/postgres/ by default and could conflict with other containers if you use more than one DB. I set it to /mnt/disk1/appdata/photonix_postgres11/ Not an issue with any of this process per se, but I tried adding an additional mount point (photos_photonix_import) and letting Photonix have a separate import folder as it asked me during the initial setup page, but it seems to just ignore that folder entirely and not import from it. Thanks again! So far this seems a bit early in the life of the app, but I like how responsive the devs are, it's got a mobile app, and some neat features. A lot of promise here.

I just managed to get the "old gen" Israel server to work.

Thanks to the brave souls willing to make the jump and test the 6.9 beta. I did end up using my 2 port gigabit card and am running on that, but it'll be nice to get the extra unneeded card out and use the onboard port once 6.9 is released. Hopefully I can get Plex to transcode once the iGPU device shows up as well. Everything else has been VERY smooth. Frankly I expected more issues and have been pleasantly surprised. Got a week left on my trial and about to buy my license.

Another update, I read that in latest versions of Unraid the i915.alpha_support=1 parameter for the kernel is no longer required. Regardless, I have been completely unable to get /dev/dri to show up. I've tried booting into legacy instead of UEFI and there really isn't much in my BIOS I can change in regards to onboard graphics. I don't think iGPU works yet. Hopefully with the new 6.9 version with the new kernel, but I'm not sure I'm willing to try out the new beta.

Hey folks, just built my first Unraid box with an Intel 10700K, ASUS TUF GAMING Z490-PLUS mobo, 4x WD Elements 8TB, 64 GB RAM (Ballistix Sport LT 16GB x4). I had some issues getting up and running, neither my mobo onboard NIC nor my USB-C ethernet adapter would work. Only way I could get online was with a super old USB-A 2.0 100 Mbps ethernet adapter. Ordered a USB-A gigabit adapter to see if that works. I also have an ethernet card lying around here somewhere and I may just slap that in, too. I hear the onboard NIC may just start working with the new kernel so I'm not terribly worried about it. Drives all came up fine, just had to format them. Got the Unassigned Devices/Plus plugins working, got drives all sorted out, assigned to array, everything functional there. Already transferring data from backup drives. I've tried enabling the onboard iGPU so I can run Plex on Docker. No dice. BIOS is set to use the CPU GFX. Go script: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & modprobe i915 chmod -R 777 /dev/dri syslinux.cfg: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot i915.alpha_support=1 label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui i915.alpha_support=1 label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest Appears to show up, but /dev/dri never appears. root@KeiserUnraid:~# lsmod | grep i915 i915 1351680 0 i2c_algo_bit 16384 1 i915 iosf_mbi 16384 1 i915 drm_kms_helper 135168 1 i915 drm 348160 2 drm_kms_helper,i915 intel_gtt 20480 1 i915 i2c_core 40960 4 drm_kms_helper,i2c_algo_bit,i915,drm video 40960 1 i915 backlight 16384 2 video,i915 root@KeiserUnraid:~# chmod 777 /dev/dri chmod: cannot access '/dev/dri': No such file or directory