Grub rescue issue can't solve

Avatar_Tech · 9 February 2022 14:23

hello garuda team ,
the electricity went down and when it back i had
grub rescue issue i have dual boot with win 10 ltsc

and i did the usual steps
ls and set boot and set prefix but all partitions are system file unknown so what to do ?
and i tried to boot from a flash usb and reinstalling grub from garuda boot repair
but it's says error could not set up choot environment please double-check the selected location

i had it before maybe 2 times but i was installing garuda again but i don't want to do this again

SGS · 9 February 2022 14:39

No snapshot works?

Avatar_Tech · 9 February 2022 14:40

didn't make one

SGS · 9 February 2022 14:46

No, coffee today , no grub no snapshot.
Check fstab with grub entries, UUID seems to differ.

Every pacman -Syu or garuda-update make a snapshot.
So the shortest way is reinstalling. My two cent.
choot or chroot?

Avatar_Tech · 9 February 2022 14:48

i just want to repair or reinstall grub to make it work
don't want to reinstall garuda again

SGS · 9 February 2022 14:55

???

Do you use chroot in live ISO in garuda-welcome?

Or How to chroot Garuda Linux ?

Avatar_Tech · 9 February 2022 16:32

can't do it

╭─garuda@garuda in ~ 
╰─λ lsblk -f
NAME FSTYPE FSVER LABEL                    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
squash 4.0                                                                       0   100% /run/miso/sfs/livefs
loop1
squash 4.0                                                                       0   100% /run/miso/sfs/mhwdfs
loop2
squash 4.0                                                                       0   100% /run/miso/sfs/desktopfs
loop3
squash 4.0                                                                       0   100% /run/miso/sfs/rootfs
sda                                                                                            
├─sda1
│    btrfs                                 70d8a845-b6da-4c31-a9f3-2c4d519a035f                
├─sda2
│    ntfs                                  01D80D3FDE46EB00                                    
├─sda3
│                                                                                              
├─sda5
│    ntfs         Games                    48984F3B984F2732                                    
├─sda6
│    ntfs         New Volume               01D7F84BE4E3F7E0                                    
└─sda7
ntfs         New Volume               01D7F84BD25DFE90                                    
sdb  iso966 Jolie GARUDA_DR460NIZEDBLACKARCH_HARPY
│                                          2021-11-29-17-30-54-00                     0   100% /run/miso/bootmnt
├─sdb1
│    iso966 Jolie GARUDA_DR460NIZEDBLACKARCH_HARPY
│                                          2021-11-29-17-30-54-00                              
└─sdb2
vfat   FAT12 MISO_EFI                 5ED8-A115                                           
sdc
sr0
zram0
[SWAP]
McFly: Importing shell history for the first time. This may take a minute or two...done.

and then

╭─garuda@garuda in ~ took 710ms
[⚡] × sudo mkdir -p /mnt/broken

and then

╭─garuda@garuda in ~ took 193ms
╰─λ sudo mount /dev/sda1 /mnt/broken
mount: /mnt/broken: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.

ant it's stops here

filo · 9 February 2022 16:41

Maybe you could try

sudo btrfs check /dev/sda1

and in case of errors

sudo btrfs check --repair /dev/sda1

Avatar_Tech · 9 February 2022 16:51

the same

╭─garuda@garuda in ~ took 250ms
[🔴] × sudo btrfs check /dev/sda1
Opening filesystem to check...
checksum verify failed on 22581870592 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 22581870592 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 22581870592 wanted 0x00000000 found 0xb6bde3e4
bad tree block 22581870592, bytenr mismatch, want=22581870592, have=0
Couldn't read tree root
ERROR: cannot open file system

╭─garuda@garuda in ~ took 1s
[🔴] × sudo btrfs check --repair /dev/sda1
enabling repair mode
WARNING:

Do not use --repair unless you are advised to do so by a developer
or an experienced user, and then only after having accepted that no
fsck can successfully repair all types of filesystem corruption. Eg.
some software or hardware bugs can fatally damage a volume.
The operation will start in 10 seconds.
Use Ctrl-C to stop it.
10 9 8 7 6 5 4 3 2 1
Starting repair.
Opening filesystem to check...
checksum verify failed on 22581870592 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 22581870592 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 22581870592 wanted 0x00000000 found 0xb6bde3e4
bad tree block 22581870592, bytenr mismatch, want=22581870592, have=0
Couldn't read tree root
ERROR: cannot open file system

SGS · 9 February 2022 16:55

cat /etc/fstab
sudo blkid

PerfMonk · 9 February 2022 16:56

To rebuild the filesystem tree try: btrfs check --init-extent-tree

read this tree_repair

I hope last btrfs repair did not do more damage ...

SGS · 9 February 2022 16:58

So, it dos not change anything.

Avatar_Tech · 9 February 2022 17:34

╭─garuda@garuda in ~ took 89ms
╰─λ cat /etc/fstab
File: /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
/dev/mapper/root-image /             auto      defaults           0      0

╭─garuda@garuda in ~ took 249ms
╰─λ sudo blkid
/dev/loop1: TYPE="squashfs"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="5ED8-A115" BLOCK_SIZE="512" TYPE="vfat"
/dev/sdb1: BLOCK_SIZE="2048" UUID="2021-11-29-17-30-54-00" LABEL="GARUDA_DR460NIZEDBLACKARCH_HARPY" TYPE="iso9660"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/sda2: BLOCK_SIZE="512" UUID="01D80D3FDE46EB00" TYPE="ntfs" PARTUUID="a01d6bb2-02"
/dev/sda7: LABEL="New Volume" BLOCK_SIZE="512" UUID="01D7F84BD25DFE90" TYPE="ntfs" PARTUUID="a01d6bb2-07"
/dev/sda5: LABEL="Games" BLOCK_SIZE="512" UUID="48984F3B984F2732" TYPE="ntfs" PARTUUID="a01d6bb2-05"
/dev/sda1: UUID="70d8a845-b6da-4c31-a9f3-2c4d519a035f" UUID_SUB="cecd53da-da5e-4350-830a-e094f3a49b13"BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="a01d6bb2-01"
/dev/sda6: LABEL="New Volume" BLOCK_SIZE="512" UUID="01D7F84BE4E3F7E0" TYPE="ntfs" PARTUUID="a01d6bb2-06"
/dev/zram0: LABEL="zram0" UUID="d467ad12-5bd1-4858-b483-f8a3eb7a490b" TYPE="swap"
/dev/loop3: TYPE="squashfs"

SGS · 9 February 2022 17:46

fstab is destroyed.

Avatar_Tech · 9 February 2022 17:48

so what i have to do?

SGS · 9 February 2022 17:52

lsblk -f

nvme0n1p2btrfs   af57  802,2G    14% /run/timeshift/backup
  /var/cache
  /var/log
  /root
  /var/tmp
  /home
  /srv
  /

Also missing, "tree"

Install again.

SGS · 9 February 2022 17:52

fstab from live ISO?

Avatar_Tech · 9 February 2022 17:53

install what exactly?

Avatar_Tech · 9 February 2022 17:53

how or where?

SGS · 9 February 2022 17:59

The lost of power destroy grub, maybe more
(like fstab? You do not answer my question),
if some fixes let you boot, you never know if something more is broken. It's risky.

You can't chroot, so, you can't restore anything, sad, but we can't change it.

Best is clean, fresh installation.