Cannot boot into system: mount: /new_root: can't find UUID

[LukeS03]

Hello everybody,

The day before yesterday, I decided to update my system before going to sleep. All seemed well. When I woke up and booted up my computer yesterday however, I found myself faced with this error message:

mount: /new_root: can't find UUID=07e8a8dc-c48d-429d-8973-ce03202d38c1.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#

I have chrooted in using manjaro-chroot -a using a live USB, and I have followed the following steps in an attempt to rectify this issue:

• I have followed the steps given in this wiki article https://wiki.manjaro.org/index.php/GRUB/Restore_the_GRUB_Bootloader
• I have installed downgrade, and downgraded mkinitcpio based on another forum post I saw here. However, it did not fix my system so I have reverted the downgrade.

Running lsblk -o PATH,PTTYPE,PARTTYPE,FSTYPE,PARTTYPENAME outside of the chroot gives the following output:

PATH               PTTYPE PARTTYPE                             FSTYPE   PARTTYPENAME
/dev/loop0                                                     squashfs 
/dev/loop1                                                     squashfs 
/dev/loop2                                                     squashfs 
/dev/loop3                                                     squashfs 
/dev/sda           dos                                                  
/dev/sda1          dos    0x7                                  exfat    HPFS/NTFS/exFAT
/dev/sda2          dos    0xef                                 vfat     EFI (FAT-12/16/32)
/dev/mmcblk0       gpt                                                  
/dev/mmcblk0p1     gpt    c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat     EFI System
/dev/mmcblk0p2     gpt    0fc63daf-8483-4772-8e79-3d69d8477de4 ext4     Linux filesystem
/dev/mmcblk0boot0  gpt                                                  
/dev/mmcblk0boot1  gpt                                                  
/dev/mmcblk1       gpt                                                  
/dev/mmcblk1p1     gpt    0fc63daf-8483-4772-8e79-3d69d8477de4 btrfs    Linux filesystem
/dev/mapper/ventoy dos                                         iso9660  

Running fdisk -l gives me the following output:

Disk /dev/loop0: 138.02 MiB, 144719872 bytes, 282656 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 643.18 MiB, 674422784 bytes, 1317232 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1.66 GiB, 1787170816 bytes, 3490568 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 645.26 MiB, 676605952 bytes, 1321496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0: 58.24 GiB, 62537072640 bytes, 122142720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F70E741A-1BD1-D844-A128-8BD461402881

Device          Start       End   Sectors  Size Type
/dev/mmcblk0p1   4096    618495    614400  300M EFI System
/dev/mmcblk0p2 618496 122142194 121523699 57.9G Linux filesystem


Disk /dev/mmcblk1: 58.94 GiB, 63281561600 bytes, 123596800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 97E964DD-4F08-F64A-BA4A-E667783721D6

Device         Start       End   Sectors Size Type
/dev/mmcblk1p1  2048 119490559 119488512  57G Linux filesystem


Disk /dev/sda: 57.62 GiB, 61865984000 bytes, 120832000 sectors
Disk model: STORE N GO      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2418214d

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1  *         2048 120766463 120764416 57.6G  7 HPFS/NTFS/exFAT
/dev/sda2       120766464 120831999     65536   32M ef EFI (FAT-12/16/32)


Disk /dev/mapper/ventoy: 3.13 GiB, 3361880064 bytes, 6566172 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device                   Boot   Start     End Sectors  Size Id Type
/dev/mapper/ventoy-part1 *         64 6557979 6557916  3.1G  0 Empty
/dev/mapper/ventoy-part2      6557980 6566171    8192    4M ef EFI (FAT-12/16/32)

Here is the output from lsblk -f

NAME         FSTYPE   FSVER            LABEL             UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0        squashfs 4.0                                                                           0   100% /run/miso/sfs/livefs
loop1        squashfs 4.0                                                                           0   100% /run/miso/sfs/mhwdfs
loop2        squashfs 4.0                                                                           0   100% /run/miso/sfs/desktopfs
loop3        squashfs 4.0                                                                           0   100% /run/miso/sfs/rootfs
sda                                                                                                          
├─sda1       exfat    1.0              Ventoy            4DA3-6E6A                                           
│ └─ventoy   iso9660  Joliet Extension MANJARO_MATE_2137 2022-08-17-09-12-34-00                     0   100% /run/miso/bootmnt
└─sda2       vfat     FAT16            VTOYEFI           7CDB-00D9                                           
mmcblk0                                                                                                      
├─mmcblk0p1  vfat     FAT32            NO_LABEL          3FF8-C423                                           
└─mmcblk0p2  ext4     1.0                                07e8a8dc-c48d-429d-8973-ce03202d38c1                
mmcblk0boot0                                                                                                 
mmcblk0boot1                                                                                                 
mmcblk1                                                                                                      
└─mmcblk1p1  btrfs                     MicroSSD1         992c0196-a5a3-4371-babe-22aa5155fb6a   43.5G    20% /run/media/manjaro/MicroSSD1

My computer is a Lenovo Ideapad with an eMMC as it’s primary storage. I also have a microSD card slotted in. I must have made a typo which is why the microSD called “MicroSSD1” in the menu.

I have tried to give as much useful information as I could but I apologise if I have left anything out; I am a bit of a noob and this is my first time posting. Many thanks

Edit: I edited the original error message to include the problematic UUID rather than the placeholder “<>”. I had to copy it from a picture off my phone. I also clarified what “MicroSSD1” was.

[cscs]

cat /etc/fstab

[LukeS03]

Here is what it gives when I run it in manjaro-chroot:

[manjaro-mate /]# cat /etc/fstab
# /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=3FF8-C423                            /boot/efi      vfat    umask=0077 0 2
UUID=07e8a8dc-c48d-429d-8973-ce03202d38c1 /              ext4    defaults,noatime 0 1
/swapfile                                 swap           swap    defaults,noatime 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

[LukeS03]

I have no idea what is going on because it seems that the UUID in fstab and the UUID in lsblk are the same. However, I managed to boot into my OS by entering the following commands at the first screen.

mount /dev/mmcblk0p2 /new_root
exit

Very odd. And also very amusing considering that I have been poking around with a liveUSB all day.

[cscs]

@LukeS03

mount /dev/mmcblk0p2 /new_root

Does not match

@LukeS03

UUID=07e8a8dc-c48d-429d-8973-ce03202d38c1 /              ext4    defaults,noatime 0 1

… So … which way should it be really?
What should be ‘real root’ / and what should be /new_root ?

Your fstab doesnt have /new_root and lists that UUID as /

[brahma]

looks like this issue:

System not booting after update

Hello, I installed Manjaro a few weeks back, after using Debian based distros for years. It worked perfectly till I recently installed updates. After that boot fails with the messages in the screenshot. Since I reinstalled it twice. It always booted up fine at first, then I installed updates and afterwards it fails to boot. Link to screenshot: https:// ibb. co/NL5CLCG (Sorry, I could neither attach the picture directly nor enter the normal link) Any idea what the problem is? Thanks in adv…

downgrade mkinitcpio as outplined there and see if it helped…