official rpios bookworm issue

[ProblemChild4901]

The official rpios bookworm release has changed the mount point /boot to /boot/firmware. The current rpi-clone can back up, but the backup media is not bootable because the cmdline.txt file is not updated with the new PARTUUID.
/boot/cmdline.txt -> /boot/firmware/cmdline.txt Consider adding lines like this after these variable assignments "cmdline_txt=${clone}/boot/cmdline.txt"

if [ -h $cmdline_txt ] ; then cmdline_txt=${clone}/boot/firmware/cmdline.txt fi

This tests if the /boot/cmdline.txt is a link and changes it to the actual file.

[jdrch]

Has anyone tried this: https://github.com/seamusdemora/RonR-RPi-image-utils?

[framps]

Yes. It's a nice tool to create a clone also. But in contrast to rpi-clone the clone is stored in a dd image and you have to restore the dd image first before you can use it. With rpi-clone you have a cold standy because the clone is already stored on an SD card or USB disk and can be used immediately.

In addition don't use the code from this repo ! The code is outdated and it's not the repo of Ron, the author of the code. He doesn't maintain his code on github. If you want to use his code grab the latest code directly from his thread in https://forums.raspberrypi.com/

[seamusdemora]

@framps

Yes. It's a nice tool to create a clone also. But in contrast to rpi-clone the clone is stored in a dd image and you have to restore the dd image first before you can use it. With rpi-clone you have a cold standy because the clone is already stored on an SD card or USB disk and can be used immediately.

Huh!?!? That is poppycock... every word of it is BS.

In addition don't use the code from this repo ! The code is outdated and it's not the repo of Ron, the author of the code. He doesn't maintain his code on github. If you want to use his code grab the latest code directly from his thread in https://forums.raspberrypi.com/

This must be Slag Seamus Day in your world!

Everything you've said in this post is provably and objectively UNTRUE. No idea what you've got a hard-on about, but please find someone else to invent stories about!

[framps]

Proof that every word is BS :wink:

[jdrch]

Hey folks I didn't mean to start an argument. I came across the script I asked about in an XDA post and was curious since I'd never heard of it before. Currently only @framps' tool is actively developed by the original developer, so there's that.

[seamusdemora]

@framps

Proof that every word is BS 😉

How do you figure that? What has possessed you to start this mud-slinging? Do I know you... have I wronged you somehow that I'm unaware of? What makes people just go running off at the mouth (keyboard), and just make stuff up?

[framps]

Either proove my statements in https://github.com/billw2/rpi-clone/issues/168#issuecomment-2082106387 are wrong or shut up.

[seamusdemora]

@framps

1. OK... first: "you have to restore the dd image first before you can use it."

No - that's utter nonsense... you can do a loop mount on the .img file to copy or edit any file you want. There's even a utility in image-utils that will do this for you: image-mount. And of course you can keep an image-backup-produced image file on a USB, SD, NAS, local drive - whatever. Finally - it is not a "dd image"... image-backup uses rsync to copy files from the "live" system to the *.img file. Only a nincompoop would try to use dd on a live, mounted filesystem! You have shown more ignorance in this one statement than I would have imagined humanly possible... where do you get these nonsense ideas??

2. Second: "In addition don't use the code from this repo ! The code is outdated..."

Wrong again... If you'll actually bother to "look", you will see that the files from the GitHub repo are exactly the same as the latest posted version from RonR on the RPi forum page. You don't need to take my word for this... you can download the zip file from the forum & clone the GitHub repo - and then do a diff on the two. But you've not done that have you?... No - I didn't think so.

So - are you now going to "shut up", and retract your ignorance? ... I suspect not, but we shall see.

[seamusdemora]

@jdrch

Hey folks I didn't mean to start an argument. I came across the script I asked about in an XDA post and was curious since I'd never heard of it before. Currently only @framps' tool is actively developed by the original developer, so there's that.

Which tool is that?... framps' tool I mean.

[jdrch]

Which tool is that?... framps' tool I mean.

@seamusdemora scroll up, it's linked to in the thread.

[seamusdemora]

@jdrch : Do you mean a fork he created of this repo (rpi-clone)??

[jdrch]

@seamusdemora https://github.com/framps/raspiBackup/

[framps]

@seamusdemora

Great you now started to explain in detail what's wrong for you in my statements above instead of just grumbling :+1:

Please note: I'm not saying image-backup is a bad tool. It's used by a lot of folks. It's a nice tool similar to rpi-clone which is also used by a lot of folks. image-backup has another design and because of this has other users.

(a) you can do a loop mount on the .img file to copy or edit any file you want.

Sure. You don't have to restore the whole backup if you just need some files to restore. losetup is the tool which helps to access any individual files in the backup.

(b) And of course you can keep an image-backup-produced image file on a USB, SD, NAS, local drive - whatever.

Sure. That's a difference to rpi-clone where you can only have a device as a target instead of a directory. There is a PR out there for rpi-clone to support loop devices. Then rpi-clone also will be able to store a clone in any directory.

(c) Finally - it is not a "dd image"... image-backup uses rsync to copy files from the "live" system to the *.img file.

Sure. rsync is used to populate an image mounted with losetup - not dd.

Please read my statement from above again carefully :wink:

But in contrast to rpi-clone the clone is stored in a dd image and you have to restore the dd image first before you can use it. With rpi-clone you have a cold standy because the clone is already stored on an SD card or USB disk and can be used immediately.

(a) I didn't talk about partial restore of some data. I talked about a full restore of the whole clone. If you want to do this with image-backup you have to restore the backup on Linux with dd first (I didn't write anything about creation of the backup with dd). In contrast rpi-clone has the backup already available and no restore is required. That's one of the major difference for me between rpi-clone and image-backup.

(b) I didn't write this cannot be done with image-backup. I wrote rpi-clone creates the clone on a device like a SD card or SSD which then can be used immediately to boot the system. That's something image-backup cannot do.

(c) I didn't write dd is used to create the backup. I wrote you have to use dd to restore the backup. And keep in mind: The result of image-backup is an dd image which can be accessed with losetup and be restored with dd on Linux and other tools like Etcher, Rufus or win32diskimager on Windows. That's something I learned a lot of folks like because they can restore the backup on Windows instead on Linux. Mostly because they don't have another Linux system available - even the Raspberry runs with Linux and can be used to restore a backup or they feel much more comfortable on Windows than on Linux.

Please read my statement from above again carefully :wink:

In addition don't use the code from this repo ! The code is outdated and it's not the repo of Ron, the author of the code. He doesn't maintain his code on github. If you want to use his code grab the latest code directly from his thread in https://forums.raspberrypi.com/

Your repo was updated 3 months ago. In the mean time Ron added multiple new versions of his code in the forum. So your repo is outdated. And I've seen multiple times folks grabbed Rons code from some github repos (not sure whether it was yours or others) and reported an issue in the forum thread and Ron just answered it's already fixed: Just grab my latest code from my first post in this thread.

[scargill]

The updated RPI-clone vis backing up directories..... RPI-clone is so fast, who cares about all the detail about which directories need backing up – it does the lot – just changes – typically. Using my aliases - a typical clone to SD involves the word CLONE and that;'s it - can do a clone blind drunk - often in a minute - no thought - no effort.... when I refer to rpi-clone, today on RPI and Bookworm of course, I'm referring to this. curl https://raw.githubusercontent.com/geerlingguy/rpi-clone/master/install | sudo bash

[framps]

The updated RPI-clone vis backing up directories..... RPI-clone is so fast, who cares about all the detail about which directories need backing up – it does the lot – just changes – typically.

image-backup is also very fast because it uses rsync to backup only changes. I don't want to have a flame war rpi-clone against image-backup here :flushed: . Both are nice and heavily used tools. I just want to make sure everybody understands the major differences between them and then can decide which tool is the best one for his Raspberries.

[jdrch]

Both are nice and heavily used tools. I just want to make sure everybody understands the major differences between them and then can decide which tool is the best one for his Raspberries

Agreed. The more options we have, the better.

[seamusdemora]

@framps

The updated RPI-clone vis backing up directories..... RPI-clone is so fast, who cares about all the detail about which directories need backing up – it does the lot – just changes – typically.

image-backup is also very fast because it uses rsync to backup only changes. I don't want to have a flame war rpi-clone against image-backup here 😳 . Both are nice and heavily used tools. I just want to make sure everybody understands the major differences between them and then can decide which tool is the best one for his Raspberries.

Is this what you call a "graceful retreat"? LOL

[framps]

No. It's just a statement to make sure we're on the same page :wink:

[seamusdemora]

Ah - so is that an admission that you were mistaken?

But after your BS rant - NO... We are not now, nor will we ever be "on the same page". You have issues, my friend - you should get some help.

[framps]

<((((*>

[seamusdemora]

Oh-h-h!... look everyone - he's so clever. :)

[fmarzocca]

Is there anyone who can help me on this issue?