A
ATyler - Life Flight Network
I need some help. I have a Windows server 2012 R2 system with 6 drives participating in a storage pool. I created a virtual disk a while back on this storage pool and for some reason it won't mount any longer. All drives display as present and working. Status commands from PowerShell (get-virtualdisk | get-storagepool) show that status is "Healthy". I have pulled every drive and completed a short diagnostic as well as a SMART test. All pass.
This storage pool was created with this server and nothing has changed. It seems problems started back on 10/27 when quite a few of these alerts were written to the event log:
Source: ReFS | Event ID: 133 | The file system detected a checksum error and was not able to correct it. The name of the file or folder is "<unable to determine file name>".
Source: ReFS | Event ID: 134 | The file system was unable to write metadata to the media backing volume E:. A write failed with status "The volume repair was not successful." ReFS will take the volume offline. It may be mounted again automatically.
Now all that is logged is the following:
Source ReFS | Event ID: 135 | Volume is formatted as ReFS but ReFS is unable to mount it; ReFS encountered status The specified data could not be written to any of the copies..
Continue reading...
This storage pool was created with this server and nothing has changed. It seems problems started back on 10/27 when quite a few of these alerts were written to the event log:
Source: ReFS | Event ID: 133 | The file system detected a checksum error and was not able to correct it. The name of the file or folder is "<unable to determine file name>".
Source: ReFS | Event ID: 134 | The file system was unable to write metadata to the media backing volume E:. A write failed with status "The volume repair was not successful." ReFS will take the volume offline. It may be mounted again automatically.
Now all that is logged is the following:
Source ReFS | Event ID: 135 | Volume is formatted as ReFS but ReFS is unable to mount it; ReFS encountered status The specified data could not be written to any of the copies..
Continue reading...