I have dual boot Win10 and Linux (manjaro), and I want to shrink my NTFS C:\ partition to free up space in my ext4 root partition on the same physical drive.

I keep reading online that NTFS partitioning is best handled by Windows itself. However, Windows cannot partition ext4, so I thought I’d use a live GParted session for the ext4 extending part only.

So why not shrink my C:\ partition IN WINDOWS, obtain my unallocated space, then boot into live GParted, and use the unallocated space to extend my ext4 root.

This, or do everything from GParted in one go? What has the best chance of success?

I could also install GParted on my running Linux distro, and do the extending from there. But I feel like GParted live would somehow be more… better?

  • PlasticExistence@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    Whatever you decide, make sure you’ve got a backup of any important data before you start making any partition changes. Things go wrong occasionally even when they shouldn’t.

  • funkajunk@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    Depends on how the partitions are arranged. I’m assuming your Windows is first (going left to right), then probably your boot partition, then your main ext4, and then maybe a swap?

    Definitely shrink the windows partition using disk management, but then in Linux you can clone your boot partition to the beginning of the free space, delete the old boot, and then expand the ext4. You don’t HAVE to do it from a live environment, but it is the safest.

    I didn’t google much, but this seems about right: https://www.baeldung.com/linux/resize-partitions

  • catloaf@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 months ago

    I don’t think you can shrink an active partition, especially if you’re booted from it. Just use gparted live, it’s fine. I prefer doing all my resizes offline. The only thing I do online is extending.

          • catloaf@lemm.ee
            link
            fedilink
            English
            arrow-up
            0
            ·
            7 months ago

            Yup. If data has to be moved, that’s one read and one write, in different parts of the disk. That’s going to be slow. (At least they’d be sequential, I think.)

        • catloaf@lemm.ee
          link
          fedilink
          English
          arrow-up
          0
          ·
          7 months ago

          Huh, they must have changed that at some point. Last time I checked (which was probably many years ago at this point) they didn’t support it. I’ve just always used tools like gparted because I got used to them.

          • MentalEdge@sopuli.xyz
            link
            fedilink
            arrow-up
            0
            ·
            7 months ago

            It’s kind of hit or miss. Depending on how full the partition is and how exactly the data is arranged, windows may not be able to shrink even a non-boot partition.

            The built-in partition manager doesn’t seem to be capable of rearranging anything, so you kind of just have to rely on luck for the shrink operation to be possible.

            Hence why third party tools like easus are still in business on the windows side.

              • MrTHXcertified@lemdro.id
                link
                fedilink
                English
                arrow-up
                0
                ·
                7 months ago

                I seem to remember disabling hibernation and swapfile, then defragging, seemed to significantly increase the chances of success shrinking an active partition.

                (Re-enable hibernation/swap after the shrink operation is finished.)

    • Stillhart@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      7 months ago

      I shrunk my Win10 partition from within Windows to make space to dual boot into linux so you definitely can shrink an active partition.

  • bloodfart@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    You will be fine doing your first plan. Defragment your windows drive first (you’re not wearing down your ssd with that operation. Modern ssds have wear leveling tech and are good for like 100k writes so it’s not a big deal to defragment it. Also if it’s getting slower doing a level uhh 2 spinrite scan will fix that by rewriting everything. Ask if you want to know why).

    • laurelraven@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      Oh, Gibson finally stopped mucking around with his certainly DOA SQRL project long enough to get Spinrite working on modern systems?

      • bloodfart@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        6 months ago

        No it’s still only x86 lol.

        I’m almost 100% you can get the equivalent of a lvl2 spinrite scan out of badblocks but haven’t tried it yet.

  • db2@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    IMO your first plan is best given your setup. Personally I keep Windows in a VM, that way it’s entirely controlled and I don’t need to reboot.

    • dysprosium@lemmy.dbzer0.comOP
      link
      fedilink
      arrow-up
      0
      ·
      7 months ago

      I see, thanks. I’d love to use Win in a VM but I doubt it’s as flawless as on metal. For example, would WebSerial API work as well? Idk, maybe.

      • db2@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        Unless you have a dedicated GPU just for the VM(s) it isn’t awesome for anything graphical, other than that it works for most things.