Hello Linux friends,

Looking for some help today. Some dummy who won’t be named undersized the partition for his Debian VM at 32Gb. This was not enough space, as the VM is already out of storage. In Proxmox where the VM is hosted, I’ve already allocated extra space for this VM using Proxmox’s built in GUI tools. The problem is, I’m not sure how to properly extend the partition within the VM itself, using the terminal only, without breaking everything (something I obviously don’t want to do, lol).

I’ve done a bit of searching and people seem to be recommending tools like fdisk and resize2fs, both of which are not installed, and I’m afraid that I don’t have any available space to install them. I’m also a bit of a noob and some of the language for drives and partitioning just flies over my head.

Any tips on:

  • Clearing a bit of space on a Debian VM (that’s mostly using Docker, no other programs/files running constantly)
  • Resizing root partitions without too much headache
    Would be greatly appreciated!

Thanks, and have a beautiful and safe day!

    • marighost@piefed.socialOPEnglish
      2·
      9 days ago

      Here it is, the dumb question: How can I boot from an iso to modify a VM’s partitions? Further, would the VM’s / dir need to be unmounted first to resize it? Thanks for the guidance.

      • fuckwit_mcbumcrumble@lemmy.dbzer0.comEnglish
        1·
        9 days ago

        Just configure your VM to boot the gparted iso. What virtulization software are you using? If it’s proxmox on your VM there’s the options on the side bar, then boot order. Just untick the main boot drive and only have the CD drive bootable until you’re done resizing.

        When you reboot nothing is mounted because it’s off. Boot gparted and it will handle everything.

  • glitching@lemmy.mlEnglish
    21·
    8 days ago

    I really don’t wanna sound like an asshole, but based on the question and its style, you’ll fuck something up and lose data. there’s too many moving targets in your stack; put aside the idea that a beginner is dicking around with proxmox (why!?)

    exfil data, nuke the thing, create a new one sized right, import data, done.

    if you really wanna have at it, add a live ISO to proxmox boot order for that VM, boot off it and once you get the desktop use KDE Partition Manager or Gparted to expand the file system. after you’re done, shut down the VM, remove the live ISO and put the old boot order back in.

    then, maybe, get rid of proxmox and have a regular debian server with a buncha docker services where you’ll never have to pre-allocate virtual disks and such. good luck!

    • marighost@piefed.socialOPEnglish
      2·
      8 days ago

      put aside the idea that a beginner is dicking around with proxmox (why!?)

      Fun :)

      But seriously, I wanted to throw myself into it to see if I could learn it. I totally get the impulse to question a beginner’s choice for promox; I am questioning it too, frankly. I may follow your advice of restarting that server, but the thought of setting everything up again hurts my soul… At least I know how, though!

      Thanks for the kind response.

    • Bakkoda@sh.itjust.worksEnglish
      1·
      8 days ago

      I jumped into proxmox blind. Make a full backup and blow that shit up. Break things, have fun, roll it back.

      Get a gparted iso, boot into it, resize shit and if it fucks up, restore from backup and try again.

  • Consti@lemmy.worldEnglish
    1·
    9 days ago

    Since you’re using docker, also ensure your containers are set to rotate log files. By default, docker does not enable this, but you can change the defaults. Otherwise you can quickly get gigabytes of logs that eat up space.