06-30-2021, 10:20 AM
Hi,
thank you again for your reply!
I think the UUID is set correct. I booted the RP64 from Sdcard and attached the eMMC using an USB Adapter.
I then issued the command blkid.
jean@rockpro64:~/Desktop$ blkid
/dev/mmcblk1p1: UUID="7def08b4-fb4d-43ec-8e86-79ae058d10d8" TYPE="ext4" PARTUUID="26413df4-01"
/dev/zram0: UUID="74dadee5-30e9-4614-8f4c-4b9573af4bb7" TYPE="swap"
/dev/zram1: LABEL="log2ram" UUID="9f430707-9213-4188-ac14-7f39b43cc0c0" TYPE="ext4"
/dev/sda1: UUID="fbc89545-e72e-44f3-bbbc-44a3ff945d2a" TYPE="ext4" PARTUUID="1ab4d7e8-01"
I mounted the sda1 partition on /mnt and checked /mnt/boot/armbianEnv.txt:
verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=fbc89545-e72e-44f3-bbbc-44a3ff945d2a
rootfstype=ext4
(bootlogo=false - would this mean I shouldn't see the armbian logo at startup? Because I do (when the boot fails))
So I believe everything is set correct?
I did some further tests:
I wrote Armbian buster (4.x kernel) to eMMC => eMMC boot succesful
I wrote Armbian focal (5.x kernel) to eMMC => eMMC boot failed (with the output referenced in the other post)
I wrote Armbian focal (5.x. kernel) to SDCard => SDCard boot succesful
I also attached the eMMC (with Armbian focal on it) with a usb adapter and could read it's contents and mount the eMMC partition.
I thought perhaps I could use the board booting from SDcard but storing my docker data on the eMMC.
I unmounted the /dev/sda1 partition, then using fdisk I removed the /dev/sda1 partition.
I then tried booting Armbian focal from SDcard with the eMMC connected (on the RP64 itself, not over usb) => boot failed, the output on screen was:
Loading, please wait...
Starting version 245.4-4ubuntu3.6
I rebooted from SDCard and attached eMMC over usb and cleared the MBR (dd if=/dev/zero of=/dev/sda bs=512 count=1).
I tried booting again from SDCard with an empty eMMC attached but it failed with the same output on screen.
I know eMMC has preference over SDCard to boot, but I would assume when eMMC boot fails it would try the next boot option being SDCard.
Is there any way I can interupt the uboot proces , and force an SDcard boot through some uboot command? I'm not so familiar with that to be honest.
thank you again for your reply!
I think the UUID is set correct. I booted the RP64 from Sdcard and attached the eMMC using an USB Adapter.
I then issued the command blkid.
jean@rockpro64:~/Desktop$ blkid
/dev/mmcblk1p1: UUID="7def08b4-fb4d-43ec-8e86-79ae058d10d8" TYPE="ext4" PARTUUID="26413df4-01"
/dev/zram0: UUID="74dadee5-30e9-4614-8f4c-4b9573af4bb7" TYPE="swap"
/dev/zram1: LABEL="log2ram" UUID="9f430707-9213-4188-ac14-7f39b43cc0c0" TYPE="ext4"
/dev/sda1: UUID="fbc89545-e72e-44f3-bbbc-44a3ff945d2a" TYPE="ext4" PARTUUID="1ab4d7e8-01"
I mounted the sda1 partition on /mnt and checked /mnt/boot/armbianEnv.txt:
verbosity=1
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=fbc89545-e72e-44f3-bbbc-44a3ff945d2a
rootfstype=ext4
(bootlogo=false - would this mean I shouldn't see the armbian logo at startup? Because I do (when the boot fails))
So I believe everything is set correct?
I did some further tests:
I wrote Armbian buster (4.x kernel) to eMMC => eMMC boot succesful
I wrote Armbian focal (5.x kernel) to eMMC => eMMC boot failed (with the output referenced in the other post)
I wrote Armbian focal (5.x. kernel) to SDCard => SDCard boot succesful
I also attached the eMMC (with Armbian focal on it) with a usb adapter and could read it's contents and mount the eMMC partition.
I thought perhaps I could use the board booting from SDcard but storing my docker data on the eMMC.
I unmounted the /dev/sda1 partition, then using fdisk I removed the /dev/sda1 partition.
I then tried booting Armbian focal from SDcard with the eMMC connected (on the RP64 itself, not over usb) => boot failed, the output on screen was:
Loading, please wait...
Starting version 245.4-4ubuntu3.6
I rebooted from SDCard and attached eMMC over usb and cleared the MBR (dd if=/dev/zero of=/dev/sda bs=512 count=1).
I tried booting again from SDCard with an empty eMMC attached but it failed with the same output on screen.
I know eMMC has preference over SDCard to boot, but I would assume when eMMC boot fails it would try the next boot option being SDCard.
Is there any way I can interupt the uboot proces , and force an SDcard boot through some uboot command? I'm not so familiar with that to be honest.
