ошибка: ошибка чтения сектора 0x802 из 'hd0'. Вход в режим восстановления grub rescue>

Your hard disk is failing. We can try a few things, so keep your fingers crossed. You have two partitions on your hard disk, and both partitions are having problems, which suggests a problem with the MBR partition table, or just the hard disk failing in a very complicated way. You may have to replace the disk drive.

fsck

This is a file system check. It's the first step to try and diagnose and repair your disk. If we can't get it to run successfully, we'll have to go to the gparted step.

For 17.10 or older...

• boot to the GRUB menu
• choose Advanced Options
• choose Recovery mode
• choose Root access
• at the # prompt, type sudo fsck -f /
• repeat the fsck command if there were errors
• type reboot

For 18.04 or newer... (or if the above steps don't work for you)...

• boot to a Ubuntu Live DVD/USB in “Try Ubuntu” mode
• open a terminal window by pressing Ctrl+Alt+T
• type sudo fdisk -l
• identify the /dev/sdXX device name for your "Linux Filesystem"
• type sudo fsck -f /dev/sdb1, replacing sdXX with the number you found earlier
• repeat the fsck command if there were errors
• type reboot

gparted

If fsck can't be run successfully, we'll try the Check option in gparted. Start gparted. Select /dev/sdb1. Go to the Partition menu and select Check.

If that's not able to fix the errors, assuming that you don't have good data backups, we'll attempt at recovering your data.

In gparted, go to the Device menu, and select Attempt Data Rescue. Follow the instructions to try and copy your data off to an external disk drive.

bad block

As a last ditch effort to repair your hard disk, we'll try to bad block the disk, as you do have some bad sectors on the disk. This may fail, and leave your disk in an unknown state.

Note: do NOT abort a bad block scan!

Note: do NOT bad block a SSD

Note: backup your important files FIRST!

Note: this will take many hours

Note: you may have a pending HDD failure

Boot to a Ubuntu Live DVD/USB in “Try Ubuntu” mode.

In terminal...

sudo fdisk -l # identify all "Linux Filesystem" partitions

sudo e2fsck -fcky /dev/sdXX # read-only test

or

sudo e2fsck -fccky /dev/sdb1 # non-destructive read/write test (recommended)

The -k is important, because it saves the previous bad block table, and adds any new bad blocks to that table. Without -k, you loose all of the prior bad block information.

The -fccky parameter...

   -f    Force checking even if the file system seems clean.

   -c    This option causes e2fsck to use badblocks(8) program to do
         a read-only scan of the device in order to find any bad blocks.
         If any bad blocks are found, they are added to the bad block
         inode to prevent them from being allocated to a file or direc‐
         tory.  If this option is specified twice, then the bad block scan
         will be done using a non-destructive read-write test.

   -k    When combined with the -c option, any existing bad blocks in the
         bad blocks list are preserved, and any new bad blocks found by
         running badblocks(8) will be added to the existing bad blocks
         list.

   -y    Assume an answer of `yes' to all questions; allows e2fsck to be
         used non-interactively. This option may not be specified at the
         same time as the -n or -p options.

sdb2

This extended partition is also having problems, and the partition is empty, and can be deleted, using gparted.

Update #1:

The HDD is defective. Replace it.