3

On a Windows Server 2016 the ReFS volume can't be mounted any more. The eventlog shows

refs 133

The file system detected a checksum error and was not able to correct it. The name of the file or folder is ....

refs 135

Volume is formatted as ReFS but ReFS is unable to mount it; ReFS encountered status The volume repair was not successful.

Diskpart shows an emtpy, raw formatted 50TB disk.

All suggestion I found were to unmount / mount the disk (which didn't help) or to use a data recovery software.

The underlying hardware raid seems to work properly.

Has anybody faced this errors and solved it?

2

You can try to restore ReFS one time by using free software which is simply restoring the partition if no blocks were written. However, it can be a rare situation where nothing can help restoring ReFS partition cause metadata just corrupted or missed and nothing will help...

Do you have any backups?

What is your reason to use ReFS instead of NTFS

| improve this answer | |
  • 3
    This is the backupserver. We use ReFS due to the veeam integration in ReFS. Yes, we have offsite backups but would loose the backups older than 4 weeks. – marsh-wiggle May 27 '19 at 13:31
  • 2
    Can you recommend me any recovery solution? – marsh-wiggle May 27 '19 at 13:33
  • @marsh-wiggle If you really need to use ReFS for backup repo you'd better stick with Windows Server 2016 as it has ReFS more or less working. Windows Server 2019 should be avoided according to Veeam B&R PM guy. reddit.com/r/Veeam/comments/bc5qen/… – BaronSamedi1958 May 28 '19 at 12:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.