I bought a laptop with windows 11 instaled in its 256gb nmve ssd. I want to install linux but I want to first create an image of the ssd and store it in an external 4tb ssd with a ext4 filesystem (that I use for different backups) so in case I want to sell the laptop later I can restore windows 11 to the same ssd from the image. So what i’m planning to do is:

  • dd if=/dev/drive_device of=external_ssd/images/windows11.img

for creating the image and swapping if and of for restoring. My question is if creating the image of a drive with a windows 11 filesystem and storing it in a ext4 filesystem is possible or can have any issue. I ask this because I read that in the case of cloning the target drive will end up with the filesystem of the source drive in case they are different, which caused me some hesitation.

  • atzanteol@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    9
    ·
    13 hours ago

    I used to do this frequently “back in the day”…

    dd will create a complete bit-for-bit copy of the drive and put its contents into a file. All the way down to the boot sector, partitions, etc. Filesystem doesn’t even matter a little.

    I used to do something like “dd /dev/sda bs=1M | nc remote.server 1234” and then on the remote server “nc -l 1234 -p > file.img </dev/null”. I was swapping back and forth between Linux and Windows on a work laptop that I was using for non-work related things on the weekend, at conferences, etc.

    Wasn’t perhaps my most intelligent moment, but it worked!

  • Onno (VK6FLAB)@lemmy.radio
    link
    fedilink
    arrow-up
    8
    ·
    14 hours ago

    The file you create using the dd command is just a file. It can live on any filesystem capable of storing a 256 GB file.

    Make sure that you compare the checksum between the drive and the file and store a copy of it with the file, so you can check it after restoring the data.

    Note that you can even mount that file using a loopback interface, so you can read the content, but if you alter it, the checksum will change.

    Welcome to Linux where all manner of magic is built-in.

  • catloaf@lemm.ee
    link
    fedilink
    English
    arrow-up
    3
    ·
    15 hours ago

    No, a dd image is just a raw stream of bits. It doesn’t care about filesystems, neither inside nor outside the file.

    • corvus@lemmy.mlOP
      link
      fedilink
      arrow-up
      4
      ·
      12 hours ago

      What are the pros of using Clonezilla instead of dd, in terms of simplicity the command that I wrote it’s hard to beat.

      • blackstrat@lemmy.fwgx.uk
        link
        fedilink
        arrow-up
        3
        ·
        6 hours ago

        Backups only used blocks. Backup to or from various locations, NFS shares, ftp, WebDAV, ssh server, samba, etc. Encryption of the images, backup of single partitions or whole disks.

        If you want to deploy to several machines at once it also has a load of tools for that too.

  • bamboo
    link
    fedilink
    English
    arrow-up
    2
    ·
    14 hours ago

    As others have said, using dd will be a bit for bit copy of the drive, regardless of the filesystem. If you were only using 10GB, and the rest of the drive was “empty”, the output of dd will still be a 256GB file. You could compress this file with gzip if storage is a concern.

    With regard to your plan with Windows, there is a hardware check that OS will perform and if the hardware drifts too much, the OS will not be activated anymore and will need a new license. I’m not familiar with recent versions of Windows, but if you have a Pro version of the OS, it might not work on new hardware.

    • corvus@lemmy.mlOP
      link
      fedilink
      arrow-up
      2
      ·
      12 hours ago

      The idea is to restore Windows to the same laptop in case I want to sell it, so it shouldn’t have any issues, right?

      • catloaf@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        9 hours ago

        You can just reinstall base Windows at that time, either plain or your OEM version if they provide it. There’s not much use in preserving the current image.

        • ReversalHatchery@beehaw.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 hours ago

          there are. for one because of the license key, but also because it’s not rare that its hard to find all the drivers that make all of the laptop work

          • catloaf@lemm.ee
            link
            fedilink
            English
            arrow-up
            2
            ·
            8 hours ago

            OEM license keys have been stored in the BIOS for several versions now: https://en.wikipedia.org/wiki/System_Locked_Pre-installation

            For 99% of drivers, the on-disc ones are enough to get up and running, and as long as you have an Internet connection you can download any that aren’t on-disc. The remaining 1% can be obtained directly from the OEM. Modem Windows is very good about this.

            • ReversalHatchery@beehaw.org
              link
              fedilink
              English
              arrow-up
              1
              ·
              6 hours ago

              For 99% of drivers, the on-disc ones

              op will wipe the disk

              as long as you have an Internet connection you can download any that aren’t on-disc

              if windows update can guess correctly what kind of device you have

              The remaining 1% can be obtained directly from the OEM

              I did not have that experience last time with an acer laptop

      • bamboo
        link
        fedilink
        English
        arrow-up
        3
        ·
        12 hours ago

        Ah I see ok yeah that should be fine. I misread and thought you were going to sell the windows laptop and transfer the OS to a new machine.