22 hours ago, SimonF said:

Do you have the connect plugin installed? If yes try removing to see if it fixes?

I do not have it installed. On a separate note, Unraid Connect has not worked for me since a 6.x release couple years back (API or CORS errors).

Appears to be a bug in the dashboard responsive code that if you empty a column of all gadgets, you cannot drag and drop back into anymore. Doing a dashboard reset via the "blue wrench" works, but probably should make sure empty columns get a drag and drop target added.

On 11/2/2025 at 7:01 PM, itimpi said:

Here

Worked a treat

Thanks team

Minor but in future I'd probably be inclined to change the highlighted underline nav bar to a .
as a dot looks better when the length of nav bar titles changes length?

Edited November 4, 2025Nov 4 by dopeytree

A dot would be less visible than a line.

In design less is more.

At the moment the line not adjusting to the length of the characters is more disturbing.
Could have the line be the same width and align to the left of the text.
Also needs a 5px gap above the line or something its too close to the words.

Other options include just changing the colour of the active nav point or fading etc.

All will probably be possible with new theme engine?

Perhaps swap to icons like homeassistant.

Edited November 4, 2025Nov 4 by dopeytree

Upgraded 48hrs ago and all is working.

Thanks to a warning notification "Share name contains restricted character(s)" and subsequent name change of that share, my log rotates now.

https://forums.unraid.net/topic/186899-syslog-server-log-rotation-not-working-unraid-7/?&do=getNewComment

On 11/2/2025 at 12:09 PM, evergreen.dazed said:

Oddly the Processor graph from the dashboard view is now blank (save for temp) after update. On a AMD Ryzen 5 5600G server. Tried a restart as initial diagnostic, no joy.

Stats page shows CPU load graph correctly.

Having the exact same problem with a Ryzen 2700. Processor model and temp, but usage is all zero.

I renewed my license just for that mobile support. So cool that it's finally a thing. Good work!

Completed upgrades 2 days ago on both servers. So far no issues to report!

no issues here but noticed this, when selecting tools|updateOS a cloudflare screen is displayed,

After updating to 7.2.0, every click to another section of the WebUI refreshes the entire page and makes the entire dashbar section across the top flash and reload. Happens in Firefox and Chrome. No installed plugins that should be related.

Before the update (and on my other server that is not updated yet), every click to other sections (Dashboard, Main, Settings, Tools, etc.) does not refresh the whole page and the top portion of the WebUI does not flash or visually reload, just the bottom section changed, which was normal.

This new bug (?) is a minor UI annoyance but it feels a lot less polished this way. I noticed it immediately and it's annoying when doing a lot in the WebUI at night. Hope it gets noticed and fixed. Other than that, the update was fast and working well so far. Thank you Unraid team!

Upgraded from 7.14 to 7.2

Ive got three dockers (out of many) causing a SERVER ERROR when they try and start

Tdarr Node (Main Tdarr running fine)

LSIO - Emby

ICH777 - Jellyfin

maybe something to do with nvidia runtime.

Otherwise all good. Thanks

Just a reminder this this is not a support thread :) If you have an issue please start a new topic under General Support. Be sure to include your diagnostics.zip

Also, a pre-release of the next version is available which fixes the majority of issues that have been reported:

This WSD conflict stems from the cloned machine-id, an essential system UUID (distinct from the hostname) often duplicated when the Unraid flash drive is replicated. The technical fix requires manually generating a new unique UUID into /etc/machine-id on the second server, ensuring it persists on the Unraid flash drive configuration. This principle of unique system identifiers is critical for any deployment, a key scaling consideration often discussed in architecture growth analyses, such as those found on MagStartup. Should Unraid's boot process include an integrity check for machine ID uniqueness in virtualized or cloned environments?

Edited November 19, 2025Nov 19 by avensis

1 hour ago, avensis said:

This WSD conflict

This should be fixed in 7.2.1-rc.1, if you are affected, please upgrade and retest, though other users have already confirmed it's working correctly in that release.

Can I do, is it even safe to do, a direct from 6.7.2 -> 7.2.0 ?

1 hour ago, sota said:

Can I do, is it even safe to do, a direct from 6.7.2 -> 7.2.0 ?

It should be OK, but create flash drive backup before updating, also a good idea to read the release notes for every minor release in between, e.g., 6.8.0, 6.9.0, 6.10.0, etc

Couldn't upgrade my servers yet. However, I noticed that ZFS has been updated to the 2.3.4 version, including the "zfs rewrite" command, which is a most after editing a zpool with more vdev for example to rebalance the datas already written on the vdevs.
This command should be available through GUI.

More info there : https://forums.unraid.net/topic/194993-propose-zfs-rewrite-command-within-gui/

Edited November 11, 2025Nov 11 by gyto6

My server does not run 24/7. Since Unraid 7.2.0, the parity check starts when my server is restarted. In the previous version, the parity check was performed once a month. Now it runs every time the server is started.

Under what conditions is an automatic parity check started?
Scheduled parity check: monthly First Day 15:00

Parity Operation History: Parity sync after array encryption

Parity-Check	2025-11-12, 21:41:03 (Wednesday)	14 TB	3 min, 55 sec	Unavailable	Canceled	0
Parity-Check	2025-11-11, 19:50:45 (Tuesday)	14 TB	20 hr, 30 min, 3 sec	189.7 MB/s	OK	0
Parity-Check	2025-11-09, 22:58:51 (Sunday)	14 TB	58 sec	Unavailable	Canceled	0
Parity-Check	2025-11-09, 11:20:34 (Sunday)	14 TB	1 hr, 6 min, 34 sec	Unavailable	Canceled	0
Parity-Check	2025-11-08, 22:17:10 (Saturday)	14 TB	35 sec	Unavailable	Canceled	0
Parity-Sync	2025-11-08, 06:45:17 (Saturday)	14 TB	20 hr, 31 min, 48 sec	189.4 MB/s	OK

Edited November 12, 2025Nov 12 by Thorsten

4 hours ago, Thorsten said:

Under what conditions is an automatic parity check started?

When you have an unclean shutdown - as in the array did not complete it's shut down process before the server powered off.

You should open a new thread in General Support if you need help diagnosing and resolving your issue. But this thread is a good place to start reading.

Servers upgraded to 7.2. No dysfunctions to notice for 2 days long.

3 Servers upgraded without issue from 7.1.4 to 7.2 with no data loss like last time.

On 11/1/2025 at 11:19 AM, JorgeB said:

If after updating to this release one or more shares stopped being exported and/or you see this warning on that share's settings page:

This means the cfg file for that share that is stored on the flash drive doesn't match the case used for the share on the array/pool, example:

You have a share called data, but the cfg is saved on the flash drive as /config/shares/Data.cfg

Previous Unraid releases didn't check for that, and it would make the share settings not work correctly, for example, with the mover.

There are two options to resolve the issue:

1. Rename /config/shares/Data.cfg to data.cfg (note that it cannot be done in place, since FAT is case insensitive, but you can, for example, move it to a temporary place first using

   mv /boot/config/shares/Data.cfg /tmp/data.cfg

   and then move it back to the flash with

   mv /tmp/data.cfg /boot/config/shares/data.cfg

2. Delete /boot/config/shares/Data.cfg from the flash drive, then go to the share, reapply the settings, and a new cfg will be created with the correct case.

I was also unable to access any of my shares via Windows after updating to 7.2.2, and I can confirm this resolved the issue.

The strange thing is that I only had one share with this problem, but I could not access any of the shares. I guess this issue is preventing SMB from starting correctly and so none of the shares were accessible.

The best thing to do is to go in /config/shares, and check if there are any share config files with name that do not match the configured value, and then proceed as Jorge recommended for all of the affected shares.

After fixing the issue with the config files, an array restart was required to bring everything back to functionality.

Edited November 30, 2025Nov 30 by Thozur

On 11/1/2025 at 12:19 PM, JorgeB said:

If after updating to this release one or more shares stopped being exported and/or you see this warning on that share's settings page:

This means the cfg file for that share that is stored on the flash drive doesn't match the case used for the share on the array/pool, example:

You have a share called data, but the cfg is saved on the flash drive as /config/shares/Data.cfg

Previous Unraid releases didn't check for that, and it would make the share settings not work correctly, for example, with the mover.

There are two options to resolve the issue:

1. Rename /config/shares/Data.cfg to data.cfg (note that it cannot be done in place, since FAT is case insensitive, but you can, for example, move it to a temporary place first using

   mv /boot/config/shares/Data.cfg /tmp/data.cfg

   and then move it back to the flash with

   mv /tmp/data.cfg /boot/config/shares/data.cfg

2. Delete /boot/config/shares/Data.cfg from the flash drive, then go to the share, reapply the settings, and a new cfg will be created with the correct case.

Thank You!
7.0.1 -> 7.2.2
Turned down the server. Removed USB drive. Moved shareName.cfg to desktop. Renamed it. Pasted it back.