[SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

Halikular · 2018-11-05 01:48:05

I'm on the very last step to finish the installation of Arch Linux, that is installing a boot loader. I've settled on systemd-boot and followed the official Arch Wiki systemd-boot installation guide: https://wiki.archlinux.org/index.php/Systemd-boot

I followed the steps rigorously installing the package, and setting it up. When doing my own research on the internet I found that it may have something to do with the PARTUUID, and that you should use either the partition LABEL or UUID. As said I did follow the guide as it suggested that the root partition can be identified with either its LABEL or PARTUUID. Now, I looked at a video tutorial on the same subject where their systemd-boot configuration file had the line:

options root=UUID=<string of characters> rw

As I've been instructed to follow the Arch Wiki, so I did. Therefore mine looked like this:

options root=PARTUUID=153e6e69-8579-2c43-bb42-cb9ee7cd95db rw

So I'm now asking you what is the correct way to launch the root partition or if something else is causing the system boot failure, the correct procedure to make the boot successful.

I've no idea where to go from here, when trying to boot I get a couple of messages printed on the screen and then lands me in a shell called rootfs. This is all the text it prints out:

:: running early hook [udev]
starting version 239
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/disk/by-partuuid/153e6e69-8579-2c43-bb42-cb9ee7cd95db ...
ERROR: device 'PARTUUID=153e6e69-8579-2c43-bb42-cb9ee7cd95db' not found. Skipping fsck.
:: mounting 'PARTUUID=153e6e69-8579-2c43-bb42-cb9ee7cd95db' on real root
mount: /new-root: can't find PARTUUID=153e6e69-8579-2c43-bb42-cb9ee7cd95db.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#

Last edited by Halikular (2018-11-12 15:37:10)

jasonwryan · 2018-11-05 01:57:58

Please paste the output of `blkid` from the chroot.

Halikular · 2018-11-05 01:59:45

How do I do that? When in this rootfs shell it's hard to do anything. What is the exact steps I've to do to first get out of rootfs and secondly chroot into the system.

Last edited by Halikular (2018-11-05 02:03:26)

Trilby · 2018-11-05 02:21:50

Halikular wrote:

What is the exact steps I've to do to first get out of rootfs and secondly chroot into the system.

The same exact steps you followed to do this when you installed arch linux - assuming, of course, that you actually installed arch following the installation guide, which according to this it sounds like you didnt. And if you didn't, you should not ask for help here.

Halikular · 2018-11-05 02:29:41

I've followed the official Arch Wiki Installation guide for Arch Linux in detail, making sure to understand every step I've made. So basically what I'm going to do is to boot into the installation media again, not making any new partitions as they already exists. Then mounting the filesystem, and finally Chrooting? Also regarding the old post, I've done a complete re installation of Arch Linux making sure to wipe all signatures and partitions before doing so.

Last edited by Halikular (2018-11-05 02:31:48)

Trilby · 2018-11-05 03:23:20

Halikular wrote:

So basically what I'm going to do is to boot into the installation media again, not making any new partitions as they already exists. Then mounting the filesystem, and finally Chrooting?

Yes.

Halikular · 2018-11-05 08:22:24

jasonwryan wrote:

Please paste the output of `blkid` from the chroot.

This output of "blkid" http://ix.io/1r0L

seth · 2018-11-05 08:57:06

Can you boot the failsafe initramfs?

Halikular · 2018-11-11 17:51:17

The problem is that I do not know how to do that, could you please elaborate on the steps I have to take to do that? Can't find online.

jasonwryan · 2018-11-11 17:59:12

From the UEFI Menu, choose the Fallback Image to boot from.

Halikular · 2018-11-11 18:02:27

Also I tried replacing PARTUUID with UUID and then systemd-boot could boot me into the Arch system. However it prints out some errors and prompts me to press ctrl + d to proceed to the system. I think I'll have to have you judge what is most important in this case and what should be focused on troubleshooting.

Halikular · 2018-11-11 18:03:00

jasonwryan wrote:

From the UEFI Menu, choose the Fallback Image to boot from.

Alright, I'll try that.

Trilby · 2018-11-11 18:05:25

Halikular wrote:

However it prints out some errors ... I think I'll have to have you judge what is most important ...

We can't possibly do that without actual information: "some errors" is meaningless.

Halikular · 2018-11-11 23:55:17

Okay so one thing leads to the other. Now I've been trying to troubleshoot internet connectivity issues following the "Network configuration" article without getting the issue resolved. So for the lack of internet connectivity I opted to boot into the installation media and run the command: "journalctl -xb" to view the report, which was what the system told me to do after the boot of the actual Arch system. I hope this will give us some new leads. This is the output of "journalctl -xb": http://ix.io/1rBl

Last edited by Halikular (2018-11-11 23:56:08)

jasonwryan · 2018-11-12 00:08:38

That's the journal for the live medium, I don't see how that is going to help.

loqs · 2018-11-12 00:10:26

See jasonwryan's request in post #2 now you can boot from the live media and post output.

Halikular · 2018-11-12 01:56:04

Okay then, I hoped that I would never have to do this, but for the convenience sake. I know you don't want it but I'm empty handed in these regards. I'm going to have to post pictures taken by my smartphone of of the monitor. This is the result (I know it looks terrible):

https://transfer.sh/jYKNE/outputCombined.pdf

Last edited by Halikular (2018-11-12 01:56:47)

Halikular · 2018-11-12 01:58:25

loqs wrote:

See jasonwryan's request in post #2 now you can boot from the live media and post output.

What am I supposed to post output of?

loqs · 2018-11-12 01:59:19

Halikular wrote:

loqs wrote:
See jasonwryan's request in post #2 now you can boot from the live media and post output.
What am I supposed to post output of?

jasonwryan wrote:

Please paste the output of `blkid` from the chroot.

Halikular · 2018-11-12 02:11:12

Okay I'll do it again for good measure. I've added a label for the root partition as it was tedious to work with the UUID. http://ix.io/1rBC

Last edited by Halikular (2018-11-12 02:11:28)

loqs · 2018-11-12 02:21:15

The PARTUUID matches so perhaps the NVME device is not being detected. In the recue shell does the output of `ls /dev/` contain any entries starting nvme?

Halikular · 2018-11-12 02:30:53

Yes it does. I can show you the single shot of what the rescue shell prints out: https://imgur.com/V2F3rnX

jasonwryan · 2018-11-12 03:11:13

So, it is /home that is failing. Paste your fstab.

loqs · 2018-11-12 03:42:14

@jasonwryan looking at the blkid output for what I presume is home

/dev/nvme0n1p7: PARTUUID="daddf4c1-8b17-594f-834a-8c3712817ff8"

The lack of UUID and TYPE entries make me wonder if the partition is unformatted.

Last edited by loqs (2018-11-12 03:42:45)

jasonwryan · 2018-11-12 04:48:16

Wouldn't the fsck fail if it was unformatted? Or is it failing because it can't mount it to run fsck?

In any event, the system is bootable...

Arch Linux

#1 2018-11-05 01:48:05

[SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#2 2018-11-05 01:57:58

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#3 2018-11-05 01:59:45

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#4 2018-11-05 02:21:50

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#5 2018-11-05 02:29:41

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#6 2018-11-05 03:23:20

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#7 2018-11-05 08:22:24

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#8 2018-11-05 08:57:06

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#9 2018-11-11 17:51:17

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#10 2018-11-11 17:59:12

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#11 2018-11-11 18:02:27

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#12 2018-11-11 18:03:00

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#13 2018-11-11 18:05:25

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#14 2018-11-11 23:55:17

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#15 2018-11-12 00:08:38

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#16 2018-11-12 00:10:26

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#17 2018-11-12 01:56:04

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#18 2018-11-12 01:58:25

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#19 2018-11-12 01:59:19

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#20 2018-11-12 02:11:12

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#21 2018-11-12 02:21:15

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#22 2018-11-12 02:30:53

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#23 2018-11-12 03:11:13

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#24 2018-11-12 03:42:14

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

#25 2018-11-12 04:48:16

Re: [SOLVED] ERROR: device 'PARTUUID=<string of characters>' not found.

Board footer