10-04-2022, 07:03 AM
(This post was last modified: 10-04-2022, 07:38 AM by elitegamercody.)
Hi,
After multiple renamings of the UUID of armbian_root, I still don't understand what's going on.
Upon boot into the eMMC I reach the "Begin: Running /scripts/local-block ... done." loop.
I have renamed the UUID of the eMMC root partition to fit what was in fstab, but then get ALERT! UUID=the_uuid_of_the_armbian_root_partition_on_the_eMMC_card does not exist, which is not true.
I don't understand why this is so hard! I even have a RESUME=UUID=the_uuid_of_the_armbian_root_partition_on_the_eMMC_card in the initramfs-tools conf.d.
This just doesn't make sense - are pinebook pros unable to read UUIDs properly?
Can someone help? Btw WDT temp2fs is not usually in PATH you have to use /sbin/temp2fs.
Also WDT please be mindful that a lot of people don't even have a bootable system or are able to boot but not enter their root partition, so they might be in a busybox/initramfs shell instead of a full Linux shell
After multiple renamings of the UUID of armbian_root, I still don't understand what's going on.
Upon boot into the eMMC I reach the "Begin: Running /scripts/local-block ... done." loop.
I have renamed the UUID of the eMMC root partition to fit what was in fstab, but then get ALERT! UUID=the_uuid_of_the_armbian_root_partition_on_the_eMMC_card does not exist, which is not true.
I don't understand why this is so hard! I even have a RESUME=UUID=the_uuid_of_the_armbian_root_partition_on_the_eMMC_card in the initramfs-tools conf.d.
This just doesn't make sense - are pinebook pros unable to read UUIDs properly?
Can someone help? Btw WDT temp2fs is not usually in PATH you have to use /sbin/temp2fs.
Also WDT please be mindful that a lot of people don't even have a bootable system or are able to boot but not enter their root partition, so they might be in a busybox/initramfs shell instead of a full Linux shell