On 6/18/24 19:58, Frank Bures wrote:
Or I could just live with it. Let the machine decide, which disk it wants to mount and then copy the boot disk to that disk. I could even automatize the backup script to make the decision by itself. In fact, there is no difference between mounting sda or sdg as /boot if they are the same with the same UUID..
You have to be careful to always have the two in sync. Otherwise you install a new kernel in boot(sda), then reboot and it start from boot(sdg) where the new kernel is missing. If you want to keep them aligned with dd, consider that the uuid can be changed for the copy by using tune2fs for ext2/3/4, and something else (mlabel?) for FAT32. As for the "copying all the blocks and stress the SSD", you can fstrim the filesystem after the copy to release the unused blocks (fstrim works for FAT32 too). Regards. -- Roberto Ragusa mail at robertoragusa.it -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
