by VernonRobinson » Sun Sep 04, 2016 3:25 am
Bob,
Thanks for the reply. I will reconfirm. But my recollection is that the Raid 0+ 1 will boot Win 7 as long as the Win10 SSD is out of the system. The Win10 will not boot when the Raid is in the system.
When I installed Win10 there were no other drives in the system.
If I recalled (circa 2007) when I installed this, I believed that I did separate the operating system onto its own drive and only the data was 0 + 1. I guess I can pull the drives and look at their serial numbers. I think the raid software will tell me which drives are involved in the raid. I will check on it a little later today.
There are 5 drives in the system. I had one drive separated from the drive cage of 4. I thought this was the system disk. But it might not be. This could explain why the strange behavior. If this drive was part of the Raid configuration, it might cause this type of behavior. But I would have thought that with a 0 + 1 configuration and it being part of the data drive and not the OS, that the system would boot and tell me that I had a failure in the Raid that needed to be rebuilt.
Also, if I remember correctly, doesn't the system normally require Raid Drivers to be installed? When I installed Win10, the Raid was not plugged in and I do not believe there were prompts to do so. The motherboard is so old, I doubt that there are drivers compatible with Win 10. The mother board is an ABIT IP35 Pro.
Thanks for your help.
-Vernon