Friday, May 26, 2017

windows 7 - Hot-insert (non-RAID) SATA drive causes Intel RAID array to rebuild

Inserting a SATA drive into a “hot swap” tray causes a momentary problem that leads the Intel RST RAID 10 array to begin rebuilding. The first message from Intel begins like this:



SATA array disk: Removed.

Volume FS_RAID10_A: Degraded.
Volume FS_RAID10_B: No longer present on system.
Volume FS_RAID10_B: Detected.


On one occasion one of the volumes was at this point flagged as having 23 parity errors; the other had none.



The OS is Window 7, and the freeware program HotSwap! is installed so the drive can be easily removed later. It’s resident, but it's not clear that it is involved upon drive insertion. (On XP I need to invoke it when I insert a drive, else the OS won't see it, but that's not the case with Window 7.)



What there is of common wisdom on the subject holds that it’s a power supply problem, and powering the drive from a different cable will be the solution. I’ll try that, but if the system were that glitch-sensitive people with similar loading would be seeing it every time a drive (or array of drives) woke from napping.




The RAID array is serviced by the Intel hardware on the motherboard; the drive being swapped connects to the other RAID controller on the motherboard. The hot-swap tray is passive and just passes the SATA connections through.



Thoughts from anybody with specific knowledge about what's happening?

No comments:

Post a Comment

hard drive - Leaving bad sectors in unformatted partition?

Laptop was acting really weird, and copy and seek times were really slow, so I decided to scan the hard drive surface. I have a couple hundr...