Hello! I have a 215Gb fat32 partition on my external SSD, and a 100Gb unallocated space right next to it, and I’s like to extend it to 315Gb. So, on KDE partition manager, I right-click on the fat32 partition, select “resize/move”, and this is the windows that pops up:

as you can see, the textbox with the size is grayed out, so I can only move the partition, but not resize it. Why? the device is not mounted of course, and I can operate on other partitions without problems.

thanks in advance!

  • Lvxferre@lemmy.ml
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    1 year ago

    I don’t have a FAT32 partition available at hand to test this out, but couldn’t you first move the partition to the left, and then extend it? Because IIRC FAT in general whines if you change its starting point, so you need to actually tell it “move yourself, you fat32ass!”.

    Also note that, for most purposes, you’d be better off with NTFS than FAT32.

    • tubbadu@lemmy.kde.socialOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      thanks for the reply! I’ll try to move it then. But without moving it, shouldn’t I be able to extend it right by 4.01Mb?

      IIRC FAT in general whines if you change its starting point, so you need to actually tell it “move yourself, you fat32ass!”

      XD

      Also note that, for most purposes, you’d be better off with NTFS than FAT32.

      Why this? isn’t NTFS primary a windows partition type?

      • taladar@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year ago

        isn’t NTFS primary a windows partition type?

        So is FAT32. Only FAT32 is more primitive and its origins trace back to a time long before Windows when DOS was still the primary MS OS.

      • Lvxferre@lemmy.ml
        link
        fedilink
        arrow-up
        6
        ·
        edit-2
        1 year ago

        Why this? isn’t NTFS primary a windows partition type?

        Because FAT32 has a 4GB file size limit, it’s generally slower, and it’s easier for hardware faults to corrupt files in a FAT32 filesystem.

        Usually I wouldn’t bother with FAT32 unless some device specifically requires it, but this is uncommon nowadays. (Be sure to check it out first though, just in case, before ever thinking about changing filesystems!) And nowadays, even if NTFS was originally a Windows partition type (and FAT32 a DOS/W9x one), Linux has excellent support for both, both writing and accessing.

        But without moving it, shouldn’t I be able to extend it right by 4.01Mb?

        It’s probably aligning the round edge to the hardware. Odds are that you can turn this off (in gparted you can), check if there isn’t something about this in “Advanced >>”.

        Either way, I wouldn’t worry too much. It’s just 4MB.

          • Lvxferre@lemmy.ml
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            I don’t know much about exFAT, besides the fact that it’s encumbered by Microsoft patents.

            • SteveTech@programming.dev
              link
              fedilink
              English
              arrow-up
              5
              ·
              1 year ago

              I believe Microsoft published the spec and opened up the patents for exfat a while ago. So Linux has had a pretty good exfat driver from Samsung since Kernel 5.7.

              • Lvxferre@lemmy.ml
                link
                fedilink
                arrow-up
                4
                ·
                1 year ago

                Thanks for the info - as I mentioned, I don’t know much about it. And frankly I never saw a point on using it, I usually go with ext4 > NTFS > FAT32.

          • Lvxferre@lemmy.ml
            link
            fedilink
            arrow-up
            6
            ·
            1 year ago

            Cases like this are why I told OP to check it out first, just in case. Or why I said that devices requiring it are uncommon, not non-existent.