Jump to content
|Topic||Stats||Last action by|
|Girl, 6, rats out father to police||
|Minecraft: Windows 10 Edition announced||
|cisco - determining what user/device is connected to a port||
|[OFFICIAL] Windows 10 RTM Discussion - Build Number 10.0.xxxxx||
|New music app: am I missing something?||
Posted 30 March 2013 - 21:15
Posted 30 March 2013 - 21:46
Posted 31 March 2013 - 17:12
Posted 31 March 2013 - 20:00
Posted 31 March 2013 - 23:03
Posted 31 March 2013 - 23:11
Posted 01 April 2013 - 03:27
Posted 01 April 2013 - 04:05
Posted 01 April 2013 - 16:47
^ I don't get this, My write cache is enabled and I have hit the reset button plenty of times with no issues. How would this be a file system issue ? If you've got redundancy surely the file system would be happy.
We have a 100GB ReFS volume. The volume was filled to capacity and now the volume is unaccesible. If you click on the drive letter in Windows Explorer it displays the following "W:\ is not accessible. The volume repair was not successful." There are several events in the system event log for 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>"." I have tried added additional space to the drive via Disk Management as well but it failed with the following error. "The volume cannot be extended because the volume does not contain a recognized file system."
Anyone have any ideas on how to fix an ReFS volume?
So far I am not too impressed with this "resilient" file system...
Yes, the same space of total space and free space is the reason why drive could not be restored correctly and we recieved the error message. For RAID 5 corruption, currently there is no fix to fix the issue except rebuilding. Thanks.
After electrical break at shutdown process 13Tb ReFS volume becomes unavailable with same symptoms as in Nick case. Volume filled at ~8Tb.
Volume based on Logical Disk hosted on LSI Hardware RAID controller. Level RAID-5. Data is very sensitive and should be restored.
My case was similar, after an electrical break, the ReFS formatted volume (mirrored on two hard drives) did not survived. What is funny, NTFS formatted volume located on the same hard drives survived (chkdisk corrected all errors)
After the incident, both hard drives are healthy (no reallocated, pending or unstable sectors).
I agree that the concept of self-healing file system is the future, but as we see, the ReFS is not ready yet. Also I could not find any data recovery option on the local market yet.
In my opinion, people should be warned. The documentation should contain huge warning "[experimental, potential data loss possible]"
Posted 27 May 2013 - 10:45
Posted 27 May 2013 - 11:42
^^ Read that. Basically the same issue I experienced
I emphasized the relevant post from a Microsoft employee which basically says "Sorry..you lost your data.. bye" Not very resilient if you ask me.
Posted 29 May 2013 - 20:59
None of that means the same couldn't have happened with NTFS though.
Posted 29 May 2013 - 21:14