You are not logged in.

#1 2026-10-07 15:58:33

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

"Failed to mount the real root device" after -Syu

I made a full system update today and after the update I can no longer boot into my system. After grub I directly go into emergency shell rootfs, with the following output:

 ERROR: device'UUID=ccb76741-Obb4-46f1-a04c-63c2c?f a2996' not found. Skipping fsck,
MDunt: /susroot: can't find UUID=ccb76741-Obb4-46f1-a84c-63c2c?f a2996.
ERROR:Failed to mount'UUID=ccb76741-Obb4-46f 1-a84c-63c2c?f a2996' on real root
You are now being dropped into an emergency shel1.
sh: can't access tty: Job control turned off 

As I dont have much experience, I dont know what else to post, this is my work laptop and I need to get it back immediately

Offline

#2 2026-10-07 19:04:01

jonno2002
Member
Registered: 2016-11-21
Posts: 913

Re: "Failed to mount the real root device" after -Syu

the error is saying that it cant find your root partition to mount to continue booting, you need to fix that..
from the emergency shell you should be able to run "blkid" and get the correct UUID for your root partition, write that down then reboot and press "E" at the grub menu to edit the boot entry, find the line similar to:

linux	/boot/vmlinuz-linux root=UUID=ccb76741-Obb4-46f1-a04c-63c2c?f rw  audit=0 loglevel=3

and change the UUID to match the one youve written down, then boot the system and fix the issue by reconfiguring grub and make sure your all your partitions are mounted correctly so this doesnt happen again.
post back here if you get stuck with info so we can help

Offline

#3 2026-10-07 19:26:32

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

I made a full system update today and after the update I can no longer boot into my system

Any chance the drive is encrypted and fails to decrypt before you get that error?
See eg. https://bbs.archlinux.org/viewtopic.php … 5#p2311445

MDunt: /susroot: can't

Avoid manually transcribing stuff, rather link a screenshot.
If stuff flies by too fast to see: your phone has a camera that can read faster than you. Use a tripod, makeshift one out of two books if need be ( -\_ )

Online

#4 2026-10-07 20:58:08

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

The UUID in "blkid" output was indeed diffent and putting that into the grub entry actually let me into desktop. But after running "sudo grub-mkconfig -o /boot/grub/grub.cfg" and "sudo mkinitcpio -P" I end up in same situation again, I checked into the grub.cfg file and it still contains the old UUID


Just to be clear, yes, the partition is encrypted.

Offline

#5 2026-10-07 21:01:33

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

into the grub.cfg file and it still contains the old UUID

lsblk -f
cat /etc/fstab
lsmod | grep vfat

Apparently not the TPM situation, though.

Online

#6 2026-10-07 21:19:33

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

outputs of;

lsblk -f:

NAME        FSTYPE      FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
zram0       swap        1     zram0 785c2fa9-3233-4c46-a649-9ceb4a6c749e                [SWAP]
nvme0n1                                                                                 
├─nvme0n1p1 vfat        FAT32       F918-5FDE                               2,4G    39% /boot
└─nvme0n1p2 crypto_LUKS 2           a9b0c3e0-b1de-4a03-83e1-0d6fd53947dd                
  └─root    btrfs                   ccb76741-0bb4-46f1-a84c-63c2c7fa2996  589,9G    38% /home
                                                                                        /var/log
                                                                                        /var/cache/pacman/pkg
                                                                                        / 

cat /etc/fstab:

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/root
UUID=ccb76741-0bb4-46f1-a84c-63c2c7fa2996	/         	btrfs     	rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvol=/@	0 0

# /dev/mapper/root
UUID=ccb76741-0bb4-46f1-a84c-63c2c7fa2996	/home     	btrfs     	rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvol=/@home	0 0

# /dev/mapper/root
UUID=ccb76741-0bb4-46f1-a84c-63c2c7fa2996	/var/cache/pacman/pkg	btrfs     	rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvol=/@pkg	0 0

# /dev/mapper/root
UUID=ccb76741-0bb4-46f1-a84c-63c2c7fa2996	/var/log  	btrfs     	rw,relatime,compress=zstd:3,ssd,space_cache=v2,subvol=/@log	0 0

# /dev/nvme0n1p1
UUID=F918-5FDE      	/boot     	vfat      	rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro0 2 

lsmod | grep vfat:

 vfat                   28672  1
fat                   118784  1 vfat 

Offline

#7 2026-10-07 21:28:43

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

It's not a missing vfat module and all partitions/subvolumes mount
I assume 'UUID=ccb76741-Obb4-46f1-a04c-63c2c?f a2996' is the result of some failing OCR or otherwise a transcription error and the actual error says indeed "UUID=ccb76741-0bb4-46f1-a84c-63c2c7fa2996"?
Otherwise what does /boot/grub/grub.cfg actually look like?

But if it does (ie. the kernel complains about the correct UUID missing), what value did you actually enter instead?
Does it help to simply delay the boot (by waiting some seconds in grub)

Online

#8 2026-10-07 21:34:47

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

I entered the value of nvme0n1p2 that goes "a9b0c3..." and not the /root part. I am guessing the "ccb7..." is not old but broken, and that is what grub.cfg still contains

Offline

#9 2026-10-07 21:39:27

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

a9b0c3e0-b1de-4a03-83e1-0d6fd53947dd is the LUKS container, you cannot boot that (but it's gonna be part of the commandline)
nb. there're syntatctical differences between the systemd and busybox encrypt hooks:
https://wiki.archlinux.org/title/Dm-cry … -generator
https://wiki.archlinux.org/title/Dm-cry … crypt_hook

seth wrote:

what does /boot/grub/grub.cfg actually look like?

Online

#10 2026-10-07 21:46:07

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

full file here:

 #
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi

if [ "${env_block}" ] ; then
  set env_block="(${root})${env_block}"
  export env_block
  load_env -f "${env_block}"
fi

if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   if [ "${env_block}" ] ; then
     save_env -f "${env_block}" next_entry
   else
     save_env next_entry
   fi
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    if [ "${env_block}" ] ; then
      save_env -f "${env_block}" saved_entry
    else
      save_env saved_entry
    fi

  fi
}

function load_video {
  if [ x$grub_platform = xefi ]; then
    insmod efi_gop
  elif [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if loadfont unicode ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=tr_TR
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-ccb76741-0bb4-46f1-a84c-63c2c7fa2996' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt
	insmod fat
	search --no-floppy --fs-uuid --set=root F918-5FDE
	echo	'Linux linux-zen yükleniyor ...'
	linux	/vmlinuz-linux-zen root=UUID=ccb76741-0bb4-46f1-a84c-63c2c7fa2996 rw rootflags=subvol=@  loglevel=3 quiet nvidia-drm.modeset=1 nvidia_drm.fbdev=1
	echo	'Başlangıç ramdiski yükleniyor ...'
	initrd	/amd-ucode.img /initramfs-linux-zen.img
}
submenu 'Arch Linux için gelişmiş seçenekler' $menuentry_id_option 'gnulinux-advanced-ccb76741-0bb4-46f1-a84c-63c2c7fa2996' {
	menuentry 'Arch Linux, with Linux linux-zen' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-zen-advanced-ccb76741-0bb4-46f1-a84c-63c2c7fa2996' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		search --no-floppy --fs-uuid --set=root F918-5FDE
		echo	'Linux linux-zen yükleniyor ...'
		linux	/vmlinuz-linux-zen root=UUID=ccb76741-0bb4-46f1-a84c-63c2c7fa2996 rw rootflags=subvol=@  loglevel=3 quiet nvidia-drm.modeset=1 nvidia_drm.fbdev=1
		echo	'Başlangıç ramdiski yükleniyor ...'
		initrd	/amd-ucode.img /initramfs-linux-zen.img
	}
	menuentry 'Arch Linux, with Linux linux-lts' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-lts-advanced-ccb76741-0bb4-46f1-a84c-63c2c7fa2996' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		search --no-floppy --fs-uuid --set=root F918-5FDE
		echo	'Linux linux-lts yükleniyor ...'
		linux	/vmlinuz-linux-lts root=UUID=ccb76741-0bb4-46f1-a84c-63c2c7fa2996 rw rootflags=subvol=@  loglevel=3 quiet nvidia-drm.modeset=1 nvidia_drm.fbdev=1
		echo	'Başlangıç ramdiski yükleniyor ...'
		initrd	/amd-ucode.img /initramfs-linux-lts.img
	}
	menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-ccb76741-0bb4-46f1-a84c-63c2c7fa2996' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt
		insmod fat
		search --no-floppy --fs-uuid --set=root F918-5FDE
		echo	'Linux linux yükleniyor ...'
		linux	/vmlinuz-linux root=UUID=ccb76741-0bb4-46f1-a84c-63c2c7fa2996 rw rootflags=subvol=@  loglevel=3 quiet nvidia-drm.modeset=1 nvidia_drm.fbdev=1
		echo	'Başlangıç ramdiski yükleniyor ...'
		initrd	/amd-ucode.img /initramfs-linux.img
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/15_uki ###
if [ "$grub_platform" = "efi" ]; then
  uki
fi
### END /etc/grub.d/15_uki ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/25_bli ###
if [ "$grub_platform" = "efi" ]; then
  insmod bli
fi
### END /etc/grub.d/25_bli ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
if [ "$grub_platform" = "efi" ]; then
	fwsetup --is-supported
	if [ "$?" = 0 ]; then
		menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
			fwsetup
		}
	fi
fi
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/31_efi_bootnext ###
if [ "$grub_platform" = "efi" ]; then
  menuentry 'GRUB (EFI BootNext)' --class grub --class os $menuentry_id_option 'efi-bootnext-0000' {
    if bootnext 0000; then
      
      reboot
    fi
  }
fi
if [ "$grub_platform" = "efi" ]; then
  menuentry 'HDD0: 24144992C261-Micron_3500_MTFDKBA1T0TGD-1BK15ABYY (EFI BootNext)' --class hdd0_ --class os $menuentry_id_option 'efi-bootnext-0001' {
    if bootnext 0001; then
      
      reboot
    fi
  }
fi
if [ "$grub_platform" = "efi" ]; then
  menuentry 'EFI USB Device (EFI BootNext)' --class efi --class os $menuentry_id_option 'efi-bootnext-2001' {
    if bootnext 2001; then
      
      reboot
    fi
  }
fi
if [ "$grub_platform" = "efi" ]; then
  menuentry 'EFI DVD/CDROM (EFI BootNext)' --class efi --class os $menuentry_id_option 'efi-bootnext-2002' {
    if bootnext 2002; then
      
      reboot
    fi
  }
fi
if [ "$grub_platform" = "efi" ]; then
  menuentry 'EFI Network (EFI BootNext)' --class efi --class os $menuentry_id_option 'efi-bootnext-2003' {
    if bootnext 2003; then
      
      reboot
    fi
  }
fi
### END /etc/grub.d/31_efi_bootnext ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###

### BEGIN /etc/grub.d/41_snapshots-btrfs ###
if [ ! -e "${prefix}/grub-btrfs.cfg" ]; then
echo ""
else
submenu 'Arch Linux snapshots' {
    configfile "${prefix}/grub-btrfs.cfg"
}
fi
### END /etc/grub.d/41_snapshots-btrfs ###

Offline

#11 2026-10-07 22:02:01

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

So nothing's decrypted there - does your crypttab look correct? Is it in the initramfs? Resp. how did you actually configure the decryption?
Are you asked for a password?
Are  you sure the initramfs gets updated and you're not booting a UKI (seeing the module from archinstall listed)?

Online

#12 2026-10-07 23:34:02

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

cat /etc/crypttab output:

 # Configuration for encrypted block devices.
# See crypttab(5) for details.

# NOTE: Do not list your root (/) partition here, it must be set up
#       beforehand by the initramfs (/etc/mkinitcpio.conf).

# <name>       <device>                                     <password>              <options>
# home         UUID=b8ad5c18-f445-495d-9095-c9ec4f9d2f37    /etc/mypassword1
# data1        /dev/sda3                                    /etc/mypassword2
# data2        /dev/sda5                                    /etc/cryptfs.key
# swap         /dev/sdx4                                    /dev/urandom            swap,cipher=aes-cbc-essiv:sha256,size=256
# vol          /dev/sdb7                                    none 

/etc/mkinitcpio.conf hooks:

 HOOKS=(base udev autodetect microcode modconf kms keyboard keymap consolefont block encrypt filesystems fsck) 

how did I configure decryption? idk what to say or where to look, whatever archinstall did when I set disk encryption there and I didnt touch anything else.
yes I used to get asked for password, but after whatever happened I could not reach password prompt

Are  you sure the initramfs gets updated and you're not booting a UKI (seeing the module from archinstall listed)?

I also dont know where to look, to not come empty handed I asked AI and it told me to send those:

cat /etc/mkinitcpio.d/linux-zen.preset:

 linux-lts.preset  linux.preset      linux-zen.preset  
[root@zplarch zplenox]# cat /etc/mkinitcpio.d/linux
linux-lts.preset  linux.preset      linux-zen.preset  
[root@zplarch zplenox]# cat /etc/mkinitcpio.d/linux-zen.preset 
# mkinitcpio preset file for the 'linux-zen' package

#ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-linux-zen"
#ALL_kerneldest="/boot/vmlinuz-linux-zen"

PRESETS=('default')
#PRESETS=('default' 'fallback')

#default_config="/etc/mkinitcpio.conf"
default_image="/boot/initramfs-linux-zen.img"
default_uki="/boot/EFI/Linux/arch-linux-zen.efi"
default_options="--splash /usr/share/systemd/bootctl/splash-arch.bmp"

#fallback_config="/etc/mkinitcpio.conf"
#fallback_image="/boot/initramfs-linux-zen-fallback.img"
fallback_uki="/boot/EFI/Linux/arch-linux-zen-fallback.efi"
#fallback_options="-S autodetect"

ls -lh /boot/EFI/Linux:

  toplam 795M
-rwx------ 1 root root 266M Eyl 22 16:13 arch-linux.efi
-rwx------ 1 root root 263M Eyl 22 16:13 arch-linux-lts.efi
-rwx------ 1 root root 268M Eyl 22 16:13 arch-linux-zen.efi

Offline

#13 2026-10-08 07:39:53

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

whatever archinstall did when I set disk encryption

roll
So crypttab is virtually empty and you're using the busybox hooks and you're *maybe* booting a UKI, but those have not been updated since September 22nd

https://wiki.archlinux.org/title/Unifie … mkinitcpio

head -n1000 /etc/kernel/* /etc/cmdline.d/*
mkinitcpio -P # notably does this yell any errors at you?

Online

#14 2026-10-08 17:16:43

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

full output here :

 ==> /etc/kernel/cmdline <==
cryptdevice=PARTUUID=7ad8d625-8ae8-46c2-8276-7fb490ffb980:root root=/dev/mapper/root zswap.enabled=0 rootflags=subvol=@ rw rootfstype=btrfs

==> /etc/kernel/install.d <==
head: '/etc/kernel/install.d' okunurken hata: Bir dizin
head: '/etc/cmdline.d/*' okuma için açılamadı: Böyle bir dosya ya da dizin yok
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-lts -U /boot/EFI/Linux/arch-linux-lts.efi -g /boot/initramfs-linux-lts.img --splash /usr/share/systemd/bootctl/splash-arch.bmp
==> Starting build: '6.18.55-1-lts'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_6xxx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-lts.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Creating unified kernel image: '/boot/EFI/Linux/arch-linux-lts.efi'
==> Unified kernel image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -U /boot/EFI/Linux/arch-linux.efi -g /boot/initramfs-linux.img --splash /usr/share/systemd/bootctl/splash-arch.bmp
==> Starting build: '7.2.9-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_6xxx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Creating unified kernel image: '/boot/EFI/Linux/arch-linux.efi'
==> Unified kernel image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-zen.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux-zen -U /boot/EFI/Linux/arch-linux-zen.efi -g /boot/initramfs-linux-zen.img --splash /usr/share/systemd/bootctl/splash-arch.bmp
==> Starting build: '7.2.9-zen1-1-zen'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_6xxx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-zen.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Creating unified kernel image: '/boot/EFI/Linux/arch-linux-zen.efi'
==> Unified kernel image generation successful  

Offline

#15 2026-10-08 19:02:49

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

/etc/kernel/cmdline looks like it's doing what it's supposed to and the UKI generation succeeds - so most likely you're trying to boot the bogus entries for the kernel + initramfs; have you tried to just boot the UKI instead?

Online

#16 2026-10-08 19:54:26

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

seth wrote:

have you tried to just boot the UKI instead?

can you please explain how can I do that exactly?

also just in case, after replacing grub entry I get this error right before disk password prompt

  The syntax 'root-UUID=a9bBc3e0-b1de-4a03-83e1-Ba6f a53947da' where 'UUID-a9c3eg-bide-4a03-83e1-0d6f d53947dd' is' an encrupted volume is deprecated

Use cryptdevice-UUID-a9bBc3e0-b1de-4a03-83e1-0a6f a53947aa:root root=/dev/mapper/root' instead.  

Offline

#17 2026-10-08 20:24:25

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

By selecting it in the grub menu (it'll have a generic name, you could  relabel "Arch Linux, with Linux linux" to distinguish it if unsure)

Online

#18 2026-10-08 20:30:07

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

I tried every single option inside grub, half of them leads into same emergency shell, other just sends me into grub again

Offline

#19 2026-10-08 20:35:37

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

I'm not even sure why you've both variants, archinstall apparently deactivates the regular hook by default.
Remove or chmod -x /etc/grub.d/15_uki and fix the other entries.

Online

#20 2026-10-08 21:10:46

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

fix the other entries.

I know I am being kinda annoying but I dont know how should I proceed doing that and I didnt want to trust AI for this purpose. If you could explain to me I would be quite pleased

Offline

#21 Yesterday 07:03:18

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

With the texteditor of your choice and preferably sudoedit, though /etc/grub.d/10_linux is actually supposed to handle the encrypted device on grub-mkconfig
Like the concurrent seupt w/ 15_uki and the UKIs apparently not even booting but "just sends me into grub again" this is rather odd about your system.


pacman -Qs grub
pacman -Qikk grub

Did you try to mess around w/ eg. https://aur.archlinux.org/packages/grub-customizer or things like that?

Online

#22 Yesterday 14:21:40

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

Did you try to mess around w/ eg. https://aur.archlinux.org/packages/grub-customizer or things like that?

nope, this is my first time hearing that software.

UKIs apparently not even booting but "just sends me into grub again" this is rather odd about your system.

Maybe I should have told earlier but a bunch of entries that I have never seen appeared in the grub menu after the update, those between GRUB (EFI BootNext) and snapshots. and the "Arch Linux" trio was here since the installation and disappeared after "chmod -x /etc/grub.d/15_uki" but in my testing all of them just booted zen kernel and caused no problems in that time

 *Arch Linux
Arch Linux için gelişmiş seçenekler
Arch Linux
Arch Linux
Arch Linux
UEFI Firmware Settings
GRUB (EFI BootNext)
HDD0: 24144992C261-Micron_3500_MTFDKBA1T0TGD-1BK15ABYY (EFI BootNext)
EFI USB Device (EFI BootNext)
EFI DVD/CDROM (EFI BootNext)
EFI Network (EFI BootNext)
Arch Linux snapshots
 local/grub 2:2.16-1
    GNU GRand Unified Bootloader (2)
local/grub-btrfs 4.14-1
    Include btrfs snapshots in GRUB boot options
İsim                   : grub
Sürüm                  : 2:2.16-1
Açıklama               : GNU GRand Unified Bootloader (2)
Mimari                 : x86_64
URL                    : https://gnu-grub.freedesktop.org/
Lisanslar              : GPL-3.0-or-later
Gruplar                : Hiçbiri
Sağlananlar            : grub-common  grub-emu  grub-bios  grub-efi-x86_64
Bağımlılıkları         : device-mapper  gettext  sh  xz
Tercihli Bağımlılıklar : dosfstools: For grub-mkrescue FAT FS and EFI support
                         efibootmgr: For grub-install EFI support [kuruldu]
                         freetype2: For grub-mkfont usage [kuruldu]
                         fuse3: For grub-mount usage [kuruldu]
                         libisoburn: Provides xorriso for generating grub rescue iso using grub-mkrescue
                         libusb: For grub-emu USB support [kuruldu]
                         lzop: For grub-mkrescue LZO support
                         mtools: For grub-mkrescue FAT FS support
                         os-prober: To detect other OSes when generating grub.cfg in BIOS systems
                         sdl: For grub-emu SDL support
İhtiyaç Duyulanlar     : grub-btrfs
İsteğe Bağlı           : Hiçbiri
Çakışıyor              : grub-common  grub-emu  grub-legacy  grub-bios  grub-efi-x86_64
Değiştirilenler        : grub-common  grub-emu  grub-bios  grub-efi-x86_64
Kurulum Boyutu         : 43,16 MiB
Paketçi                : Christian Hesse <eworm@archlinux.org>
İnşa Tarihi            : Sal 22 Eyl 2026 23:14:11
Yükleme Tarihi         : Çrş 07 Eki 2026 15:02:32
Yükleme Sebebi         : Doğrudan kurulmuş
Kurulum Betiği         : Evet
Doğrulayan             : İmza

yedekleme dosyası: grub: /etc/default/grub (Değiştirme zamanı uyuşmazlığı)
yedekleme dosyası: grub: /etc/default/grub (Boyut uyuşmazlığı)
yedekleme dosyası: grub: /etc/default/grub (SHA256 doğrulama uyuşmazlığı)
grub: 1245 toplam dosya, 0 değiştirilmiş dosya 

Offline

#23 Yesterday 15:09:43

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,218

Re: "Failed to mount the real root device" after -Syu

Those should come from the /etc/grub.d/31_efi_bootnext hook
Which of the entries "just sends me into grub again"?

Did you manage to fix the normal entries and do they boot now?

Online

#24 Yesterday 18:38:38

Acor
Member
Registered: 2026-10-02
Posts: 10

Re: "Failed to mount the real root device" after -Syu

Can the missing space in "errors=remount-ro0 2" after fvat mount options cause a problem?

UUID=F918-5FDE          /boot         vfat          rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro0 2

Offline

#25 Yesterday 19:13:00

ZplenoX
Member
Registered: 2024-12-13
Posts: 17

Re: "Failed to mount the real root device" after -Syu

Which of the entries "just sends me into grub again"?

those between GRUB (EFI BootNext) and snapshots.

Did you manage to fix the normal entries and do they boot now?

I have absolutely no idea how can I do that, as I mentioned before

Offline

Board footer

Powered by FluxBB