Unsolved
This post is more than 5 years old
1 Rookie
•
4 Posts
0
12670
April 25th, 2017 07:00
Aurora R6 selected boot device failed
Yesterday I did a fresh install of Windows 10 (with creators update) on the m.2 nvme drive in my Aurora R6. Before the installation I changed the SATA mode from 'RAID on' to 'AHCI', because I want to run Linux on a 2.5 inch ssd. The installation of windows 10 went well and after the installation I installed the latest updates and driver software (from Dell).
After shutting down and rebooting I now get the following message (just after the Alienware logo):
Selected boot device failed
'Window boot manager' is the first option in the UEFI boot order and manually selecting 'windows boot manager' in the one-time boot menu results in the same error message.
Interestingly I can still boot windows 10 by using the installation media:
On boot press F12 -> installation USB -> recovery -> continue to windows
I did not expect that changing the SATA mode to AHCI would effect a pcie nvme ssd.
Online I found some suggestions including registry fixes and booting in safe mode, but no success, I still get the boot device failed message when booting normally.
Some BIOS information:
Version 1.0.4
UEFI with secure boot disabled
SATA mode: AHCI
Does anyone have any experience with booting windows 10 from a m.2 nvme ssd with SATA mode set to AHCI? Is it a driver issue or is this not supported by the BIOS or mobo or something else?
Tesla1856
10 Wizard
•
17.9K Posts
•
71.3K Points
0
July 10th, 2017 12:00
1. I finally got around to installing v1.0.4 and v1.0.5 on mine the other day. Not much of a difference that I saw, but just glad it still boots and generally works. Looks like they skipped v1.0.6.
2. Keep the reports coming. I'm not participating in AHCI-Mode testing (but glad yall are). I'm still wondering why AHCI settings even matter with PCIe/NVMe since it's totally separate. I'm guessing it has something to do with Intel Optane.
3. So, more strangeness
. So, the choices are 0gb or 185275945gb , Hmm.
4. Not much of a difference between that Dell ISO and Microsoft's, AFAIK. Also, I think generic PCIe/NVMe support is bundled in OS.
Tesla1856
10 Wizard
•
17.9K Posts
•
71.3K Points
0
July 10th, 2017 12:00
If it's M.2-NVMe in MB-Slot, try RAID Mode.
See my Favorites ... there is a thread or two with steps.
strawmetal
9 Posts
0
July 22nd, 2017 01:00
I'm having the same issues on my Aurora R6 (250GB NVMe SSD, 2TB HDD, i7-7700K, GTX 1080).
BIOS Version: 1.0.7
Using AHCI mode
Using RAIDon mode
Since this issue happens with a feature SATA Operation ( AHCI / RAID on ) in the BIOS with a supported OS (Windows 10), Dell should fix it.
Irrespective of whether I'm dual booting or not. I could have my own reasons for running Windows 10 using SATA in AHCI mode.
ifame
8 Posts
0
August 2nd, 2017 23:00
Dell release 1.0.8, but the same problem, IDK why they release an update without solving any problem...
strawmetal
9 Posts
0
August 26th, 2017 10:00
After a lot of back and forth with Dell Tech Support, they were clueless as to why it wasn't working.
Their solution was to send me a replacement drive made by Toshiba.
This is what I find to be confusing:
BIOS v.1.0.8 with AHCI enabled
Old NVMe SSD:
New replacement NVMe SSD:
Do you think the problem lies with their BIOS and they just sent me a drive which they've deemed to be more compatible?
I was able to install Windows 10 in AHCI mode without any issues. It boots perfectly after that too.
boatsie
3 Posts
0
August 28th, 2017 17:00
Same issue as everybody else, can boot Windows from the m.2 NVMe while SATA setting is RAID On, but not in ACHI mode. In ACHI mode with the PCIe SSD connected, it always results in "boot device failed".
Does anyone know if swapping out the motherboard will work and what board would be compatible? Am using Samsung 960 EVO m.2 nvme.
msavic6
2 Posts
0
August 28th, 2017 18:00
What is the issue with running the drive in RAID mode besides losing out on some features of the EVO 960? I assume you're still able to have the NVME be your boot drive and have the origins drive remain in as a storage drive without any mirroring/striping.
boatsie
3 Posts
0
August 28th, 2017 22:00
Linux cannot be installed as the primary OS or dual booted from the NVME device when in the "Raid On" mode. Windows install works.
areo47
1 Message
0
September 13th, 2017 18:00
Hi waLLkie, gerster
I have been trying to dual-boot windows and ubuntu linux on an Aurora R6 (with nvme ssd) without much success. After reading this thread, I took out the nvme drive and also decided to just boot linux for now (I have ordered a non-samsung nvme ssd and will try that plus dual-booting if I can ever get linux to boot...)
I have set my bios to AHCI, uefi boot with secure boot off.
I create 3 partitions on the spinning - an EFI partition with the linux boot loader, a swap and a "/" ext4 partition.
I have tried other variants - using legacy boot, installing the boot loader on the root partition, installing it on a separate bios/grub partition etc.
However, I can't get linux to boot. I get either 'Selected boot device failed. Press any key to reboot system.' or linux hangs on a purple screen while booting without any access to recovery mode.
I am guessing you guys got this to work, so would highly appreciate it if you could share your bios settings, how you partitioned your HD and installed the boot loader, any special grub flags etc.
Thanks!
jefa.
1 Message
0
September 18th, 2017 07:00
Updated to Dell release 1.0.9 with the same exact problem. Historically, Dell is one of the most uneducated computer companies when it comes to BIOS. They also can't seem to understand vPro and several other new BIOS standards. That along with the "says its UEFI but looks like Legacy" BIOS screens with limited options keeps me from buying their stuff for my personal systems.
Eimy_B
6 Operator
•
4.4K Posts
0
October 17th, 2017 12:00
It is on our support site but the problem is that the website is having some issues. Engineering is working on fixing these problems as soon as possible.
ifame
8 Posts
1
November 9th, 2017 16:00
Hey guys,
Here is a good news. Finally I can install windows 10 with samsung 960 evo in AHCI mode on Aurora R6 with the new released bios version 1.0.10.
Also, the samsung driver for 960 evo can be installed and Read/Write is around 3100MB/S and 1500MB/S.
One suggestion for installation: use motherboard DisplayPort.
One problem I met: As I download chrome using edge browser, the system crash (before update). I didn’t use edge after update the OS.
ChryssalidZombi
1 Message
0
November 10th, 2017 04:00
I had the same problem described a few times here where the NVMe would show up as 180 million GB or something when the BIOS was set to AHCI mode. This was with an SK hynix 512GB drive that shipped with my R6. What worked for me was to move Windows to a secondary SATA SSD and then install Linux on the NVMe, but still using the EFI partition on the SATA drive (so GRUB is on the SATA SSD). This was with the older BIOS that it shipped with (I think 1.0.8)
After upgrading to BIOS 1.0.10 last night the NVMe drive does show the correct size. But when I tried running Windows from the NVMe, I only got as far as a Windows bluescreen with the error "INACCESSIBLE_BOOT_DEVICE". This was with a system clone so maybe something else had gone wrong, for the record, I haven't tried a clean wipe and reinstall of Windows on the NVMe after upgrading to 1.0.10. Since dual booting is working for now I'm going to use it for a week before fussing again.
Thanks to everyone posting in this thread, it was very valuable.
Andcircle
1 Message
0
November 16th, 2017 08:00
I have a similar issue, but my r6 has intel optane.
I changed to safe mode, and then change RAID ON to AHCI, the computer can not be booted in win 10.
Even when I change back to RAID ON, still give me boot device failure error. Tried many ways, it's still dead.
Dell said they gonna send a technician to replace some part...
My bios is 1.0.7, don't know if 1.0.10 would help for intel optane.
Thanks for this thread, I'm fresh new to Linux, learned a lot from here....