OriginalFlavor

root@Tower:~# cat /etc/resolv.conf # Generated by rc.inet1 nameserver 208.67.222.222 # eth0:v4 nameserver 208.67.220.220 # eth0:v4 root@Tower:~# ip route default via 192.168.1.254 dev br0 metric 4 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-af6a406d9e6b proto kernel scope link src 172.18.0.1 linkdown 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.238 metric 1 root@Tower:~# ping -c 3 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. 64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=0.825 ms 64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=0.352 ms 64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=0.793 ms --- 192.168.1.254 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2079ms rtt min/avg/max/mdev = 0.352/0.656/0.825/0.215 ms root@Tower:~# ping -c 3 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. --- 8.8.8.8 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2071ms root@Tower:~# ping -c 3 208.67.222.222 PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data. --- 208.67.222.222 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2026ms root@Tower:~# nslookup github.com ;; communications error to 208.67.222.222#53: timed out ;; communications error to 208.67.222.222#53: timed out ;; communications error to 208.67.222.222#53: timed out ;; communications error to 208.67.220.220#53: timed out ;; no servers could be reached DNS Servers 208.67.222.222 208.67.220.220 Rebooting. Rebooting fixed everything. (Sorry, I thought I had tried rebooting before making my original post.) Thank you for your help.

Not able to connect remotely via unRaid connect or Tailscale (The plot thickens). Will update this evening when I have local access.

unRAID 7.3.2 Fix common problems is reporting the following issue. Errors Found Suggested Fix Unable to communicate with GitHub.com Reset your modem / router or try again later, or set your to 8.8.8.8 and 8.8.4.4 Also make sure that you have a Gateway address set up (Your Routers IP address). Additionally, this may also mean that GitHub is currently down. This error means that you may not be able to update your OS or plugins More Information Warnings Found Suggested Fix No Warnings found Other Comments Comments Could not check for blacklisted plugins The download of the blacklist failed Could not perform unknown plugins installed checks The download of the application feed failed.tower-diagnostics-20260928-0243.zip

(SOLVED) Unable to communicate with GitHub Errors Found Suggested Fix Unable to communicate with GitHub.com Reset your modem / router or try again later, or set your to 8.8.8.8 and 8.8.4.4 Also make sure that you have a Gateway address set up (Your Routers IP address). Additionally, this may also mean that GitHub is currently down. This error means that you may not be able to update your OS or plugins More Information Warnings Found Suggested Fix No Warnings found Other Comments Comments Could not check for blacklisted plugins The download of the blacklist failed Could not perform unknown plugins installed checks The download of the application feed failed.Diagnostics attached. unRAID 7.3.2 tower-diagnostics-20260928-0243.zip

I could not create the system share even though "system" was not on the list of existing shares. However, after creating appdata, when I turned Docker off in settings and then back on, system share was created automatically. Docker running great. I did need to run "Docker Safe New Perms" to reach data with recreated Docker containers. Thank you for your help.

It is not on any of the drives. I did find an earlier backup from 2024. I had saved the current backup to the same directory. Oh well. I think I figured out my weekend project--recreating Docker containers.

The purpose of the pool was to add more space and be faster than my array. The cache pool is all NVMe SSD drives. The array are spinning HDDs. Is stripe the fastest? I think I am willing to risk redundancy for speed with the cace. That's my reasoning. But I am listening.

Solved!

unRAID ver 7.3.2 Following migration from cache drive "cache" to cache pool "cache_pool" , Fix Common Problems reports... Fix Common Problems reports Warnings Found Suggested Fix Share Boring references non existent pool cache If you have renamed a pool this will have to be adjusted in the share's settings More InformationIn the share settings... Share Settings Share name: Boring Comments: Minimum free space: Free Space will be calculated Share status: Share contains data Exclusive access: No Primary storage (for new files and folders): Cache_pool Secondary storage: None Mover action: Not used Case-insensitive Share name is not uniqueNote that the drop-down boxes in the share settings are greyed out. See image. In the list of my shares, I do see "Boring" (capitalized) but I do not see "boring" I am having Docker issues as well but I posted that in a separate thread. https://forums.unraid.net/topic/200688-appdata-share-deleted-docker-service-failed-to-start-following-migration-to-cache-pool/ Diagnostics attached. tower-diagnostics-20260925-1323.zip

unRAID ver 7.3.2 AppData share is deleted. The Docker tab displays, "Docker Service failed to start" This problem was caused by migration from a cache drive to a cache pool. Before migrating, I backed up my appdata using the plugin. I created a cache pool with 3 cache drives including the original "cache drive". I switched from default (BTRS?) in cache drive to ZFS in cache pool. After restarting array, I watched the appdata.zip backup disappear from the document share. (Maybe the appdata_backup.zip had never been moved from cache to array before moving cache drive into new cache array?) I would like to recover and restore those backed up docker images. I can live with recreating the docker images if the backup is gone. I have no appdata share on my array after the cache mighration. Are there instructions/guidance on restoring / recreating the appdata share? Any suggestions for trying to find and restore the missing appdata_backup.zip file? tower-diagnostics-20260925-1323.zip

I got Glotrends SA20 to work. A NVMe drive needed to be inserted in both slots. Only one slot did not work. See https://forums.unraid.net/topic/200668-solved-glotrends-pa20-pcie-x4-card-using-asm2812-chipset-detected-but-nvme-drive-installed-in-card-not-detected/

I got the Glotrends PA 20 to work. Both slots had to have a NVMe drive inserted, then motherboard and OS recognized the drives. See https://forums.unraid.net/topic/200668-solved-glotrends-pa20-pcie-x4-card-using-asm2812-chipset-detected-but-nvme-drive-installed-in-card-not-detected/

Experiment 1 try one boot with pci=pcie_bus_safe Fresh diagnostics are attached. Did not detect drive. Removed parameter. Rebooted Answers to questionsNVMe info. I have two identical NVMe drives. I do not know the exact make and model. I do know that the NVMe drives use Silicon Motion SM2263XT controllers. I have been using one of the discs ("NVMe_old") as my Cache drive by using the M.2 slot on the motherboard. The other disc is identical make/model/size ("NVME_new"). smps63x86-ab The motherboard x4 slot (PCH SLOT2 PCI-E 3.0 X4) holds the PA20 card. The PA20 has two slots labeled "1" and "2" Experiment 2Powered down Removed PA20 card Removed NVMe_old from M.2 slot Inserted NVMe_new in M.2 slot Rebooted unRAID Found unformated NVME_New Attached diagnostics file. Conclusion. NVME_new is okay. Experiment 3Tried different board. StarTech PEX2M2 NVME_old in card slot 1 NVME_new in card slot 2 motherboard m.2 empty Did not detect drives. attached diagnostics file Experiment 4Motherboard M.2 slot empty NVME_new in PA20 slot 1 NVME_old in PA20 slot 2. It worked. Both drives detected! 🫨 (I am shocked. Would have bet the house that this was going to be a failure.) Any idea why this worked? tower-diagnostics-20260923-2149.zip tower-diagnostics-20260923-2250_Experiment2.zip tower-diagnostics-20260923-2323_experiment3.zip tower-diagnostics-20260924-0002_Experiment4.zip

unRAID does not detect the NVMe drive installed in a new Glotrends PA20 card. unRAID does detect the card, but not the drive. The BIOS sees the card but not the drive. I am starting troubleshooting. (i.e., switching drives, slots, PCIe slots, BIOS settings, contacting MB manufacturer, card manufacturer) My system Supermicro C7H170-M Card: Glotrends PA20 that utilizes ASM2812 chipset. Unraid 7.3.2 Diagnostics attached tower-diagnostics-20260923-1417.zip

Did you ever buy? Did the card work? Or did you choose an alternative that worked? I purchased a Glotrends PA20 that utilizes ASM2812 chipset. My BIOS and unRAID detect the card. Neither detects the NVME drive in the card. I am at the beginning of troubleshooting. I have a Supermicro C7H170-M motherboard unRAID 7.3.2