Merry Christmas and happy holidays!
We had a brief power outage / surge the other day which overloaded our UPS and pulled all of our servers down at once. I didn't get any file corruption on any of them except for the Server 2012 file server, whose data storage volume got corrupt. This volume is NTFS with de-duplication enabled. The RAID controller is battery backed, so I'm not sure why it corrupted its filestore. Now it reports
A corruption was discovered in the file system structure on volume E:.
A corruption was found in a file system index structure. The file reference number is 0x9000000000009. The name of the file is "<unable to determine file name>". The corrupted index attribute is ":$SII:$INDEX_ROOT". The corrupted index block is located at Vcn 0xffffffffffffffff, Lcn 0xffffffffffffffff. The corruption begins at offset 64 within the index block.
As well as
Deduplication information enumeration failed. Error occured during enumeration of Data Deduplication volumes: MSFT_DedupVolume - HRESULT 0x8056530e.
And
NFS shares enumeration failed. Error occured during enumeration of NFS shares: A general error occured that is not covered by a more specific error code.
I've run chkdsk with every conceivable option, including scheduling a boot-time scan, and it finds nothing wrong with any of the drives. How do I fix this? I cannot re-enable deduplication until this is fixed, and I really need it because of the type of data that it's storing. 2012 seems to handle file corruption quite a bit differently than I'm used to.
Ideas? Thanks
Rhiannon
Rhiannon