February 12, 20251 yr Hello! I've got the Lincstation N1 all SSD NAS appliance from LincPlus. When Unraid 7 with zfs support finally arrived I decided to scratch all, upgrade to 7 and add a zfs pool only (no array). To this I added two TeamGroup TM44 4TB M.2 sticks. Everything was set as default, including the device name. It all worked smooth for a couple of days. Then I decided to tweak the machine a bit and took down the pool and changed some parms. Nothing complicated (I think anyway). Set compression to on (Lz4 I guess), turned off spin down, turned on autotrim and set a monthly scrub schedule. But I also changed the host name from Tower to something more personal. I then rebooted and tried to mount the zfs pool with no luck. The GUI refuses to mount it while console command zpool insists that it's online and fully working without errors. In fact I can find no errors at all using console but the GUI still refuses to mount it. The message is 'invalid config' and this is where I am now. Also, both nginx and device restarted more than once. Any ideas?
February 13, 20251 yr Author Hello and thank you! Running console command zpool import. Name of zfs pool is 'cache': pool: cache id: 13103263492025029201 state: ONLINE status: Some supported features are not enabled on the pool. (Note that they may be intentionally disabled if the 'compatibility' property is set.) action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: cache ONLINE mirror-0 ONLINE nvme1n1p1 ONLINE nvme0n1p1 ONLINE
February 13, 20251 yr Community Expert 4 hours ago, JorgeB said: Please post the diagnostics This also.
February 13, 20251 yr Author Ah, right. Sorry. Diagnostics file enclosed. Hopefully anonymized. Arnebys-N1-diagnostics.zip
February 13, 20251 yr Community Expert Since there are no array devices assigned, you must delete the array, change slots to none.
February 13, 20251 yr Author Not sure I understand this. So I go into the Main tab and set the slots to 'none'. Then what?
February 13, 20251 yr Community Expert Then start the array, you won't be able to start it with an array without any assigned devices.
February 13, 20251 yr Author OK - slots for the array (up top) have been set to 'none' all the time. It looks like this:
February 13, 20251 yr Community Expert Solution Yes, sorry, got confused there, there's an issue with the pool config, to correct: on main click on the first device for that pool and then "remove pool" back on main, create a new pool with the same name and number of slots assign the pool device(s), leave the filesystem set to auto start the array to import the pool
February 13, 20251 yr Author Thank you, that worked out good! Pool is up and all data seems to be intact. But does this mean that I should not play with the settings for the pool? Or are some settings more dangerous than others? Is it dangerous to change the name of the host after setting up a pool even if its not mounted at the time of name change? Please advice!
February 13, 20251 yr Community Expert That wasn't caused by changing the trim and compression settings, the pool was configured for 3 devices, when it's only two, so something else caused that. Changing the pool settings in the GUI should be safe.
February 13, 20251 yr Author OK - but are there any options or features of zfs that I'd better not turn on .. or off? Does turning compression on make any real difference ie?
February 14, 20251 yr Community Expert Compression should be used with compressible data, it can make a big different, it won't if it's uncompressible data, like movies or already compressed music files and photos.
February 16, 20251 yr Author Followup: I just noticed that Fix Common Problems dont seem to like my zfs pool: Not sure what settings for the cache pool I can change to make FCP happy again. Does Docker actually *require* an array?
February 17, 20251 yr Community Expert Since your only assigned storage is cache, and all your user shares are on cache, you need to go to the settings for each of those shares and set them to Primary:cache; Secondary:none
February 17, 20251 yr Author Yes, but every single one of them is already setup just like that. Or is there a trick in how to or which order to do it?
February 18, 20251 yr Community Expert 3 hours ago, Arneby said: Yes, but every single one of them is already setup just like that. Not according to the diagnostics! a------------p shareUseCache="no" # Share exists on cache appdata shareUseCache="no" # Share exists on cache s-------e shareUseCache="only" # Share exists on cache v---o shareUseCache="no" # Share exists on cache b--------------i shareUseCache="no" # Share exists on cache d-----s shareUseCache="no" # Share exists on cache i--s shareUseCache="no" # Share exists on cache s----m shareUseCache="no" # Share exists on cache The only one that appears correct is the one anonymised as ‘s————e’. I suggest making a dummy change on each share, and hitting Apply to force a new configuration file to be written for that share. After doing that post new diagnostics so we can check everything now looks good.
February 18, 20251 yr Author Thank you! However, since I dont have any other array or pool a dummy change is not possible. I guess I could just delete and restart with most of them but appdata ie sure would be nice to keep due to my HA setup. Could I edit the config file directly somehow?
February 18, 20251 yr Community Expert 1 hour ago, Arneby said: However, since I dont have any other array or pool a dummy change is not possible. You could always change something in the comments field! The idea is to get the Apply button activated so that you can press it and get a new .cfg file generated for that share. I think that what you have encountered is probably a bug and a side-effect of having nothing in the array and only one pool. BTW: In a case such as yours I would not have called the pool 'cache' as that is not what you are using it for. I suspect you just accepted 'cache' as the default name for the first pool you create?
February 18, 20251 yr Author OK - so I added to or changed the comments for and hit apply for every share and that seemed to do the trick. Thank you! Could/should I change the name of the pool from cache to maybe zfs pool even now when all is setup and working? Edited February 18, 20251 yr by Arneby
February 19, 20251 yr Community Expert 12 hours ago, Arneby said: Could/should I change the name of the pool from cache to maybe zfs pool even now when all is setup and working? I probably would because I do not like having a pool called 'cache' that is never going to be used for that purpose but it is up to you. If you do then make sure any shares are updated appropriately and any docker or VM configurations.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.