dd ssd to usb
-
-
dd is copying the complete device, not only a partition. However, the result should be ok. Did you try?
If not it might be a Gb vs. GB issue.
-
The mistake you are making is that /dev/sda and /dev/sdg refer to entire disks, not any particular partition. The result is a copy of 256Gb onto a device that is only 32Gb..........not enough room.
Then, if you "correct" your procedure to use partitions, ie /dev/sda1 copied to /dev/sdg1 enough room will exist. However, this does not copy the MBR so the disk copy will not boot.
Often times what you tried will in fact actually work even though it threw an insufficient space error. In a case like this, it failed when copying empty space that doesn't matter. Try booting the failed copy if you haven't.
-
-
OK. I tried to mount the usb in OMV but it doesn't appear.There is not even a file system anymore
-
OK. I tried to mount the usb in OMV but it doesn't appear.There is not even a file system anymore
What may have happened is that when the copy operation failed due to insufficient space, disks were not sync'd and the data didn't actually get copied to the destination disk, it was left in memory instead. Always run a sync command after a dd, even if it succeeded.
-
can you write the sync command for me please. I am still learning. Thanks.
ok just sync. i got it.
-
-
I tried dd again.
Coderoot@nasomv:~# dd if=/dev/sda of=/dev/sdg bs=1M status=progress 30761025536 bytes (31 GB, 29 GiB) copied, 1160 s, 26.5 MB/s dd: error writing '/dev/sdg': No space left on device 29341+0 records in 29340+0 records out 30765219840 bytes (31 GB, 29 GiB) copied, 1250.12 s, 24.6 MB/s
then
But same result. No file system
-
Use clonezilla. Or create the partition table on the destination usb and just dd the partitions. The latter is harder to get right.
-
It's just:
sync
-
-
OK. I used just sync first and then sync /dev/sdg.
dd is the command of choice but leaves me with an empty flashdrive. How do i proceed with moving OMV?
-
Why do you not want to use clonezilla? This is what it is made for.
-
I reduced the partition size to 27 Gb
Did you make sure that all partitions are moved to the left in gparted?
-
-
Why do you not want to use clonezilla? This is what it is made for.
I am at beginner level and I like to learn some commands. It seemed simpler to use putty and ssh. no reboot needed. But I can try clonezilla
-
Did you make sure that all partitions are moved to the left in gparted
You mean to the left of the unallocated space on the ssd. No I didn't make sure. But I take a look before I try clonezilla
-
I am at beginner level and I like to learn some commands
Using dd to clone a larger disk to a smaller disk is not something for beginner level.
-
-
When I am sure it can't much harm I just do it. I like to find out things by myself(with research). Doing things with command is so much faster and more fun.
-
Doing things with command is so much faster and more fun.
While I can do this and have done this many times, clonezilla is faster and easier. clonezilla won't use dd either. It will use partclone. dd is slow since it copies every bit even if empty.
-
OK. Thanks for the advice. Clonezilla is running now.
-
-
clonezilla terminated without cloning because disk size 32 Gb flash drive too small for 256GB SSD. I shrinked the system partition to 27 GB and moved everything to the left.
Followed this guide
-
clonezilla terminated without cloning because disk size 32 Gb flash drive too small for 256GB SSD
Have you tested if it starts? Even if the final part of the disk was not copied, it could still boot. The part that has not been copied is assumed to be empty.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!