I’m not coming up with a lot of useful (clear) results when searching for a solution to this issue.

Is it OK to simply dd the 128GB disk to the 32GB disk using count to stop after the 16GB partition was cloned?

A bit more context: I had to clone a 16GB eMMC and only had a 128GB SD around. Now I purchased a 32GB eMMC and want to clone it again. The partition holds a root filesystem for an ARMv8 device. I don’t have the 16GB eMMC anymore, that would have been the easy way out.

  • zelifcam@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    2 months ago

    I’d use clonezilla

    E: It’s not that it can’t be done other ways, it’s just clonezilla will work and has worked for nearly 2 decades. Also there’s no information provided above about the data. So clonezilla is nice if it’s a complicated scenario.

    Plus, it’s a nice tool to throw in the toolbox once you know how to use it.

    E. Why do you feel like you have to use something like dd for this particular task? Less than 16 GB of data? Ya probably could have copied it over manually by now.

    • InFerNo@lemmy.mlOP
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      2 months ago

      It’s not an active partition/disk I want to clone. Clonezilla seems like something I need to boot into?

      • hushable@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        2 months ago

        Yes, Clonezilla runs off a live USB. If it is large enough it can also store the partition you want to clone, making the whole process a lot simpler.

  • friend_of_satan@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 months ago

    If I understand the problem correctly it has a pretty simple solution that I have done before. Make a new partition on the destination and dd if=/dev/diskAsB of=/dev/diskXsY where A is the source disk and B is the source partition and X is the destination disk and Y is the destination partition. You may have to run fsck on the destination afterwards and maybe a gpt repair tool.

    Honestly though, since it’s an ext filesystem, if it were me I’d just mount the source and dest and rsync.

  • Rin@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    Do you only have the root parition or do you have everything else too (like /boot)?

    1. If you only have root, reinstall the OS then just overwrite the root partition with your old one.
    2. Run fsck on the root partition and/or use gparted to expand the ext4 partition. You might have to fuck around with the disk UUIDs to get it to boot again. You’ll most likely have to at the very least change your /etc/fstab file to update the UUID of the boot partition.

    if you have everything, you can just dd the sd disk to the emmc, provided that you didn’t mess around with the partitions after.

    1. Copy with dd to the emmc with or without the count, it doesn’t matter that much if time isn’t a priority. (something like dd if=/dev/sdcard of=/dev/newemmc). If it fails and says the device is out of memory after 32GB, that’s fine. Any other error is not fine.
    2. Use gparted to expand the root partition.
    3. fsck the partition.
  • seaQueue@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    2 months ago

    Is the 16gb partition the first partition? If so I’d just dd the 128gb drive at the 32gb drive then fix the partition table and remove the others.

    If it’s not the first partition use gparted to copy it to the new drive.