User Profile
stephc_msft
MicrosoftJoined Feb 01, 2019
User Widgets
Recent Discussions
Re: ReFS volume inaccessible after update from Windows 10 22H2 to Windows 11 23H2
I've not heard on any other reports of this, but will check. Use of ReFS on Windows11/client is, or was, non-typical. But there is now a new 'Dev Drive' feature that uses ReFS https://learn.microsoft.com/en-us/windows/dev-drive/18KViews1like17CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
And since you cant easily boot from alternate med0a (usb/dvd/sio) there is no way to tempoarily boot ws2012r2 to see if that still recognises it [of was possible then would boot the install disk and exut setup into recovery, and the necessary spaces drive etc would be working]. So what is the actual set up of any hdd / spaces that the refs volume lives on? And chance of adding a dumb 2TB disk as we could 'copy over' the raw refs volume to that to see if that recognises it.4.5KViews0likes2CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
So there is a set of disks (hdd probably) set up as storage spaces, and the storage spaces virtualdisk has an ReFS volume. That spaces disk/volume shouldnt be considered removable, and hence not sure this is showing RAW due to the 'no longer supporting removable media with Refs v1' issue. What hba adapter of the relevant hdd's on? probably a HP something or iaStorAVC (msinfo32, storage, scsi should show it eh Intel chipset sata raid controller) Find that drive in the system registry (system\currentcontrolset\services\xxxx) and look under Parameters for the BusType if set to 10 (0x0a) = sas [and removable] then try changing to 8 (raid, even though not using raid)4.5KViews1like6CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
Well earlier OS's (like WS2019 with Refs 3.4) CANT use refs (3.7) (eg from a disk formatted by a ws2022 system), so you DONT want to update the refs v3 version UNLESS you update the OS AND never need to present the disk to an older OS ever again. A few people have been caught out by this. There is a registry key that can be set to avoid a later OS updateing the refs version but MUST be set before the disk is presented to it5.3KViews1like11CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
As per my Jan28 message If you mean v1.2 to v3.x then no. Only option would be to create a new disk, format refs (which will be v3.x) and copy data over (with Exchange or anything using the volume tempoarily off)(or maybe Exchange has a way to move/migrate data to a new drive whilst it all live). Note you will only be using refs v1.2 if the data disks were originally created by Server 2012/2012R2. If you are already on refs v3.x then Im not sure I understand the question5.4KViews1like13CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
Hunduma_Merzo so did you do anything to that system or disk before it became RAW ? eg temporarily attach the disk to a server running a later OS version? Does the ReFS event log (Applications and services, Microsoft, Windows, ReFS) say anything? 4.4TB physical disk on a physical server or is it a VM ? What OS version ?6.1KViews1like0CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
Agreed. Note however that refs v1 does not get auto updated to v3 That only happens on the v3.x versions ie 3.1>3.4->3.7 Hence why 'stuck' with older refs v1 volumes in some cases ANother option is to to boot the 'Recovery OS' or boot from an Install iso /usb and select reapir. That will be a base OS version (without patches) and can access the data on refsv1 and copy it off. Reminder - all this hassle only affects drives that are removable or have charactereistics of removable (like on vmware). With the exception of Mikes original issue which is a weird and unexplained one.15KViews1like5CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
Agreed. Try removing Jan22 update, and any later updates, and confirm if the volumes are then accessable. If they are still showing RAW then it is likely you have some other real corruption issues . There are some utilities (including refsutil.exe from later OS versions) and 3rd party tools like www.r-studio.com that understand refs and can attempt to scan and copy out any data it can find.13KViews1like8CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
Yes, refs v3.1 on WS2016 will be ok after Feb updates. Note that if still using v1.2 refs disk on WS2016 or later, then the v1.2 disks will still be affected, it they are detected as removable/hoypluggable.13KViews0likes13CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
ngruendl Can you confirm if you are running on VMWare ? Have you tried the vmware solution of disabling hotplug? As that is the only solution for WS2012R2 using refs on disks that are showing characteristics of 'removal' (like VMWare presents) Cant comment on why updates got applied even after you were 'disabling' updates.14KViews0likes5CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
Unfortunately the only way to upgrade the ReFS version (if using refsv1 disks on WS2016 or later) is to create new disks or reformat old disks (and confirm refsv3.x) and copy/restore data. For those still on WS2012R2 (which doesnt support refsv3), then the best (and only) soln if on VMWare is the vmware disable hotplug soln . If WS2012R2 and NOT on VMWare then shouldnt be affected by the issues (except in much rarer circumstances such as really using removable USB drives etc) KB5010691: ReFS-formatted removable media may fail to mount or mounts as RAW after installing the January 11, 2022 Windows updates (microsoft.com) But only briefly touches on the refs version and WS2012R2 aspect81KViews0likes28CommentsRe: ReFS volume appears RAW (version doesn't match expected value) after Windows Update
The main issue is there are various versions of REFS ReFS v1 as used on Server 2012R2 and ReFS v3 used on later OS's The Updated fix, for Refs on removable drives, only addresses the ReFS v3 case and does not (and never will) address the refsv1 case. Note that some disks, even on later OS's might be using ReFS v1 if they were originally set up on earlier systems And so the fix will not help on those disks on those systems Since its mainly VMWare VM's that are affected, as they consider hotplug disks as removable, suggest using the vmware devices.hotplug solution described earlier You can check the Refs version with fsutil fsinfo refsinfo x: (although cant do this if the drive is currently showing as RAW)82KViews1like47Comments
Recent Blog Articles
No content to show