Summary
This article describes how to troubleshoot a corrupted or unmountable local disk on a standalone Windows Server 2022 Standard system that uses the Resilient File System (ReFS). The server experiences a series of stop errors, and then the local disk volume becomes inaccessible. The issue is caused by driver conflicts between Windows Server storage drivers and third-party security or backup software.
Symptoms
While you run a standalone Windows Server 2022 Standard system that uses ReFS, you experience one or more of the following symptoms:
- Stop errors occur during normal operation.
- After you restart the computer, the local drive (for example, drive D) doesn't mount.
- You can't manually access or mount the local drive.
- The Disk Management tool displays the local drive as RAW.
- Uninstalling antivirus software doesn't resolve the instability.
- The local drive appears to be corrupted or damaged.
- Backup operations fail because the backup engine can't access the local drive.
Cause
This issue occurs because of conflicts between Windows Server drivers for third-party security or backup software such as Veeam, ESET, or CrowdStrike. Typically, the driver or driver altitude settings of the software are incorrect.
These conflicts can cause corruption of the ReFS file system. At that point, the volume dismounts or enters a RAW state.
Resolution
To restore access to the affected drive and recover data, follow these steps:
-
To put the affected volume in read-only mode, open a Command Prompt window, and run the following commands, in sequence:
diskpart list volume select volume <VolumeID> attributes volume set readonly exit[!NOTE]
In these commands, <VolumeID> represents the number or drive letter that identifies the volume. -
Review and correct the driver altitude settings of any installed security or backup software to make sure that they don't conflict with storage drivers.
-
If you can't resolve the conflicts, uninstall any conflicting security or backup tools.
-
Use the ReFS salvage tool (
refs-util) to recover data from the volume, and then try to restore the volume to a healthy state. -
Remount the volume.
-
Run
chkdskorrefs-utilto verify the integrity of the data on the volume. -
To prevent future failures, verify that backup operations run correctly.
Data collection
If the issue persists after you finish the resolution steps, collect the following data, and then contact Microsoft Support:
- The exact Windows Server 2022 Standard build version. To find this information, run
winverat a command prompt. - Details of installed security or backup software and driver versions.
- A list of recent changes or updates that were applied to the system.
- Event data that covers the period during which the stop errors occurred. You can export this information from Event Viewer.
- Output from the DiskPart tool that shows the current state of the affected volume.
- Results from ReFS salvage tool (
refs-util) operations.
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
