I've got a Windows 10 desktop with a few different disks/filesytems installed:
- 1TB SSD, primary/Windows is installed here
- 500GB SSD, secondary, used for VM's
- 120GB SSD, secondary, used for installing games
- 4TB RAID-1 (2x4TB Seagate HDD's), secondary, media storage
- 2TB RAID-1 (2x2TB WD HDD's), secondary, media storage
The problem is, I think, with the 2TB RAID volume. What's been happening lately is that if I browse/access this filesystem it'll eventually hang completely. To the point where I can't even end-task the hung process or even shut the computer down gracefully (I don't even get a BSOD; the system is basically stuck until I do a hard reboot). I can still move the mouse and interact with preexisting programs (so long as they're not also trying to access that volume, I guess).
This doesn't happen immediately, but if I go through several different folders or try to copy lots of new data to it (from the 4TB volume) that seems to be enough to trigger it.
So anyways, my assumption is that volume is the problem (it's also using the two oldest HDD's in the system). Though I could be wrong about that; happy to hear alternative explanations for the problem if there are any.
I installed a SMART-checker utility and checked the disks in the suspect array. Both passed the 'short self test'. The attributes for one disk report as:
...and the other looks like:
There doesn't seem to be a huge difference, although the second disk does show a non-zero 'Raw Read Error Rate' and a much larger 'Multi Zone Error Rate'.
Is it plausible that these errors are responsible for the system hanging when accessing this RAID volume? Should I be heading out to pick up a replacement disk?
UPDATE (from comments)
The RAID is using the integrated controller supplied by the Asus B360M-K mainboard. Here's the device-manager screenshot:
The only obvious thing in the system event log is a couple of "Reset to device, \Device\RaidPort1, was issued" messages.