F5F Stay Refreshed Software Operating Systems The top SSD cloning tools for Linux include ddrescue, Clonezilla, and GParted.

The top SSD cloning tools for Linux include ddrescue, Clonezilla, and GParted.

The top SSD cloning tools for Linux include ddrescue, Clonezilla, and GParted.

Pages (2): 1 2 Next
S
ShootingStar11
Junior Member
38
09-21-2016, 08:10 AM
#1
You're looking for a straightforward cloning solution that works well with SteamOS. Since you already have a M.2 to USB-C adapter, it’s a good setup. I’d recommend using a user-friendly app like Clonezilla or a simpler tool such as DiskClone. Both allow clean cloning and are compatible with SteamOS. If you want something even easier, consider using a pre-built USB adapter cloning app that supports Steam’s format. Just make sure to back up your data first!
S
ShootingStar11
09-21-2016, 08:10 AM #1

You're looking for a straightforward cloning solution that works well with SteamOS. Since you already have a M.2 to USB-C adapter, it’s a good setup. I’d recommend using a user-friendly app like Clonezilla or a simpler tool such as DiskClone. Both allow clean cloning and are compatible with SteamOS. If you want something even easier, consider using a pre-built USB adapter cloning app that supports Steam’s format. Just make sure to back up your data first!

M
MrSarx
Senior Member
375
09-21-2016, 03:56 PM
#2
Clonezilla, rsync, dd, gnome-disks
M
MrSarx
09-21-2016, 03:56 PM #2

Clonezilla, rsync, dd, gnome-disks

R
rektyourmom21
Member
226
09-22-2016, 07:52 PM
#3
Clonezilla offers a GUI with a Gnome disk, but it seems to work best with Gnome rsync. dd is simpler for beginners and works well in the terminal, though it might not be the most user-friendly option.
R
rektyourmom21
09-22-2016, 07:52 PM #3

Clonezilla offers a GUI with a Gnome disk, but it seems to work best with Gnome rsync. dd is simpler for beginners and works well in the terminal, though it might not be the most user-friendly option.

B
BendoNoel
Member
227
09-23-2016, 02:55 AM
#4
You're looking into using rsync or dd to clone the Steam Deck's SSD. The dd method seems straightforward once you understand the steps—connect the new SSD, identify the existing and new drives, then run the command as described. It's not overly complicated if you follow it carefully. The rsync approach might be more convenient for transferring files, especially if you're already comfortable with it. Both methods can work safely if done correctly, but ensure you back up important data first.
B
BendoNoel
09-23-2016, 02:55 AM #4

You're looking into using rsync or dd to clone the Steam Deck's SSD. The dd method seems straightforward once you understand the steps—connect the new SSD, identify the existing and new drives, then run the command as described. It's not overly complicated if you follow it carefully. The rsync approach might be more convenient for transferring files, especially if you're already comfortable with it. Both methods can work safely if done correctly, but ensure you back up important data first.

X
220
09-28-2016, 12:10 AM
#5
It functions beyond the gnome environment as well.
X
XxEmmyLouWhoxX
09-28-2016, 12:10 AM #5

It functions beyond the gnome environment as well.

C
Creepsone
Junior Member
23
09-28-2016, 09:14 PM
#6
I hadn't tried Gnome before, so I relied on the title to decide and didn't explore it further.
C
Creepsone
09-28-2016, 09:14 PM #6

I hadn't tried Gnome before, so I relied on the title to decide and didn't explore it further.

M
Megaol_
Member
61
09-30-2016, 01:32 AM
#7
Aye, when dealing with input files, using dd can duplicate unused areas on storage, which isn't ideal for minimal empty space. For backups, rsync or tar work better. If your new SSD is much bigger than the original, storing images as files makes sense—just ensure proper formatting first. When mounting the larger drive, you can create snapshots with dd, compress them with xz, and restore as needed.
M
Megaol_
09-30-2016, 01:32 AM #7

Aye, when dealing with input files, using dd can duplicate unused areas on storage, which isn't ideal for minimal empty space. For backups, rsync or tar work better. If your new SSD is much bigger than the original, storing images as files makes sense—just ensure proper formatting first. When mounting the larger drive, you can create snapshots with dd, compress them with xz, and restore as needed.

G
234
10-01-2016, 02:48 PM
#8
Initial script utilizes dialogue to indicate advancement and employs pv (pipeview and dd) with the command `pv -n $1 | dd of=$2 bs=16M conv=notrunc,noerror`. Redirects output to `2>&1` and displays a gauge showing "Cloning $1 to $2 ..." at 10 seconds, 70% completion, 0 seconds remaining. It runs in the terminal and provides approximate ETA unlike native progress reports. #!/usr/bin/env bash
G
ghostghillie07
10-01-2016, 02:48 PM #8

Initial script utilizes dialogue to indicate advancement and employs pv (pipeview and dd) with the command `pv -n $1 | dd of=$2 bs=16M conv=notrunc,noerror`. Redirects output to `2>&1` and displays a gauge showing "Cloning $1 to $2 ..." at 10 seconds, 70% completion, 0 seconds remaining. It runs in the terminal and provides approximate ETA unlike native progress reports. #!/usr/bin/env bash

K
Komodo88
Senior Member
749
10-01-2016, 04:42 PM
#9
It seems intimidating at first, but if you're just copying data from one disk to another and the second is equal in size or larger, I suggest using the basic dd command. It's a command-line utility that's straightforward and easy to use, offering a simple way to transfer files without unnecessary complexity. The command structure is straightforward: dd if=/dev/source-device of=/dev/destination-device. It works by copying data block by block, from start to finish, without trying to optimize the process. You can find it on most systems, including non-Linux platforms like BSD and macOS. Be aware that it doesn't include progress indicators—your cursor will stay paused until the transfer completes, which is normal. While you can enhance it with progress tracking, the basic version is sufficient for simple HDD or SSD copies.
K
Komodo88
10-01-2016, 04:42 PM #9

It seems intimidating at first, but if you're just copying data from one disk to another and the second is equal in size or larger, I suggest using the basic dd command. It's a command-line utility that's straightforward and easy to use, offering a simple way to transfer files without unnecessary complexity. The command structure is straightforward: dd if=/dev/source-device of=/dev/destination-device. It works by copying data block by block, from start to finish, without trying to optimize the process. You can find it on most systems, including non-Linux platforms like BSD and macOS. Be aware that it doesn't include progress indicators—your cursor will stay paused until the transfer completes, which is normal. While you can enhance it with progress tracking, the basic version is sufficient for simple HDD or SSD copies.

D
djpumuslink01
Senior Member
577
10-06-2016, 09:21 AM
#10
Yes, it functions properly. You can determine whether 'if and' is the source or 'of' is the destination for the data. In your scenario it will retrieve all information from /dev/nvme0n1 and store a duplicate in /dev/sda. A block size of 256M determines the chunk size, handling data transfers in larger units. This value exceeds typical usage but is suitable for contemporary SSDs and should not cause problems. Usually, this setting influences only copy speed without affecting other aspects. Using 'conv=sync' instructs dd to write directly to the disk and prevent caching, which is ideal for copying tasks. 'status=progress' provides real-time updates on the operation. Not every dd version supports this feature; some only display summary stats at the end and keep displaying the cursor as if stuck.
D
djpumuslink01
10-06-2016, 09:21 AM #10

Yes, it functions properly. You can determine whether 'if and' is the source or 'of' is the destination for the data. In your scenario it will retrieve all information from /dev/nvme0n1 and store a duplicate in /dev/sda. A block size of 256M determines the chunk size, handling data transfers in larger units. This value exceeds typical usage but is suitable for contemporary SSDs and should not cause problems. Usually, this setting influences only copy speed without affecting other aspects. Using 'conv=sync' instructs dd to write directly to the disk and prevent caching, which is ideal for copying tasks. 'status=progress' provides real-time updates on the operation. Not every dd version supports this feature; some only display summary stats at the end and keep displaying the cursor as if stuck.

Pages (2): 1 2 Next