Virtualbox & Grub

enigma9o7 · 08-21-2018, 01:34 AM

I have dual boot windows 10. Decided I want to put windows 10 in virtualbox.

Installed virtualbox no problem.

Code:

sudo apt install virtualbox virtualbox-dkms

I've tried creating the image several ways
1)sudo VBoxManage internalcommands createrawvmdk -filename Win10.vmdk -rawdisk /dev/sda
2)sudo VBoxManage internalcommands createrawvmdk -filename Win10.vmdk -rawdisk /dev/sda -partitions 2
3)sudo VBoxManage internalcommands createrawvmdk -filename Win10.vmdk -rawdisk /dev/sda -partitions 1,2
4)sudo VBoxManage internalcommands createrawvmdk -filename Win10.vmdk -rawdisk /dev/sda -partitions 1,2,3

I am aware I should execute the following command to prevent windows from wanting to re-authenticate itself:

Code:

sudo vboxmanage modifyvm Win10 --hardwareuuid D7E694A0-D74B-11DD-83FA-0024BEC73635

I've done this on and it seems to work fine but isn't related to my problem as I haven't even started booting windows yet.

Since I have grub defaulting to linux with no menu, using option 1 booted linux as I wasn't fast enough to pull up the menu as I wasn't prepared. Even starting to boot linux caused file system errors I had to fix with fsck. So I'm not going to try that again unless that's the only option, in which case I'll bring back my grub menu... but I really prefer no menu as I rarely boot windows, and if this virtualbox works, I probably never will...

The other versions don't boot. Grub says invalid file system.
https://i.imgur.com/IojmAus.jpg

FYI:

Code:

bodhi@VPCF115FM:~$ sudo fdisk -l
Disk /dev/loop0: 135.8 MiB, 142352384 bytes, 278032 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 135.8 MiB, 142352384 bytes, 278032 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop2: 87 MiB, 91160576 bytes, 178048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x98cc18fc

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1  *          2048     718847     716800   350M  7 HPFS/NTFS/exFAT
/dev/sda2           718848 1267616420 1266897573 604.1G  7 HPFS/NTFS/exFAT
/dev/sda3       1463410688 1465143295    1732608   846M 27 Hidden NTFS WinRE
/dev/sda4       1267617790 1463410687  195792898  93.4G  5 Extended
/dev/sda5       1267617792 1463410687  195792896  93.4G 83 Linux

Partition 4 does not start on physical sector boundary.
Partition table entries are not in disk order.

Partion 1 is a recovery partition created by windows 10 clean install.
Partition 2 is the actual windows 10 ntfs partition
Partition 3 is I think a sony system recovery partition but not sure.
Partition 4/5 is Linux.

whansard · 08-21-2018, 01:57 AM

are you talking about booting a virtual box image, or your system boot? are you saying your virtualbox commands you ran corrupted your hard drive partitions filesystems?

enigma9o7 · 08-21-2018, 02:00 AM

I'm talking about using virtualbox to boot my actual installed windows 10. There are several guides for this, but they don't address the issue I'm having.
For example https://www.linkedin.com/pulse/use-y...nux-from-pavic or https://greenash.net.au/thoughts/201...lbox-on-linux/

When I created the disk image using the command that did my entire hard drive/all partitions (#1 above), then when I booted that in virtualbox it ran linux cuz grub defaults to linux. So I was running the same linux under linux. Which understandably caused file system errors, so I corrected them, all is well now.

So I want to create the image using just the partitions that windows needs, but then when I try to boot that, in virtual box, grub gives the file system error. This is because grub can't find grub installed (since the image doesn't include the linux partitions). If there is a way to manually boot to windows from the grub rescue prompt, that'd work for my purposes.

enigma9o7 · 08-21-2018, 01:25 PM

From searching it seems there isn't a way to boot windows from the grub rescue promp. The only thing that seemed promising was to install something called LILO but was pretty old advice so I didn't try it. I guess if I want to do this, I have to use option 1. I brought back my grub menu for 5 seconds
so I have time to select Windows and that works. Just wish I didn't have to.