starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Debian VM disk space #172

New Issue
Closed
opened 2026-02-04 16:57:26 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 16:57:26 +03:00
Owner
Copy Link

Originally created by @uSlackr on GitHub (Dec 14, 2024).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Debian 12 VM

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/vm/debian-vm.sh)"

📝 Provide a clear and concise description of the issue.

I'm creating a debian VM using the script and it creates the disk with on 2G drive. I'm finding while trying to patch it, it doesn't have sufficient space to recreate the initrd.img-6.1.0-21-amd64.
I downloaded the script and tried editing line 410 to set the drive size to 6G, but that doesn't affect the initial disk size. But issue is seen running direct from repo

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Run the vm script. Login to the shell. Run apt uppdate and apt upgrade. apt update fails with this issue and drive is now 97%

❌ Paste the full error output (if available).

Captured as an image - see below

🖼️ Additional context (optional).

image

Originally created by @uSlackr on GitHub (Dec 14, 2024). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Debian 12 VM ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/vm/debian-vm.sh)" ### 📝 Provide a clear and concise description of the issue. I'm creating a debian VM using the script and it creates the disk with on 2G drive. I'm finding while trying to patch it, it doesn't have sufficient space to recreate the initrd.img-6.1.0-21-amd64. I downloaded the script and tried editing line 410 to set the drive size to 6G, but that doesn't affect the initial disk size. But issue is seen running direct from repo ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Run the vm script. Login to the shell. Run `apt uppdate` and `apt upgrade`. apt update fails with this issue and drive is now 97% ### ❌ Paste the full error output (if available). Captured as an image - see below ### 🖼️ Additional context (optional). ![image](https://github.com/user-attachments/assets/adbaf4ea-0df3-46a4-a25f-b89efbc14da7)
OVERLORD added the question label 2026-02-04 16:57:26 +03:00
OVERLORD commented 2026-02-04 16:57:37 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Dec 14, 2024):

You can either run the script in advanced mode and set a higher disk capacity there (you my leace the rest untouched if you want all other things to stay like the deafult settings), or you can after the installation resize the LXC disk in the Pproxmox UI. Look at something like this tutorial.

@michelroegl-brunner commented on GitHub (Dec 14, 2024): You can either run the script in advanced mode and set a higher disk capacity there (you my leace the rest untouched if you want all other things to stay like the deafult settings), or you can after the installation resize the LXC disk in the Pproxmox UI. Look at something like [this](https://pakstech.com/blog/proxmox-increase-lxc-disk/) tutorial.
OVERLORD commented 2026-02-04 16:57:39 +03:00
Author
Owner
Copy Link

@uSlackr commented on GitHub (Dec 15, 2024):

Advanced mode doesn't offer the option to increase the disk size.
I tried resizing the disk using the proxmox gui. It works fine but the VM does not see the new disk size. Also there is not enough space in the VM to add resize2fs or growpart used to resize the disk in the vm.

@uSlackr commented on GitHub (Dec 15, 2024): Advanced mode doesn't offer the option to increase the disk size. I tried resizing the disk using the proxmox gui. It works fine but the VM does not see the new disk size. Also there is not enough space in the VM to add `resize2fs` or `growpart` used to resize the disk in the vm.
OVERLORD commented 2026-02-04 16:57:48 +03:00
Author
Owner
Copy Link

@uSlackr commented on GitHub (Dec 15, 2024):

I was able to workaround this. I built the vm, and used the gui to resize it to 4GiB. I ran apt update but not the upgrade then installed cloud-guest-utils in order to get growpart. Then I ran
growpart /dev/sda 1 and
resize2fs /dev/sda1
This grew the partition and resixed the filesystem.

IMO, the script should be changed to make the VM disk size 4G by default. The 2GB size is not usable.

@uSlackr commented on GitHub (Dec 15, 2024): I was able to workaround this. I built the vm, and used the gui to resize it to 4GiB. I ran `apt update` but not the upgrade then installed `cloud-guest-utils` in order to get `growpart`. Then I ran `growpart /dev/sda 1` and `resize2fs /dev/sda1` This grew the partition and resixed the filesystem. IMO, the script should be changed to make the VM disk size 4G by default. The 2GB size is not usable.
OVERLORD commented 2026-02-04 16:57:58 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 16, 2024):

What you do with the vm? Its an fresh clean vm?

fresh install:
image

apt-get update & apt-get upgrade
image

space after initramfs:
image

but i can do it in a new pr.

@MickLesk commented on GitHub (Dec 16, 2024): What you do with the vm? Its an fresh clean vm? fresh install: ![image](https://github.com/user-attachments/assets/12babf4b-5d25-4aae-be67-0fc8c684605e) apt-get update & apt-get upgrade ![image](https://github.com/user-attachments/assets/add61f30-c2c3-4798-a771-ea0b496a67d1) space after initramfs: ![image](https://github.com/user-attachments/assets/3841a78e-8ae9-4855-aec7-b2be3ecafa71) but i can do it in a new pr.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#172
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?