8000 Update 7.0.0.md by spencerjunraid · Pull Request #203 · unraid/docs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update 7.0.0.md #203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 18, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions docs/unraid-os/release-notes/7.0.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,8 +40,8 @@ And sincere thanks to everyone who has requested features, reported bugs, and te
## Upgrading

When upgrading, upon first boot you may notice on Main page some of
your pool File Sytem Types have been changed to 'auto'. This is normal and permtis a one-time update of stored pool
configuration upon array Start. Please do not chnage any pool slot configuration util after first Start.
your pool File System Types have been changed to 'auto'. This is normal and permits a one-time update of stored pool
configuration upon array Start. Please do not change any pool slot configuration until after the first Start.

### Known issues

Expand All @@ -60,8 +60,8 @@ all slots, then reboot into 6.12 and your hybrid pools should import correctly.
You could drop to the command line and do it, but this will greatly complicate pool config, ie, don't do it.
This will be fixed in a future release.
* Currently unable to import TrueNAS pools. This will be fixed in a future release.
* If you are using **Docker data-root=directory** on a ZFS volume, we recommand that you switch the
**Docker storage driver** to **overlay2**, delete the directory contents, and then let Docker redownload
* If you are using **Docker data-root=directory** on a ZFS volume, we recommend that you switch the
**Docker storage driver** to **overlay2**, delete the directory contents and then let Docker redownload
the image layers.
* We check that VM names do not include characters that are not valid for ZFS. Existing VMs are not modified
but will throw an error and disable update if invalid characters are found.
Expand Down Expand Up @@ -91,13 +91,13 @@ If rolling back earlier than 6.12.10, also see the [6.12.10 release notes](https

### unRAID array optional

You can now set the number of unRAID array slots to 'none'. This will allow array Start without any
You can now set the number of unRAID array slots to 'none'. This will allow the array to Start without any
devices assigned to the unRAID array itself.

If you are running an all-SSD/NMVe server, we recommend assigning all devices
to one or more ZFS/BTRFS pools, since Trim/Discard is not supported with unRAID array devices.

To remove the unRAID array from an existing server, first unassign all Arry slots on Main page, and then
To remove the unRAID array from an existing server, first unassign all Array slots on the Main page, and then
set the Slots to 'none'.

For new installs, the default number of slots to reserve for the unRAID array is now 'none'.
Expand Down Expand Up @@ -186,7 +186,7 @@ the number of slots (devices) initially assigned to the pool:

There is special handling for btrfs raid1 pools and single-group zfs pools/subpools:

* For btrfs raid1 and zfs single-group mirror pools (and subpools), removing a device results in decreasing
* For btrfs raid1 and zfs single-group mirror pools (and subpools), removing a device decreases
the pool slot count. When/if the slot count reaches 1, a btrfs 'raid1' or zfs 'mirror' profile is changed
to 'single'.

Expand Down
0