Errors during boot after resize via gparted

Evo · July 27, 2021, 7:58pm

EndeavourOS was awesome so far but I might have fucked up a little bit with a recent change (which I assumed would not even touch my EndeavourOS installation but welp). I’m really hoping you guys can help me out here.

Background:
I have two SSDs.
sda1 popOS
sda2 windows10 boot sector
sda3 windows10

sdb1 grub2 core.img
sdb2 EndeavourOS with a btrfs filesystem (@, @home, @snapshots)

What I wanted to do is give my Windows10 partition a bit more space. I used gparted to reduce the size of sda1 by 80GB, I moved sda2 and sda3 “left” and then added 80GB onto sda3 (win10). I also performed a system update via yay that I had put off for a few weeks (was just below 200 updates).

I don’t care much about the data on the windows partition but it’d be nice to avoid a reinstall there. I do very much care about my EndeavourOS. :<

Aftermath:
On reboot EndeavourOS failed with “error: file ‘/@/boot/vmzlinuz-linux’ not found”. The lts-version also failed, as did my latest snapshot.

Windows 10 also failed to boot and is asking for a recovery medium.

PopOS was and is booting up just fine.

What I tried so far:
I booted into an EndeavourOS live medium and chrooted into my installation following this guide (“Practical chroot with btrfs subvolumes”).

mkinitcpio -P

returned some errors that I don’t exactly remember.

pacman -S linux

Seemed to work fine and I verified vmzlinuz-linux showing up in /@/boot/ afterwards.

On reboot I was greeted with this error, I also do not have access to my usb keyboard at that point. Trying to boot into linux-lts results in this error.

I tried reinstalling libutil-linux and

pacman -Syyuu

via the live medium & chroot again, but nothing seems to change at this point.

So uh… help, please? ;;

Let me know if you guys need any additional information but I hope I got everything that could be relevant and thank you for your time in advance. <3

dalto · July 27, 2021, 8:02pm

It is possible that your partition operation changed the UUID of the partition.

Can we see the contents of /etc/fstab as well as the output of lsblk -o name,type,fstype,uuid,size

Evo · July 27, 2021, 8:06pm

Oh god, I did not even think about this.

evo@pop-os:~$ lsblk -o name,type,fstype,uuid,size
NAME          TYPE  FSTYPE  UUID                                   SIZE
sda           disk                                               931,5G
├─sda1        part  ext4    399cabc3-c5a4-4b58-965f-745351207608 619,9G
├─sda2        part  ntfs    920E739D0E7378D5                        50M
├─sda3        part  ntfs    B86A75456A750184                     307,6G
└─sda4        part  swap    7b15e5af-8ae3-48b7-a5ad-b2529b2e139d     4G
  └─cryptswap crypt swap    b2f7e532-7787-4623-9b0c-df79d684545b     4G
sdb           disk                                               931,5G
├─sdb1        part                                                   8M
└─sdb2        part  btrfs   32166223-8f4f-4f69-9149-fe979df93e58 931,5G
sdc           disk                                                 1,8T
├─sdc1        part  ntfs    6276CC3176CC082D                       100M
└─sdc2        part  ntfs    4C8AB5D98AB5BFAE                       1,8T
sdd           disk                                                 2,7T
├─sdd1        part                                                 128M
└─sdd2        part  ntfs    983EA77B3EA750D4                       2,7T
sde           disk  iso9660 2020-09-20-20-31-31-00                14,3G
├─sde1        part  iso9660 2020-09-20-20-31-31-00                 1,8G
└─sde2        part  vfat    8D52-3AEA                               64M

fstab is from /@/etc of course:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=32166223-8f4f-4f69-9149-fe979df93e58 /              btrfs   subvol=@,defaults,noatime,space_cache,autodefrag,compress=lzo 0 1
UUID=32166223-8f4f-4f69-9149-fe979df93e58 /home          btrfs   subvol=@home,defaults,noatime,space_cache,autodefrag,compress=lzo 0 2
UUID=32166223-8f4f-4f69-9149-fe979df93e58 /mnt/ssd       btrfs   subvol=/,defaults 
# UUID=399cabc3-c5a4-4b58-965f-745351207608 /run/media/evo/popos         ext4    noatime 0 0	
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

(Don’t ask me why I removed popos from my fstab there, but do tell me please how I get the UUIDs from subvolumes again. Neither of these work from my pop install as of now, a reminder on how to get those would be sweet!):

btrfs subvolume list
btrfs subvolume show

e: Nevermind me, read the UUIDs wrong.

dalto · July 27, 2021, 8:09pm

That all looks fine.

Can you go back into the arch-chroot and run pacman -Syu linux-lts and if there are errors, let us know what they are?

Evo · July 27, 2021, 8:24pm

Just in case, that's how I'm getting in there:

[liveuser@eos-2020.09.20 ~]$ sudo su
[root@archiso liveuser]# mount /dev/sdb2 /mnt/ -t btrfs -o subvol=@
[root@archiso liveuser]# mount /dev/sdb2 /mnt/home -t btrfs -o subvol=@home
[root@archiso liveuser]# mount --bind /dev /mnt/dev
[root@archiso liveuser]# mount -t proc /proc /mnt/proc
[root@archiso liveuser]# mount -t sysfs /sys /mnt/sys
[root@archiso liveuser]# mount -t tmpfs tmpfs /mnt/run
[root@archiso liveuser]# mkdir -p /mnt/run/systemd/resolve/
[root@archiso liveuser]# echo 'nameserver 1.1.1.1' > /mnt/run/systemd/resolve/stub-resolv.conf
[root@archiso liveuser]# ls /mnt/boot
grub                          initramfs-linux.img  vmlinuz-linux
initramfs-linux-fallback.img  intel-ucode.img      vmlinuz-linux-lts
[root@archiso liveuser]# chroot /mnt

`pacman -Syu linux-lts`:

[root@archiso /]# pacman -Syu linux-lts
warning: config file /etc/pacman.conf, line 38: directive 'TotalDownload' in section 'options' not recognized.
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community                         5.6 MiB  9.69 MiB/s 00:01 [--------------------------------] 100%
 multilib                        149.9 KiB  5.42 MiB/s 00:00 [--------------------------------] 100%
 endeavouros                      18.6 KiB   164 KiB/s 00:00 [--------------------------------] 100%
warning: linux-lts-5.10.53-1 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Package (3)               Old Version  New Version  Net Change  Download Size

endeavouros/eos-log-tool  1.4.6-1      1.4.7-1        0.00 MiB       0.02 MiB
multilib/steam            1.0.0.70-1   1.0.0.71-1     0.01 MiB       3.24 MiB
core/linux-lts            5.10.53-1    5.10.53-1      0.00 MiB               

Total Download Size:    3.26 MiB
Total Installed Size:  82.70 MiB
Net Upgrade Size:       0.01 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 eos-log-tool-1.4.7-1-any                                                             15.5 KiB   455 KiB/s 00:00 [-------------------------------------------------------------------] 100%
 steam-1.0.0.71-1-x86_64                                                               3.2 MiB  9.26 MiB/s 00:00 [-------------------------------------------------------------------] 100%
 Total (2/2)                                                                           3.3 MiB  7.81 MiB/s 00:00 [-------------------------------------------------------------------] 100%
(3/3) checking keys in keyring                                                                                   [-------------------------------------------------------------------] 100%
(3/3) checking package integrity                                                                                 [-------------------------------------------------------------------] 100%
(3/3) loading package files                                                                                      [-------------------------------------------------------------------] 100%
(3/3) checking for file conflicts                                                                                [-------------------------------------------------------------------] 100%
(3/3) checking available disk space                                                                              [-------------------------------------------------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Remove upgraded DKMS modules
:: Processing package changes...
(1/3) reinstalling linux-lts                                                                                     [-------------------------------------------------------------------] 100%
(2/3) upgrading eos-log-tool                                                                                     [-------------------------------------------------------------------] 100%
(3/3) upgrading steam                                                                                            [-------------------------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/9) Reloading device manager configuration...
  Skipped: Running in chroot.
(2/9) Arming ConditionNeedsUpdate...
(3/9) Updating module dependencies...
(4/9) Install DKMS modules
(5/9) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 5.10.53-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating xz-compressed initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 5.10.53-1-lts
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: xhci_pci
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [filesystems]
  -> Running build hook: [grub-btrfs-overlayfs]
==> Generating module dependencies
==> Creating xz-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successful
(6/9) Cleaning pacman cache...
warning: config file /etc/pacman.conf, line 38: directive 'TotalDownload' in section 'options' not recognized.

==> finished: 2 packages removed (disk space saved: 2.81 MiB)
(7/9) Check if user should be informed about rebooting after certain system package upgrades.
(8/9) Updating icon theme caches...
(9/9) Updating the desktop file MIME type cache...

…that should have done something to the linux-lts error at least if I read this right.

The firmware errors are completely normal afaik, been like that since ages now.

e: Is there a specific reason you said arch-chroot and not chroot and should that worry me?

dalto · July 27, 2021, 8:36pm

Evo:

[liveuser@eos-2020.09.20 ~]$ sudo su
[root@archiso liveuser]# mount /dev/sdb2 /mnt/ -t btrfs -o subvol=@
[root@archiso liveuser]# mount /dev/sdb2 /mnt/home -t btrfs -o subvol=@home
[root@archiso liveuser]# mount --bind /dev /mnt/dev
[root@archiso liveuser]# mount -t proc /proc /mnt/proc
[root@archiso liveuser]# mount -t sysfs /sys /mnt/sys
[root@archiso liveuser]# mount -t tmpfs tmpfs /mnt/run
[root@archiso liveuser]# mkdir -p /mnt/run/systemd/resolve/
[root@archiso liveuser]# echo 'nameserver 1.1.1.1' > /mnt/run/systemd/resolve/stub-resolv.conf
[root@archiso liveuser]# ls /mnt/boot
grub                          initramfs-linux.img  vmlinuz-linux
initramfs-linux-fallback.img  intel-ucode.img      vmlinuz-linux-lts
[root@archiso liveuser]# chroot /mnt

I don’t see anything wrong in that but it is certainly more complicated than it needs to be.

sudo mount /dev/sdb2 /mnt -o subvol=@
sudo arch-chroot /mnt

Yes. Can you reboot and see if anything is changed?

Yes, those are normal

Because it is way easier than building a chroot manually

Evo · July 27, 2021, 8:45pm

After „starting version xxx arch“ (which seems rather slow) I’m getting just a blinking cursor in the top left.

That’s for both the regular linux-lts and with fallback initramfs.

e:

Oh god, thank you.

e2: After some google-fu the blinking cursor sounds like an unrelated error with GDM? I can’t remember the last time I booted into linux-lts so that might very well be the case.

dalto · July 27, 2021, 8:59pm

Alright, well, if all the errors are gone, my job is done.

OK, so, a couple of questions.

After letting it sit there for a couple of minutes, can you use ctrl+alt+f3 to switch to a TTY?
If not, does it eventually fail and give you an error if you let it timeout?

Evo · July 27, 2021, 9:05pm

I do get into a tty this way and can login just fine. I’m not sure what to do from here, but that’s something I could hopefully figure out on my own unless you have a quick and obvious solution to throw my way.

…that being said, hold up a second (pretty please)! How do I fix this mess for the regular kernel? That still looks like this afterall

dalto · July 27, 2021, 9:06pm

I don’t have a quick solution without getting some more information about your hardware but graphics drivers are the most likely cause.

Try running sudo mkinitcpio -p linux from the TTY.

Evo · July 27, 2021, 9:21pm

I have great news and bad news and I’m pretty sure I’ll (deservedly) get slapped for that bad news part.

Good news: That fixed that part, I can now boot into my regular linux kernel fine, thank you. <3

Bad news: After logging in (excuse the blurriness) my desktop looks like this with no input being recognized (swapping to tty works fine) and I have a suspicion: I’ve been putting off the update to Gnome 40 until earlier today and I’m 99% sure I didn’t reboot since. That has to be what’s going on here. So yes, partial updates and yes, two big changes to my system without rebooting in between.

I assumed a partial update like this should be fine if nothing breaks and I can just be fine with something like -pacman -Syyuu once it does, but there’s nothing to do according to pacman.

…should I open a new thread for that one? ;;

dalto · July 27, 2021, 9:25pm

Yeah, you can’t hold things back forever. If you are ready to update, just edit /etc/pacman.conf and remove everything from the ignorepkg line.

EDIT: Am I reading that right or are you saying you just updated to gnome 40 and now you are having issues?

Evo · July 27, 2021, 9:28pm

Oh, I have. That section looks like this now and the update earlier seemed fine:

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
IgnorePkg   = 
#gnome-desktop gcr evolution-data-server gnome-tweaks gsettings-desktop-schemas libgdm libgweather
IgnoreGroup = 
#gnome

are you saying you just updated to gnome 40 and now you are having issues?

Yes. I’ll do some digging and see if I can figure it out on my own and I’ll open a new issue if I end up lost. Thank you again. <3

Edit: just in case someone else ends up here because they’re unable to interact with Gnome 40 after logging in. Disabling all extensions did the trick:

gsettings set org.gnome.shell disable-user-extensions true

…and yes, you will regret having to deal with setting up extensions afterwards.

system · July 29, 2021, 9:29pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.