EndeavourOS ARM Install missing UUID real root

ARM Installation
1

I have the Pinebook Pro & tried to get the EMMC working with EndeavourOS Neo. I flashed the image onto the EMMC via a USB adapter (pulled chip from laptop).

I have verified the Neo boots from SDcard.

Error presented:

:: running early hook [udev]
Starting systemd-udevd version 256.6-1-arch
:: running hook [udev]
:: Triggering uevents…
:: running hook [keymap]
:: loading keymap…done.
Waiting 10 seconds for device /dev/disk/by-uuid/1591aead-7880b-49c8-8c3b-18c7d9230cbd …
Waiting 10 seconds for device /dev/disk/by-uuid/1591aead-7880b-49c8-8c3b-18c7d9230cbd …
ERROR device UUID=1591aead-7880b-49c8-8c3b-18c7d9230cbd … not found. Skipping fsck.
:: mounting ‘1591aead-7880b-49c8-8c3b-18c7d9230cbd …’ on real root
mount: /new_root: can’t find 1591aead-7880b-49c8-8c3b-18c7d9230cbd … on real root
You are now being dropped into an emergency shell.
sh: can’t access tty: job control turned off
[rootfs ~]#

I’ve flashed the SPI with the 2023 Tow-boot which works perfectly, but I still can’t get the EOS to boot from EMMC - same error as above.

2

I’ll add the latest Manjaro (2023) does not boot from EMMC, but I’ve found PostMarketOS does. For the moment I am testing Kali, but really would love to get my Favorite EndeavourOS on this lightweight laptop.

3

I am confused here. EndeavourOS Neo is for x86_64 devices, not ARM devices like the Pinebook Pro.

Here is the image you should burn to the eMMC

Flash the image to the eMMC then install in the pinebook pro. It should boot up and then auto run the script to enter personal data and choose a Desktop Environment.

Pudge

1 Like
4

Thanks for the help.

I used this one and thought it was also called Neo. Sorry about that.
I have this version on the EMMC and sdcard.
[https://github.com/endeavouros-arm/images/releases/download/pinebook-pro-image/enosLinuxARM-pbp-latest.img.xz]

I added a delay of 5 & ‘single’ to the initramfs fallback in /boot/extlinux/extlinux.conf. This allowed me see the following:

mmc2 card stuck being busy!

I searched deeper on the net and located a similar message here on the armbian irc log:

Ordering another EMMC to really know if that is the issue.

5

No worries.

I have never installed EnOS ARM to the eMMC on pinebook pro. I just never decided to tear apart my pinebook pro, so it still has the original eMMC with Manjaro on it.

I do have an extra eMMC and USB adapter. After dinner tonight, I will do a test install of EnOS to eMMC and see what I come up with.

Pudge

6

@Pudge forgive jump in

i have spare eMMc , so i try for you . it work ok ( wifi hit miss ) that on go problem so no thing new .

i use usb reader + boot it from reader + inside device . all work ok.

Screenshot_2024-10-19_02-28-31
Screenshot_2024-10-19_02-28-311920×1080 248 KB

eos-eMMC
eos-eMMC1920×1431 149 KB

think i save you try. ( you busy enough )

2 Likes
7

New thoughts help. I tried booting the same EMMC from USB and it worked fine. Wow.
No clue why it won’t boot while installed in the Pinebook Pro.

1 Like
8

I did an install on eMMC the way I planned and hoped it would work.

  1. On my x86_64 daily driver I downloaded the Pinebook Pro image from github.
  2. Using gnome-disk-utility I flashed the PBP image to the 64 GB eMMC
  3. Opened up the back of the Pinebook Pro and removed the Manjaro eMMC and replaced it with
    the EOS eMMC
  4. I put the PBP back together and booted up with no uSD card, strictly the eMMC only
  5. When I pressed the power button, the power led turned red instead of green. Then the power
    led turned green. I saw some activity on the screen, then reddish colored garbage, then
    “initiating please wait”

Answered all the questions and chose Plasma. The install finished and rebooted into a working Plasma desktop.

desktop
desktop1920×1080 79.4 KB

fastfetch
fastfetch1303×862 165 KB

Here is what I think is going on. When the Pinebook Pro image gets downloaded from github then flashed to a storage device, then the partitions on that storage device are the same as what was on the image. For the October 6, 2024 version the UUIDS are as follows.

[don@PBP-emmc ~]$ lsblk -f
NAME         FSTYPE FSVER LABEL     UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
mmcblk2                                                                                 
├─mmcblk2p1  vfat   FAT16 BOOT_ENOS FB2D-D935                             312.5M    19% /boot
└─mmcblk2p2  ext4   1.0   ROOT_ENOS 1591aead-780b-49c8-8c3b-18c7d9230cbd   47.1G    13% /
[don@PBP-emmc ~]$

So if you downloaded theOctober 6, 2024 version PBP image and flashed it to say a uSD, it would have the above partition UUIDs.

Then if you flashed the same version image to a eMMC, it also would have the exact same partition UUIDS.

If you had the above uSD and eMMC connected at the same time, one would have conflicting UUIDs. Hence all the /dev/disk/by-uuid/ errors.

Next I will poweroff and connect a uSD which I think has the same UUIDs from October 6, 2024 and see what happens.

Be back shortly with results.

Pudge

1 Like
9

I now have both the uSD and eMMC connected.
It complained but booted into the uSD card.

don@PBP ~]$ lsblk -f
NAME         FSTYPE FSVER LABEL     UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
mmcblk2                                                                                 
├─mmcblk2p1  vfat   FAT16 BOOT_ENOS FB2D-D935                                           
└─mmcblk2p2  ext4   1.0   ROOT_ENOS 1591aead-780b-49c8-8c3b-18c7d9230cbd                
mmcblk2boot0                                                                            
mmcblk2boot1                                                                            
mmcblk1                                                                                 
├─mmcblk1p1  vfat   FAT16 BOOT_ENOS FB2D-D935                             312.5M    19% /boot
└─mmcblk1p2  ext4   1.0   ROOT_ENOS 1591aead-780b-49c8-8c3b-18c7d9230cbd  104.4G     7% /
[don@PBP ~]$

mmcblk1 is the uSD and mmcblk2 is the eMMC. Notice that /boot and / are mounted to mmcblk1 which is the uSD. Notice the hostname for the lsblk -f in the above post and this post
don@BPB-eemc verses don@BPB

The only thing out of the ordinary is since I installed the EnOS eMMC in the PBP, I keep getting at boot up, a towboot icon followed by greenish garbage on the display. Then normal bootup.

Something is going on with towboot and either the onboard SPI or the SPI on the storage device that is being booted from. I will look at that another time.

Pudge

1 Like
10

Awesome. Thanks for the work you do on this project! Seriously thanks!

The display garbage happens on mine and it did that before I flashed the latest SPI image.
Sadly it still can’t find the UUID I posted in my initial post, but at least I can boot EOS from uSD. It’s really odd… same condition with Kali - boots from uSD, but not EMMC - and this extremely odd one - PostMarketOS boots perfectly fine from the EMMC.

1 Like