ReFS volume got corrupted in a matter of hours

[Guest /u/OscarCalvo74]

I am setting up a storage tier with parity with 2 disk tolerance with Windows Storage Spaces, formated a brand new volume with ReFS.

 

At 3 am, i got these errors:

 

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

 

The file system detected a global metadata corruption and was not able to repair it on volume Q:. Attempting a readonly volume mount may succeed.

 

The file system structure on volume Q: cannot be corrected.

 

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

 

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

 

All my disks report healthy.

 

I have now, reformatted the volume, but I dont trust this anymore.

 

Update:

 

The system won't boot if using virtual disk with a "RAID6"

 

New-StorageTier -StoragePoolFriendlyName "HOME Storage Pool" -FriendlyName "HDD" -MediaType HDD -ResiliencySettingName Parity -PhysicalDiskRedundancy 2

 

New-StorageTier -StoragePoolFriendlyName "HOME Storage Pool" -FriendlyName "SSD" -MediaType SSD -ResiliencySettingName Parity -PhysicalDiskRedundancy 2

 

Is having disks with different physical sector size in the same tier a problem?

 

I have 2 old disks with a sector size of 512

 

└ $ Get-PhysicalDisk | where { $_.MediaType -eq "HDD" } | select -Property FriendlyName,PhysicalSectorSize

 

FriendlyName PhysicalSectorSize

 

Pool_HDD_08 4096

 

SAMSUNG HD204UI 512

 

Pool_HDD_05 4096

 

ATA SAMSUNG HD204UI 512

 

Pool_HDD_06 4096

 

Pool_HDD_01 4096

 

Pool_HDD_07 4096

 

Pool_HDD_04 4096

 

Pool_HDD_02 4096

 

Pool_HDD_03 4096

 

submitted by /u/OscarCalvo74

[link] [comments]

 

Continue reading...