Edit: managed to boot by reinstalling grub, reinstalling the kernel (latest) with Artix’ own basestrap script and then updating grub from a live USB. System saved. Now it won’t accept a new IP from my dhcp server but that’s tomorrow’s problem. Thank you all for your quick respones! 🥰

Artix Linux
Thinkpad T480
Symptoms appeared after a system upgrade

A1MIyZrtTV1qJcl.jpg

Error log:

[    0.801115] VFS: Cannot open root device "UUID=ed827e9a-47e4-490c-8a9a-0f0145925e0b" or unknown-block(0,0): error -6  
[    0.801117] Please append a correct "root=" boot option; here are the available partitions:  
[    0.801119] List of all bdev filesystems:  
[    0.801119]  ext3  
[    0.801120]  ext2  
[    0.801121]  ext4  
[    0.801122]  fuseblk  
[    0.801122]  btrfs  
[    0.801123] 
[    0.801124] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)  

Should I adjust something in fstab from a live USB or can I point to the root partition from GRUB’s CLI?

  • gnufuu@lemmy.ca
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    17 hours ago

    Booting a live USB and reinstalling GRUB as follows has saved my butt in the past. Obviously replace the /dev/sdXY paths with your own. Further adjustments might be needed depending on your system.

    # mount root partition:
    sudo mount /dev/sdXY2 /mnt
    # mount boot partition (if there is any)
    sudo mount /dev/sdXY3 /mnt/boot
    # mount efi partition (if there is any)
    sudo mount /dev/sdXY1 /mnt/boot/efi
    # mount other partitions:
    for dir in /dev /dev/pts /proc /sys /sys/firmware/efi/efivars /run; do sudo mount --bind $dir /mnt$dir; done  
    # chroot into mounted system:
    sudo chroot /mnt /bin/bash -i 
    # reinstall grub:
    grub-install 
    # rebuild grub.cfg:
    update-grub 
    # rebuild initramfs (not sure if necessary):
    update-initramfs -u
    # sync, exit chroot, reboot:
    sync
    exit
    sudo reboot
    
    • DickFiasco@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      13 hours ago

      This is also the basic starting point for fixing many boot problems; boot from live USB, mount system partitions, chroot into temporary environment. Most problems are fairly easy to fix if you can just get to a command line.