Boot in emergency mode, unresponsive

[emilev]

@TriMoon

@emilev

UUID=490D-66EF /boot/efi

You don’t have any partition with that UUID…

I think I do, blkid (listed above) shows:

/dev/nvme1n1p1: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="490D-66EF" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f004ec93-5084-6f4c-a9a0-69d9298506fc"

@TriMoon

@emilev

nvme1n1                                            
|-nvme1n1p1                          299.1M     0% /boot/efi
|-nvme1n1p2                          113.8G    82% /
`-nvme1n1p3                                        

Please don’t cut-out any info from program outputs, the provided info as-is has now become useless, because it doesn’t show critical info…

I don’t think I did, I think you are referring to the lsblk --all --fs output, that was a copy/paste without edit afaik.

@TriMoon

@emilev

Failed to find module 'vboxdrv'

And the like: Are you booting from within a virtual machine

No, I do remember trying to load my windows drive/partition as a virtual machine under manjaro (trying to prevent I had to reboot into windows when I had to use windows for a bit), which somewhat worked at some point, but was some time ago now, don’t remember too much about that. Not sure, but maybe it has to do with that?

@TriMoon

@emilev

[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC misobasedir=manjaro misolabel=MANJARO_GNOME_2204 quiet systemd.show_status=1 splash driver=nonfree nouveau.modeset=0 i915.modeset=1 radeon.modeset=1

This shows you are showing logs from the Live-ISO session, which is not really helpful except to see some hardware and driver errors.

Ok, thanks. So the dmsg output is not helpful like that. I might try some suggestions from [HowTo] Reach a minimal system .