MonkderZweite, (edited )

You can just use `# cat /dev/your-disk > /dev/your-stick, no need for a (dd) scalpel there.

If your system uses UUID’s in /etc/fstab, you have to change them to match the current partitions to have it bootable. lsblk -o+UUID is nice for that.

bartolomeo,

Ok, thanks. That sounds pretty good.

If i want to compress it and save it as a backup can I do

cat /dev/sda3 | gzip -9 > drive.img.gz

?

kuneho,
@kuneho@lemmy.world avatar

fill up the remaining space on the drive completely with 0s with a dummy file you delete then, before gzipping

MonkderZweite, (edited )

Yes, but like @kuneho said, since “deleted” stuff only is marked as deleted (not wiped), there’s always a bunch of random on the “empty” space part of a disk, which compresses badly.

Do cat /dev/zero > /path/to/mounted/partition/zeroes and delete it after cat errored out because no space, to fill the “empty” space with zeroes.

bartolomeo,

That worked really well! I got a 50gb partition with about 30gb free space into a 10gb zipped image. Is there any way to show progress during the operation like with dd’s status=progress?

MonkderZweite,

I often use pv instead of cat for this. And there’s some ‘hack’ where some tool looks at some kernel feature to guess progress of cp & co. But i forgot it’s name.

Secret300,

Wait what? You can use cat like that?! That’s dope

MonkderZweite,

Everything is a file. ☺

yianiris,
@yianiris@kafeneio.social avatar

.. not if you took a blue pill overdose ..

@MonkderZweite @Secret300

MonkderZweite,

?

smb, (edited )

you can copy your system live, but that would involve other tools than dd too.

with dd when copying the whole device (instead of just partitions) everything gets cloned. This includes uuids, labes, lvm devices with the names of their lv and vg names and raid devices in case you have any. all of these (c|w)ould collide unless the original disk was taken out or either the new or old disks labrls uuids etc are previously to the boot changed to prevent collusions or accidently mounting/booting the original partitions. also if (!) you use device names i.e. in fstab, crypttab, scripts or such, like with the uuids things could break. also you might have to take action for your bios to actually boot from the stick. most people disable usb boot on notebooks for security reasons.

using dd, cloning the full disk to the full stick, then removing the original disk + set bios boot setting might work out of the box, i’ld try that first as it takes only the effort to boot from another os to do the dd-copy offline (preventing filesystem damage while copying).

a live copy could be done by cloning only the partition layout and bootloader, then setting up new filesystems (with new uuids) and new lvm group/volumes etc if any, copying original disk using rsync then (maybe “bind” mounting to separate partitions if needed), then adjusting boot config to match new uuids/labels. This could be done while running the system to be copied, but of course even running rsync twice might lack some updates of currently open files by sth like desktop programs or logfiles.

Without knowing the exact setup, only limited answers can be given, but you have to make sure the boot process will work, so at least the boot loader (grub?) and its files will be needed, which -at least in the past and for old lilo/grub- could not reside at some position on the disk after some “high value” like some number GBs. if that limitation is still there, your new exact partition layout on the usb stick might be relevant for success, but try/error should give you the hints you need.

you might use “language models” for getting hints, but they are language models, not friends, their “solution” might break your system and delete your data, and they are trained to say they are sorry afterwards, but the are’nt sorry, its just a sequenze of probabilities and words to them not more.

So always only work on data that has been backed up and prooven to be suitable for you to recover everything you need from scratch, no matter if friends, language models or lemmy users assist you ;-)

UPDATE: just learned that batocera is “designed” to be just copied to usb stick and run from there, so it will most likely already include everything you need. best is to follow their instructions how to create the usb stick to boot from. if you already have it running from partition, you most likely can copy your current data using rsync. but beware, if you have two copies with the same uuids (partition +usb) that might not work as expected.

bartolomeo,

Thanks, I’m gonna have to read that a few times ':D

smb,

and i hope that has nothing to do with my chaotic style of writing =D

z00s,

tip: use chatGPT to help you with commands.

You can say something like “I want to backup my entire file system using [this program]. I want to create a tar file, and then copy that to an external drive. I want the program to display progress while it’s copying, then verify the files have been copied correctly once it has finished. I am using [whatever distro]. Please give me the commands I need to achieve this.”

Then it will spit out the commands you need to input with the correct syntax.

The best part is that you can then ask it to clarify any parts of its answer so you can learn how it all works and make sure the commands are doing what you asked. And if your computer spits out an error, just paste that back into chatgpt and it will help you resolve it.

Seriously, chatgpt is like a 24 hour on call Linux guru friend. It’s saved me so much time and effort over the last few months doing things like this.

Secret300,

Swear to God. I hope someone develops something so I can just say what I want to do in the terminal and an AI will create the command then prompt “run this command? Y/N/E” E to explain it

z00s,

Someone’s probably working on that as we speak

possiblylinux127,

First tar up your filesystem. You can use gzip to save space. Once that’s done copy it over. Make sure you use a good filesystem on the USB device that isn’t going to cause data loss. (ie not fat)

Keep in mind that you can’t do this live and that copying the archive over will take time and the drive may lie to you. Its always best practice to run sync or eject before unplugging.

Squizzy,

I just moved to Linux two days ago and omg there is so much to learn but something I never heard of until 20.minutes ago and again right now is tarring…what is it?

yianiris,
@yianiris@kafeneio.social avatar

You mean tearing?
As in video screen tearing?

There is also tar which is a very common archiving system, so tarring=archiving

Stay away from debian/ubuntu if you really want to learn linux. They dictate how you do things so much you will never learn how to do it.

@Squizzy @possiblylinux127

Squizzy,

I’m on mind, which I think is Ubuntu but tbh while I’d love to learn I think it is all just too much for me with my workload. I’m enjoying tinkering but I’m getting nowhere.

possiblylinux127,

Its a compression program for making file archives.

Ascend-910,
Ascend-910 avatar

So basically Zip but better?

possiblylinux127,

Its not necessary better as tar by itself doesn’t have compression. You need gzip, bzip2 or something else. On modern systems with gnu tar can handle tar with compression.

If your still curious I would look up how to use it.

clever_banana,

Tape ARchiver. It just takes a tree of inodes and puts it in one long format that can be written out to tape or stored as a single file.

bartolomeo,

Wait why can’t I do it live? Thanks for the tips.

possiblylinux127,

Because it is in use. You technically can hot swap a file system by switching run levels and temporarily switching to a tmpfs but I’ve never succeeded.

backhdlp, (edited )
@backhdlp@iusearchlinux.fyi avatar

you can also use cp

possiblylinux127,

Use this with tar

bartolomeo,

How woild you do it?

UntouchedWagons,
@UntouchedWagons@lemmy.ca avatar

I wouldn’t recommend this as cp might not persist file ownership and permissions or maintain hard/soft links properly.

bizdelnick, (edited )

I guess, she meant copying not files but block devices, like cp /dev/sda1 /dev/sdb1. With GNU cp this indeed works similar to dd.

bartolomeo,

That’s cool, I didn’t know you could use cp on partitions.

backhdlp,
@backhdlp@iusearchlinux.fyi avatar

My bad, forgot that.

ricecake,

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.

stewi1914,

dd’ing /dev/sdx will copy all IDs

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

bartolomeo,

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

ricecake,

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

Deckweiss,

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,

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.

skullgiver, (edited )
@skullgiver@popplesburger.hilciferous.nl avatar

deleted_by_author

  • Loading...
  • bartolomeo,

    Ok awesome, thanks for the list, I was just asking user ricecakes about that.

    bizdelnick,

    What usually specified in fstab and other configs are FS UUIDs, not partition UUIDs. They are kept when cloning with dd.

    tkk13909,

    If you dd your entire laptop drive to the entire flash drive it should be able to boot. It might not work the same with just one partition though. Also, how big is your USB stick!?!?

    Thade780,

    You can easily get 1TB USB sticks.

    tkk13909,

    The biggest flash drive I’ve ever used is 32gb lol

    tonyn,

    ( ͡° ͜ʖ ͡°)

    bartolomeo,

    Lmao they are huge these days! But I’m talking about a 40gb partition, cloning it to a 64gb stick.

    You can’t even buy 2gb sticks anymore :/

    cmnybo,

    Small USB flash drives are still available, you just won’t find them in the local stores. There are expensive, industrial grade drives from places like digikey and dirt cheap, no name drives from Chinese sellers where they will print your logo on them for free if you buy a hundred of them.

    bizdelnick,

    One partition is not enough. You also need to copy a EFI boot partition and create a correct partition table manually. And note that you cannot get a correct result when partitions you are copying are mounted. You need to boot some live system to do this.

    caseyweederman,

    I’ve heard that systemd-boot can do it with just one partition but I don’t know howww also somebody please eli5 BTRFS to me, my brain’s doing the full-sponge thing.

    bizdelnick,

    It is possible to boot from a single partition, USB live images work this way. But regular installation that OP wants to clone likely has a separate partition.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • linux@lemmy.ml
  • DreamBathrooms
  • magazineikmin
  • InstantRegret
  • GTA5RPClips
  • ethstaker
  • Youngstown
  • everett
  • slotface
  • osvaldo12
  • rosin
  • mdbf
  • kavyap
  • thenastyranch
  • ngwrru68w68
  • megavids
  • Durango
  • modclub
  • cubers
  • khanakhh
  • Leos
  • tacticalgear
  • cisconetworking
  • vwfavf
  • tester
  • anitta
  • normalnudes
  • provamag3
  • JUstTest
  • All magazines