The update from 7.2.4 to 7.3.1 went smoothly. I stuck with the standard USB setup, just like I’ve been doing for years. Before updating Unraid, as always, I updated the plugins, stopped all Docker containers, and prevented them from starting after the reboot. In addition, the Update Helper plugin automatically downloaded the latest update for Coral-Driver after 7.3.1 was installed. I also have some fairly advanced scripts that help me save power on my server. I disabled those scripts during the update as well, even though theoretically they shouldn’t cause any problems and are currently working.

Edited June 29Jun 29 by Xwint5

Upgraded from 6.12.13 to 7.2.7 in the last few days. The update path went pretty well so far due to good documentation of (breaking) changes.

Now I stumbled across this entry in the 7.3.1 changelog:

Fix: replacing an online raidz device no longer fails in affected configurations

Could someone please tell me which configurations are affected? I could not find any hint in this thread or bug reports. Actually, I would like to wait with the update to 7.3.x until version 7.4.x is out. But if there is a serious issue with drive replacement I'd better not wait.

32 minutes ago, Gorf said:

Could someone please tell me which configurations are affected?

Fails for RAIDZ pools, unless the pool is degraded, but only 7.3.0 is affected by this, not 7.2.x