You are not logged in.

#1 2019-01-09 00:05:04

happyslowly
Member
Registered: 2017-08-28
Posts: 5

[SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Hi there,

After today's upgrade, the system suddenly cannot boot, the error message is: (sorry for the potato quality)
https://i.imgur.com/NF8ipBP.jpg


The root partition is /dev/sdb3, the UEFI parition is /dev/sdb1, I've verified the following aspects:

1. blkid

[root@archiso /]# blkid
/dev/sda1: UUID="2019-01-01-15-22-42-00" LABEL="ARCH_201901" TYPE="iso9660" PTUUID="0d7a8182" PTTYPE="dos" PARTUUID="0d7a8182-01"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="ARCHISO_EFI" LABEL="ARCHISO_EFI" UUID="59A5-857A" TYPE="vfat" PARTUUID="0d7a8182-02"
/dev/loop0: TYPE="squashfs"
/dev/sdb1: UUID="C0C0-54AB" TYPE="vfat" PARTUUID="f3254eb7-7ba2-4dc6-8807-f291ea6c1e53"
/dev/sdb2: UUID="715db2e5-4ac9-4aff-af76-e011f3e0c0f5" TYPE="swap" PARTUUID="b2944f37-4be3-481c-b747-ce4a84394e54"
/dev/sdb3: UUID="490addf6-6041-4d9a-b0c0-429bb067111c" TYPE="ext4" PARTUUID="31e01974-390e-4ba0-bbae-30181142ef6f"
/dev/sdc1: UUID="013c7a57-993c-43a6-b7e9-2d9938f98015" TYPE="ext4" PARTUUID="bdbc02ed-2b27-4fcf-8dc7-f5286c9b9a99"
/dev/sdd1: UUID="dbb6ddda-7898-4219-83db-27dad84aff6a" TYPE="ext4" PARTUUID="e99edf8b-d506-4465-9b2b-cd4d47b6517c"

2. systemd boot entry

[root@archiso entries]# cat arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options root=PARTUUID=31e01974-390e-4ba0-bbae-30181142ef6f rw

I also rerun

mkinitcpio -p linux

the mkinitcpio.conf looks like (removed all the comments):

MODULES=()
BINARIES=()
FILES=()
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)

Is there anything else I can check? I simply cannot understand how come it isn't able to find the partition...

Last edited by HalosGhost (2019-01-10 18:43:36)

Offline

#2 2019-01-09 02:05:01

Scimmia
Bug Wrangler
Registered: 2012-09-01
Posts: 7,226

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Does booting the fallback initramfs work?

Offline

#3 2019-01-09 02:41:24

brenix
Member
From: California
Registered: 2008-03-05
Posts: 184

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Having the same issue today after returning home and upgrading. Fallback doesn't seem to work.. Still digging into it

EDIT: downgrading systemd packages from 240 --> 239 seems to have fixed it for me.. Now wondering if there is a bug..

Last edited by brenix (2019-01-09 02:49:56)

Offline

#4 2019-01-09 02:55:02

happyslowly
Member
Registered: 2017-08-28
Posts: 5

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Add output for bootctl and efibootmgr

[root@archiso /]# bootctl status
System:
     Firmware: UEFI 2.40 (American Megatrends 5.09)
  Secure Boot: disabled
   Setup Mode: user

Current Boot Loader:
      Product: systemd-boot 239
     Features: ✗ Boot counting
               ✓ Menu timeout control
               ✗ One-shot menu timeout control
               ✓ Default entry control
               ✓ One-shot entry control
          ESP: n/a
         File: └─EFI/boot/loader.efi

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/f3254eb7-7ba2-4dc6-8807-f291ea6c1e53)
         File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 240)
         File: └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 240)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/f3254eb7-7ba2-4dc6-8807-f291ea6c1e53
         File: └─/EFI/systemd/systemd-bootx64.efi

Default Boot Loader Entry:
        title: Arch Linux
           id: arch
        linux: /vmlinuz-linux
       initrd: /intel-ucode.img /initramfs-linux.img
      options: root=PARTUUID=31e01974-390e-4ba0-bbae-30181142ef6f rw
[root@archiso /]# efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0003,0004,0008,0009,000A,000B
Boot0000* Linux Boot Manager	HD(1,GPT,f3254eb7-7ba2-4dc6-8807-f291ea6c1e53,0x800,0x200000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0003* UEFI: KingstonDataTraveler 2.01.00	HD(1,MBR,0xd7a8182,0xa4,0x20000)/File(EFI\boot\bootx64.efi)..BO
Boot0004* Diskette Drive	BBS(Floppy,Diskette Drive,0x0)..BO
Boot0008* USB Storage Device	BBS(USB,KingstonDataTraveler 2.01.00,0x0)..BO
Boot0009* CD/DVD/CD-RW Drive	BBS(CDROM,CD/DVD/CD-RW Drive,0x0)..BO
Boot000A* Onboard NIC	BBS(Network,Onboard NIC,0x0)..BO
Boot000B* Internal HDD	BBS(HD,Internal HDD,0x0)..BO

Would "ESP: N/A" in the "Current Boot Loader" cause the issue? Totally lost...

Offline

#5 2019-01-09 03:07:23

happyslowly
Member
Registered: 2017-08-28
Posts: 5

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

brenix wrote:

Having the same issue today after returning home and upgrading. Fallback doesn't seem to work.. Still digging into it

EDIT: downgrading systemd packages from 240 --> 239 seems to have fixed it for me.. Now wondering if there is a bug..

Yes! Thank you!. It looks like downgrade systemd did pass this issue. Now I'm running into other issues... still fight with it.

Offline

#6 2019-01-09 06:45:09

chr0mag
Member
From: Canada
Registered: 2017-02-02
Posts: 85

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Current Boot Loader:
      Product: systemd-boot 239

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/f3254eb7-7ba2-4dc6-8807-f291ea6c1e53)
         File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 240)
         File: └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 240)

There is a version mismatch between the current and available boot loader output. Did 'bootctl update' fail or generate errors when it was run after systemd was updated? It looks like it was executed, at least partially, since the v240 .efi files were copied to the ESP. I'd try reinstalling your boot loader.

Offline

#7 2019-01-09 06:58:47

rusty725
Member
Registered: 2014-02-16
Posts: 82

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

there's a bug for sure in systemd-240 had to downgrade 4 packages to make system run normal, these are the packages ( systemd-240.0-3  lib32-systemd-240.0-1  libsystemd-240.0-3  systemd-240.0-3 systemd-sysvcompat-240.0-3 ), someone needs to flag these packages until the issue is resolved.

Offline

#8 2019-01-09 11:00:51

harkor
Member
Registered: 2017-03-30
Posts: 7

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Same problem for me on a virtual machine on VMware.

Downgrade libsystemd working.

I don't have the problem on my main computer. It's weird.

Last edited by harkor (2019-01-09 11:01:31)

Offline

#9 2019-01-09 11:49:12

petecan
Member
Registered: 2013-05-02
Posts: 6

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Same issue here, downgrading to systemd-239 also worked. To apply the workaround, boot into an arch usb and:

mount <your arch partition> /mnt
arch-chroot /mnt
mount /boot
downgrade systemd lib32-systemd libsystemd systemd-sysvcompat

Offline

#10 2019-01-09 11:57:48

tompear
Member
Registered: 2013-10-23
Posts: 7

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

I can commit that bug exists on VMware.

Downgrade systemd and libsystemd to version 239 works.
No matter if i use /dev/sdaX / UUID in fstab or grub.cfg.

Last edited by tompear (2019-01-09 11:58:35)

Offline

#11 2019-01-09 15:30:28

Skitter
Member
Registered: 2013-09-28
Posts: 35

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

I confirm that the issue occurs in vmware-workstation 15.0.2-1. Downgrading systemd and libsystemd from 240 to 239.370-1 fixed it. You can find these packages here: https://ftp.gnome.org/mirror/archlinux/core/os/x86_64/

Offline

#12 2019-01-09 15:36:54

berny99
Member
From: Canary Islands (Spain)
Registered: 2010-10-05
Posts: 17

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Confirming the bug in systemd 240. No boot using legacy BIOS mode (no UEFI), only Arch Linux installed on pc.

Downgraded to 239 now booting again!

Greetings

Offline

#13 2019-01-09 15:58:59

irishwoody
Member
Registered: 2016-01-08
Posts: 4

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Similar issue - my / partition is on a lvm volume. After update to systemd 240  - it would not boot.  (hangs at key entry input)
downgraded to 239.370-1 - can enter key and boots fine now !

Offline

#14 2019-01-09 16:01:15

2ManyDogs
Forum Moderator
Registered: 2012-01-15
Posts: 2,572

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

I think that's enough "me too" posts now. If anyone wants to actually try to track down the problem, feel free to post.

Offline

#15 2019-01-09 16:14:38

dmartins
Member
Registered: 2006-09-23
Posts: 360

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

It looks like it could be related to upstream bug https://github.com/systemd/systemd/issues/11362
The related Arch ticket is https://bugs.archlinux.org/task/61324

Could someone check if their logs are similar to those in the bug report?
I wasn't able to replicate this so far on a fresh VM.

Offline

#16 2019-01-09 17:50:48

petecan
Member
Registered: 2013-05-02
Posts: 6

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

@dmartins My logs do not seem to contain these messages

Offline

#17 2019-01-09 18:34:06

happyslowly
Member
Registered: 2017-08-28
Posts: 5

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Thank you all! Downgrade systemd did fix the issue for me. Yet it is weird that I cannot reproduce the issue on another machine which is upgraded to systemd 240...

Offline

#18 2019-01-09 23:41:05

dmartins
Member
Registered: 2006-09-23
Posts: 360

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

After digging some more, this issue may be related to this systemd issue report: https://github.com/systemd/systemd/issues/11314
Arch has https://bugs.archlinux.org/task/61317 which appears to be similar.

Offline

#19 2019-01-10 17:31:50

dmartins
Member
Registered: 2006-09-23
Posts: 360

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

There are some systemd packages available to test: https://bugs.archlinux.org/task/61317#comment176209
I can't replicate this issue but have  installed these and my system still boots. If you try them and they solve your problem, please report back here (and to the bug tracker as well if you'd like).

Offline

#20 2019-01-10 18:44:21

HalosGhost
Forum Moderator
From: Twin Cities, MN
Registered: 2012-06-22
Posts: 1,772
Website

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

happyslowly,

Please go back and read the Code of Conduct (particularly the section regarding image size). I have edited your post to remove the inline rendering.

All the best,

-HG


"All errors are ᴘᴇʙᴋᴀᴄ errors—It's just a matter of narrowing down which keyboard and chair." -Trilby
\ldots

Online

#21 2019-01-10 20:18:05

jamsla
Member
Registered: 2019-01-10
Posts: 1

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

dmartins wrote:

There are some systemd packages available to test: https://bugs.archlinux.org/task/61317#comment176209

I just tried these, but for me they have the same problem.

Offline

#22 2019-01-10 20:26:41

winksaville
Member
Registered: 2015-09-21
Posts: 36

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

dmartins wrote:

There are some systemd packages available to test: https://bugs.archlinux.org/task/61317#comment176209
I can't replicate this issue but have  installed these and my system still boots. If you try them and they solve your problem, please report back here (and to the bug tracker as well if you'd like).

I attempted to upgrade to 240-156-gd26c904+:

$ sudo pacman -U [url]https://pkgbuild.com/~dreisner/packages/systemd-240.156-1-x86_64.pkg.tar.xz[/url] [url]https://pkgbuild.com/~dreisner/packages/libsystemd-240.156-1-x86_64.pkg.tar.xz[/url]
[sudo] password for wink: 
 systemd-240.156-1-x86_64                           4.5 MiB  3.35M/s 00:01 [#####################] 100%
 systemd-240.156-1-x86_64.sig                     310.0   B  0.00B/s 00:00 [#####################] 100%
 libsystemd-240.156-1-x86_64                      386.4 KiB  27.0M/s 00:00 [#####################] 100%
 libsystemd-240.156-1-x86_64.sig                  310.0   B  0.00B/s 00:00 [#####################] 100%
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (2) libsystemd-240.156-1  systemd-240.15

Total Installed Size:  22.46 MiB
Net Upgrade Size:       1.56 MiB

:: Proceed with installation? [Y/n] 
(2/2) checking keys in keyring                                             [#####################] 100%
(2/2) checking package integrity                                           [#####################] 100%
(2/2) loading package files                                                [#####################] 100%
(2/2) checking for file conflicts                                          [#####################] 100%
(2/2) checking available disk space                                        [#####################] 100%
:: Processing package changes...
(1/2) upgrading libsystemd                                                 [#####################] 100%
(2/2) upgrading systemd                                                    [#####################] 100%
:: Running post-transaction hooks...
( 1/10) Updating linux-custom initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-custom.preset: 'default'
  -> -k /boot/vmlinuz-linux-custom -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-custom.img
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux-custom'
==> Building image from preset: /etc/mkinitcpio.d/linux-custom.preset: 'fallback'
  -> -k /boot/vmlinuz-linux-custom -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-custom-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux-custom'
error: command failed to execute correctly
( 2/10) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.20.0-arch1-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.20.0-arch1-1-ARCH
  -> 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
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
( 3/10) Updating journal message catalog...
( 4/10) Reloading system manager configuration...
( 5/10) Updating udev hardware database...
( 6/10) Applying kernel sysctl settings...
( 7/10) Creating system user accounts...
( 8/10) Creating temporary files...
( 9/10) Reloading device manager configuration...
(10/10) Arming ConditionNeedsUpdate..

It failed as before with the output below and the emergency shell wouldn't accept input:

Starting version 240-156-qb26c904+
ERROR: device 'UUID=faa2047d-...' not found. Skipping fsck.
mount: /new_root: can't find UUID=faa2047d...
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#

Last edited by winksaville (2019-01-10 20:49:38)

Offline

#23 2019-01-10 20:31:04

2ManyDogs
Forum Moderator
Registered: 2012-01-15
Posts: 2,572

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Please edit your post and use [ code ] tags (not quote tags) when posting output.

https://wiki.archlinux.org/index.php/Co … s_and_code
https://bbs.archlinux.org/help.php#bbcode

Offline

#24 2019-01-10 20:43:22

dmartins
Member
Registered: 2006-09-23
Posts: 360

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

jamsla, winksaville,
Thanks for testing it, and sorry that it did not work for you. I'll update the bug tracker.

For now then, you could downgrade to systemd 239.
The packages can be found here if needed: https://ftp.gnome.org/mirror/archlinux/core/os/x86_64/

You'll want to downgrade any of these that you have installed: systemd, libsystemd, systemd-sysvcompat, systemd-resolvconf

Offline

#25 2019-01-11 00:00:38

wongsyrone
Member
Registered: 2015-03-01
Posts: 1

Re: [SOLVED]System boot issue (mount: /new_root: can't find PARTUUID)

Hi all,

I posted a ticket to describe the situation and how I solve it, you may check https://bugs.archlinux.org/task/61334

Offline

Board footer

Powered by FluxBB