Dec 03 2023 01:15 PM - edited Dec 09 2023 11:04 AM
The starting point of this post was an up-to-date Windows 10 22H2 system, with two mirrored Storage Spaces (one NTFS, the other ReFS).
ReFS always was officially supported in this scenario, as this is Windows Pro for Workstations. The ReFS volume was formatted directly with ReFS version 3.4, six months ago. BitLocker is enabled.
Today I gave in to the insisting Windows Update prompts, finally allowing it to update to Windows 11 23H2. All went apparently well, without pre-check warnings, and with no update errors.
After the update to Windows 11 (build 22631.2715, refs.sys 10.0.22621.2506), the ReFS drive shows up as "Local Disk", but cannot be opened in File Explorer. The event log contains entries like "Volume X: is formatted as ReFS but ReFS is unable to mount it; ReFS encountered status The file system encountered a metadata file with inconsistent data."
On the affected system, fsutil fsinfo refsinfo x: now gives "Error: The file system encountered a metadata file with inconsistent data. A local REFS volume is required for this operation."
The storage space still mounts and works well on a different (Windows 10) system, providing these details:
REFS Volume Serial Number : [redacted]
REFS Version : 3.4
Number Sectors : 0x0000000121994000
Total Clusters : 0x0000000121994000
Free Clusters : 0x0000000022f8ff75
Total Reserved : 0x0000000000084548
Bytes Per Sector : 4096
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Fast Tier Data Fill Percentage : 0.0%
Slow Tier Data Fill Percentage : 0.0%
Fast Tier to Slow Tier Rate (Clusters/s) : 0
Checksum Type : CHECKSUM_TYPE_NONE
This reminds me of similar issues Windows Server had last year after a Windows Update, although at the time the affected ReFS version was 1.x, while now it is 3.4:
I suppose that the (expensive) workaround will be, as in the past, to copy everything to a storage space with a newer ReFS version, so I already ordered some new disks.
Perhaps ReFS experts @stephc_msft or @RajDas_FS can give the issue a look?
P.S.: I found a comment at https://gist.github.com/0xbadfca11/da0598e47dd643d933dc that says "11 v22H2 (refs.sys 10.0.2621.1) can't mount 3.1 3.2 3.3 and 3.4 with read-only, or with RefsDisableVolumeUpgrade. Maybe bug."
Dec 05 2023 11:19 PM
Dec 08 2023 02:08 PM
Dec 08 2023 06:01 PM
Dec 08 2023 08:38 PM
Dec 11 2023 02:30 PM - edited Dec 11 2023 02:31 PM
No this is an entirely different thing and more like by design. The one I talk about does affect Windows Server vNext and ReFS 3.10
Dec 14 2023 06:34 AM
Dec 18 2023 10:16 AM
Hey @MikeLabatt,
I am facing the exact same issue.
Updated to Windows 11 because of the annoying popups.
Going back to Windows 10 is not a solution. I can´t read the ReFs File system any more.
Running ReFSUtil Salvage -QS I: C:\refsutil get´s no errors as far as a can see.
Versión de ReFS: 3.4
Using https://www.reclaime.com/ I can see that all the files are there.
I have 3 x 4TB drives in parity mode. No hardware problem found.
Now I am waiting for a new drive to copy all my data.
This is not what I was expecting from a "Resilient " File System.
No solution found yet. Let me know if you get some success.
Dec 19 2023 03:39 PM
Update... Out of curiosity, I attached the same ReFS 3.4 (mirrored storage space) volume which won't mount on Windows 11 (but works fine on Windows 10), to a Windows Server 2022 system. Not only it mounts fine, but it auto-updated to ReFS 3.7 (per fsutil fsinfo refsinfo x:)
Right now I can't power off the Windows 11 box to see if the disks mount fine there as well after the update to 3.7, but I will post an update. There is some hope that the updated volume can now be seen by Windows 11 without requiring the lengthy copy process. Still a waste of money and time on new disks and troubleshooting before Christmas, while there has been no official answer here in more than two weeks...
Jan 02 2024 08:10 AM
Jan 03 2024 06:13 AM
I solved my issue by creating a new Hyper-V virtual machine with Win10 on the existing Win11 machine and connected the storage pool to the virtual machine. Interestingly, the storage pool shows as a simple drive machine. Previously, I had to take the pool drive offline from the main Win11 machine in order to connect it to the virtual machine. Now I can backup the data and no longer use RefS on a storage pool. Simply not reliable to me.
Feb 06 2024 01:22 PM - edited Feb 06 2024 01:24 PM
SolutionSince opening this thread in December, I'd like to share two "solutions" (workarounds):
1) As mentioned before, I attached the ReFS 3.4 volume which wouldn't read on Windows 11, to a Windows Server 2022 system, which auto-updated it to ReFS 3.7. Moving the disks back to the Windows 11 system, I can confirm that they now work fine. Storage Spaces on Windows 11 prompted to upgrade the pool, but the data was readable both before and after this upgrade. The ReFS version remained unchanged at 3.7. This solution does not require purchasing new disks, but it does require access to a Windows Server 2022 system.
2) The other method is to get new disks and copy the data, using an OS version like Windows 10, which can read the ReFS 3.4 volume which became unreadable after the upgrade to Windows 11.
Feb 15 2024 05:27 AM
Feb 20 2024 05:08 AM
@MikeLabatt I ended up installing Windows Server 2022 and both ReFS drives were fixed in seconds. Then I switched back to Windows 11 and it works fine. Thanks for the working solution.
I don't understand why MS couldn't put functionality that converts ReFS to a newer version to Windows 11 as well.
Feb 20 2024 11:19 AM
Mar 06 2024 04:55 AM
Feb 06 2024 01:22 PM - edited Feb 06 2024 01:24 PM
SolutionSince opening this thread in December, I'd like to share two "solutions" (workarounds):
1) As mentioned before, I attached the ReFS 3.4 volume which wouldn't read on Windows 11, to a Windows Server 2022 system, which auto-updated it to ReFS 3.7. Moving the disks back to the Windows 11 system, I can confirm that they now work fine. Storage Spaces on Windows 11 prompted to upgrade the pool, but the data was readable both before and after this upgrade. The ReFS version remained unchanged at 3.7. This solution does not require purchasing new disks, but it does require access to a Windows Server 2022 system.
2) The other method is to get new disks and copy the data, using an OS version like Windows 10, which can read the ReFS 3.4 volume which became unreadable after the upgrade to Windows 11.