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.
Server 2012 R2 on HP Micro Gen8 server. Absolutely awful hardware as far as boot is concerned! (it can only boot from internal USB if one used ODD bay for SSD, MBR only, just awful)
Could not upgrade to either 2019 or 2022 because setup would throw all sorts of error on reboot & always revert back to original OS, 2012 R2
I did not want to do clean install, because could not be bothered to re-configure the all the bits on the server
Took the SSD out, converted to vhd, used Virtualbox, disabled plenty of hardware related services, run Server 2022 upgrade, worked fine.
Converted vhd back to SSD, server boots fine
But ofcourse the existing Storage Spaces with ReFS are showing as RAW
Not huge amount of data, < 2 Tb
What is now the quickest way to access it?
Seb
MicrosoftWhat 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)
Booting from MBR WinPE USB created by ADK 8.100.26020 can see the Storage Spaces volume & access it just fine. So just (as per https://superuser.com/questions/696004/copying-a-directory-by-retaining-its-permission )
xcopy c:\source_folder_name e:\destination_folder_name /O /X /E /H /K /Crobocopy F:\ H:\ /MIR /LOG:c:\temp\ReFS-mirror-log.txt
to USB 3 attached 2Tb drive does the job of saving the data.And once rebooted FreeFileSync back onto newly formatted ReFS 3.x
But is is INSANE that WinPE from (by now) abandonware version Win 8.1 CAN read ReFS 1.2, but full Server 2022 cannot do that
At least provide RO capability!!! in worse case
Seb- I am sure the filesystem is fine, just not being read. In worse case I will swap the SSD to previous one (with Windows 2012 R2), but wanted to avoid it (fuff going up the ladder to the high cabinet - this is where I have the server)
First I will try to boot to USB made with WinPE from ADK 8.100.26020 - stephc_msftAnd 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. - Just Operational & it is blank
- stephc_msftmsinfo would probably show that under storage, ide
but no way to set any BusType for that.
Not sure if the 'removable' aspect is the cause here.
Does the refs event log say anything ? msinfo32, storage, scsi gives only Microsoft Storage Spaces Controller
Controller is set to AHCI in BIOS
Seb