Open eddiem5 opened 3 years ago
Same problem here, it is due to the bootloader being able to start from USB. I advise you to use version 1.71, never wrong, this new V2 at least here has only problems.
Unzip to /usr/local/sbin, then "sudo chmod +x rpi-clone" and use it, end of problems. First full backup:
sudo rpi-clone sda -f
Then progressive backup with:
sudo rpi-clone sda
@robustini That's a very old version 1.7.1 of rpi-clone. Current version is 2.0.22. Would be great if you create an PR on 2.0.22.
@robustini That's a very old version 1.7.1 of rpi-clone. Current version is 2.0.22. Would be great if you create an PR on 2.0.22.
I know it's old, but at least this one almost always works! The result with V2.0.22:
Sda is not the boot disk here, damn! :-) V2.0.22 should be debugged better.
I know it's old, but at least this one almost always works! The result with V2.0.22:
It's great you provided a workaround for this issue :+1: I thought you created some fix in 1.7.1 and will be able to roll in this fix into the current version.
Hello,
Love rpi-clone - Thank you..
I have a PI doing USB boot and another USB drive for a clone backup.
The problem is when the system is rebooted, it is indeterminate which device gets the boot...
I was hoping the -l flag from rpi-clone would do the trick but it only works for SD cards...
Any ideas or help would be great..