Hi Everyone, I had some hickups with the GRUB update issue and those issues are now resolved it seems now that I get GRUB screen on restart and I see both Linux 5.19 and LTS kernels.
However, I am seeing this error message and from reading few threads on Arch and other forums, fstab entry seems to be corrupt or incorrect. However, I haven’t made any changes…
As part of GRUB, I did update my system and updated Linux kernels from what I recall.
Here is the fstab
Error
Can we see the output of lsblk -o name,type,fstype,size,label,uuid
Please don’t post a picture of the lsblk output. Copy paste it here.
NAME TYPE FSTYPE SIZE LABEL UUID
loop0 loop 1.6G
sda disk 476.9G
├─sda1 part 511M
└─sda2 part 476.4G
└─mycryptdevice crypt 476.4G
sdb disk 14.9G
└─sdb1 part 14.9G
My apologies. fixed.
Didn’t know paste text will show up same as picture. thanks for the info.
The UUIDs are missing. It looks like you only copied part of it.
use code blocks too please. Either using Ctrl + E or press this button on top of your post
Make it easier for people who are trying to help you. They’ll appreciate it
It didn’t print…
I also ran blkid and seeing the following output
/dev/sdb1: LABEL="EOS_202208" UUID="B806-B15F" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="6d13e565-01"
/dev/loop0: TYPE="squashfs"
/dev/mapper/mycryptdevice: UUID="48b604c7-8ba1-41c8-a430-309c5c20aefb" UUID_SUB="9b277848-f718-4895-b4ea-3806ca74d2b8" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sda2: UUID="477afc62-10fd-4399-8dfd-be348508e3df" TYPE="crypto_LUKS" PARTLABEL="primary" PARTUUID="84fbde54-d58c-4de9-8615-8ce5e93b77f0"
/dev/sda1: UUID="B6C7-D403" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="d1dece63-3878-4cfa-b492-54c20d0b760b"
and my cat /etc/fstab shows the following UUID.
UUID=48b604c7-8ba1-41c8-a430-309c5c20aefb / btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/@ 0 0
# /dev/sda1
UUID=3B96-7080 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
# /dev/mapper/ainstsda2
UUID=48b604c7-8ba1-41c8-a430-309c5c20aefb /home btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/@home 0 0
# /dev/mapper/ainstsda2
UUID=48b604c7-8ba1-41c8-a430-309c5c20aefb /var/cache/pacman/pkg btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=259,subvol=/@pkg 0 0
# /dev/mapper/ainstsda2
UUID=48b604c7-8ba1-41c8-a430-309c5c20aefb /var/log btrfs rw,noatime,compress=zstd:3,ssd,discard=async,space_cache=v2,subvolid=258,subvol=/@log 0 0
They don’t match … Does that mean I need to manually update the fstab to those UUID from blkid output?
Yes. For /boot. Looks like it should be B6C7-D403
Should I update the UUID for the subvols in FSTAB or not required?
It looks correct to me.
WOOW!! You are a lifesaver 
Really appreciate your help.
I am now typing from fixed OS. Huge Thank you!
couple of questions and sorry if they are stupid ones.
blkid showed /dev/sda2: UUID="477afc62-10fd-4399-8dfd-be348508e3df" for sda2where as /etc/fstab shows UUID=48b604c7-8ba1-41c8-a430-309c5c20aefb for the sda2…
But you are correct that /dev/mapper/cryptlvm: UUID="48b604c7-8ba1-41c8-a430-309c5c20aefb" shows same UUID as FSTAB… so I am just confused on two different IDs.
I know you mentioned in other GRUB thread that my boot is a mess. Is there any need to clean up?
I couldn’t run btrfs-assistantwhen I chrooted to fix the GRUB issues. Is that a limitation or chroot won’t allow to run it ? What do you suggest to use if GRUB breaks in future and we need to restore to earlier backup? Would Timeshift work from chroot? Do you know?
This is the UUID of the device itself. However, the device itself isn’t what you are mounting. What you are mounting is the device created after unlocking the encrypted volume.
There are two strange things:
/boot. That works but is very atypical. For grub, it makes more sense to mount the EFI partition at /boot/efi or /efi because grub doesn’t require the kernel and initrams to be in the EFI partition./boot on your / partition that you are mounting over with your EFI partition. Again, that isn’t a problem but it probably means something went wrong at some point in the past.There is no reason to run btrfs-assistant from a chroot. If you want to use btrfs-assistant to restore, you can do that without a chroot. You just need to unlock your luks partition and mount some part of the btrfs partition.
I used the archinstall script from the July iso and this was its setup. On my manual install, I did install it to /boot/efi. I’ll take a note of this.
For the fun, I’m back into live iso and unlocked and mounted my subvols as usual. I didn’t chroot yet
I ran btrfs-assistant but get a msg saying command not found.
Did you install it? Btrfs Assistant isn’t on the ISO by default.
Yes, I have it installed and taken few snapshots this morning after the GRUB fix.
silly me. so I need to chroot to use the command?
after chroot into subvols, running btrfs-assistant -l, I get the following message:
[root@EndeavourOS /]# sudo btrfs-assistant -l
Authorization required, but no authorization protocol specified
qt.qpa.xcb: could not connect to display :0.0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
/usr/bin/btrfs-assistant: line 42: 6 Aborted (core dumped) btrfs-assistant-bin ${params}
Running sudo from within chroot-env. isn’t possible, because root is alread root.
same error if I run without sudo
[root@EndeavourOS /]# btrfs-assistant -l
Authorization required, but no authorization protocol specified
qt.qpa.xcb: could not connect to display :0.0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
/usr/bin/btrfs-assistant: line 42: 15 Aborted (core dumped) btrfs-assistant-bin ${params}
That means, btrfs-assistant can’t be run within chroot, then.