Azure Local: The file system detected a checksum error and was not able to correct it. The file(s) or folder(s) impacted are Container Metrics Table

Richard Beyer 136 Reputation points
2026-07-04T17:24:21.1266667+00:00

I have a two node Azure Local HCI cluster on Dell AX-760 systems. I just did the update to 12.2606.1003.205 and I now see two alerts that were not there before the update in the WAC dashboard.

One is a warning: The file system detected a checksum error and was able to correct it. The file(s) or folder(s) impacted are Duplicate Container Table,Medium Allocator.

The other is a Critical: The file system detected a checksum error and was not able to correct it. The file(s) or folder(s) impacted are Container Metrics Table.

Neither the Dell Open Manage Integration extension or the WAC console are reporting any storage health issues

What are my next steps to resolve this?

Regards,

Rich Beyer

One more thing: I am not using any containers, only VMs.

Azure Local
Answer accepted by question author
Alex Burlachenko 25,120 Reputation points MVP Volunteer Moderator
2026-07-14T08:16:26.6966667+00:00

hi Richard Beyer & thx for sharing urs issue here at Q&A portal,

fact that these alerts appeared immediately after the Azure Local update makes me wonder whether the update triggered a metadata consistency check rather than introducing new corruption. The warning for the Duplicate Container Table indicates the filesystem detected and corrected an issue. The Container Metrics Table alert is more concerning because it couldn't be corrected automatically. Despite the name, those 'Container' structures are internal ReFS metadata and aren't related to Windows containers or Kubernetes, so it's expected to see them even if you're only running VMs.

The first thing I'd do is review the Storage Spaces Direct and ReFS event logs around the time of the upgrade, then run a cluster validation focused on storage. If Get-StorageHealthReport and Get-StorageJob are clean and Dell OMSA isn't reporting disk or controller issues, this could be a ReFS metadata issue rather than a hardware failure.

I wouldn't ignore the critical alert, though. If the checksum error remains after a reboot and there are no active repair jobs, I'd open a Microsoft support case. Include the cluster logs (Get-SddcDiagnosticInfo), the event IDs for the ReFS errors, and mention that the issue first appeared immediately after updating to 12.2606.1003.205. That will allow the Azure Local team to determine whether this is a known regression in that build or whether the filesystem metadata needs repair.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/

 

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.