Closed yandritos closed 3 years ago
Many thanks for your report.
Indeed there is a bug in the script, which is able to detect the root entry on Odroid XU4 correctly (https://github.com/MichaIng/DietPi/blob/master/boot_xu4.ini#L11) but not on C2 due to the leading "
double quote character in front "root=": https://github.com/MichaIng/DietPi/blob/master/boot_c2.ini#L126
Fixed with: https://github.com/MichaIng/DietPi/commit/ed19661a5bf09252867e19173adedd775f4c0d54 Changelog: https://github.com/MichaIng/DietPi/commit/82fb47a9ead3c732f3ac4a692dbb7ee4e5cdc412
What is that the on your Odroid now? Is it still running after you exited drive manager? Before rebooting, apply this change manually to boot.ini
:
# Store the content of the old entry in a variable
rootfs_current=$(mawk '-F[" ]' '{for(i=1;i<=NF;i++) if($i~/^root=/) {print $i;exit}}' /boot/boot.ini)
# Verify that it is valid
echo "$rootfs_current"
# The output of the above should look like "root=UUID=24d16755-9c44-4541-b2ea-0fa717ad2bec" just with a different a different UUID.
# If so, apply it to your boot.ini
sed -i "s#$rootfs_current#root=UUID=24d16755-9c44-4541-b2ea-0fa717ad2bec#g" /boot/boot.ini
# You can then verify that is has been applied correctly
cat /boot/boot.ini
It should then look like here: https://github.com/MichaIng/DietPi/blob/master/boot_c2.ini#L126
but with /dev/mmcblk0p2
replaced by UUID=24d16755-9c44-4541-b2ea-0fa717ad2bec
.
Dear Michalng,
Thanks a lot for your very fast reply and the fix. I just finish to impement it and all worked!
Thanks again and have a nice day!
- DietPi version | G_DIETPI_VERSION_CORE=7 G_DIETPI_VERSION_SUB=5 G_DIETPI_VERSION_RC=2 G_GITBRANCH='master' G_GITOWNER='MichaIng' G_LIVE_PATCH_STATUS[0]='not applicable'
- Distro version | 10.10
- Kernel version |
Linux DietPi 3.16.85+ #1 SMP PREEMPT Tue Jun 30 19:02:35 CEST 2020 aarch64 GNU/Linux
- SBC model | Odroid C2 (aarch64)
- Power supply used | 5V 2A
- SDcard used | SanDisk ultra 16Gb
Additional Information (if applicable)
- Was the software title installed freshly or updated/migrated? -Fresh install
Can this issue be replicated on a fresh installation of DietPi? Yes
- Bug report ID |
echo $G_HW_UUID
[ OK ] DietPi-Bugreport | Sending bug report [ INFO ] DietPi-Bugreport | Reference code: f1f426f5-51d7-4d2b-bd70-ed8902dc2967Steps to reproduce
Expected behaviour
Complete the transfer process
Actual behaviour
Raises this next error:
Extra details
This is the full trace of the execution: