Boot-up displays UEFI Interactive Shell

[Andrew77]

Hello, I am trying to boot my Windows 10 partition from within VirtualBox running on Kubuntu. I have created a vmdk file and updated permissions, but when I start it, it just boots into the UEFI Interactive Shell. I have tried switching between "Windows UEFI Mode" and "Other OS" in the BIOS but it doesn't appear to make any difference. I have read I need to locate the EFI file on the System Reserved partition to be able to continue the boot. I mounted the partition, but can only seem to get limited access, and can't find any reference to an EFI file. These is my setup instructions so far -

Code: Select all

: sudo VBoxManage internalcommands listpartitions -rawdisk /dev/sda

Number  Type   StartCHS       EndCHS      Size (MiB)  Start (Sect)
1       0x07  0   /32 /33  12  /223/19           100         2048 (System Reserved)
2       0x07  12  /223/20  1023/254/63        299899       206848 (Windows 10)
3       0x83  1023/254/63  1023/254/63        300000    614400000 (Kubuntu 16.04)
4       0x07  1023/254/63  1023/254/63        300000   1228800000 (Storage)

: sudo VBoxManage internalcommands createrawvmdk -filename Win10.vmdk -rawdisk /dev/sda -partitions 1,2 -relative
: sudo chown asr:asr Win10*
: sudo chmod 666 Win10*

: cd /dev
: ll sda*

rw-rw---- 1 root disk 8, 0 Jun 18 10:40 sda
brw-rw---- 1 root disk 8, 1 Jun 18 10:40 sda1
brw-rw---- 1 root disk 8, 2 Jun 18 10:40 sda2
brw-rw---- 1 root disk 8, 3 Jun 18 10:40 sda3
brw-rw---- 1 root disk 8, 4 Jun 18 10:40 sda4

: sudo chmod 666 sda1 sda2

UPDATE

This is the screen I'm presented with regarding the UEFI Interactive Shell -



I'm not having much luck getting past the UEFI Interactive Shell so I've created a new vmdk file without the "System Reserved" partition and just using my Windows 10 partition to attempt to boot from (rightly or wrongly?). I boot this virtual disk and am presented with, and tried the commands, as follow -

Code: Select all

error: unknown filesystem.
Entering rescue mode...
grub rescue> ls
(hd0) (hd0,msdos4) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)
grub rescue> insmod part_msdos
grub rescue> ls (hd0,msdos1)/
error: unknown filesystem.
grub rescue> insmod ntfs
error: unknown filesystem.

These are the first few lines of the Windows 10 section of the /boot/grub/grub.cfg file, which don't seem to work if I run them manually.

Any pointers on what I can do to continue the boot, with or without the System Reserved partition, would be greatly appreciated.

Thanks in advance.
Andrew.

[Andrew77]

Hello. I have shelved the above two methods for now and I have now created a new vmdk file consisting of both my Reserved Partitions and the Windows 10 partition, and am using a grub2 recovery disk to boot VirtualBox from, which shows this screen -



Detect and show boot methods, shows -



But booting the first option gives me a Windows logo with the text "Preparing Automatic Repair", and the second option just gives me a Windows logo, both hang indefinitely.

UPDATE

I found the commands that grub2 executes and can run them at a command prompt manually -

Code: Select all

set root=(hd0,msdos1)
chainloader +1
boot

.. but it does exactly the same thing, I'm not sure how I can debug it any further?

Any suggestions would be greatly appreciated.
Andrew.