![]() ![]() It also gives us a high degree of confusion as to what is actually wrong with the volume. This gave us a high degree of confidence we probably could recover the data. ![]() “ -x” means “unmount the volume” before we go (if we didn’t do this we had access denied errors) and “ -v” means be verbose about the output.Īs described in the output above, there were no issues on the volume. ![]() “ C:\salvage” was the directory where we were storing metadata about the recovery process. “ E:” is the drive that was not mounting (our corrupted ReFS volume). To explain, “ -D” says “diagnose” why the volume is failed. Fascinatingly, ReFSutil thought everything was fine: C:\salvage>refsutil salvage -D E: C:\salvage -x -v Knowing that our volume had data, the first thing we wanted to do was to verify if ReFSutil could see the corruption. You can see all of the options available in ReFSutil for data salvage by running “refsutil salvage” with no options. Much of our learning was greatly assisted by this article. There is almost no documentation or information about this tool, but it saved the day for us – and so I thought it was worth noting down some useful things we learnt about how to use the tool. The post in the Veeam digest indicated that it existed, was probably good, but no one really knows what it does. This tool provides a mechanism to triage and recover failed ReFS volumes. While the differences don’t necessarily explain why it might not work, I had a hunch that maybe the reason the restore wasn’t working correctly was because we were in fact on too new a version of ReFS for the ReclaiMe software to work.Ī few weeks ago, Anton Gostev from Veeam wrote about a new, otherwise undocumented tool in Windows 2019 called “refsutil”. ReclaimMe identified the disk as a ReFS 2 volume. It turns out that MS has several versions of ReFS, and the current version is 3.4 (as of Windows 2019 and the Windows 2016 1803 update). We could see that it should be working, but couldn’t understand why it wasn’t. We provisioned a new NTFS volume and ran the data recovery however the majority of the data we recovered was unreadable. It found all the files we were expecting to find on the volume, and displayed them in the tree. ReclaiMe is a commercial tool that allows you to do data recovery from a number of volumes. We really wanted to get the data that was on this disk to avoid having to roll back to an earlier backup.Īfter much anxiety (and googling) we decided to try a few strategies to get the data back. Entirely helpful messages from the Event Log Windows provides “really helpful” error messages: Attempting to open the volume in Explorer provides this immensely helpful error message. Doing some investigation, it looked like all the data was there, but just the metadata was obstructed in some way. Instead we got hit with a classic ReFS RAW Volume essentially a disk that Windows could see, but was unable to mount. The error generated was a useless generic “An Unexpected Error Occurred.” We opened a support case with Microsoft, and after some basic testing came to the conclusion that the error might have been caused be a specific registry setting, and so brought our storage online.Įxcept that it didn’t come online. Essentially, we’d been experiencing some issues with a Windows 2019 Hyper V Cluster resulting in storage becoming unavailable. I’m no technical expert on ReFS, but we’ve recently run into an issue with an ReFS Cluster Shared Volume in Windows 2019 that was nice and yucky. It scales beautifully, and has no fixed capacity limitations that matter in this day and age. It offers many awesome new features, particularly if you are using Storage Spaces and lots of disks. ReFS is Microsoft’s new file system that will one day replace NTFS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |