GRUB cannot recognise filesystem

joe213

On my VirtualBox, I had Windows installed on the 2nd partition. I had Linux (Xubuntu) installed on the 3rd partition and I had GRUB installed on the same Drive. When I installed DragonFlyBSD on partition 3, first of all I selected Use legacy BIOS and did not install Bootlock and Packet Mode. And now I get this error from GRUB when I finished installing DragonFlyBSD.

Any ideas as to how to prevent this issue in the first place?

https://drive.google.com/open?id=1lfuesNx0ciT4-hW4nT2ZH-RQqzRvyWSR

Jay

joe213 these might help

https://www.dkade.com/bsd/dragonflybsd/2016/10/10/Dual-Boot-DragonflyBSD-Windows10.html

https://tech.cccp.io/post/20_dragonflybsd_uefi_dualboot_with_linux/

joe213

Jay To understand better what is going on in your first link,

First install Windows 10 then install DragonFly BSD take note of the slice you installed DFBSD, DON’T install boot0 ou bootblocks in the instaler, instead after it finished the installation drop to a shell by going to Live CD Utilities and execute the following command disklabel64 -B da0s5 (change da0s5 for your slice) to install the bootblocks that will be chainloaded by the Windows Boot Manager.

Wait if I change from disklabel64 to da0s5 then how does this install bootblocks? What does this command do and what is da0s5?

Do you have any idea how come just simply installing bootblocks screws up Windows and produces this error as I am trying to understand better what is going on?

https://drive.google.com/file/d/1VY3GHq41cQHGLg9YsoCaQ-knwzmg_Ayl/view?usp=sharing

joe213

Jay I got it to work fine with EasyBCD thanks for the link ?

But I still don't get why does GRUB completely screw up if DragonFly is installed but it has no problems if Windows was installed, do you know why?

Jay

joe213 glad to hear that. I don't know the reason ?