Grub4dos prompt with Kali Linux

#1
Hello,

I've read many posts to find solution for my problem. I found lots of similar discussions but I couldn't get any success with that so I need a little help.

I have a Win10 installed notebook and EasyBCD 2.3 with UEFI disabled in BIOS. I started to install Kali Linux 2018.1 to the unallocated space of the same drive. I made a 2GB /boot partition and I installed the grub bootloader to this which was /dev/sda5 not to the MBR. After installation finished I started EasyBCD from Win10 and added a Grub2 entry with autoselect option. When I restart I got the metro bootloader screen with the option select Kali but the OS not loaded. I only get a Grub4Dos prompt.

The debugger mode in EasyBCD shows the following configuration:

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale hu-HU
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {c3d9bd8a-143d-11e8-8036-d879c8bd3f01}
resumeobject {c3d9bd89-143d-11e8-8036-d879c8bd3f01}
displayorder {c3d9bd8a-143d-11e8-8036-d879c8bd3f01}
{c3d9bd8d-143d-11e8-8036-d879c8bd3f01}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Windows Boot Loader
-------------------
identifier {c3d9bd8a-143d-11e8-8036-d879c8bd3f01}
device partition=C:
path \Windows\system32\winload.exe
description Windows 10
locale hu-HU
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {c3d9bd8b-143d-11e8-8036-d879c8bd3f01}
displaymessageoverride Recovery
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {c3d9bd89-143d-11e8-8036-d879c8bd3f01}
nx OptIn
bootmenupolicy Standard

Real-mode Boot Sector
---------------------
identifier {c3d9bd8d-143d-11e8-8036-d879c8bd3f01}
device partition=C:
path \NST\AutoNeoGrub0.mbr
description Kali Linux
locale hu-HU
custom:250000c2 1


What I did wrong?


Thanks for reply,
Sandor
 

mqudsi

Mostly Harmless
Staff member
#2
It's possible you've run into a bug in NeoGrub. Let me post a beta build in a couple of hours.
 
#4
Could you please inform me when can I get the beta version of NeoGrub? If it's a bit help for you I can check the NST/AutoNeoGrub0.mbr file in a hex editor but of course I don't know what should I check in it. :grinning:

Sandor
 

mqudsi

Mostly Harmless
Staff member
#5
Hi Sandor,

Sorry about that; I got sidetracked trying to set up an automated build system for EasyBCD. (You can thank @Ex_Brit for setting me straight!)

Can you give the attached build a try? Make sure to use it to first delete the existing Kali entry then add a new one from scratch, before rebooting to test.
 

Attachments

mqudsi

Mostly Harmless
Staff member
#6
If you do run into the same issue, can you check if there's any text displayed before the Grub4Dos prompt to indicate what went wrong?
 
#7
Hi! Thanks to you and @Ex_Brit about working my problem and made a new build. Something is still went wrong but we could step the next level in debug because instead of Grub4Dos prompt I got a "No GRLDR detected in all drives" error message. I'm sure that I installed GRUB on /dev/sda5 in the Kali installation process which is the "hd 0,4" device but I don't know why it isn't detected.