Menu ▾ ▴

#308 Rewriting device UUIDs in /etc/default/grub and /etc/default/grub_installdevice

testing_clonezilla
open
nobody
None
5
2018-10-21
2018-10-18
Peter Schüller
No

Thank you for making CloneZilla!

Cloning an OpenSUSE Leap 15.0 installation with CloneZilla (disk clone) causes the machine to boot very slow, because the "resume=" kernel command line parameter was not rewritten and the machine waits in vain for 1:30 for the swap device (which has an UUID that changed).

Also, starting the Yast2 tool for the bootloader crashes because of the wrong UUID in /etc/default/grub in the "resume=" setting of the kernel commandline, and because of the wrong UUID in /etc/default/grub_installdevice

I have filed a bug regarding the crash with OpenSUSE, see https://bugzilla.suse.com/show_bug.cgi?id=1111236

Still, I think it would be good if CloneZilla would rewrite the UUIDs in above mentioned files (maybe also in /boot/grub/grub.conf) in addition to those in /etc/fstab to enable a faster boot and a more consistent grub configuration of the target system.

Discussion

  • Peter Schüller

    Peter Schüller - 2018-10-18

    I confused UUIDs with Disk IDs, actually the Disk ID changes because of cloning the machine and the Disk ID would need to be rewritten.

     

  • Steven Shiau

    Steven Shiau - 2018-10-21

    Thanks. The problem is only SuSE has such issue. Other Linux distribution has no such issue. This is because no other distribution uses Disk ID in /etc/fstab. It's not portable. Of couse it's better to have a mechanism to change the /etc/fstab after cloning in Clonezilla. IIRC, OpenSuSE has changed its way that Disk ID is not used in /etc/fstab anymore. Maybe I am wrong?
    Thanks.

    Steven

     

Log in to post a comment.