socratis wrote:You have an external HD in which you installed Win10 with WinToUSB. The latter requires Windows to run. How did you do it? In a VM? (that's how I did it)
Yes, I used VM.
socratis wrote:You use this HD to also boot your Mac? If so, the Win10 uses EFI, or actually it should use EFI if you set it up properly.
Yes, I boot it from Mac by setting this HD in "Startup Disk" application. I'm not sure about EFI part. According to tutorial I set "200MB EFI partition".
socratis wrote:I'll need to see the contents of the VMDK
I tried to create VMD for /dev/disk2 and /dev/disk2s
Code: Select all
MacBook-Pro:~ my$ sudo vboxmanage internalcommands listpartitions -rawdisk /dev/disk2
Number Type StartCHS EndCHS Size (MiB) Start (Sect)
1 0x00 0 /0 /0 0 /0 /0 200 40
2 0x00 0 /0 /0 0 /0 /0 243997 411648
MacBook-Pro:~ my$ sudo vboxmanage internalcommands listpartitions -rawdisk /dev/disk2s1
Number Type StartCHS EndCHS Size (MiB) Start (Sect)
MacBook-Pro:~ my$ sudo vboxmanage internalcommands listpartitions -rawdisk /dev/disk2s2
VBoxManage: error: Overlapping MBR partitions
Number Type StartCHS EndCHS Size (MiB) Start (Sect)
1 0x72 80 /13 /10 371 /101/51 886821 1920221984
2 0x6c 357 /43 /4 367 /32 /52 953932 1936028192
/dev/disk2:
Code: Select all
sudo VBoxManage internalcommands createrawvmdk -filename "/Users/my/Documents/Windows10.vmdk" -rawdisk /dev/disk2
Code: Select all
# Disk DescriptorFile
version=1
CID=437ec59f
parentCID=ffffffff
createType="fullDevice"
# Extent description
RW 500118192 FLAT "/dev/disk2" 0
# The disk Data Base
#DDB
ddb.virtualHWVersion = "4"
ddb.adapterType="ide"
ddb.geometry.cylinders="16383"
ddb.geometry.heads="16"
ddb.geometry.sectors="63"
ddb.uuid.image="0489d5da-48dd-4008-b5f7-835dc0c2f6c4"
ddb.uuid.parent="00000000-0000-0000-0000-000000000000"
ddb.uuid.modification="00000000-0000-0000-0000-000000000000"
ddb.uuid.parentmodification="00000000-0000-0000-0000-000000000000"
and /dev/disk2s2:
Code: Select all
sudo VBoxManage internalcommands createrawvmdk -filename "/Users/my/Documents/Windows10.vmdk" -rawdisk /dev/disk2s2
Code: Select all
# Disk DescriptorFile
version=1
CID=da71997e
parentCID=ffffffff
createType="fullDevice"
# Extent description
RW 499705856 FLAT "/dev/disk2s2" 0
# The disk Data Base
#DDB
ddb.virtualHWVersion = "4"
ddb.adapterType="ide"
ddb.geometry.cylinders="16383"
ddb.geometry.heads="16"
ddb.geometry.sectors="63"
ddb.uuid.image="bfd65a3d-9545-42ee-b975-b6533d65fa14"
ddb.uuid.parent="00000000-0000-0000-0000-000000000000"
ddb.uuid.modification="00000000-0000-0000-0000-000000000000"
ddb.uuid.parentmodification="00000000-0000-0000-0000-000000000000"
ddb.geometry.biosCylinders="1024"
ddb.geometry.biosHeads="255"
ddb.geometry.biosSectors="63"
Then I set chmod 777 for /dev/disk2* and my VMDK file. When I try to run VMDK for /dev/disk2s2 I get this error:
Code: Select all
VD: error VERR_NOT_SUPPORTED opening image file '/Users/my/Documents/Windows10.vmdk' (VERR_NOT_SUPPORTED).
VD: error VERR_ACCESS_DENIED opening image file '/Users/my/Documents/Windows10.vmdk' (VERR_ACCESS_DENIED).
Failed to open image '/Users/my/Documents/Windows10.vmdk' in read-write mode (VERR_ACCESS_DENIED).
AHCI: Failed to attach drive to Port0 (VERR_ACCESS_DENIED).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
And when I change controller from SATA to IDE, it starts, I see blinking underscore and that's it. The last entry in logs:
Code: Select all
00:00:04.149517 VMMDev: Guest Log: BIOS: Booting from Hard Disk...