Hello , its SOS..

I turned on my work PC and it wont boot GRUB , at times it will display "GRUB" , "GRUB LoadingREad Error" or display the two lines .. grub loading welcome to kali and throw an error and end up in grub_rescue> ..
so the first step was to book from KALI live USB and follow the many available tutorials already shared .

when I open Gparted

so i'll started off with this Tutorial (altough i am not on dual boot but it will serve the purpose ? )

##my kali installation is on /dev/sda1

the first command as per tut returns this
Code:
root@kali:~# mount /dev/sda1 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
dmesg : pastebin

anyone can put me wise as to what the dmesg indicates ? or how to recover from it ?

following the Error on first step , got to run

Code:
fsck.ext4 -v /dev/sda1
e2fsck 1.42.5 (29-Jul-2012)
fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda1
Could this be a zero-length partition?
Code:
root@kali:~# mke2fs -n /dev/sda1
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
20078592 inodes, 80296448 blocks
4014822 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
2451 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968
following some of tips from here
Code:
root@kali:~# e2fsck -b 32768 /dev/sda1
e2fsck 1.42.5 (29-Jul-2012)
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
/dev/sda1: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix<y>? yes
Inode 1321572 was part of the orphaned inode list.  FIXED.
Deleted inode 1330990 has zero dtime.  Fix<y>? yes
Inode 1331035 was part of the orphaned inode list.  FIXED.
Inode 1331038 was part of the orphaned inode list.  FIXED.
Inode 1331261 was part of the orphaned inode list.  FIXED.
Inode 1331263 was part of the orphaned inode list.  FIXED.
Inode 1331278 was part of the orphaned inode list.  FIXED.
Inode 1331280 was part of the orphaned inode list.  FIXED.
Inode 1455971 was part of the orphaned inode list.  FIXED.
Inode 1456017 was part of the orphaned inode list.  FIXED.
Inode 1465110 was part of the orphaned inode list.  FIXED.
Inode 1471804 was part of the orphaned inode list.  FIXED.
Error reading block 6816664 (Attempt to read block from filesystem resulted in short read) while getting next inode from scan.  Ignore error<y>?
lots of messages with different block came i pressed yes for many but aborted..feared the worst

help from here or tips please ?

thanks