i want to test debian trixie (13) so i can report bugs and troubleshoot before the release later this year. i thought about simply installing trixie alongside my current bookworm installation, but that won’t be my scenario when the time comes, since i’ve been updating my system instead of reinstalling it since debian jessie (8) and this time it won’t be different. how can i clone my current system so i can simulate an update to trixie? do i simply create a new partition and copy my files over, then chroot to it and install grub?

  • mina86@lemmy.wtfEnglish
    6·
    1 day ago

    What others wrote except don’t use dd. Use rsync or make a backup with tar. dd will waste time reading unallocated regions of the disk.

  • monovergent 🛠️@lemmy.ml
    1·
    1 day ago

    I’m also considering this when it comes time for me to update. I would:

    • Throw a spare SSD or equal or greater size into a USB enclosure
    • Clone my boot drive to it using Clonezilla
    • Remove the original boot drive to avoid UUID collisions
    • Boot off the spare SSD and perform the update
  • darius@lemmy.ml
    6·
    2 days ago

    I would recommend cloning the entire disk to another disk of equal or greater size before, best procedure is to boot to a USB installation, run Gnome-Disk-Utility, create a disk image onto a second larger disk, then restore that image to a third disk which is equal or greater in terms of capacity to your bookworm disk, then unplug your orignal bookwork disk amd then attempt to boot from that third disk (fingers crossed)

    If you’re comfortable with the dd command that’s another route to take but if you’re not paying attention you can very easily wipe your own disk!

  • pewpew@feddit.it
    1·
    1 day ago

    I just went full nuclear upgrading my Bookworm install to Trixie and then to Unstable

  • harsh3466@lemmy.ml
    5·
    2 days ago

    You can do this with the dd command. To prep:

    Set up a live boot USB stick with your distro of choice.

    Install another SSD/nvme/HDD at least the same size as your bookworm install into your bookworm machine. If that’s not an option connect a USB drive that’s at least the same size as the drive with your bookworm installation.

    Boot into the live USB on the bookworm machine.

    Make sure the partition(s) from your bookworm install are unmounted.

    Quadruple check the drives/devices for the dd command. Here’s the basics of the command:

    dd if=/device/where/bookworm/is/installed of=USB/or/second/drive/in/machine bs=8M status=progress

    So, if your bookworm install is on /dev/sda, and the USB or secondary is /dev/sdb, then the Cmand would be:

    dd if=/dev/sda of=/dev/sdb bs=8M status=progress

    • signofzeta@lemmygrad.mlEnglish
      1·
      2 days ago

      This is literally what dd does and what I would have recommended, if this person hadn’t beaten me to it.

      However, if you’re cloning to another disk or partition that will be plugged in at the same time as your existing installation, you’ll wind up with two partitions with the same identifier — a recipe for eventual disaster. In that case, I would run through setup (with your current disk unplugged) and then rsync over the new root partition.

  • lordnikon@lemmy.worldEnglish
    3·
    2 days ago

    Using timeshift would be perfect for this. I run sid and use this all the time to restore back to a snapshot on a bad upgrade.

  • britaliope@kourjetez.bzhEnglish
    1·
    2 days ago

    There are multiple way to de this. The easiest solution would be to une a second disk with same size or bigger and clone the current one onto the new one, using dd or clonezilla

    if you have enough size on your dis_ for a second root partition, you can use dd to clone the existing root partition in the new one, edit /etc/fstab on the new one to point to the correct root partition, and us grub-mkconfig if you use grub, use grub-mkconfig to reconfigure it. It should automatically detect the new partition.

  • just_another_person@lemmy.world
    1·
    2 days ago

    If you have a second clean drive to work with, you can clone it there and just change your boot target in your BIOS. This is the simplest way.

    If you’re simply concerned about config incompatibilities and finding what will break (not hardware), you could clone down to a VM image and boot that then run the upgrade, and boot it again.

    If you’re concerned about hardware issues, you could clone down to a liveUSB compatible image (skipping heavy media files) and boot that from an external device and see how it runs.

    It’s a bit of an early release to test with your daily driver, so it’s going to be a nightmare. Just a heads up.