What have you tried:
I tried starting my system which usually starts into the booting screen where I choose to start into Kali Linux or start the Windows operating system. Now the starting screen doesn’t start and the error: unknown filesystem. grub rescue> pops up.
Also when I try to implant commands it seems like the keyboard doesn’t work as it should and the strokes are shifted one to the right and the / doesn’t seem to work at all which is required to do ls commands as I understand from other posts.
Any solutions in this regard from anyone?
what is the solution to get back into the regular starting screen?
What is the error:
error: unknown filesystem
grub/rescue> How can I start into the booting screen?
What device is this on:
Lenovo Notebook Windows 11
Thank you Fred,
exactly what I was looking for. Additionally I got an error: missing ‘)’ symbol now - which is inhibiting the ability to put in commands (I tried to put in ls (hd0, 1). Also the keyboard strokes are shifted by a stroke and the ( symbol isn’t working) any solutions in regard to this
As I understand it the only hard drive/partition is (hd0,gpt5) which is identified as filesystem ext2 a file system for Linux kernel. This leads me to believe that the others use file systems for Windows kernel as “filesystem is unknown” is given back. is this assumption correct?
I tried some commands which were suggested but the results didn’t show up. Like the “set prefix, set root” commands, I am unable to understand if they come into effect aswell what the effect is. The ls -lh(h0,5) don’t give anything back aswell aswell as the “cat command” and the insmod normal command ■■■■■■ up the writing line and I couldn’t use the command line properly anymore.
Any suggestions? I didn’t manage to reboot with the boot command
In the last step I tried to check for all the directories. I tried to follow the guidance of the online ressources which didn’t really work. The ls -lh command doesn’t work.
In the boot directory seems to be the grub file, which has the system.map and initrd.img files in them. Is this interpretation correct? How do I proceed from here or can get to the next step as the insmod normal gives back the file /boot/x86_64-efi/normal.mod which hasn’t been found.
Also if I try the insmod normal command it doesn’t seem to switch into normal.mode.
As for no ) bracket symbols, as they are usually above the 9 and 0 keys, try both the right and left shift keys to see if that gives you the symbols, they can often give different results.
yes, the non identified file system is probably windows…
this;
/boot/x86_64-efi/
is where an UEFI device will look for a boot file if it finds nothing anywhere else, this file is always included in an ISO bootable live image of an OS (even windows), to enable it to boot, its basically a bootstrap that tells the computer where to find the boot files.
Because you installed the file to hard disk, you don’t have this file (nor do you need it for such an install, its basically saying, “I’ve looked everywhere else, and can’t find this fallback file”, so it doesn’t know what to do now.
You have found your boot partition, it has the /boot /etc /media folders, so your nearly there, you just need to mount it and boot from it, this is perhaps a better guide;
Or if you have access to another computer to create an ISO USB you could use this to sort it out for you, especially if you have a dual boot with Windows to set grub up for
appreciate your help instructor Fred! I managed to get into he grub boot menu aswell on the desktop using the
set root=(hd0,gptX)
set prefix=(hd0,gptX)/boot/grub
insmod normal
normal
Now the next problem occuring is that I get into desktop aswell the partition with Debian/Kali Linux. Though if I restart the system I get into grub rescue mode again. So there is no permanent change in the system.
Thanks for your help Fred.
I learned a lot through this process and given upper ressources and others there seem to multiple paths to solve the problem with which this was one solution.
In specific.
1.Finding the right disk and the right partition. (using ls command)
2.Locating the right directory (boot/grub) using ls / commands.
3.using the right commands to manually boot into OS.
4. update grub/install a specific file.
If there is anymore to say or any useful insights. Let me know.
Thanks Fred
