![]() |
RAID enabled won't boot from M.2 |
Post Reply ![]() |
Page 12> |
Author | |
aspired ![]() Newbie ![]() Joined: 16 Nov 2015 Status: Offline Points: 11 |
![]() ![]() ![]() ![]() ![]() Posted: 21 Nov 2015 at 2:45pm |
Initially I have just slapped the workstation together with just the M.2 and didn't even go into the UEFI and it installed flawlessly to my surprise after reading all the difficulties on various MB.s with the 951 so I was pretty happy.
Both win8.1 and win10 where created from .iso with good old Rufus to make bootable USB's using UEFI not classic. When I was trying to reistall win 10 again and had all my other drives installed and deleted the old install volumes I click my app SSD and notice it said it couldn't install there as was not GPT. I didn't get this error when installing 8. According the MSDN UEFI loads will always be GPT. https://msdn.microsoft.com/en-us/library/windows/hardware/dn898510(v=vs.85).aspx Also there is a different partition layout of a layover install than a fresh install. I did not change that setting in the UEFI your referring to. Was on my list to test next as I noticed some others changing on ASUS boards. But it's running great with the overload so at this time I don't plan on messing with. I have my lab up and running and am happy enough. Ran some heavy IOPS testing and things are pretty decent but need to do some benchmarking and overclock a slight bit. Thanks for the reply's!
|
|
![]() |
|
parsec ![]() Moderator Group ![]() ![]() Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
![]() ![]() ![]() ![]() ![]() |
Sorry for missing your progress.
I have an ASRock X99 Extreme6/3.1 with Windows 10 installed in RAID mode, using a Samsung SM951 as the OS drive. The SM951 is not an NVMe type of SSD, while the 950 is, and that may make a difference. Also, I always install Windows in UEFI mode, so the OS and other drives are formatted as GPT. GPT partitioning has no affect on installing in RAID mode. My question is why you are getting GPT partitions suddenly with Windows 10. I just remembered that my Windows 10 installation on the SM951 is a clone from a SATA SSD. This is not a mother board issue, you would have the same situation with any X99 board. Your issue is related to the Intel RAID driver when installing Windows on a drive that does NOT use the same storage controller. Are you installing Windows with any other drives powered up in the PC besides the 950? When installing Windows on your 950 Pro, have you modified the CSM option settings in the UEFI from the default settings before you start the Windows installation? Minimally, you should have the CSM sub-option, Launch Storage OpROM Policy set to UEFI Only. When you select your Windows installation media as the first boot device, are you seeing multiple options for that device, one with the prefix "UEFI" and another with "AHCI"? If so, which entry are you using? Using the UEFI prefix causes the Windows EFI bootloader to be used, which is required for PCIe SSDs. Sorry, half asleep while writing this, not a good thing while trying to explain this situation. More later... |
|
![]() |
|
ziko ![]() Newbie ![]() Joined: 17 Nov 2015 Status: Offline Points: 11 |
![]() ![]() ![]() ![]() ![]() |
I had the same Problems with my X99 Extreme 4 3.1.
Switched from Bios A to B,, upgrade.... My first Asrock and my last Asrock. Today it dont boot. Freeze at Asrock logo. Power off at PSU and power on and it boots. Yesterday the Windows repair Screen appears. Worst shxxt i brought in my entire life. Let aside overclocking or other things. Asrock wont BOOT !!!! not to speek about RAID, M2, AHCI and other stuff. Sorry guys, but ist true.
|
|
![]() |
|
aspired ![]() Newbie ![]() Joined: 16 Nov 2015 Status: Offline Points: 11 |
![]() ![]() ![]() ![]() ![]() |
Here what worked, what least for me.
Installed 8.1 then lay 10 over it. This keeps the MBR partitions from 8 and seems to boot fine. The GPT partitions that 10 creates seem to possibly be the issue. Installing 10 then doing the 8 reg edits have no effect. It's not a perfect solution but later I will backup and try to get 10 on a straight install and maybe get a few UEFI updates from ASrock and some Windows 10 updates by then to help.
|
|
![]() |
|
wardog ![]() Moderator Group ![]() Joined: 15 Jul 2015 Status: Offline Points: 6447 |
![]() ![]() ![]() ![]() ![]() |
I can't find one specific to Win10 in what little I did spend Googling it but here's one that covers Win8
http://superuser.com/questions/530464/switching-from-raid-to-ahci-with-windows-8 < id="kpm_plugin" ="application/x-KPMPlugin">
|
|
![]() |
|
aspired ![]() Newbie ![]() Joined: 16 Nov 2015 Status: Offline Points: 11 |
![]() ![]() ![]() ![]() ![]() |
Do you or anyone know the Windows 10 reg edits or have a link to a knowledge article on the subject matter? |
|
![]() |
|
aspired ![]() Newbie ![]() Joined: 16 Nov 2015 Status: Offline Points: 11 |
![]() ![]() ![]() ![]() ![]() |
Looked for a firmware update for Samsung SSD 950 PRO = nothing
- they just came out as I had to preorder so didn't expect much tested base again to know where I am still at = as soon as disable RAID windows boots Win 10 Ent Tried switching S_SATA drives to IDE based on another forum post = no change noticed when I enable and disabled RAID with an array built that the array goes into a failed status and I see 2 drives ID2 and ID3 showing as non member disks Unplugged ID2 and ID3 which is SATA3_2 and STAT3_3 build a new RAID 5 array on the 3 disks tried to boot to OS on M.2 = no change so just confirms not a typo in the manual when says S_SATA3_2 is shared with M.2 Installed windows 8 with RAID enabled on SATA3 drives and array built on but installed OS on M.2 drive just like win 10 before = booted Ok so something with Windows 10 or lack of UEFI full support for win 10 yet great I hate windows 8.1 maybe if I lay over 10 on 8.1 instead of fresh install or back to Windows 7 but then loose Hyper-V Anyways making some progress it seems, few more hours of troubleshooting and should have something usable hopefully and can use this more instead on my physical lab that is expensive to run and tedious to keep updated. Edited by aspired - 18 Nov 2015 at 1:02pm |
|
![]() |
|
aspired ![]() Newbie ![]() Joined: 16 Nov 2015 Status: Offline Points: 11 |
![]() ![]() ![]() ![]() ![]() |
Well to confirm not a OS issue I will install Windows 8.1 Ent and test.
Then to confirm not a M.2 issue I will installed OS to a non RAID SATA3 drive Past that I have nothing left I can think of to test so if anyone has a ideas that would be great! Or if anyone has setup this setup (OS on non RAID but running RAID for data) before and got it working without issue on this or similar ASRock board.
|
|
![]() |
|
aspired ![]() Newbie ![]() Joined: 16 Nov 2015 Status: Offline Points: 11 |
![]() ![]() ![]() ![]() ![]() |
Well I opened a support case. Unfortunately this is a serious issue for my build and if doesn't work will have to get another motherboard. I read the whole manual before purchasing and nothing related to this not being supported.
Strange though don't even get a case number when create a case and heavy push to contact reseller. Resellers say the opposite, they want you to contact manufacturer. Might have to contact NewEgg and see about return but give it a week to see what happens. |
|
![]() |
|
aspired ![]() Newbie ![]() Joined: 16 Nov 2015 Status: Offline Points: 11 |
![]() ![]() ![]() ![]() ![]() |
So bad news.
The ASrock RAID fix from the App Store did not fix the issue. Also the reinstall of the OS did not fix the issue. Messed around a bit more but no more success. Tried to open case from UEFI but stuck @ 5% so have to do from website. Bummer!
|
|
![]() |
Post Reply ![]() |
Page 12> |
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |