hello one and all,
I think I have found a bug. I've used rip-clone for many years. I'm using raspbian/debian 13.2 (trixie) in console mode only, kernel version 6.12.47+rpt-rpi-2712 which is the latest version of raspian. I "rpi-clone sda -v" to that drive and when I replace the original drive with the cloned drive I get something like:
bof...
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! PARTUUID=2fb75be3-02 does not exist. Dropping to a shell!
BusyBox v1.37.0 (Debian 1:1.37.0-6+b3) built-in shell (ash)
Enter 'help' for a list of built-in command.
...eof
whereas before, when I replaced the cloned drive it would just boot into as if it were the original drive.
I hope this helps. lucas
hello one and all,
I think I have found a bug. I've used rip-clone for many years. I'm using raspbian/debian 13.2 (trixie) in console mode only, kernel version 6.12.47+rpt-rpi-2712 which is the latest version of raspian. I "rpi-clone sda -v" to that drive and when I replace the original drive with the cloned drive I get something like:
bof...
Gave up waiting for root file system device. Common problems:
ALERT! PARTUUID=2fb75be3-02 does not exist. Dropping to a shell!
BusyBox v1.37.0 (Debian 1:1.37.0-6+b3) built-in shell (ash)
Enter 'help' for a list of built-in command.
...eof
whereas before, when I replaced the cloned drive it would just boot into as if it were the original drive.
I hope this helps. lucas