Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


timmmay

20863 posts

Uber Geek
+1 received by user: 5350

Trusted
Lifetime subscriber

#165922 24-Feb-2015 18:36
Send private message

NOTE: please read from this post 9 March further down the thread, this post is now out of date.

I have the latest W10 build, fully up to date. It's running on an i7 2600K, 16GB RAM (which passes memtest x86 tests), good brand motherboard (I forget which one I got but I could check), two SSS (Samsung 840 pro, OWC 120 pro) and four hard disks. Two of the disks are 4TB HGST formatted ReFS in a mirror pair.

I've just run a Macrium Reflect image, putting the image onto my OWC SSD. The image has been successfully verified twice. I copied the image file (16GB) from the SSD to the ReFS SS volume, which completed without error. When I ran the Reflect verify on the file it failed. I copied the image again and it passed verification.

Looking into the event logs I can see events that are ReFS failures - around one a day, different files. It fixes the errors each time.

Text: The file system detected a checksum error and was able to correct it. 
Source: ReFSv1
EventID: 132

Unfortunately it doesn't seem to say which disk the error was with so I don't know if it's just one faulty disk. It seems that Windows copy is the thing that's failing - you'd have thought that was an absolute basic that was licked years ago. There doesn't seem to be a good program to copy then verify - I tried one but it made little difference.

I'm looking for general advice or suggestions. Memtest x86 has been run for > 24 hours, no issues there.

NOTE: please read from this post 9 March further down the thread, this post is now out of date.

View this topic in a long page with up to 500 replies per page Create new topic

This is a filtered page: currently showing replies marked as answers. Click here to see full discussion.

timmmay

20863 posts

Uber Geek
+1 received by user: 5350

Trusted
Lifetime subscriber

  #1260742 17-Mar-2015 08:19
Send private message

A motherboard replacement seems to have fixed the problem. It probably was the chipset bug I posted a link to above. Solved!

View this topic in a long page with up to 500 replies per page Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.