[Help] grub error

[Goofychex]

[Help] grub error

[SarKaa]

You can try the etcher image, which I added in the latest release, but its probably not gonna work, as it is incompatible. I suggest using checkn1x, as it support more types of computers. The only drawback to this is the lack of project sandcastle and irecovery features, but most people don't need it, so its quite a niche problem. If you do need irecovery, you could make an ubuntu/debian live usb, and use that instead.
I'm really sorry I can't help, but in order to add support, I'll have to redownload and manually install a LOT of debs, which is too complex to do for project sandcastle and irecovery manually. I did it earlier as I added them one at a time, whereas now I have to download a lot of seperate files and work out conflicts and stuff.
I hope you understand

[SarKaa]

Ok lemme look into this

[SarKaa]

Try disabling secure boot, because it could be stopping the filesystem from being read

[Goofychex]

Try disabling secure boot, because it could be stopping the filesystem from being read

Thanks for the suggestion.
But "Secure Boot" is already disabled!

• Any other ideas? 🤔

[JorgeCavalcantiC]

Having same problem, using Windows 10, secure boot already disabled.

[SarKaa]

You are amd 64 right (x86_64)

[Goofychex]

You are amd 64 right (x86_64)

Yes.

[WiesoBistnSo]

Have the Same issue.

[Goofychex]

You can try the etcher image, which I added in the latest release, but its probably not gonna work, as it is incompatible. I suggest using checkn1x, as it support more types of computers. The only drawback to this is the lack of project sandcastle and irecovery features, but most people don't need it, so its quite a niche problem. If you do need irecovery, you could make an ubuntu/debian live usb, and use that instead.

I'm really sorry I can't help, but in order to add support, I'll have to redownload and manually install a LOT of debs, which is too complex to do for project sandcastle and irecovery manually. I did it earlier as I added them one at a time, whereas now I have to download a lot of seperate files and work out conflicts and stuff.

I hope you understand

Okay.

• Thanks!

[SarKaa]

Well it seems like we found a fix on discord, but it's a temporary one, you will have to repeat it every time you boot. I am trying to automate the process, currently, but if you want the temporary fix, here it is:

After you boot jailm8, if you get the unknown filesystem error, you should crash into a grub rescue prompt. In that prompt:

Type ls
It should output a list of devices like this :
(hd0),(hd0,msdos1)(hd0,msdos2)(hd0,msdos4)

For every value in brackets, so say for example (hd0,msdos1), type in the commands
set prefix=(hd0,msdos1)/boot/grub

set root=(hd0,msdos1)

If that says unknown filesystem again, try again with the next value, so:

set prefix=(hd0,msdos2)/boot/grub

set root=(hd0,msdos2)

Keep trying until they don't show an error
When one of them doesn't return an error, type the following commands:

insmod normal
normal

You should boot into jailm8 successfully. If you don't, make sure secure boot is disabled, and you are using the latest version of jailm8

Edit: could you also try version 4.0.0 in releases, it's a pre-release, solely for testing, but it should work.

[SarKaa]

Well we've made some progress, and you only need 4 commands now:

set root=(hd0,1)
set prefix=(hd0,1)/boot/grub/
insmod normal
normal

[favna]

I just ran into this issue on a system whose primary OS is Windows 11 so my bios didn't even allow me to disable secureboot. That said however, the comment above solved it instantly.

I did have to put my BIOS's SecureBoot OS Type from "Windows UEFI mode" to "Other OS", but that is to be expected when launching a Linux based OS.

[FeBe95]

My Boot Override list in the UEFI contained the following items:

DVD-ROM
Windows Boot Manager
...
VendorCoProductCode
UEFI: VendorCoProductCode

I had to choose VendorCoProductCode in order for grub/jailm8 to work. UEFI: VendorCoProductCode gave me the same error you were getting.

I suppose the latter tries to start grub/jailm8 in UEFI mode which fails somehow. The other one boots in Legacy BIOS mode which worked for me.