Windows 10 upgrade ruins dual boot

I have a laptop with Windows 10 and Slackware64-14.2-current. Windows recently upgraded to a newer build of 10. This did something to my GRUB menu. Now I can't boot Slackware. Where before when I started my computer and waited, I would get a GRUB menu with Slackware 14+ and Windows 10 options. Now, if I don't press F9 at start up, I get

Quote:

Welcome to GRUB! error: unknown filesystem. Entering rescue mode... grub rescue>

I looked up how to respond to the grub rescue and found this. I used the following from the answer on that page:

Code:grub rescue>set boot=(hd0,gpt6)
grub rescue>set prefix=(hd0,gpt6)/boot/grub
grub rescue>insmod normal
grub rescue>normalAnd I get my old GRUB menu. I select Slackware and it starts to boot. But then I get the following:Quote:

Checking root filesystem: fsck from util-linux 2.35.1 /sbin/e2fsck: Bad magic number in super-block while trying to open /dev/sda5 /dev/sda5: The superblock could be be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or usf or something else), the the superblock is corrupt, and you migt try running e2fsck with an alternate suprblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> /dev/sda5 contains a ntfs file system *** * An error occurred during the root filesystem check. * You will now be given a chance to log into the system in single-user mode to fix the problem. * * If you are using the ext2 filesystem, running 'ef2sck -v -y <partition>' might help. *** Once you exit the single-user shell, the system will reboot.

I run:

Code:root@darkstar:/# e2fsck -b 8193 /dev/sda5Quote:

e2fsck 1.45.5 (07-Jan-2020) e2fsck: Bad magic number in super-block while trying to open /dev/sda5 The superblock could be be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), the the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> /dev/sda5 contains a ntfs file system

Code:root@darkstar:/# e2fsck -b 32768 /dev/sda5Quote:

e2fsck 1.45.5 (07-Jan-2020) e2fsck: Invalid argument while trying to open /dev/sda5 The superblock could be be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), the the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>

So is my Slackware partition really destroyed? I can't fix GRUB2 and get back to it at this point?