Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copy problem on Bullseye with rpi-clone #154

Open
mgnthe54 opened this issue Apr 28, 2023 · 0 comments
Open

Copy problem on Bullseye with rpi-clone #154

mgnthe54 opened this issue Apr 28, 2023 · 0 comments

Comments

@mgnthe54
Copy link

Hello, I have a new problem with Bullseye 64 bit and this time it's with rpi-clone.

I boot on a 120 G0 SSD and my crontab I make a weekly backup of this SSD on an SD (in the SD slot of the raspberry).
via the command:
sudo rpi-clone mmcblk0 -v -U >> /home/pi/script/copy_disk_boot.log
On Buster no worries, but since I switched to bullseye the copy no longer works (the files are present but if I put this SD in another pi no boot, I don't even make the image of Raspberry 4 bit I have a blinking cursor).
If I make a copy using the SD Card Copier accessory, no problem, the copy is operational!
However, the sudo rpi-clone command's action tracking file...
tells me this:
`Booted disk: sda 128.0GB Destination disk: mmcblk0 63.9GB


Part Size FS Label Part Size FS Label
1 256.0M fat32 -- 1 256.0M fat32 --
2 root 119.0G ext4 rootfs 2 59.2G ext4 rootfs


== SYNC sda file systems to mmcblk0 ==
/ (4.5G used): SYNC to mmcblk0p2 (59.2G size)


Run setup script: no.

Verbose mode: yes.
Destination disk has same Disk ID as source, changing it.
Disk identifier changed from 0x392a8b00 to 0x5e35b5bb.

Syncing file systems (can take a long time)
Syncing mounted partitions:
Mounting /dev/mmcblk0p2 on /mnt/clone
=> rsync // /mnt/clone with-root-excludes ...sending incremental file list
dev/
etc/fake-hwclock.data
etc/resolv.conf
...
...
sent 467,172,063 bytes received 20,626 bytes 11,535,621.95 bytes/sec
total size is 5,181,620,046 speedup is 11.09

Editing /mnt/clone/etc/fstab PARTUUID to use 5e35b5bb

Done with clone to /dev/mmcblk0
Start - 21:34:04 End - 21:34:49 Elapsed Time - 0:45
unmount /mnt/clone
===============================`

Booted disk: sda 128.0GB Destination disk: mmcblk0 63.9GB


Part Size FS Label Part Size FS Label
1 256.0M fat32 -- 1 256.0M fat32 --
2 root 119.0G ext4 rootfs 2 59.2G ext4 rootfs


== SYNC sda file systems to mmcblk0 ==
/ (4.5G used): SYNC to mmcblk0p2 (59.2G size)


Run setup script: no.

Verbose mode: yes.
Destination disk has same Disk ID as source, changing it.
Disk identifier changed from 0x392a8b00 to 0x5e35b5bb.

Syncing file systems (can take a long time)
Syncing mounted partitions:
Mounting /dev/mmcblk0p2 on /mnt/clone
=> rsync // /mnt/clone with-root-excludes ...sending incremental file list
dev/
etc/fake-hwclock.data
etc/resolv.conf
...
...
sent 467,172,063 bytes received 20,626 bytes 11,535,621.95 bytes/sec
total size is 5,181,620,046 speedup is 11.09

Editing /mnt/clone/etc/fstab PARTUUID to use 5e35b5bb

Done with clone to /dev/mmcblk0
Start - 21:34:04 End - 21:34:49 Elapsed Time - 0:45
unmount /mnt/clone

Has anyone had this problem before and found a solution? THANKS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant