refsutil does not work on server 2022 with refs version 3.7 #6950
Comments
|
I have the same issue, but my version is 3.9. Very frustrating! |
|
@clonea1 @morgenman Can you both share what version and SKU of Windows you're running? @morgenman Presumably you're on an Insider build. I don't think 3.9 is in-market anywhere yet, but the point is valid that refsutil should always be compatible. |
|
It does help - we have this fixed in the latest Windows Server 2022 Datacenter: Azure Edition builds but we're working to get this backported to the in-market Windows Server 2022 SKUs that run on-prem. Unfortunately I don't have a timeline for you today. I'll follow up ASAP. |
|
Thanks so far I have only had refs corruption on one of the volumes I used for client backups with dedup running. The first time was due to storage bus cache drive failure and thankfully the volume remounted after the failed bus cache disk was removed so no data loss. But the most recent time I could not recover the volume so I purged it instead. But no prod data as just backups, so I lost historical roll back but restored with a fresh volume backup services. So far though yeh these refs corruptions circle around dedup volumes for me. And then with out a working util...
Anway good to see it was fixed I also noticed that w11 refs util is a newer version but I couldn't figure out a way to hack and slash that into server 2022. And no way I would be able to mount my storage spaces virtual disks to client os lol
…________________________________
From: Billy Smolen ***@***.***>
Sent: Tuesday, February 14, 2023 6:15:55 PM
To: MicrosoftDocs/windowsserverdocs ***@***.***>
Cc: clonea1 ***@***.***>; Mention ***@***.***>
Subject: Re: [MicrosoftDocs/windowsserverdocs] refsutil does not work on server 2022 with refs version 3.7 (Issue #6950)
It does help - we have this fixed in the latest Windows Server 2022 Datacenter: Azure Edition builds but we're working to get this backported to the in-market Windows Server 2022 SKUs that run on-prem.
Unfortunately I don't have a timeline for you today. I'll follow up ASAP.
—
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindowsserverdocs%2Fissues%2F6950%23issuecomment-1430517593&data=05%7C01%7C%7Cf09b8c5779d94298f2a608db0ee16cdb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638120133571516266%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lQjyU7CqzlzZ5VKw1d8t7%2B2GafGm7fLA6lbCHs42mlw%3D&reserved=0>, or unsubscribe<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIAVQGNNPWF7EY2ZX3BLQNDWXQG2XANCNFSM6AAAAAATUDS6WM&data=05%7C01%7C%7Cf09b8c5779d94298f2a608db0ee16cdb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638120133571516266%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WaYwV%2BZIgSnNeaecd3p8%2BuKMfNv8n%2Fp4S0G04vVYsEA%3D&reserved=0>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
@clonea1 try copying refsutil.exe from Win11 and pasting it into C:\Windows\System32 on the affected system. That should work for ReFS 3.7 (you will need to overwrite the existing binary) |
@clonea1 If you can repro this, I would love to chat live. Feel free to DM me here on GitHub, or if you have Teams federated with Microsoft's tenant, you can ping me directly at -removed- |
|
I copied refsutil.exe from Windows 11 Dev to Windows Server 2022 and it worked for me. there is no error of |
|
Hi all. I'm in a bit of a pickle with ReFS. Here's a timeline: -Server hardware failed. ReFS drive in question had dedupe enabled on Server 2022, failure was related to motherboard. Windows 11 22H2 doesn't recognize deduped blocks. I've tried using tools like UFSExplorer but it fails, cannot read data when trying to copy volume. Using salvage and copying the contents to a new disk still carries the corruption over. Any suggestions are greatly appreciated. ReFS is incredibly fragile, this is unfortunate. |
|
Correct the client sku OS does not support dedup feature enable, their used to be some old back door ways to get dedup working on client os but it was fickle ever time a feature update came down.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
From: ***@***.***>
Sent: Tuesday, August 1, 2023 7:38 PM
To: ***@***.***>
Cc: ***@***.***>; ***@***.***>
Subject: Re: [MicrosoftDocs/windowsserverdocs] refsutil does not work on server 2022 with refs version 3.7 (Issue #6950)
Hi all. I'm in a bit of a pickle with ReFS. Here's a timeline:
…-Server hardware failed. ReFS drive in question had dedupe enabled on Server 2022, failure was related to motherboard.
-I plugged drive into a Windows 11 22H2 workstation to verify drive was fine. ReFS updated to 3.9 (jfc Microsoft)
-I plugged the ReFS deduped volume back into replacement server hardware, shows up as RAW (incompatible with Server 2022)
Windows 11 22H2 doesn't recognize deduped blocks. I've tried using tools like UFSExplorer but it fails, cannot read data when trying to copy volume. Using salvage and copying the contents to a new disk still carries the corruption over.
Any suggestions are greatly appreciated. ReFS is incredibly fragile, this is unfortunate.
—
Reply to this email directly, view it on GitHub<#6950 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIAVQGMIBNZGVHRTSYOAIUTXTGHNTANCNFSM6AAAAAATUDS6WM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
refs is in need of update
ReFS version: 3.7
Error: The volume is an unsupported ReFS version. This utility supports versions up to 3.5. Volume is 3.7.
Error: Command failed.
Error: The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupt.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: