Just updated from 7.2.6 and get this nasty one:

Corruption errors was instant i did not see it accumulate, and the number hasnt gone up...

skabet-diagnostics-20260513-2153.zip

Edited May 13May 13 by jensrobot

2 hours ago, manilx said:

Migrated 2 Ugreen NAS, DXP480T and DXP6800 Pro, to boot from internal (old UGOS) nvme and also move licenses to TPM (which I was happy to find out that this worked with Ugreen).

All green.

You're lucky 😭

Just tried to upgrad my DXP6800Pro to 7.3 and:
- I can't connect to the GUI despite the terminal/console showing the right IP adress
- Booting into Safe mode (no plugins) with or without GUI doesn't work...so it's not plugins ? It gives me the "Unraid Login" with the hypervisor error - but I don't think it's the VMBackup plugin errors because...safe mode ?
- RE-updating fails every time.

Thank the lord of the "previous folder" and easy rollback, I was able to simply plug my USB key into another computer and restore 7.2.5...

This makes me think, with the new internal boot : I plan on migrating to an NVME SSD that is absolutely a nightmare to access (Ugreen hidden OS SSD)

• Is there a functionnality like "when updating, backup boot to USB device" ?

• If this would have happened with only the internal device, I would have LOST IT

Here are a bunch of diagnostics from all attemps (safe mode etc)

Help is appreciated :-)

I think I found a bug in this release.

I have a custom network set up for some of my docker containers, and after upgrade they became unreachable, although kept communicating to each other.

In the past their traffic went through unraid default gateway. It does not work in 7.3.0, and the only way to make them work was to add another DG just for that network like so:

Hi. Thank you for your work.

I have successfully updated to this last version.

1 hour ago, craigr said:

Went from 7.2.6 to 7.3.0. Everything is working as expected except this. I see no errors when I click on the pool and it is operating fine. What does this mean? I'm running a scrub to see if that shows any errors.

It is a RAID0 pool BTRFS

Click on the online it will take you to the info page.

You will see some errors displayed. There is a reset button, but they may reappear.

Also if you hoover of the warning triangle next to the number is will show more detail on the errors.

Updated one of my servers today. 7.2.4 - 7.3.0. The server is only running Nextcloud AIO and Vaultwarden. But all is well so far.

I'm waiting to update the other server(7.2.4) which has everything else on it. Cannot afford for that server to go down.

Edited May 13May 13 by m411b

I just had a bad time migrating from 7.2.6 to 7.3.0.

System: 4 data disks + 2 parity, all SSD, XFS filesystem. No cache pools. Docker and VMs disabled.

Upgrade path: 7.2.6 → 7.3.0 stable

Symptoms:

1. After upgrading, /mnt/user/ only showed 3 directories (leftover Docker mount points). shfs process was not running at all.

2. Data was confirmed present on individual disks (/mnt/disk1/ through /mnt/disk4/) but the FUSE aggregation layer never initialized.

3. Attempting to stop the array hung indefinitely — emhttp showed fsState="Stopping" with message "Retry unmounting user share(s)" despite no mounts under /mnt/user/.

4. After a clean reboot back into 7.3.0, the problem reproduced identically. Array start in maintenance mode worked, but stopping maintenance mode hung the same way.

5. mdcmd stop returned "Device or resource busy."

6. Downgrading to 7.2.6 resolved the issue — shfs started normally and all shares re-appeared. However, a stale /mnt/user/personal/ phantom directory (0 bytes, empty subdirs) persisted from the 7.3.0 session and had to be manually removed before emhttp would fully re-scan shares.

Key syslog entry from 7.2.6 after downgrade (the same pattern likely occurred silently under 7.3.0):

emhttpd: error: malloc_share_locations, 8656: Operation not supported (95): getxattr: /mnt/user/personal

This repeated in a tight loop, suggesting a race or failure in the getxattr call against the FUSE mount.

Relevant release note: The 7.3.0 release mentions an "md/unraid driver crash that could make encrypted XFS array disks report a missing or wrong encryption key when affected systems used 4Kn parity." While these disks are not encrypted and not 4Kn, the failure mode (shfs never starting, array unable to cleanly stop) appears related.

1 hour ago, SimonF said:

Click on the online it will take you to the info page.

You will see some errors displayed. There is a reset button, but they may reappear.

Also if you hoover of the warning triangle next to the number is will show more detail on the errors.

Not very informative. What are corruption errors? As you can see, "RESET" is greyed out.

Balance is now not available in the pulldown and also greyed out. And finally SCRUB is greyed out.

unraid-diagnostics-20260513-1837.zip

Edited May 13May 13 by craigr

2 hours ago, SimonF said:

Click on the online it will take you to the info page.

You will see some errors displayed. There is a reset button, but they may reappear.

Also if you hoover of the warning triangle next to the number is will show more detail on the errors.

If I click the disc and not "ONLINE" than nothing is greyed out including reset. But what are corruption errors? And were the errors there before the upgrade, or were they caused by the upgrade? The SCRUB returned no errors.

Edited May 14May 14 by craigr
The SCRUB returned no errors

Upgraded from 7.2.6 to 7.3. Went well however the dashboard under Processor shows: AMD FX™-8350 Eight-Core @ 4000 MHz Total Power 0.00 W Temperature -1° C. Obviously not correct. TIt displayed correctly under 7.2.6. he motherboard temp is displayed correctly. Any suggestions?

Going to wait for 7.3.1

6 hours ago, craigr said:

Not very informative. What are corruption errors? As you can see, "RESET" is greyed out.

These are errors reported by the btrfs filesystem, and they come from before, just that they weren't monitored, though I'm not sure why the buttons are greyed out, they work for me, will take a look

Corruption errors mean that btrfs detected mismatched CRCs for some blocks on that device.

The first step is to reset the stats, if you cannot do it using the GUI, open a terminal window and type

btrfs dev stats -z /mnt/pool_name

Then run a scrub and see if more errors come up

btrfs scrub start -B /mnt/pool_name

Updated from 7.2.6. Uneventful so far. No issues observed so far.

I briefly tried 7.2.5, but I ran into some Docker issues. So I went back to 7.2.4 and am now on 7.3.0.

The upgrade went almost flawlessly. Only one Docker instance was thrown off by the time zone setting.

Otherwise, it’s been stable for over 24 hours.

-faxxe

Upgraded to 7.3.0 without issue.

It seems to me that my power consumption has dropped? I think my CPU is falling into low-power states more easily/often now.

Thanks for all the hard work ✌️

I cannot reproduce the pool RESET/SCRUB buttons not working, one of the affected users, please retest in safe mode to rule out a plugin issue, and if it's the same, create a new thread in the general support forum, and we can continue there.

Updated today to 7.3.0 and got this message. 

{
  "request": {
    "operation": "CreateInternalBootPool",
    "variables": {
      "poolName": "boot",
      "devices": [
        "INTEL_MEMPEK1J016GAL_PHBT90950652016N"
      ],
      "bootSizeMiB": 0,
      "updateBios": true,
      "reboot": false
    }
  },
  "response": {
    "ok": false,
    "code": 1,
    "output": "assignableDisks snapshot: [{\"id\":\"INTEL_MEMPEK1J016GAL_PHBT90950652016N\",\"serialNum\":\"INTEL_MEMPEK1J016GAL_PHBT90950652016N\",\"device\":\"/dev/nvme0n1\"}]\nassignableDisks resolved serialNum->device: [[\"INTEL_MEMPEK1J016GAL_PHBT90950652016N\",{\"bootId\":\"INTEL_MEMPEK1J016GAL_PHBT90950652016N\",\"devicePath\":\"/dev/nvme0n1\"}]]\nRunning: emcmd debug=cmdCreatePool,cmdAssignDisk,cmdMakeBootable\nRunning: emcmd cmdCreatePool=apply&poolName=boot&poolSlots=1\nmkbootpool: command failed or timed out\nemcmd request fa...[truncated]"
  },
  "status": 1,
  "error": {
    "name": "Error",
    "code": 1,
    "message": "Internal boot setup returned ok=false",
    "category": "unknown",
    "networkError": {
      "status": 1,
      "result": {
        "ok": false,
        "code": 1,
        "output": "assignableDisks snapshot: [{\"id\":\"INTEL_MEMPEK1J016GAL_PHBT90950652016N\",\"serialNum\":\"INTEL_MEMPEK1J016GAL_PHBT90950652016N\",\"device\":\"/dev/nvme0n1\"}]\nassignableDisks resolved serialNum->device: [[\"INTEL_MEMPEK1J016GAL_PHBT90950652016N\",{\"bootId\":\"INTEL_MEMPEK1J016GAL_PHBT90950652016N\",\"devicePath\":\"/dev/nvme0n1\"}]]\nRunning: emcmd debug=cmdCreatePool,cmdAssignDisk,cmdMakeBootable\nRunning: emcmd cmdCreatePool=apply&poolName=boot&poolSlots=1\nmkbootpool: command failed or timed out\nemcmd request fa...[truncated]"
      }
    }
  }
}

Upgraded both systems last night from 7.2.2, no signs of any issues yet. GUI feels faster and more responsive including the login screen. Like the new onboarding experience as well. Very nice release so far all around.

Updated three servers from 7.2.6 to 7.3.0. No issues on any of the three have been discovered.

I am still using USB boot on all three servers. It isn't broken and I don't yet see a need to "fix" it. Nice to have the option in the future if needed, but, happy to stand pat for now.

I skipped the onboarding process on all three upgrades and left everything "as-is"

14 hours ago, GuiltlessGibbon said:

4 data disks + 2 parity, all SSD

Probably not directly related to your problems, but in case you weren't aware, SSDs in the array cannot be trimmed.

I've got a strange problem with any update after 7.2.4. The system will be stuck at (Starting Array: Mounting Disks) for a long time and when the system is finally up it will be sluggish (barely responsive) and one of my drives will always fail and be offline.

When I downgrade back to 7.2.4 all is working fine again.

I tried it with 7.2.5, 7.2.6, 7.3.0 all the same, my second server upgraded without an issue.

Attached is the diagnostics if anyone can figure it out...

vidas-diagnostics-20260514-1603.zip

Upgraded from last Stable / LOG is now getting flooded with the same message

detailed here: https://forums.unraid.net/topic/198830-help-730-causing-runaway-logging/

Edited May 14May 14 by landS

2 hours ago, JorgeB said:

I cannot reproduce the pool RESET/SCRUB buttons not working, one of the affected users, please create a new thread in the general support forum, and we can continue there.

Sorry but what does the reset button do? corruption errors doesn't seem like something you just reset.
I had a bunch of corruption errors on 2 pool drives (see earlier post). Reset button was clickable im pretty sure, but i got scared and downgraded to 7.2.6 instead

34 minutes ago, PSYCHOPATHiO said:

I've got a strange problem with any update after 7.2.4. The system will be stuck at (Starting Array: Mounting Disks) for a long time and when the system is finally up it will be sluggish (barely responsive) and one of my drives will always fail and be offline.

Diags are from 7.1.4, please create a new thread in the general support forum and post diags after updating.

7 minutes ago, jensrobot said:

I had a bunch of corruption errors on 2 pool drives (see earlier post). Reset button was clickable im pretty sure, but i got scared and downgraded to 7.2.6 instead

7.2 will have the same pool errors; it just won't warn you about them.

If you need further help, please create a new post in the general support forum and post the diags, this thread is not the best place for troubleshooting