Arch Linux

valandil

Member

Registered: 2008-03-11

Posts: 82

[SOLVED] Procedure to follow after cloning system to a new hard drive

I have bought a new, larger hard drive, and I am in the process of understanding the steps necessary to get the system working after cloning. My laptop is UEFI-based, with systemd-boot as the boot loader, and I dual-boot with Windows 8.1.

The cloning part was actually quite easy (CloneZilla refused to work, but ddrescue worked perfectly). Now, after the cloning is done, and the partitions are resized to fill the larger new drive, what are the steps to follow? I know I need to "fix" the bootloader, as it refers to partitions with their GUUID instead of their device ids (i.e. /dev/sdaX), but I'm not sure how to proceed­. Also, /etc/fstab should also be modified to refer to the new GUUIDs.

More specifically, my questions are:

1. After cloning, should the bootloader be reinstalled or updated, and how should it be done?

2. What other steps should be taken in order to have a fully-functioning system? Could you provide details on how to proceed for each one?

Cheers,

Last edited by valandil (2017-07-18 15:08:13)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: [SOLVED] Procedure to follow after cloning system to a new hard drive

If you're cloning, the UUIDs should stay the same. There really shouldn't be anything that needs to be done.

valandil

Member

Registered: 2008-03-11

Posts: 82

Re: [SOLVED] Procedure to follow after cloning system to a new hard drive

I'll retry to clone later, but so far the bootloader wouldn't even start.

Sorry for the delay, I wasn't subscribed to the topic for some reason.

valandil

Member

Registered: 2008-03-11

Posts: 82

Re: [SOLVED] Procedure to follow after cloning system to a new hard drive

I was having issues cloning due to a faulty hard drive, and I had tried using the expert mode of CloneZilla. After using the beginner mode of CloneZilla to clone the entire hard drive and the expert mode to clone the problematic partition (I had to use the rescue option), everything seems to be working fine. As @Scimmia mentioned, UUIDs stayed the same and there was nothing to be done. Everything booted up nicely.

Not sure what went wrong in the first place...

Cheers!