Asked by:
The ReFS volume can not be recognized even though all the HDDs are recognizing the parity configuration storage space

-
The title is as follows.
A few years ago, I created a parity drive on Windows Server 2012. The configuration is as follows.
HDD: SATA 3 TB x 4, file system: ReFS v 1, recoverability: parity, number of columns: 4
I tried to connect this parity drive to the Windows 10 Enterprise Edition Insider Preview version and copy the data to a new HDD.
However, I missed the entire parity drive in the middle of copying. (Now I should suspend processing at this point in doubt, I was confidently overconfidence of ReFS 's recoverability)
After rebooting, the drive became visible again, so I updated the driver of the SATA I / F card that I have connected and started copying again. But again the drive came out of sight. And when I restarted the PC, I got into a strange situation.
I can mount the drive, but I can not see the file system. It became recognized as "RAW" file system. Supplemental note: I have used version v1 without raising the version of ReFS.
I thought it was funny and I connected the drive to the machine at Window Server 2012 again, but the result was the same. The drive appears, but when you access it the following message will be displayed.
"Z: \ is not accessible. The parameter is incorrect."
I attempted to rescue the file with ReclaiMe or R-Studio, but it seemed that some files were corrupted. I do not know if this comes from the imperfections of these software, or it really got broken.
Since ReFS is not a premise that it is damaged, chkdsk does not exist, so I think that it can not be set to the previous mount state.
As a question, is there a way to mount this parity drive again so that it can be successfully accessed from the Explorer?
The HealthStatus of Get-PhysicalDisk of the HDD belonging to the parity drive is all Healty.
ReclaiMe can make VHDX file, but even mounts of 8 TB VHDX files mounted as RAW drive. It was impossible to repair the created VHDX with VHDTool.exe.
Perhaps it seems to be a problem with the I / F card, but maybe it is a bug against ReFS v1 in Windows 10. (It may be wet clothing)
Please let me know if you have any additional information to provide.
As an interesting behavior, I attempted mounting after removing four HDDs one by one and connecting three HDDs, the following two different behaviors have taken place.
1. Can mount but ReFS volume is not visible from Explorer
2. Can not mount. A red error mark appears instead of a warning in Server Manager
When I right-click Virtual Disks in Server Manager, "Repair Virtual Disk" appears. Even though all HDDs are connected and all are in Healthy state. Should I try "Repair Virtual Disk"?
I also found the following log in the Event log.
Drive hosting data for virtual disk {e7c3c7f8-e323-11e2-93f0-001fd095158f} have failed or are missing. As a result, no copy of data is available at offset [Slab 0x0 Column 1 Copy 0 State 4 Reason 1] [Slab 0x0 Column 2 Copy 0 State 2 Reason 1].If I have no choice but to recover from the backup, I will not be able to trust ReFS's parity drive, but if it can be confirmed that two or more drives are corrupt it may be inevitable.
- Edited by watercolor Saturday, November 11, 2017 7:48 AM
Question
All replies
-
Hi watercolor,
According to error message, " Drives hosting data for storage space have failed or are missing...". The problem may still related to failed or missing drives in a Storage Spaces storage pool.
And according to your description, "can mount the drive, but I can not see the file system. It became recognized as "RAW" file system".
When a volume shows up a RAW, it means that for whatever reason, the file system cannot be mounted. It doesn't have anything to do with Windows detecting the drive. If Windows couldn't detect the drive, it wouldn't show up in Disk Management at all.
Since ReFS cannot be chkdsk-ed fastest way would be recovering from backup.
Maybe you could refer to the thread discussed before.
In your scenario, you move the drive from server to client. Since it's two version, please also make sure the drives are certified hardware when moving between two different version computers.
Best Regards,
Mary
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com. -
Thank you for your reply.
Yes, restoring from backup is the correct solution.
But what I wanted to ask is, in this way, is ReFS the whole drive becomes a single point of failure.
And when I get into this situation I have to destroy the entire drive.
When I become like this I want to know that there is not any remedy for ReFS as Windows.
Whether it is a bidirectional mirror or a parity, I think that it is necessary to clearly indicate the possibility that ReFS will lose its entire drive due to a power failure or the like.A certain amount of downtime is acceptable, but if the whole drive goes down like this, I will use features like Drive Extender on Windows Home Server.
ReFS is a wonderful file system with self-healing capability, but since it is not assumed that it is damaged, we will see one side that is occasionally weaker than NTFS. -
Hi watercolor,
Thanks for your feedback.
Based on my knowledge, in theory, if corruption occurs, ReFS can detect and, when configured with Storage Spaces, automatically correct the corruption.
https://docs.microsoft.com/en-us/windows-server/storage/refs/refs-overview
https://msdn.microsoft.com/en-us/windows/compatibility/resilient-file-system
And as suggested, since you move drives between two version computers, please also make sure the drives are certified hardware when moving between two different version computers.
Appreciate your support and understanding.
Best Regards,
Mary
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Proposed as answer by Mary DongMicrosoft contingent staff, Moderator Friday, November 17, 2017 7:10 AM
-
Hi,
Could the above reply be of help? If yes, you may mark it as answer, if not, feel free to feed back
Best Regards,
MaryPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.