@
@
@atoro2019-05-17 13:17:12
ubuntu
@atoro, 2019-05-17 13:17:12

Moving Ubuntu 14.04 from a larger SSD to a smaller one?

I have a 512 GB SSD running Ubuntu 14.04 with a bunch of my own handmade ledges that I've been building up from 2014 to 2018. Accordingly, several IDEs, build systems, a bunch of libraries, etc. A year ago, I transferred / rebuilt / reinstalled everything that was more or less relevant on a new disk with a new OS, and left the old one for every fireman. A year later, the probability of a fire dropped to a level when it became a pity to keep 512 gigs just like that and the idea arose to transfer all this to some budget SSD, especially since on the old one the system itself and everything that is attached to it from the strength of gigs occupies 80 80. Here I read, googled, it seems to be generally clear - we boot from a flash drive and dd, clonzilla, etc. But two things are confusing:
1) Six months ago, I got a new disk with the new Ubuntu 16.04 only after creating a partition with EFI. As a result, fdisk -l for it looks like this:
Disklabel type: gpt
Device Start End Sectors Size Type
/dev/sda1 2048 391167 389120 190M EFI System
/dev/sda2 391168 1953916267 1953525101 931.5G Linux filesystem
While the old one is like this:
of the type disklabel: dos the
Device the Boot Etpu Start End Sectors Size Id the Type
/ dev / sdb1 * 2048 984 068 095 984 066 048 83 469,2G the Linux
/ dev / sdb2 984,070,142 1,000,214,527 16,144,386 7,7G 5 the Extended
/ dev / sdb5 984,070,144 1,000,214,527 16,144,384 7,7G 82 Linux swap / solaris
And all the instructions for the specific moment with UEFI were somehow ignored.
2) The meaning of the dances is that the new disk is 4 times smaller than the old one. And although on the old one, as I already said, after cleaning, a maximum of 80 gigs will remain, in many sources it slips that both dd and clonezilla do not like this very much.
It makes sense to worry about these two reasons, taking into account the fact that I would like to get not a backup of the system, but a disk that can be lying around somewhere on a shelf, but when connected to "its" computer, without unnecessary movements, it will correctly load the old system with everything its body kit in working condition?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
R
Rsa97, 2019-05-17
_

gparted, shrink/move partitions so that they occupy less than the volume of the new screw from the beginning of the disk.
In clonezilla, select expert mode, disk-to-disk migration, set the option to ignore the size of the new disk.
Everything that was on the new disk will be erased by clonezilla.
After the transfer, again gparted and push the partitions as you need.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question