Kali linux dual boout (Win 10) mounting problem

Hello.

I am using Kali Linux quite some time already. Have had it with Win7 on dual boot for more than 3 years.

Switched PC like 2 months ago and installed Kali Linux on dual boot with Win10. I have 2 physical disks. 128GB SSD + 1TB HDD.

On SSD I have all system partitions, Win C:, boot, swap, linux system (it is ext4).
On HDD I have Windows Data (D:) and Linux /home (it is NTFS).

I have been normally working on linux whole last week. Than worked a bit friday evenimg on Win 10.

Today morning, when I started my PC, linux raised error that it can't mount /home directory. I have entered emergency mode and found out that command "df -h" is unable to see 1TB HDD.

Switched over to Windows. Opened 1TB HDD, no problem. Checked files, not a slightest problem. Checked "fast boot" option in Windows, its off.

Rebooted, oppened BIOS, HDD seems fine, its listed in boot options.

Rebooted, linux still same error, cannot mount "/home". Checked fstab, seems ok, no change there.

Rebooted to Win, there are some updates waiting..might this be the problem? Lets try, pushed to install updates. PC rebooted during update, I selected to run Win in grub, it cintinued to updaye. At some 54% of update Win rebooted again..but this time, grub did not started. It says:

"error: unknown filesystem
Entering rescue mode...
grub rescue>"

I have found some link, that Windows can during update mess with partiton scheme (like ***?!).

So I have followed the guide (https://askubuntu.com/questions/6543...to-grub-rescue), it says:

Run "ls" command in grub rescue> it will list all partitions. Than execute "ls" for each partition name and find which one is boot. Fair enough, seems simple. BUT here is the problem: my partitions are:
"(hd0) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) (hd1) (hd1,gpt7) (hd1,gpt6) (hd1,gpt5) (hd1,gpt4) (hd1,gpt3), (hd1,gpt2) (hd1,gpt1)"

I have checked all of them with "ls" command. Each one says "Filesystem is unknown" except (hd0,gpt3) and (hd1,gpt6) which say "Filesystem is ext2". But none say its boot.

Could please anybody give me hints how to make my system running again?

I need to fix the grub first, and than the linux not able to mount "/home".

Updtae on the problem:

I have fixed grub, used my instinct and set

Code:

---

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

---

(bcause it was only ext2 partiton on the disk, where was boot before. It basically moved from hd1,gpt5 to hd1,gpt6).

Now for the kali starting in emergency mode..
I have found out, that for some reason, mounting 1TB HDD is failing when starting. However, if I open console of emergency mode, and mount it manually (mount /dev/sda3 /home) I can run my system normally. However, I still need to find out, why the initial mounting during system start up is failing..

I have check if UUID is right:

Code:

---

rrr-hp:~# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Dec 10 10:46 42c2ad1b-17bb-4a49-9159-c19d46f96433 -> ../../sda3
lrwxrwxrwx 1 root root 10 Dec 10 10:45 85af0a6a-3527-436a-84ac-573d13a6df82 -> ../../sdb7
lrwxrwxrwx 1 root root 10 Dec 10 10:45 90A7-B0D0 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Dec 10 10:45 C4EC3239EC322658 -> ../../sdb4
lrwxrwxrwx 1 root root 10 Dec 10 10:45 ca0cdef8-38bb-457f-8466-dc16f03e581e -> ../../sdb6
rrr-hp:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>  <type>  <options>      <dump>  <pass>
# / was on /dev/sdb5 during installation
UUID=ca0cdef8-38bb-457f-8466-dc16f03e581e /              ext4    errors=remount-ro 0      1
# /boot/efi was on /dev/sdb1 during installation
UUID=90A7-B0D0  /boot/efi      vfat    umask=0077      0      1
# /home was on /dev/sda3 during installation
UUID=42c2ad1b-17bb-4a49-9159-c19d46f96433 /home          ext4    defaults        0      2
# swap was on /dev/sdb6 during installation
UUID=85af0a6a-3527-436a-84ac-573d13a6df82 none            swap    sw              0      0
rrr-hp:~#
rrr-hp:~#
rrr-hp:~# mount UUID=42c2ad1b-17bb-4a49-9159-c19d46f96433 /home
mount: /home: /dev/sda3 already mounted on /home.
rrr-hp:~#

---

It seems to be right..it even identifies the dpartition as /dev/sda3 which is correct.