Page 1 of 1

[SOLVED]:GRUB Boots Wrong Drive After Clone

PostPosted: Jun 5th, '14, 03:49
by yankee495
Hi all,

I've never done a disk clone in Linux. Nice huh? I used Acronis to copy / and /home and the swap even though it is disabled.

I copied from a 120GB to a 240GB SSD. I used blkid and changed the fstab on the 240 to reflect the new UUID's

for the partitions on the 240. When I boot to the 240 Grub takes off on the old 120 SSD. After I boot / is the old one and /home is on the old one.

The new partitions don't mount. I assume grub is still pointing to the old ID's on the 120.

Grub need reinstalled on the 240 with proper setting for the 240. I don't know how to install grub in a terminal on a drive I am not booted to.

Re: GRUB Boots Wrong Drive After Clone

PostPosted: Jun 5th, '14, 04:28
by yankee495
Ok, I hand edited /boot/grub/menu.lst and have it booting on the new 240GB SSD.
/ and /home are mounting right and everything is running.

I don't know where it got it but I have a blank 20GB space like this.

| / | swap |blank | /home |

There is a blank 20GB there. I tried to resize /home but it won't let me go down.

I maybe could do it with a Windows program but I want to do it in Linux to learn how and make sure Linux likes the result.

I added these details of what I edited. I used blkid to ID the partitions then changed the UUID's in fstab and menu,lst.

You have to be root to do this and boot from a live CD or in my case the drive I was cloning from.

There has to be an easier way and I still don't know how a 20GB blank space, no partition, no data, just blank ended up between swap and /home.

Below I explain how I got rid of it and resized /home to use it.

Re: GRUB Boots Wrong Drive After Clone

PostPosted: Jun 5th, '14, 07:46
by yankee495
I figured it out though it was not the best way in my opinion. I used Gparted and apparently it moved all of the data and shifted it left.

That was a lot of writing to a new SSD and I think it would've been better to run from my 120GB and delete the blank space and /home on the 240 then make a new partition and put the data back. It only had 22GB on it but it moved 144GB of data to do it, just crazy.

Anyway it is done and everything checks out, aligned properly etc, just a lot of writes to move a small amount of data by comparison.

Opinions welcome please.