-
Posts
10,233 -
Joined
-
Last visited
-
Days Won
65
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by bonienl
-
-
I made an update to the Dynamix File Manager plugin, which now allows ZFS shares to be deleted or moved.
There is some caution to take into account:
- Shares created in the GUI on a ZFS pool, are automatically set as a ZFS dataset. When moving these shares to a non ZFS pool (or array), the dataset is lost, content is never lost
- Shares with a specific (only) pool designation need to be updated to reflect the new destination.
Example:
The share "third" is created and exists only on the ZFS pool
Now we want to move this share to the "cache_extra" pool, which is a btrfs pool.
It is required to update the share settings
Use the file manager to move the share
After the move the share "third" is completely gone from the ZFS pool
AGAIN: USE WITH CAUTION!
-
When the share is empty, you can use the GUI to delete it.
See Shares -> sharename -> delete
Ps keep in mind a share is a folder, but a special case at the same time.
Shares are best managed via the GUI
-
Perhaps there is corruption in your docker image.
Can you delete the docker image and recreate.
Use CA restore function to re-install all your containers and start fresh.
-
Whenever you change file system, including encryption, the device needs to be formatted, which wipes all content.
If you intend to use encryption, you might be better of waiting for rc3 and use it correctly from the start without the need to copy and restore your data.
-
zfs encryption is not working properly in rc2, this is a known issue and is solved in the next release.
For the time being use plain zfs.
- 1
-
Can you describe the steps in detail how to reproduce.
I can't replicate the issue, but maybe I need to do different steps.
-
@limetech normally follows reported issues, especially considering rc releases.
-
No, cmdline is automatically generated from the settings in syslinux.cfg, which are correct.
-
If you have no other Unraid instances running, it should work with the default UNRAID name (you can even leave the setting out). Don't know if that is the issue or the high number of cores in your situation, though all cores are properly identified.
-
I tested this on rc2 and it all works.
Tried to replicate your settings (obviously different cores), and no issue.
This is my /proc/cmdline
BOOT_IMAGE=/bzimage unraidlabel=UNRAID mitigations=off isolcpus=2-3,6-7 initrd=/bzroot
Not sure what is happening in your case.
-
Are you running your Unraid in a VM?
-
And the output of
cat /proc/cmdline
Ps. Your screenshot above shows that cpu isolation is set.
-
I don't see what is wrong.
Subject content is "Unraid SMTP Test"
(because you generated a test message)
-
Post a screenshot of Main -> Flash -> Syslinux Configuration
-
6 hours ago, goodolwheatie said:
Should the Docker reset sort button still be visible or applicable even if the dashboard is locked?
In upcoming release the reset-sort icon for both Docker and VM is locked by default
-
This is not part of stock Unraid.
Test your server in safe mode, which runs without plugins installed.
-
3 hours ago, Mihai Olimpiu said:
Remove everything from the 3rd column... Voila 2 columns with default engine.
Only way to get the 3rd back is to remove the cookies.This is expected behavior, when all elements of a column are "removed" then the column is not shown.
You can open the Management console (wrench icon) and select which elements to show or hide.
The console lets you also reset everything to default.
- 1
-
1 hour ago, Mihai Olimpiu said:
This is new:
It looks like you are using a theming plugin, your screenshots are not native GUI display.
Remove the plugin.
- 1
-
-
The number of columns is automatically adjusted depending on the screen resolution, or in case of mobile devices the viewport. It may vary between 1 and 3 columns.
-
I tested your scenario. There is indeed a bug.
Converting XFS to ZFS (and other way around) works fine, but converting an encrypted XFS disk to an encrypted ZFS disk fails. The formatting does not succeed.
Thanks for reporting.
Btw converting an encrypted XFS disk to regular ZFS (unencrypted) works fine.
-
You need to ERASE the existing pool and then assign ZFS.
-
In 6.11 the first column was made narrower to allow 3 columns at a resolution of 1680 or higher, but in 6.12 all columns have the same width. This is required because now content can be moved between columns and must stay the same regardless of position.
-
Quote
Still have issues that resizing the window will cause overlap until a refresh (Chrome)
That is a bug in Chrome, other browsers (Firefox, Edge, Safari, Brave) work fine
Quotethat the same window width that allows for 3 columns on 6.11 only gives 2 on 6.12
The Dashboard of 6.12 is not identical to the dashboard 6.11
Perhaps your screen resolution is on a border case.
[6.11.5] Cannot edit shares with a 'dot' placed anywhere in their name
in Stable Releases
Posted
Will be fixed in a next release.
Thanks