Intel RST - Auto-Verify (can I disable AUTO?)

[Jahova]

IRST (Intel Rapid Storage Technology)
Version Installed: 10.1.0.1008

After a "dirty" shutdown, the RAID array always wants to verify itself via IRST. The problem with this Automated process is the fact that it is Automated. If I list my reasons for wanting to de-automate this frustrating automated verification, it may cause confusion. So I will leave that detail out of the equation.

Example:
Lets say a computer with RAID1 and IRST loses power and shuts down without going through the normal shutdown procedure. Upon booting the computer, IRST wants to verify the RAID1 automatically. Then I have to wait and wait to go into the IRST application to disable the verification manually. I'd rather the verification procedure by executed when I am ready to execute it (like overnight, or any time I don't have to use the computer).

Please do not get confuse. I don't want to disable the IRST verification, I just don't want it to verify upon booting after an irregular computer shutdown (shutdown due to power failure or BSOD).

Does anyone know how to disable the IRST AUTOMATIC verification of a RAID array?

[OS-Wiz]

I don't use IRST and don't know the answer to the question. But, is there a reason you aren't using the new V11 drivers?

[PommieB]

I'd say it's verifying because there's a problem caused by the dirty shutdown, it's why people buy UPS's so you have time to shut down correctly.

You could re-install or install the latest IRST driver, maybe the current one is corrupted in some way.

I've no idea whether you can disable the auto verification.

[Jahova]

Originally Posted by PommieB

I'd say it's verifying because there's a problem caused by the dirty shutdown, it's why people buy UPS's so you have time to shut down correctly.

You could re-install or install the latest IRST driver, maybe the current one is corrupted in some way.

Negative, because I have 5 different machines using 3 different versions of IRST that all have the exact same behavior. 'Dirty shutdowns' are not very common, but they do happen, even with a UPS.

The problem is not related to a version of IRST, nor any other unusual corruption. The problem is that IRST will AUTO-verify upon restart because that is what it does by default. Disk activity goes to 100% and it can take up to 5-10 minutes before getting to the Windows Login screen. Then wait after login for another 5-15 minutes.

Overall I am just about ready to disable the service so that it starts manually, but was hoping I could change a setting within IRST instead. It appears a lot of other people want to do the same, but I haven't yet found any solutions online.

[PommieB]

I use raid but it's all independent of the OS, I don't use Intel drivers, gave up on that years ago, So you've had this problem for awhile, it's not something that's just turned up.

I have used the IRST driver on a single ssd to test performance, but that's different.

Doesn't look like you can disable it, it seems you need to do a verify and repair, here's a link to a PDF file on the driver. There's a short paragraph on verify and repair towards the end of the PDF. May give you a clue on how to fix your raid arrays. You may already have this info, it's the only info I could find.

http://www.intel.com/support/chipset.../CS-020670.htm

[Jahova]

I periodically run the 'verify and repair', but just because there was a 'dirty shutdown' doesn't mean there is something broken in the RAID1 array. This has to do with a default setting, not something that needs to be fixed.

In other words, the problem is not the part about the "verify and repair", I can handle that much. The real problem is with the "automatic" setting.

[PommieB]

I don't see any default settings associated with it, have you found them yet?, you seem to be the only person on the Internet with the problem, well at least I couldn't find anyone.

[Jahova]

http://windows7forums.com/windows-vi...anging-up.html

[PommieB]

Thanks for the link, was just curious as to why it was happening, had a feeling it was a driver thing as it was happening on different raid arrays.