Forum Discussion
ReFS volume appears RAW (version doesn't match expected value) after Windows Update
I solved this by uninstalling KB5009557. The ReFS volume came back working as it should, instead of appearing as RAW.
Update: since even the February 2022 Windows Update bricks ReFS in the same way, and hints from Microsoft are that ReFS 1.x is no longer supported, we copied everything to new disks, upgrading ReFS from 1.2 to 3.4 in the process. Such a (manual) ReFS upgrade should be the solution that everyone needs, allowing to re-enable Windows Update.
Are there any events in the ReFS event log ?
As a test can you temporarily connect that pass-through SAN disk to another VM that is at RTM or late 2021 build level and see if it can read it. If it can that could be related to the issue (but seems unlikely). If it also cant read it then , there is some real damage/corruption.
Thank you for your response! as far as the logs, there is nothing consequential in the hosts, the VM however lists a lot of the following:
ReFS failed to mount the volume.
Context: 0xffff928b8960f180
Error: The I/O device reported an I/O error.
Volume GUID:{1eb14e22-8b1b-4ad6-bf40-bbb5038228f9}
DeviceName:
Volume Name:R:
I removed the volume from the VM and took it offline in failover cluster manager, now when trying to bring it back online it fails and looking in the storage pool area of server manager, it shows as operation status of disconnected. If I attach it to one of the hosts, I am then able to browse the contents, so the data appears intact.
It could be something MABS/DPM is having issues with. I would try the test you suggested, except I can longer bring the volume online within the cluster.
Thank you again for jumping in here, really appreciate it!
- stephc_msft2
I created a new VM without updating it and a new passthrough SAN lun that is partitioned with refs. I'll let you know if it does the same thing.