Unknown filesystem

[DavidMotionless]

Story: I have a laptop on which I dual boot Windows 10 and Kali linux, I didnt use kali in a long time, and a few days ago I wanted to use it. It didnt load up as normal but instead it said:

Error: unknown filesystem
Entering rescue mode...
grub rescue>

So I googled it and I found a solution, which said that i should enter these commands:

set prefix=(hdy,x)/boot/grub
set root=(hdy,x)
insmod normal
normal
and after that it would boot to kali and it said that i should do these commands in my terminal:
sudo update-grub
sudo grub-install /dev/sda
but it didnt boot to kali, it went to menu with these options:

-Kali GNU/Linux
-Advanced options for Kali GNU/Linux
-Windows Boot Manager (on /dev/sda2)
-System setup

and after i select the first one (which i think i should) the boot drops to initramfs window with the following messages:

mount: mounting /dev on /root/dev failed: no such file or directory
mount: mounting /dev on /root/dev failed: no such file or directory
mount: mounting /dev on /root/run failed: no such file or directory
run-init: opeinng console: No such file or directory
Target filesystem doesn't have requested /sbin/init.
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
No init found. Try passing init= bootarg.


BusyBox v1.27.2 (Debian 1:1.2.27.2-3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) _ (blinking line waiting for me to type in something)

How can i fix this? Any help would be appreciated :) <3

[_defalt]

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

ls(LS) lists all partitions of your hard drive like this (hd0) (hd0,gpt1) (hd0,gpt2). You can make some guesses which one is your kali filesystem to replace the variable gptx.

Once you boot into kali open terminal and type:

grub-install /dev/sda
update-initramfs -u
update-grub

[DavidMotionless]

Thanks for replying.

I have alredy tried that method and I am able get out of the "grub" window,but it doesnt boot in to kali after that, it goes straight to "(initramfs)" window, so I cant get to the terminal to update. I've said this in my thread alredy. Anyways thanks for your help. Do you mind explaining what these commands do?:

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

[_defalt]

It points grub to kali filesystem to boot. You are entering these commands incorrectly.

hd0, gptx are variables. ls gives you the name of your hard drive like hd0 or hd1 or hd2 and name of partition like gpt1 or gpt2 or gpt 3 etc. Which one is your kali filesystem from the output of ls? Can you show the output of ls?

[DavidMotionless]

Okay

Output of ls is:
(hd0) (hd0,gpt7) (hd0,gpt6) (hd0,gpt5) (hd0,gpt4) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1)

So I ls all of them individually:

ls (hd0)...
ls (hd0,gpt7)...

and so on...

This is what i get:

for (hd0) Filesystem is unknown.
for (hd0,gpt7) Filesystem is unknown.
for (hd0,gpt6) Filesystem is ext2.
for (hd0,gpt5) Filesystem is unknown.
for (hd0,gpt4) Filesystem is unknown.
for (hd0,gpt3) Filesystem is unknown.
for (hd0,gpt2) Filesystem is unknown.
for (hd0,gpt1) Filesystem is unknown.

then i enter these commands:

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

and it sends me to a blue window(attached picture):


cb265df0-9f0c-437b-9626-23e7b758af01.jpg

and after i select the first option "Kali GNU/Linux" it goes to the (initramfs) window.

[_defalt]

It is going to correct place. That blue screen is grub menu where you can boot either kali or windows. I think your kali filesystem is currupted. Select advance options for kali. It takes you to older image of kali. You can then fix kali filesystem and reinstall grub from there.

[DavidMotionless]

After i select "Advanced options for kali" and i select the recovery mode, it goes to the (initramfs) window....i cant find the commands to get out of that.