Hey folks, heading into the weekend I thought you'd like to know that over 15,000 of your fellow Unraiders have installed 7.2.0 !

Updated from RC2 to 7.2.0. No issues. However, docker start times have been adjusted this release but are truncated still:

The bottom two Dockers are 100 seconds and 120 seconds respectively. If I highlight them as if to change their value, I can scroll and see the who number. But even highlighted, it only shows two digits at a time.

Finished upgrading 7.1.4 to 7.2.0. Seems to be running fine. however after the reboot it started a parity sync, for some reason.

11 hours ago, joggs said:

Very sluggish. especially docker and the containers does not seem to have internet access. i have custom network obviously, but so many problems. please tell me steps to downgrade. I chose stable so I wouldnt need to search logs etc

I agree docker seems very sluggish comparatively to 6. Nothing wrong in the logs it just seems like it's unrefined

7 hours ago, craigr said:

Updated from RC2 to 7.2.0. No issues. However, docker start times have been adjusted this release but are truncated still:

The bottom two Dockers are 100 seconds and 120 seconds respectively. If I highlight them as if to change their value, I can scroll and see the who number. But even highlighted, it only shows two digits at a time.

13 hours ago, laoban said:

How can I resolve the color inconsistency issue? I've removed the CSS and theme engine, but the problem persists.

This problem has existed since version 7.1.0. Could you tell me how to solve it, or teach me how to change the theme color?

The alternating colours for each row? By design

On 10/30/2025 at 2:31 PM, SystemZer0 said:

i think there's a visual bug in the desktop docker page. the "basic view toggle button" on the top menu is taking up a whole row leaving a big empty gap. i don't remember having this gap in the previous version

By design. Changes needed to be made for responsive, and that slider button was always hacked into the title bar there, and became a very big problem to put back in, especially if docker compose plugin was installed

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.

Need help.

Created flash backup and start update from 7.1.4 to 7.2.0

In gui got usb flash drive error and system hanged.

Replaced usb flash drive and wrote backup and system hanges up on boot with... see picture.

Img

59 minutes ago, sersh said:

Replaced usb flash drive and wrote backup and system hanges up on boot with... see picture.

Try recreating the flash drive, first backup the current one, then recreate it using the USB tool, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files.

If that doesn't help and you need more help, please start a new thread in the general support forum, this annouce post is not the right place for support.

The problem with usb flash drive did the problem with the backup, load previous backup solve the problem. Unraid starts.

Thanks.

What do supporting native ZFS mean for practical usage?

I learned that Unraid OS needed full control over the hdd, not just a partition. Is that that case still? I have 8 x Exos 2x18 dual actuator in a TrueNas server. To make use of both actuators, the hdd must be partition in two parts. Each partition acts separately in ZFS mirror.

Update failed. None of the array devices were showing in the main tab. They were visible in system devices. Unassigned Devices were visible in the main tab. (they are on same controller as array drives) Array kept starting. In terminal window lots of curl errors racing by.

Reverting back to 7.14 with no problems. towertest-diagnostics-20251101-1714.zip

Updated two servers to 7.2.0 from 7.1.4, went smoothly, but both have the following error in the log:

rc.local: error log : /var/log/graphql-api.log
root: error log : /var/log/graphql-api.log

This issue was supposedly fixed a few months back. Deleting the file and rebooting doesn't help, the error remains.

I was running 7.2 RC1 and then upgraded to RC2 with no issues. I just upgraded to stable 7.2 and it boots but the web service isn't working. I can ping fine from the console and can ssh in. Google helped me to get a login screen via the following but as soon as I login and it tries to load /main, I get a 500 error. > /etc/rc.d/rc.docker stop

1. /etc/rc.d/rc.php-fpm start

2. /etc/rc.d/rc.nginx start

I have removed the .cfg files in /boot/config/ for docker, domain, disk, and share but nothing seems to be working. /usr/local/sbin/emhttpd does not exist - should it and it just was a failed upgrade?

Updated the 2nd server to 7.2.0. So far, so good. But it really doesn't do much, so I didn't expect issues.

I'm feeling pretty good about this update. Enough that I will likely take the plunge and bring the main server up to date from 6.12.10 to 7.2.0. I have time the next day or two, so we will see how it goes. Those who know, I'm hesitant to update unless I have a compelling reason to do so. 7.2.0 looks like a stable point to take the plunge.

4 hours ago, highdefinitely said:

Updated two servers to 7.2.0 from 7.1.4, went smoothly, but both have the following error in the log:

rc.local: error log : /var/log/graphql-api.log
root: error log : /var/log/graphql-api.log

This issue was supposedly fixed a few months back. Deleting the file and rebooting doesn't help, the error remains.

Is this really an error? It does highlight lines red if they contain the word error as far as I know.

I have the same line at boot but that's just info from the api (I have Unraid Connect installed)

Nov 1 22:45:24 Server rc.local: +--- unraid-api

Nov 1 22:45:24 Server rc.local: namespace : default

Nov 1 22:45:24 Server rc.local: version : 4.25.3

Nov 1 22:45:24 Server rc.local: pid : 3190

Nov 1 22:45:24 Server rc.local: pm2 id : 0

Nov 1 22:45:24 Server rc.local: status : online

Nov 1 22:45:24 Server rc.local: mode : fork

Nov 1 22:45:24 Server rc.local: restarted : 0

Nov 1 22:45:24 Server rc.local: uptime : 6s

Nov 1 22:45:24 Server rc.local: memory usage : 204.6mb

Nov 1 22:45:24 Server rc.local: error log : /var/log/graphql-api.log

Nov 1 22:45:24 Server rc.local: watching : no

Nov 1 22:45:24 Server rc.local: PID file : /var/log/.pm2/pids/unraid-api-0.pid

Nov 1 22:45:24 Server rc.local: Unraid API service started

Edited November 2, 2025Nov 2 by Niklas

16 hours ago, frodr said:

To make use of both actuators, the hdd must be partition in two parts.

That's currently not supported by Unraid; it only uses one partition per device.

15 hours ago, Winwiz said:

In terminal window lots of curl errors racing by.

Nginx is failing to bind to ports 80 and 443 because they were already in use. Please boot in safe mode to rule out any plugin issues, if the same, create a new bug report in Stable Releases - Bug Reports and post the diags from safe mode.

Nov  1 17:05:26 TowerTest nginx: 2025/11/01 17:05:26 [emerg] 14454#14454: bind() to 127.0.0.1:80 failed (98: Address already in use)
Nov  1 17:05:26 TowerTest nginx: 2025/11/01 17:05:26 [emerg] 14454#14454: bind() to 192.168.100.210:80 failed (98: Address already in use)
Nov  1 17:05:26 TowerTest nginx: 2025/11/01 17:05:26 [emerg] 14454#14454: bind() to 100.85.62.119:80 failed (98: Address already in use)
Nov  1 17:05:26 TowerTest nginx: 2025/11/01 17:05:26 [emerg] 14454#14454: bind() to 127.0.0.1:443 failed (98: Address already in use)
Nov  1 17:05:26 TowerTest nginx: 2025/11/01 17:05:26 [emerg] 14454#14454: bind() to 192.168.100.210:443 failed (98: Address already in use)
Nov  1 17:05:26 TowerTest nginx: 2025/11/01 17:05:26 [emerg] 14454#14454: bind() to 100.85.62.119:443 failed (98: Address already in use)

12 hours ago, Rich Drinan said:

/usr/local/sbin/emhttpd does not exist

This is very strange. I would recommend first recreating the flash drive, first backup the current one, then recreate it using the USB tool with 7.2.0, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files.

If that doesn't resolve the issue, please create a new post/bug report and post the diagnostics or just the syslog if the diags don't download.

Went from 7.0.0 to 7.2.0 with no issues.

Getting low disk space alert and discovered the threshold for space for the intimal pool changed during migration. The values should have come from the top level settings yet they changed on this pool. I've also seen the disk temperature thresholds change on some drives. I recommend everyone go over there disk and pool settings to avoid harm or false alerts.

My system doesn't boot anymore... here the screenshot from the boot screen

THE F*ING USB stick died

Please remove the dependence on this stupid system and let us boot from a proper drive!

Update: the stuck needed just a "good old" unplug and re-plug

Just upgraded to 7.2.0 from 7.1.4 and MongoDB broke. There is no update for MongoDB docker yet. Doesn't seem 7.2.0 isn't compatible with the MongoDB Docker.

{"t":{"$date":"2025-11-02T09:13:34.550-06:00"},"s":"F", "c":"CONTROL", "id":20573, "ctx":"initandlisten","msg":"Wrong mongod version","attr":{"error":"UPGRADE PROBLEM: Found an invalid featureCompatibilityVersion document (ERROR: Location4926900: Invalid featureCompatibilityVersion document in admin.system.version: { _id: \"featureCompatibilityVersion\", version: \"7.0\" }. See https://docs.mongodb.com/master/release-notes/8.0-compatibility/#feature-compatibility. :: caused by :: Invalid feature compatibility version value '7.0'. Expected one of the following versions: ''8.2', '8.1', '8.0'. See https://docs.mongodb.com/master/release-notes/8.0-compatibility/#feature-compatibility.). If the current featureCompatibilityVersion is below 8.0, see the documentation on upgrading at https://docs.mongodb.com/master/release-notes/8.0/#upgrade-procedures."}}