Title.
both nvme drives, both 250GB.
#[solved] Does gnome disks "create a disk image" create a perfect copy of a disk, and can you b
blazing loom
vivid valley
Title.
both nvme drives, both 250GB.
Yes, you can also use dd
Note that the GPT UUID and the filesystem UUID are duplicated, which can cause conflicts in some cases.
You may want to change them later
blazing loom
Yes, you can also use dd
I thought dd was for HDDs only and damages nvme's?
vivid valley
I thought dd was for HDDs only and damages nvme's?
No such thing
blazing loom
Note that the GPT UUID and the filesystem UUID are duplicated, which can cause c...
oh, what issues might this cause?
Should I note the UUID's separately? ie. make a backup of the UUIDs of the original?
or both disks
vivid valley
As long as no file system or partition uses the same UUID, which is meant to be unique
blazing loom
As long as no file system or partition uses the same UUID, which is meant to be ...
how will I know
vivid valley
oh, what issues might this cause?
For example, your kernel may not know which partition you want to mount if you use something like root=UUID=32aefa97-e044-45e2-9729-6c0789095279.
vivid valley
how will I know
Use lsblk -f to see filesystem UUIDs
Use ls -lha /dev/disk/by-partuuid to see partition UUIDs
blazing loom
Use `lsblk -f` to see filesystem UUIDs
okay, so they're different currently,
if I clone the disk using gnome disks, and i check using lsblk -f, and they become identical...does this mean I should change the destination disk's UUID
vivid valley
okay, so they're different currently,
if I clone the disk using gnome disks, an...
And any occurrences of such UUIDs in the cloned disc, e.g. in the kernel command line, GRUB config, fstab, etc.
blazing loom
i'm using LUKS by the way
blazing loom
And any occurrences of such UUIDs in the cloned disc, e.g. in the kernel command...
uh, how do I check those
vivid valley
for reference only, you need to do your own research
- /etc/fstab
- /etc/default/grub - only if you are using grub as your boot loader.
blazing loom
alright
i'll just note down all the UUIDs for both disks using lsblk -f and ls -lha /dev/disk/by-partuuid
vivid valley
I thought dd was for HDDs only and damages nvme's?
In fact, gnome-disk dumping and restoring disk images does more IO.
Than a direct copy via dd
blazing loom
In fact, gnome-disk dumping and restoring disk images does more IO.
does more IO? is that a good or bad thing
@vivid valleyif I have luks on the original disk, will LUKS be transferred to the destination? is it better to encrypt destination with LUKS separately
vivid valley
does more IO? is that a good or bad thing
If you click Create Disk Images, gnome-disks will have to write 250GB to a disk image file,
When you click Restore Disk Images, gnome-disks will read this file and write it to the destination directory, this is another 250GB write.
In total, 500GB would be written.
dd would write 250 GB
blazing loom
If you click `Create Disk Images`, gnome-disks will have to write 250GB to a dis...
which of these use dd
which one should I use to clone a disk?
vivid valley
Just for information, use whatever pleases you.
blazing loom
Just for information, use whatever pleases you.
Sorry, I'm just a bit confused.
So either command do the same thing?
I don't want to do "what pleases me", I want to do the one that is designed for what I'm trying to achieve.
I hope I'm not being pushy.
vivid valley
dd and gnome-disks do the same, and gnome-disks takes an extra step by saving a disc image to a different location.
Please do your own research, and please read the DD manual page https://man.archlinux.org/man/dd.1.en
vivid valley
I hope I'm not being pushy.
No. I am sorry if I upset you.
blazing loom
Please do your own research, and please read the DD manual page https://man.arch...
okay...
blazing loom
`dd` and `gnome-disks` do the same, and gnome-disks takes an extra step by savin...
man pages are only very useful when you already know what it does
vivid valley
man pages are only very useful when you already know what it does
Mayhap this wiki will help https://wiki.archlinux.org/title/Dd
blazing loom
@vivid valleywait, now I understand...
So you have to create the image first, to a .img file, then restore that file using the restore option
I thought you could just create it
then boot off it
so that's why you said 500gb
vivid valley
So you have to create the image first, to a .img file, then restore that file us...
Yes, this is an extra step that causes the additional 250GB to be written.
blazing loom
Yes, this is an extra step that causes the additional 250GB to be written.
so in order to avoid this, I can use dd?
vivid valley
What would not happen if dd were to be used
blazing loom
It's a live system disk that I'm cloning, is that a problem
i'll read the article now
btw I'm not using arch
vivid valley
so in order to avoid this, I can use dd?
This section of the article will keep you informed. https://wiki.archlinux.org/title/Dd#Cloning_an_entire_hard_disk
vivid valley
btw I'm not using arch
It doesn't really matter.
blazing loom
It doesn't really matter.
okay. Last question, is it a problem that it's a live system that I'm cloning?
vivid valley
It's a live system disk that I'm cloning, is that a problem
Probably, please don't clone a disc with active IO
It is better to do it in another OS, such as Arch Live ISO.
vivid valley
... solved
wet ospreyBOT
#9742 📣 If there is nothing else that we can do for you, please close this thread by adding "[SOLVED]" to the title.
- You can do this on desktop by clicking the three dots on the top right of the page, and pressing "Edit Post".
- You can also do this on Android / iOS by long tapping your post in the text channel list, and tapping "Edit Post".
Your title should be like so: https://cdn.discordapp.com/attachments/503224329191030787/1039841700417384498/image.png
Thank you
