# EndeavourOS ARM Install missing UUID real root **URL:** \ **Category:** Installation\ **Created:** [October 18, 2024, 12:47pm UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982 "2024-10-18T12:47:22Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![nomasteryoda](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/9e8a1a/32.png) [@nomasteryoda](https://forum.endeavouros.com/u/nomasteryoda)\ **Post date:** [October 18, 2024, 12:47pm UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982/1 "2024-10-18T12:47:22Z")
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. ---
**Author:** ![nomasteryoda](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/9e8a1a/32.png) [@nomasteryoda](https://forum.endeavouros.com/u/nomasteryoda)\ **Post date:** [October 18, 2024, 4:16pm UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982/2 "2024-10-18T16:16:02Z")
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. ---
**Author:** ![Pudge](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pudge/32/17155_2.png) [@Pudge](https://forum.endeavouros.com/u/Pudge)\ **Post date:** [October 18, 2024, 6:10pm UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982/3 "2024-10-18T18:10:33Z")
> [@nomasteryoda](#): > > I have the Pinebook Pro & tried to get the EMMC working with EndeavourOS Neo. 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 > **[Release Pinebook Pro Image October 6, 2024 · endeavouros-arm/images](https://github.com/endeavouros-arm/images/releases/tag/pinebook-pro-image)** > > Latest image for the Pinebook Pro laptop. > Known problems: > GNOME: Welcome screen and other EnOS apps work, but cannot utilize the Dark theme. > Work around: Launch "Tweaks" then click "Appearance" the... 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 ---
**Author:** ![nomasteryoda](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/9e8a1a/32.png) [@nomasteryoda](https://forum.endeavouros.com/u/nomasteryoda)\ **Post date:** [October 18, 2024, 6:56pm UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982/4 "2024-10-18T18:56:55Z")
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](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: > **[\#armbian-rockchip on 2023-03-10 — irc logs at libera.irclog.whitequark.org](https://libera.irclog.whitequark.org/armbian-rockchip/2023-03-10)** > > channel #armbian-rockchip IRC chat logs Ordering another EMMC to really know if that is the issue. ---
**Author:** ![Pudge](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pudge/32/17155_2.png) [@Pudge](https://forum.endeavouros.com/u/Pudge)\ **Post date:** [October 18, 2024, 7:05pm UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982/5 "2024-10-18T19:05:16Z")
> [@nomasteryoda](#): > > I used this one and thought it was also called Neo. Sorry about that. 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 ---
**Author:** ![anon75994754](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/a/d78d45/32.png) [@anon75994754](https://forum.endeavouros.com/u/anon75994754)\ **Post date:** [October 18, 2024, 8:12pm UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982/6 "2024-10-18T20:12:52Z")
@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](https://forum.endeavouros.com/uploads/default/original/3X/c/9/c98c0a7eea4b3852bd7b7541659283278a9994f6.jpeg) ![eos-eMMC](https://forum.endeavouros.com/uploads/default/original/3X/f/4/f44d8fe63339661f1ace3504f72a553e03fcb00f.jpeg) think i save you try. ( you busy enough ) ---
**Author:** ![nomasteryoda](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/9e8a1a/32.png) [@nomasteryoda](https://forum.endeavouros.com/u/nomasteryoda)\ **Post date:** [October 18, 2024, 8:33pm UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982/7 "2024-10-18T20:33:39Z")
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. ---
**Author:** ![Pudge](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pudge/32/17155_2.png) [@Pudge](https://forum.endeavouros.com/u/Pudge)\ **Post date:** [October 19, 2024, 12:52am UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982/8 "2024-10-19T00:52:33Z")
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](https://forum.endeavouros.com/uploads/default/original/3X/5/1/510429b2922740fb7402cdfdce4b2a2ab9e225af.jpeg) ![fastfetch](https://forum.endeavouros.com/uploads/default/original/3X/2/3/23c58e1ea8797705404c9b3453d1494710bcd54a.png) 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. ```auto [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 ---
**Author:** ![Pudge](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pudge/32/17155_2.png) [@Pudge](https://forum.endeavouros.com/u/Pudge)\ **Post date:** [October 19, 2024, 1:17am UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982/9 "2024-10-19T01:17:27Z")
I now have both the uSD and eMMC connected. It complained but booted into the uSD card. ```auto 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 ---
**Author:** ![nomasteryoda](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/9e8a1a/32.png) [@nomasteryoda](https://forum.endeavouros.com/u/nomasteryoda)\ **Post date:** [October 19, 2024, 3:43am UTC](https://forum.endeavouros.com/t/endeavouros-arm-install-missing-uuid-real-root/61982/10 "2024-10-19T03:43:59Z")
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.