novaleaf
Members
-
Joined
-
Last visited
-
i am also wondering the same. maybe using tailscale?
-
I'm not sure if this occured before or after I upgraded to Unraid 7 (from 7rc1), but on my app (docker) drive, I see this in the ZFS Master gui: when I open terminal I can't find these anywhere. What are they? How can I delete them in bulk? EDIT: it looks like something from docker... `mount` shows EDIT: I guess I solved it, hid in the zfs master settings:
-
yes, it very well could be a coincidence. I'll try to do some more testing over the next few days.
-
What I am trying to explain is that in my situation disabling refresh did not stop the drives from immediately waking up every few tens of seconds. However after I rebooted it stopped. prior to the reboot I am certain I gave the system plenty of time. Tens of minutes where I was disabling plugins until finally disabling zfs master stopped the issue. After that I experimented and found that the reboot after disabling solves it. I am using a fresh install of Unraid7rc1 with zfs raidz2 pool.
-
I'm using Unraid 7rc1. It seems that you need to reboot after disabling refresh interval. You may want to mention this in the docs (and perhaps even in the settings page)
-
I have a RaidZ2 Zfs Pool encrypted with the passphrase "1234Test" via the gui. manually uploading a keyfile with the phrase via gui also works to start the pool. However when I try to automate it, the gui states "Wrong Encryption Key". Here is my /boot/config/go file #!/bin/bash # Define the key content key_content='1234Test' # Write the key content to /root/keyfile echo "$key_content" > /root/keyfile # Secure the keyfile by setting permissions chmod 600 /root/keyfile # Start the unraid web based Management Utility /usr/local/sbin/emhttp I have verified the contents of keyfile are "1234Test" without the quotes, and also tried changing the go file to copy a keyfile instead of creating it by script. Why urgent: it seems zfs pools can not be automatically decrypted, and perhaps the passphrase used to encrypt is not byte identical to user input Edit: attached is an image after reboot. I can press the "Delete encryption keyfile" button, then type 1234Test into the passphrase and it will start.
-
BACKSTORY: Using a new NAS running Unraid 7rc1, I created a ZFS pool and SLOG subpool. PROBLEM: Later, The nvme in my zfs SLOG subpool broke. Upon booting, Unraid shows the missing slog device, but the gui does not allow replacing the device or deleting the subpool. Attempting to start the pool with the missing slog device fails, with unraid noting the missing device. IMPACT: It should be expected that drives will fail over time. The unraid gui should make managing and maintaining pools as easy as creating them. PROPOSED SOLUTION: The GUI should let people edit zfs pools/subpools, and delete subpools like SLOG and L2ARC that are optional. WORKAROUNDS: See my reply dated 2024-12-13: Because unraid seems to pre-validate the pool before handing off to linux, if there pool is in an invalid state then linux won't see it, and it won't be editable via the zpool cmd. however when the pool is in a failed state it also can not be edited in the unraid gui. there seem to be two workarounds to the problem described: drop into terminal and manually edit/delete config under /boot/config/pools/ then reboot using the Unraid Gui, delete the entire zfs pool, and then manually construct a replacement omitting the problematic device/subpools.
