[SOLVED] grub rescue error: failure reading sector 0x2a00802 from hd0

AdrianMorales · 05-06-2021, 02:23 PM

Hello community,

The other day I was programming in IntelliJ on my ArchLinux and I press the key combination Ctrl+Shift+F10 (or maybe Ctrl+Atl+F10 idk). Then a black screen with an horizontal prompt appears. The system was running cause I heard my spotify songs, but the screen was black. I decide to poweroff the machine by holding the power button. The next time I reboot the laptop, the grub rescue prompt appears.
I try some solutions but nothings seems to work.

First try.- Try to repair grub from the rescue mode

In the grub rescue I type:

Code:

ls
>>>(hd0) (hd0,gpt4) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1)
ls (hd0,gpt4)
>>>Filesystem is ext2
ls (hd0,gpt3)
>>>(hd0,gpt3): Filesystem is unknown
>>>error: failure reading sector 0x2a00802 from hd0
set
>>>cmdpath=(hd0,gpt1)/EFI/BOOT
>>>prefix=(hd0,gpt3)/boot/grub
>>>root=hd0,gpt3
insmod normal 
>>>error: failure reading sector 0x2a00802 from hd0
normal
>>>Unknow command normal

Second try.- Boot-repair-disk

I try to repair the disk with the boot-repair-disk utility but it doesn't show me the option
of recommended repair (I see some solutions take this option)
Then I create a BootInfo summary, here the paste: http://paste.ubuntu.com/p/zhBxWCC7jg/

Thank u for the help!

pan64 · 05-11-2021, 05:18 AM

I would try to boot from an usb stick and check that disk.

AdrianMorales · 05-11-2021, 06:16 AM

Quote:

Originally Posted by pan64

I would try to boot from an usb stick and check that disk.

When I run fdisk -l in a live usb (arch) seems like not detecting my ssd:

Code:

fdisk -l : ___________________________________________________________

Disk nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 sectors
Disk identifier: BFA69E4F-6B49-41DF-A961-FDE4B64FC7FA
              Start        End   Sectors   Size Type
nvme0n1p1      2048     206847    204800   100M EFI System
nvme0n1p2    206848     239615     32768    16M Microsoft reserved
nvme0n1p3    239616  990761253 990521638 472.3G Microsoft basic data
nvme0n1p4 990763008  991823871   1060864   518M Windows recovery environment
nvme0n1p5 991825920 1000214527   8388608     4G Microsoft basic data
Disk nvme1n1: 27.3 GiB, 29260513280 bytes, 57149440 sectors
Disk identifier: 9514720E-07BC-40C4-84BA-8593636BD65F
          Start     End Sectors  Size Type
nvme1n1p1  2048 1050623 1048576  512M EFI System

The first disk is my Windows10 and the second one is an old debian installation.

yancek · 05-11-2021, 08:25 AM

Quote:

I try some solutions but nothings seems to work.

Not helpful or a good idea so now members here have no idea what those 'solutions' were and what possible further damage may have been done. Interesting that ls run from grub only shows one drive while boot repair shows five.

The first line in boot repair shows the following:

Quote:

Windows 7/8/2012 is installed in the MBR of /dev/nvme0n1.

That's the drive with Arch Linux on it. Note that it has an EFI partition with nothing in it, Lines 13-17. So you have windows boot code in the MBR of this drive and an empty EFI partition so no way to boot unless you have an EFI install and put the Arch boot code in the EFI partition of the windows drive which does not appear to be the case (lines 39-47). The output from efibootmgr doesn't show an entry for Arch unless it is the one on line 133 which shows UEFI OS and is the drive on which you had Arch installed.

In your last post you have the output from fdisk showing windows on nvme0n1 while boot repair shows that drive as a Linux install?

Not knowing what other 'solutions' you tried will make it difficult for anyone to help. You may need to reinstall Grub or the Arch OS. Make sure you do an EFI install. Arch generally has good documentation so I would try their site first. The link below is to the ARch wiki and I would suggest reading through it carefully before beginning.

https://wiki.archlinux.org/title/GRUB#Installation_2

colorpurple21859 · 05-11-2021, 09:21 AM

here is the blkid ouput of nvme0n1p3 that / is suppose to be on

Quote:

nvme0n1
├─nvme0n1p1 vfat DCB8-D238 fa56648b-c1f6-8541-a1aa-c3510c9e12cd
├─nvme0n1p2 swap a18b8a84-4ea2-448b-b519-394d45cd2f6e d00fa066-b13d-2e4a-993a-49d003630e64
├─nvme0n1p3
└─nvme0n1p4 ext4 9b342231-828c-4896-bccf-b2d05c121941 ad9eacba-201b-394f-ab52-1e39ed3e2dba

Now the drive isn't showing up.
drive/filesystem corruption, loose connection, or drive broken is my guess.

AdrianMorales · 05-12-2021, 04:39 AM

Quote:

Originally Posted by colorpurple21859

here is the blkid ouput of nvme0n1p3 that / is suppose to be on

Now the drive isn't showing up.
drive/filesystem corruption, loose connection, or drive broken is my guess.

Finally I determined that the disk is corrupted and I reinstall the entire OS.