Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, May 25, 2016 8:36 PM
My desktop has three hard drives. An 80 GB drive is drive 0 and is where Windows 10 is installed. There are also two 2 terabyte drives. When this computer operated on Windows 7, they were software RAID 1 (mirror) controlled by the AMD chipset on the Gigabyte motherboard.
When I installed Win7, there was an option to load drivers during setup. That's what I did and it worked fine - drive 0 was the single Windows drive C: and drive 1 was the RAID 1 mirror array.
When I tried to install Win10 on this box, Setup only saw the RAID array. I changed the BIOS setting from Onchip SATA type RAID to Onchip SATA type AHCI. It then saw HD 0 and installed, booted, and worked perfectly - but the RAID array was only seen as one disc. Windows took the second disc offline because of a duplicate signature. I then installed the MB manufacturer's chipset and RAID drivers.
Now when I change the BIOS setting to Set SATA as RAID, the array is seen by the chipset and/or BIOS as a healthy RAID 1 array but Windows won't boot due to an inaccessible boot device.
Is there a way to repair this installation without backing up data and reinstalling Windows 10? Google and Bing haven't been any help.
All replies (15)
Thursday, May 26, 2016 11:04 AM
Hi marcerickson,
What is your exact machine model?
What is the exact error message when Windows won’t boot after changing the BIOS setting?
Before we do the upgrade, please ensure the device manufacturer website has released the Windows 10 compatible driver for your model machine.
Based on your situation, for startup issue, we could choose Startup Repair to try fix this issue. Boot from a Windows 10 installation media, select repair, then use Startup Repair to fix it.
If the issue persists, please mark the system partition as active in CMD prompt.
1. Type and enter “diskpart”, then type and enter “list disk” after diskpart is loaded.
2. Type and enter “select disk [number of the disk the system partition is on]”.
3. type and enter “list partition”, then “select partition [system partition number]”.
4. Type and enter “active”.
Then, Use “bcdboot C:\ command to rebuild the BCD store to have a try.
If the issue still persists, we need backup data and reinstall Windows 10 to repair this installation.
Best regards
Please mark the reply as an answer if you find it is helpful.
If you have feedback for TechNet Support, contact [email protected]
Thursday, May 26, 2016 6:51 PM
Your actual description of not being able to boot after changing SATA mode is normal. There are methods people have used to offline load the RAID driver, but this should only be done for data recovery purposes.
You should not have your RAID1 array drives connected (disconnect their SATA cables) when you are reinstalling Windows onto the 80GB drive.
Saturday, May 28, 2016 4:38 PM
As I said, the error is Inaccessible boot device.
Startup Repair doesn't work. it starts working (Diagnosing your PC with the rotating dots), (Attempting repairs), I get a flash of blue screen (Windows 10 blue, NOT a BSOD) and Inaccessible boot device, and then the machine crashes and reboots.
I'm unable to complete the recommended procedure. I'm able to select disk 0 with diskpart, but am unable to select the partition on it.
*
*
DISKPART>select disk 0
Disk 0 is now the selected disk.
DISKPART> list partition
* Partition ### Type Size Offset*
* Partition 1 Primary 62 GB 0 B
DISKPART> select partition 1
There is no partition selected.
There's no way to load a driver during a repair - only during Setup?
Tuesday, May 31, 2016 8:35 AM
Hi marcerickson,
What is your exact machine model?
Considering this Windows 10 is upgraded from Windows 7, to make sure RAID array works well, we need ensure the device manufacturer website has released the Windows 10 compatible driver for your machine model.
Please confirm whether your manufacturer website has released the Windows 10 compatible RAID driver for your machine model.
Best regards
Please mark the reply as an answer if you find it is helpful.
If you have feedback for TechNet Support, contact [email protected]
Tuesday, May 31, 2016 5:34 PM
MarcErickson,
You can try this method (at your own risk, because this kind of stuff can be risky):
This safe mode/safe boot "hack" has apparently worked for some people. Not sure if it will work for Windows 10, but it could be a last resort attempt.
Thursday, June 2, 2016 11:16 AM
The motherboard is a Gigabyte GA78LMT-S2P (Rev. 5.x). The manufacturer hasn't released a Windows 10 driver yet. I have asked them to - shall we start a betting pool as to if they do? ;-(
Friday, June 3, 2016 8:48 AM
Hi marcerickson,
I have confirmed it, indeed, Gigabyte has not released Windows 10 compatible driver .
http://www.gigabyte.sg/products/product-page.aspx?pid=3833#dl
NOTE: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites.
To make sure Windows 10 working well, We do need install compatible drivers from manufacturer.
I am afraid that we cannot upgrade to Windows 10 if the manufacturer hasn't released Windows 10 compatible drivers.
Based on your situation, we need revert back to previously Windows.
Wait for Gigabyte release Windows 10 compatible driver, then perform upgrade to get Windows 10.
Best regards
Please mark the reply as an answer if you find it is helpful.
If you have feedback for TechNet Support, contact [email protected]
Saturday, June 4, 2016 4:06 PM
Alas, this method didn't work for me and Windows 10. :-(
Monday, June 6, 2016 9:40 AM
Hi marcerickson,
It is not suggested to upgrade to Windows 10 if the manufacturer hasn't released Windows 10 compatible drivers.
It will cause Incompatibility issue.
We will have to wait for Gigabyte release Windows 10 compatible driver, thanks for your understanding.
Best regards
Please mark the reply as an answer if you find it is helpful.
If you have feedback for TechNet Support, contact [email protected]
Wednesday, June 8, 2016 8:59 PM
This thread can be marked closed.
I found a driver on the AMD site for the chipset on my motherboard, but despite AMD claiming it was Win10 compatible, it wasn't.
I gave up and backed up the data from the drives, and configured them with Storage Spaces as mirrored drives. I'm now copying my data over to them. One oddity: one must give the set a name.
Thanks for everyone's help.
Wednesday, June 8, 2016 9:26 PM
All techniques suggested in this thread failed because the driver I got from AMD for its chipset isn't Win10 compatible.
Thursday, June 9, 2016 3:42 PM
I have the same issue, but my board (Gigabyte z170x UD5) is Win10 compatible and I have the drivers installed.
To reiterate the issue in this discussion as well as what I have: If I turn on RAID at the bios level (eg SATA Mode Selection), Win10 won't boot. If I turn on ACHI in bios, win10 boots just fine. I can flip between these modes where Win10 boots / does not boot based on the bios setting.
Installed new Win10 (not an upgrade from a previous version) on a single m.2 ssd which is not set up in RAID
After Win10 install, I added 3x1TB SATA disks to set up as Raid 5; I have to turn on Raid in the bios in order for the Intel Rapid Storage Technology menu to show; I configured the 3x1TB sata drives as RAID 5 and have given the new volume a name.
If I leave Raid in the bios, win10 won't boot.
If I turn bios back to ACHI and win10 boots, but I don't see my volume created in Raid 5
I would assume this is a win10/driver issue somewhere but cannot solve. Any ideas?
Friday, June 10, 2016 9:56 AM
Hi rts55,
It could be a driver issue, try to install the last version of drivers from gigabyte to have a test.
http://www.gigabyte.com/products/product-page.aspx?pid=5480#dl
NOTE: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites.
To get a better support, it is recommended to open a new case. It would attract other experts in this forum to join in the thread and it is easy to follow up the case. Thanks for your understanding and cooperation.
Best regards
Please mark the reply as an answer if you find it is helpful.
If you have feedback for TechNet Support, contact [email protected]
Wednesday, July 17, 2019 5:15 PM
if you have a raid 1 enabled the disk is mirroring (cloning) the disk the only thing you can know do is to use the shift - restart comand and choose msdos prompt and run bootsect
Wednesday, July 17, 2019 5:17 PM
both systems would be alive