Cloning SD running system to new SD card no boot

#1

Hello All,

I am using the official Radxa Debian image. All worked but when I imaged the SD-Card at customer
(Using R-Drive image to exactly same Type of SDcard) - this doesn’t boot on my testsystem
at home :frowning:

Maybee GPT is causing this issues??

This is how it ends up:
DDR version 1.16 20190528
ID:0x805 N
In
DDR3
333MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
ddrconfig:1
OUT
Boot1 Release Time: May 13 2019 17:34:36, version: 2.50
ChipType = 0x11, 232
mmc2:cmd1,20
emmc reinit
mmc2:cmd1,20
emmc reinit
mmc2:cmd1,20
SdmmcInit=2 1
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=15223MB
FwPartOffset=2000 , 0
StorageInit ok = 20123
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT part: 0, name: boot, start:0x8000, size:0x100000
GPT part: 1, name: rootfs, start:0x108000, size:0x1cb3060
no find partition:uboot.
LoadTrust Addr:0x4000
LoadTrust Addr:0x4400
LoadTrust Addr:0x4800
LoadTrust Addr:0x4c00
LoadTrust Addr:0x5000
LoadTrust Addr:0x5400
LoadTrust Addr:0x5800
LoadTrust Addr:0x5c00
Addr:0x4000 No find trust.img!
LoadTrustBL error:-3
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = -2, SecureMode = 0
SoftReset, 48543 us

The problematic lines seem to be
no find partition:uboot.
Addr:0x4000 No find trust.img!
LoadTrustBL error:-3
SecureInit ret = -2, SecureMode = 0

How can i get rid of all that GPT stuff and go back to good old MBR times (when it was possible to
copy images between systems without troubles) ?

Kind Greetings,
Marcovaldo

#2

Hi, we updated our toolkit yesterday. You can now use rockpi-backup to clone the system. However, please note that this script has not been extensively tested; our testing has been quite brief. If you encounter any issues, please provide us with your feedback promptly.

#3

Hi Shawn,

Many thanks for pointing me on this (I didn’t have this on the radar yet)!
Many thank also for providing this solution! I will try out and feedback.

NOTE:
I did some other tries to convert the Partition scheme to MBR (using gdisk), but also
no success (probably bacause afterwards I would have needed to install grub etc.)

Finally I found out that my issues were caused by the imaging software I was using
for ages with great satisfaction, R-Drive Image (A Windows Software) doing
something wrong (Maybee this software is too Windows centric on GPT?)
=> SOLUTION: Use RUFUS (A tool created primary to create bootable USB sticks
of all kind) to create images (in vhd format) and also for reimaging to new SD card.
Rufus runs on Windows and maybee uses some dd code internally (it shows a
message about dd when running)

Kind Greetings to all,

Marcovaldo