Okay, this is strange. I had not noticed that I have essentially the same problem.
I have the Gigabyte GA-EX58-UD5 motherboard. Drive assignments are (were) as follows:
- ICH10 . . . 6x Sata-2 ports
- Port 0: WD1500HLFS boot drive
- Port 1: (reserved for 2nd boot drive, RAID-0 array)
- Ports 2 & 3: 2x WD1002FBYS RE3, RAID-1 array
- Port 4: Pioneer DVR-217DBK burner
- Port 5: [was] connected to case's eSata port (used for external HD backup)
- JMicron . . .4x Sata-2 ports, 1x IDE ATA-133 port (master & slave)
- Port 0: 1.5TB WD15EADS
- Port 1: (not used)
- Port 2: 1.5TB WD15EADS
- Port 3: [was] (not used) [now] connected to case's eSata port
- IDE Port: (not used)
- Adaptec 5805 array controller . . .
- All ports: 8x 1.5TB WD15EADS, RAID-6 array
Gigabyte does not include a dedicated eSata port. Instead, it includes a dual eSata port bracket to be inserted in one of the back plane slots and connected to any of the available "regular" sata ports. However, I am not using the bracket. My case has an eSata port included in its top-panel I/O connections array. It is that eSata connection that I have attached to the ICH10/Port-5 Sata connection on the motherboard and which I use to connect my Thermaltake BlacX ST0005U docking station.
- I can hot-swap to any of the ports on the Adaptec array controller without problems (I'm notified that a drive has failed and the array begins to rebuild automatically when a drive is replaced).
- I can "hot" remove a drive from the Thermaltake BlacX (connected to the ICH10) -- although I do NOT have permission to do so -- it's grayed-out on the "Safely Remove Hardware" list.
- I can "hot" remove a drive connected to the JMicron controller -- with or without using the "Safely Remove Hardware" list.
- I can "hot" add a drive to either of the motherboard-based controllers without problems if, and only if, there was no drive connected to that port at boot time.
- If I "hot" add a drive to a port that has previously been in use with either motherboard-based controller, whether using the Thermaltake BlacX or not, I get a blue screen, core memory dump, automatic re-boot, and a message that Windows did not shut down properly.
I had discovered the problem with the JMicron controller early on; but had assumed -- incorrectly -- that it was a JMicron problem. I had added a drive using the ICH10 controller but had not tested replacing a drive. I normally change the drive in the BlacX docking station only once a week. I use 3 drives in a weekly rotation for backup purposes, a full backup of my OS and primary data space once a week and then incremental backups daily.
Based on this, I have now moved my case's eSata port connection to one of the JMicron Sata ports so that I can properly safely remove hardware, should the need arise. And I join the search for a solution to the hot-swap problem.