StudiesTheBlade
Members
-
Joined
-
Last visited
-
It worked! Looks like the TrueNAS partition scheme was the culprit. stanley-diagnostics-20230615-2337.zip
-
Ah, I needed to run just a `zpool import` not `zpool import tank`. I tried the trick you mentioned above, but still no luck. But at least I think I have a lead with the partition scheme on that one drive. I wonder if I can wipe that drive and resilver with the rest of the array. A little sketchy, but should work, no? stanley-diagnostics-20230615-1221.zip
-
Sorry about that. Here you go! stanley-diagnostics-20230615-1115.zip I've been using the pool with out issue for docker mappings, but I can't get it as an official pool.
-
Hi all, I am trying to import an existing ZFS pool into Unraid, but I am getting the "Unmountable: Unsupported or no file system" error message for all the disks after starting the array. From what I've read in the documentation, my pool seems to be a supported configuration. It is 2 raidz1 vdevs with 4 drives each (see attached image). I have tried creating the pool, assigning all drives, and then choosing zfs raidz 2x4 drives, but I still get the same result. I was hoping someone could tell me I'm missing some step somewhere or if my array is somehow incompatible and why. I don't see any log entries in Unraid that seem to give any explaination of why it couldn't be mounted. Thanks for your time!
-
Hi All, I did not find any bug reports specific to this error on this Unraid pre-release version, so I am reporting this here for others to also list their experience and diagnostics. This issue is usually noticed after dockers and VMs fail to start or fail while running and is always preceded by the following error in the syslog: shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed. I am aware this may be a bigger issue than just Unraid and this specific pre-release, but I feel it is still rather import to have it documented. This way a workaround or mitigation could be found and used in scenarios where having to perform a daily reboot to fix this is not an acceptable solution. unraid-tower-diagnostics-20210113-0916.zip
-
That worked! It seems obvious now. I should have checked that. Thanks!
-
Are there any special settings I need to set to get nested subdomains working? I've got no issues with certificates for my root and first-level subdomains, but the second-level nested aren't getting added to the cert. I'm using cloudflare and dns verification Example A records: A example.com <ip> <-- OK A *.example.com <ip> <-- OK A *.subdomain.example.com <ip> <-- Cert invalid when navigating to site
