Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, January 17, 2014 2:09 AM
I moved from Windows Server 2012 to 2012 R2. I had several drives attached to the server, including some in storage spaces, formatted as ReFS. After the upgrade I'm getting this warning in the event logs. I don't see any way to upgrade the file system. The only reference I could find was this post where the user had some corrupt files, but I don't have any corrupt files. I can't imagine that MS would plan to release a new OS every year, but no way to update file systems for each OS.
Log Name: System
Source: ReFS
Date: 1/16/2014 7:23:10 PM
Event ID: 136
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: Server.DOMAIN.local
Description:
Volume "E:" was mounted in an older version of Windows. Some features may be lost.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ReFS" Guid="{036647D2-2FB0-4E32-8349-3F5C19C16E5E}" />
<EventID>136</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-01-17T01:23:10.103041300Z" />
<EventRecordID>8567</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="4060" />
<Channel>System</Channel>
<Computer>Server.DOMAIN.local</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="VolumeIdLength">2</Data>
<Data Name="VolumeId">E:</Data>
<Data Name="FailureReason">0x0</Data>
</EventData>
</Event>
All replies (2)
Sunday, January 19, 2014 2:46 PM | 1 vote
Hi,
First please test if update-storagepool will help.
I checked the case log of the thread you provided. Currently there is no much information about the issue. ReFS team suggests to backup, re-format as ReFS and restore data for a test. Also the message seems harmless as data is still fine so they think it is fine to just ignore it.
I'll try to contact them to see if there is any update since that thread.
If you have any feedback on our support, please send to [email protected].
Sunday, January 19, 2014 3:19 PM
I had already updated the storage pool, which had no impact, just like the linked thread. Of course, reformatting the volume would resolve the issue, but I don't currently have the space available to migrate 12TB of data off and back on to the storage. I'm not experiencing an emergency right now, so I'm not opening a support incident. But, I do want to know what "features may be lost" by using an older version of ReFS. For example, could this affect automated checking and healing of data on ReFS volumes that reside in a mirrored storage space?