tuxbass Posted May 4, 2016 Share Posted May 4, 2016 Whenever Win 10 VM is started, it first drops to UEFI shell, requiring manual intervention. Immediately after the VM boot-up, black screen with text "Press any(?) key to...??" (currently it's hooked to low-res TV, and the margins are cut off, so can't read the text completely). No matter what you do there, you still end here: UEFI Interactive Shell v2.1 EDK II UEFI v2.50 (EDK II, 0x00010000) Mapping table FS0: Alias(s): CD7a1.... PciRoot(0x0)/Pci...../Ata(0x0)/CDROM(0x1) BLK0: Alias(s): PciRoot(0x0)/Pci...../Floppy(0x0) BLK1: Alias(s): PciRoot(0x0)/Pci...../Floppy(0x1) BLK2: Blias(s): PciRoot(0x0)/Pci...../Ata(0x0) BLK3: Blias(s): PciRoot(0x0)/Pci...../Ata(0x0)/CDROM(0x0) BLK5: Blias(s): PciRoot(0x0)/Pci...../Ata(0x0) Press ESC in <countdown> seconds to skip startup.nsh or any other key to continue. Shell> _ Again, pressing ESC or any other key here won't do anything; need to type 'exit', after which land in BIOS: Standard PC (i440FX + PIIX, 1996) ?c-i440fx-2.5 There I need to select 'Continue' from menu, and only then it boots to windows installation. unraid ver unRAIDServer-6.2.0-beta21 Edit: could it be, that https://lime-technology.com/forum/index.php?topic=39493.0 is still valid, and hasn't been fixed in a year? Edit2: fyi, IIRC, the issue went away after the windows was installed; this problem occurred only during initial vm startup. So I passed that screen as described, and afterwards it was okay when the vm was rebooted. Quote Link to comment
janfredrik Posted May 23, 2016 Share Posted May 23, 2016 Just wanted to say I've got the same issue. 6.2.0-beta21 Thanks for the tip, typing exit I was able to boot to the Win 10 img. Quote Link to comment
SauRoN Posted November 9, 2016 Share Posted November 9, 2016 I have this very same problem but typing "exit" and pressing continue simply loops me into Boot failed and getting the same menu. Quote Link to comment
JustinChase Posted November 21, 2016 Share Posted November 21, 2016 Anyone find a solution to this? I see the same thing. Q35-2.5 OVMF Hyper-V Windows 10 Quote Link to comment
SauRoN Posted November 24, 2016 Share Posted November 24, 2016 Doesn't seem to be anyone using it...or having the same problem. Quote Link to comment
jsdoc Posted December 1, 2016 Share Posted December 1, 2016 I have the same issue with a Hackintosh VM - supposed to boot to the Clover bootloader. I followed the guide to the letter that's supposed to work. Sent from my iPhone using Tapatalk Quote Link to comment
JoreLack Posted December 10, 2016 Share Posted December 10, 2016 Same problem. Works fine when i use Win7 template to install Win10, but when using Win10 template this happens. I want to use Win10 template cos it allows USB3 from the menu. Quote Link to comment
DoeBoye Posted December 12, 2016 Share Posted December 12, 2016 For the record, I have built at least a dozen win10 vms in the process of trying to get GPU passthrough working correctly. Here's what I have observed: Usually no UEFI shell on startup. Once Win10 is installed (I've done Home and Pro), VM boots normally. However, if I hard reset the vm a few times, something sometimes gets corrupted, and I begin to see this behaviour. In some cases, an exit and 'continue' from bios works, in other cases, it just loops over and over again and I wipe and re-install... Not sure how helpful that is, but in my experience, it seems to be related to the hard resets... Maybe something is getting corrupted in the nvram? Quote Link to comment
dadarara Posted December 12, 2016 Share Posted December 12, 2016 had the same problem of dropping to Shell at the beginning of win installation procedure. my solution was to change to another Windows ISO downloaded directly from microsoft. Quote Link to comment
poldim Posted December 25, 2016 Share Posted December 25, 2016 I'm having this issue on several iso's, is there any fix for this? Quote Link to comment
dadarara Posted December 27, 2016 Share Posted December 27, 2016 even for the ISO you downloaded from microsoft directly ? Quote Link to comment
JustinChase Posted December 27, 2016 Share Posted December 27, 2016 even for the ISO you downloaded from microsoft directly ? I've only tried ISOs from Microsoft, I remain stuck in this problem Posted from my phone, forgive any spelling errors. Quote Link to comment
sonofdbn Posted December 27, 2016 Share Posted December 27, 2016 I had the same problem using the downloaded Windows 10 iso, but I typed "exit", which took me to the BIOS and I selected the EFI DVD Rom drive (or something like that - it was the first boot option) and the install started. 4 1 1 Quote Link to comment
trevisthomas Posted January 17, 2017 Share Posted January 17, 2017 So i'm experimenting with restoring VM's from one unRaid install to a different one on different hardware. My primary unRaid system is running 6.1.7, the experimental box is running 6.2.4. I've never seen the issue described in this thread before with 6.1.7 which i've used to host various VM's for the past year, but as soon as i touched 6.2.4, i hit this issue. Someone earlier in this thread suggested that he only saw the issue when using the Windows 10 template, i saw it with Windows 10 and with Win 2012 server. I just installed Windows 2012 server using using the Windows 7 template and the problem went away. Typing exit, and then continue did not work for me. It just goes right back to that Shell command prompt. If you're hitting this issue, try installing the VM using the Windows 7 template, or try an older version of unraid. Quote Link to comment
poldim Posted January 17, 2017 Share Posted January 17, 2017 I've found that using these settings appears to allow the VM to install normally. Key is the SeaBIOS and SATA settings. 5 Quote Link to comment
jochim_vd Posted January 18, 2017 Share Posted January 18, 2017 SeaBIOS seemed to do the trick for me, SATA was not required on my machine. Thanks for helping me out poldim! Quote Link to comment
gef0rce Posted February 10, 2017 Share Posted February 10, 2017 Hi I had a similar issue , what I did was typed "exit" and then went to "Boot Manager" and I could not see my drive ... and I by chance selected "Misc Device" and it booted into my windows Partition. Hope it helps anyone with same issue. Regards Quote Link to comment
jonp Posted February 11, 2017 Share Posted February 11, 2017 Try this http://lime-technology.com/wiki/index.php/UnRAID_OS_version_6_Upgrade_Notes#My_OVMF_VM_doesn.27t_boot_correctly Sent from my SM-G930P using Tapatalk 1 Quote Link to comment
methanoid Posted June 28, 2017 Share Posted June 28, 2017 I have much the same problem twice now, and both times from completely fresh VMs. My unRAID locked last night (I think related to the Radarr docker but thats another matter) and had to be rebooted. My Win10VM failed to restart and just displays UEFI sheell and (importantly) "map: No mapping found" so there is no Fs0: and no ability to get an bootx64.efi file running. It's like the EFI shell is wiped. I'm really reluctant to wipe and re-do a 3rd time as it gets a crazy waste of time with all the config of Win10. Win10 ISO cannot repair this as its not a Win10 issue I think but related to the VM itself. Any ideas? This happened 1st time on 6.3.5 RC3 and now on RC5 but I suspect nothing to do with RCs Quote Link to comment
trevisthomas Posted June 29, 2017 Share Posted June 29, 2017 I don't have any advice for the issue that you're experiencing at the moment, but I did want to make a suggestion. I've taken to backing up my vm images that I can restore them in case things go bad. Theyre pretty easy to restore, even onto different hardware, Quote Link to comment
Muso Posted January 3, 2018 Share Posted January 3, 2018 Hi There, I'm running MacOS HighSierra on a mid-2012 MacBook and I am trying to install Windows through the Oracle VM facility. I have a similar problem as Tuxbass; I get the UEFI interactive shell: BKL0: Alias(s): PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0) BLK1: Alias(s): PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0) Press ESC in <countdown> seconds to skip startup.nsh or any other key to continue. Shell> _ I tried many solutions offered here and elsewhere, but when I get to BIOS to access boot manager, nothing happens. Quote Link to comment
1812 Posted January 3, 2018 Share Posted January 3, 2018 simple fix is use seabios instead. 1 Quote Link to comment
xerox445 Posted November 4, 2018 Share Posted November 4, 2018 On 1/3/2018 at 10:17 AM, 1812 said: simple fix is use seabios instead. On unraid 6.6.3, that selection is grayed out when you select windows 10 template, you cant select seabios Quote Link to comment
Squid Posted November 4, 2018 Share Posted November 4, 2018 2 minutes ago, xerox445 said: On unraid 6.6.3, that selection is grayed out when you select windows 10 template, you cant select seabios Only if you edit an existing VM. On a new VM you are allowed to change the BIOS. 2 Quote Link to comment
xerox445 Posted November 4, 2018 Share Posted November 4, 2018 3 hours ago, Squid said: Only if you edit an existing VM. On a new VM you are allowed to change the BIOS. That was it, I got it working with the SeaBios no problem. Thanks Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.