Quantcast
Viewing all articles
Browse latest Browse all 4325

Troubleshooting • Re: RPI-Clone & Bookworm

You detected the PARTUUID in cmdline.txt wasn't updated. That's exactly the issue of the original rpi-clone: /boot/cmdline.txt was updated but not /boot/firmware/cmdline,txt.

Did you check in /boot/cmdline.txt and /boot/firmware/cmdline.txt the PARTUUID? The latter will be used by RaspbianOS. The original rpi-clone just updates /boot/cmdline.txt which is fixed in my fork.

Frankly it looks like you still used the original rpi-clone and not my fork.

Given this I executed again a test on my CM4 which I usually use to execute raspiBackup tests and executed some additional commands to verify you use the forked rpi-clone:

Code:

# download the forked rpi-clonewget https://raw.githubusercontent.com/framps/rpi-clone/master/rpi-clone# check you use the correct fileshasum rpi-cloned4f6444cf38b038b60963a2e037e2a1785a3db17  rpi-clonechmod +x rpi-clonesudo cp rpi-clone /usr/local/bin/pi@raspberrypi-bookworm64-lite-cm4:~ $ lsblk -o NAME,FSTYPE,UUID,PARTUUID,MOUNTPOINTSNAME         FSTYPE UUID                                 PARTUUID                             MOUNTPOINTSsda|-sda1       vfat   73D7-BE94                            2d1f3fa2-01|-sda2       ext4   8813ae38-5f36-4607-8549-ddf970568229 2d1f3fa2-02mmcblk0|-mmcblk0p1  vfat   5DF9-E225                            18aea473-01                          /boot/firmware`-mmcblk0p2  ext4   3b614a3f-4a65-4480-876a-8a998e01ac9b 18aea473-02                          /mmcblk0boot0mmcblk0boot1nvme0n1|-nvme0n1p1  vfat   EB8A-F3C7                            a560a466-01`-nvme0n1p2  ext4   04508ed6-922a-4a0f-9b8c-757d677451c6 a560a466-02pi@raspberrypi-bookworm64-lite-cm4:~ $ sudo rpi-clone sdaBooted disk: mmcblk0 31.3GB                Destination disk: sda 8.1GB---------------------------------------------------------------------------Part               Size    FS     Label           Part   Size    FS     Label1 /boot/firmware   512.0M  fat32  --              1      512.0M  fat32  --2 root              28.6G  ext4   rootfs          2        7.0G  ext4   -----------------------------------------------------------------------------== Initialize: IMAGE partition table - forced by option ==1 /boot/firmware      (60.5M used)   : MKFS  SYNC to sda12 root                (1.9G used)    : RESIZE  MKFS  SYNC to sda2---------------------------------------------------------------------------Run setup script       : no.Verbose mode           : no.-----------------------:** WARNING **          : All destination disk sda data will be overwritten!-----------------------:Initialize and clone to the destination disk sda?  (yes/no): yesOptional destination ext type file system label (16 chars max):Initializing  Imaging past partition 1 start.  => dd if=/dev/mmcblk0 of=/dev/sda bs=1M count=8 ...  Resizing destination disk last partition ...    Resize success.  Changing destination Disk ID ...  => mkfs -t vfat -F 32  /dev/sda1 ...  => mkfs -t ext4  /dev/sda2 ...Syncing file systems (can take a long time)Syncing mounted partitions:  Mounting /dev/sda2 on /mnt/clonemount: (hint) your fstab has been modified, but systemd still uses       the old version; use 'systemctl daemon-reload' to reload.  => rsync // /mnt/clone with-root-excludes ...  Mounting /dev/sda1 on /mnt/clone/boot/firmwaremount: (hint) your fstab has been modified, but systemd still uses       the old version; use 'systemctl daemon-reload' to reload.  => rsync /boot/firmware/ /mnt/clone/boot/firmware  ...Editing /mnt/clone/etc/fstab PARTUUID to use 8e8f4b9d===============================Done with clone to /dev/sda   Start - 18:41:19    End - 18:50:50    Elapsed Time - 9:31Cloned partitions are mounted on /mnt/clone for inspection or customizing.Hit Enter when ready to unmount the /dev/sda partitions ...  unmounting /mnt/clone/boot/firmware  unmounting /mnt/clone===============================pi@raspberrypi-bookworm64-lite-cm4:~ $ lsblk -o NAME,FSTYPE,UUID,PARTUUID,MOUNTPOINTSNAME         FSTYPE UUID                                 PARTUUID                             MOUNTPOINTSsda|-sda1       vfat   7499-588D                            8e8f4b9d-01`-sda2       ext4   b9b35fe3-711d-4924-9d46-3ab26b5a8f8b 8e8f4b9d-02mmcblk0|-mmcblk0p1  vfat   5DF9-E225                            18aea473-01                          /boot/firmware`-mmcblk0p2  ext4   3b614a3f-4a65-4480-876a-8a998e01ac9b 18aea473-02                          /mmcblk0boot0mmcblk0boot1nvme0n1|-nvme0n1p1  vfat   EB8A-F3C7                            a560a466-01`-nvme0n1p2  ext4   04508ed6-922a-4a0f-9b8c-757d677451c6 a560a466-02# use my small script to check the PARTUUIDs and optionally update them wget https://raw.githubusercontent.com/framps/raspberryTools/master/syncUUIDs.shchmod +x syncUUIDs.shpi@raspberrypi-bookworm64-lite-cm4:~ $ sudo ./syncUUIDs.sh /dev/sda--- Root PARTUUID 8e8f4b9d-02 already used in /dev/sda1/cmdline.txt--- Boot PARTUUID 8e8f4b9d-01 already used in /dev/sda2/etc/fstab--- Root PARTUUID 8e8f4b9d-02 already used in /dev/sda2/etc/fstab
So you actually can use the original rpi-clone to create a clone and the run

Code:

syncUUIDs.sh -u
to update the incorrect PARTUUIDs. I think it's much more convenient to use the forked and updated rpi-clone Image may be NSFW.
Clik here to view.
:)

Statistics: Posted by framp — Sun Jan 21, 2024 7:39 pm



Viewing all articles
Browse latest Browse all 4325

Trending Articles