I suppose I would like to clarify your situation. You are doing clean installs to the 500 GB array? Then you remove that set of drives and install the larger drives to the same connections and do another clean install?
Are you using the UEFI configuration for the install?
What drive letters are you assigning?
Thanks for contributing, Saltgrass.
No, I am not using UEFI configuration for the install.
To clarify my situation: I like to keep it clean, take backup during install stages so that I can do a restore as needed. For that reason, I do a clean install when I change hardware. My situation is as follow:
(a) I did a clean Win7 install and was on the 500GB the last two weeks. I ran out of disk space on the 500GB array because of the number of VMs I was creating. I needed a large number of VMs because I teach Windows certifications, computer/network security, digital forensics, programming and web development. I play with worm/virus and test drive-by malware.
(b) I swapped the 500GB with 1TB drives and restart my rebuild. I discovered the problem with the 1TB drive array and had been trying to diagnose or figure out how to go around the problem.
>> What drive letters are you assigning?
I carved 60GB for Data and assigned "D" for Data.
I assigned "E" for the remainder of the array...
For those who follow this thread... I was using a mod-BIOS, so I dropped back to a clean BIOS to rule out the mod as the problem. I also backdropped the BIOS (2 versions-no mod, which worked with the 500GB array) and did a fresh install. The problem with the 1TB Seage drive array was consistent.
Information on the 1TB array drives: They came from a RAID-1 attached to my router. They were on a hardware stand-alone RAID-5.
For the time being, I am going to put the 500GB array back and move some VMs off to the hotswapable removable drive. I am going to test the 1TB config on my ASUS system after that. I couldn't remember if I had mirrored them on the ASUS, although I am confident that they worked before.