RAID5 locking entire computer up, RST no longer runs after driver update from Intel

[ZGods]

To start, here's my build: https://pcpartpicker.com/list/GLshPs https://pcpartpicker.com/list/GLshPs -- NOTE it has parts in it for the NAS I put together as well.

The basic setup is a 500GB SSD for OS, and a 6TB (3x3TB 7200 Seagate Constellation drives w/128MB cache) RAID5 array.

The long and the short of it is that I noticed my whole computer locking up when steam tried to update some of my games. I thought it was steam, but I've now seen it on other platforms that try to update large quantities of data at a time. I'm not sure what's kicking it off, but basically, when the issue happens, disk usage goes to 100% (though very little disk *activity* takes place), and I look at my resource monitor, I notice HUGE (25,000 ms+) response times for various disk activity.

I've done many things to try to diagnose and fix this, including a full surface test, and installing the latest drivers from Intel, but that actually made RST go kaput. It will not run, and when I try to bring up the application, it says, "An unknown error occurred while running this application. If the problem persists, please restart your computer or try reinstalling the application." Of course, I've tried both options multiple times.

I meant to get a thread up much sooner, but ran into some issues recovering my account/pw here, and forgot about it for awhile, but it's starting to become quite a nuisance.

I had a thread going on steam for quite a while (because I thought that's what the issue was), which you can see here: https://steamcommunity.com/discussions/forum/11/135507403159637853/ HDD usage at 100% after adding new location [raid5] :: Hardware and Operating Systems

Now, since then, I still haven't been able to fix the problem, but I the more I think about it, the more I think it has to do w/the cache on the hard disks. It seems that when it switches data out of the cache is when it's triggering this issue (this is a COMPLETE guess, btw). For instance, starting up a game that has to load a lot of files will take FOREVER, but once I do that, I'm good to go, until I load a different game, which will take forever if it loads a lot of files.

If you want links to the pictures i posted w/out having to deal w/those silly warnings, I'll compile them below.

Surface test: http://phroztnet.org/screen/ts/20170124_surfacetest.png http://phroztnet.org/screen/ts/20170124_surfacetest.png

Updating via steam showing nothing going on, but disk at 100%: http://phroztnet.org/screen/ts/20170203_steam.png http://phroztnet.org/screen/ts/20170203_steam.png

2 GB update on battlefield 1 that did not show this issue: http://phroztnet.org/screen/ts/20170207_origin.png http://phroztnet.org/screen/ts/20170207_origin.png

60 GB dl on Uplay that started smooth... : http://phroztnet.org/screen/ts/20170207_uplay.png http://phroztnet.org/screen/ts/20170207_uplay.png

Then got ugly: http://phroztnet.org/screen/ts/20170207_uplay-01.png http://phroztnet.org/screen/ts/20170207_uplay-01.png

Got better after the "stuck" files got cleared out: http://phroztnet.org/screen/ts/20170207_uplay-02.png http://phroztnet.org/screen/ts/20170207_uplay-02.png

Screenshots of bad response times

http://phroztnet.org/screen/ts/20170207_responsetime.png http://phroztnet.org/screen/ts/20170207_responsetime.png

http://phroztnet.org/screen/ts/20170207_responsetime-01.png http://phroztnet.org/screen/ts/20170207_responsetime-01.png

http://phroztnet.org/screen/ts/20170207_responsetime-02.png http://phroztnet.org/screen/ts/20170207_responsetime-02.png

Looking back at these response times, these are nothing compared to what I see now... I can hit 14k response times with ease, and I've even seen 25k response times.

I would be more than happy to run more tests/diagnostics/whatever. I got burned out for a while trying to fight this, but I'm willing to try again.

Thanks

[ZGods]

Anybody? is it ok to take the drive out of the RAID array for diagnostics, or will the entire array then become unusable?

[idata]

Phrozt: Based on your previous posts it seems to be the hard drive might got defective. So, in this case what we can try is to set the RAID to Non-RAID on control+ i menu, then disconnect the hard drive in question to test it. You will be able to use the RAID with 2 hard drives, if one more hard drive fails then the RAID will failed. Now, in order to find out if there is a tool to test the hard drive, the best thing to do will be to get in contact with the manufacturer of it for them to provide those details. Please back up all the important information you have on the system. Do you have the option to use a different hard drive that is working fine for sure?

Any questions, please let me know.

Regards,Alberto R

[ZGods]

I went into the Intel RST tray app and hit ctrl+i, but nothing happened... should I be somewhere else?

Also, it sounds like you're telling me to disable RAID (set it to "Non-RAID") but that it will still be using RAID w/2 of the drives? I'm a bit confused on that point.

I do not currently possess another drive of that capacity to fill in the third slot, so I will need to operate for a while with only 2 drives in the computer. Is that still possible?

Thank you,

-Z

[idata]

Phrozt: Let me apologize for any inconvenience. Yes, what we are trying to do is for you to be able to disconnect the hard drive that is not working properly to test it without losing the RAID functionality. In order to do that, once you get into control+ "i" menu, look for the hard drive that is not working, then choose the option just for that hard drive to: Reset Disk to Non-RAID. That way you will be able to disconnect it and then test it on a different PC or with an specific tool. The RAID will work with the other 2 hard drives, it will be degraded but it will still work.

Any questions, please let me know. Regards,Alberto R

[ZGods]

Hi Alberto,

I still be missing something, because ctrl+i doesn't bring up any menu, and when I go to select the failed drive in the RAID array, there is no option to mark it as non-Raid.

There is an option to "mark as normal," but I've done that before, and basically it just assumes that the problems were fixed and tries to rebuild it into the array, but then it fails again. I believe I've done this process 2 or 3 times.

Here's what I'm seeing:

Thanks,

-Z

[idata]

Phrozt: You are welcome. Yes, the steps provided above will only work on the RAID BIOS, which you can access with control + "i". You need to tap both the control key and the "i" key several times when the PC is starting up to access that menu.

If still, the RAID BIOS is not showing after that, then the next thing to do will be to get in contact with ASUS directly just to confirm if there is another way or shortcut to access it:

https://www.asus.com/us/support/

Any questions, please let me know.

Regards,

Alberto R

[idata]

Phrozt: I just wanted to check if the information posted previously was useful for you and if you need further assistance on this matter?

Any questions, please let me know. Regards,Alberto R