Linux

48310 readers

645 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Can I just use dd to clone my laptop to a bootable USB stick? (suppo.fi)

submitted 9 months ago by bartolomeo@suppo.fi to c/linux@lemmy.ml

50 comments fedilink hide all child comments

I know about Clonezilla and copy pasting partitions with gparted, but can I just use dd to copy a partition with batocera to a USB stick and will it then boot from the stick? Do I have to set the boot flag or take any other steps?

Thank you for any tips.

you are viewing a single comment's thread
view the rest of the comments

[–] ricecake@sh.itjust.works 15 points 9 months ago (3 children)

It might work, but probably not without a little tweaking.

A lot of things will reference drive identifiers or drive path to know where to mount them. These things don't get copied by dd.

[–] Deckweiss@lemmy.world 10 points 9 months ago* (last edited 9 months ago) (1 children)

huh?

Isn't it the other way around?

I once cloned an nvme with dd and had to physically remove one of the two, because they had the same id and the bios couldn't differentiate between them and would randomly boot into either the first or the second one, inconsistently.

And removing either one would boot into an identical system with everything mounted and working. Which caused some confusion until I realized that the id was copied over.

So unless you didn't use the id in fstab, you should be fine. Sure the device path may differ, but that can happen anyway to usually devices should be referenced by id.

[–] ricecake@sh.itjust.works 6 points 9 months ago

There are different schemes that different distros use. Some user partition id, some use fire system id, and some use device serial number and partition index.

[–] bartolomeo@suppo.fi 3 points 9 months ago (1 children)

Thanks, so just update the UUID in fstab for the stick? Or is there more?

[–] ricecake@sh.itjust.works 4 points 9 months ago

Probably all you need to do is check to make sure things look right, and actually test it.

I can't think of anything else that would be common that you'd want to check. If you're running weird virtualization setups on your laptop you might have to do more. :P

[–] stewi1914@sh.itjust.works 1 points 9 months ago* (last edited 9 months ago)

dd'ing /dev/sdx will copy all IDs

dd'ing /dev/sdx1 will keep UUID but PARTUUID will remain the same on the destination