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 11 Packages Projects Releases 10 Wiki Activity

pvesm alloc $STORAGE $VMID $DISK0 4M #1728

New Issue
Closed
opened 2026-02-05 02:04:40 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-05 02:04:40 +03:00
Owner
Copy Link

Originally created by @sawokei on GitHub (Oct 5, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Ubuntu 25.04

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/ubuntu2504-vm.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.10

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

Image

I get this error for different OS Scripts, also tried with Debian 13 and Ubuntu 24.04.
I already used the clean Orphaned lvm script, not orphans where found.

🔄 Steps to reproduce the issue.

Run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/ubuntu2504-vm.sh)" in PVE Shell

❌ Paste the full error output (if available).

[ERROR] in line 496: exit code 1: while executing command pvesm alloc $STORAGE $VMID $DISK0 4M >&/dev/null

🖼️ Additional context (optional).

This is a 3 node cluster, I tried on all 3 of the nodes.
I upgraded yesterday from 8.4.5 to 8.4.14

Originally created by @sawokei on GitHub (Oct 5, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Ubuntu 25.04 ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/ubuntu2504-vm.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.10 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. <img width="1216" height="663" alt="Image" src="https://github.com/user-attachments/assets/0a09c450-b6d8-4365-ac34-136def15f8df" /> I get this error for different OS Scripts, also tried with Debian 13 and Ubuntu 24.04. I already used the clean Orphaned lvm script, not orphans where found. ### 🔄 Steps to reproduce the issue. Run bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/ubuntu2504-vm.sh)" in PVE Shell ### ❌ Paste the full error output (if available). [ERROR] in line 496: exit code 1: while executing command pvesm alloc $STORAGE $VMID $DISK0 4M >&/dev/null ### 🖼️ Additional context (optional). This is a 3 node cluster, I tried on all 3 of the nodes. I upgraded yesterday from 8.4.5 to 8.4.14
OVERLORD added the bug label 2026-02-05 02:04:40 +03:00
OVERLORD commented 2026-02-05 02:04:48 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 5, 2025):

Try another storage

@MickLesk commented on GitHub (Oct 5, 2025): Try another storage
OVERLORD commented 2026-02-05 02:04:54 +03:00
Author
Owner
Copy Link

@sawokei commented on GitHub (Oct 5, 2025):

I tried another storage, there was no error, then I tried the original storage again, no error.
Very strange, but resolved
Thank you

@sawokei commented on GitHub (Oct 5, 2025): I tried another storage, there was no error, then I tried the original storage again, no error. Very strange, but resolved Thank you
OVERLORD commented 2026-02-05 02:04:57 +03:00
Author
Owner
Copy Link

@JoaGamo commented on GitHub (Nov 7, 2025):

Can you share more information about your cluster? Is it Ceph, NFS? I'm getting this problem with a MooseFS cluster consistently using the pve-moosefs plugin. I know that for a fact the script won't work with this plugin's block device implementation, but it should work with the standard file-based filesystem.

Luckily I had a local-lvm on only one server so I can make a template of the virtual machines.

@JoaGamo commented on GitHub (Nov 7, 2025): Can you share more information about your cluster? Is it Ceph, NFS? I'm getting this problem with a MooseFS cluster consistently using the [pve-moosefs](https://github.com/moosefs/pve-moosefs) plugin. I know that for a fact the script won't work with this plugin's block device implementation, but it should work with the standard file-based filesystem. Luckily I had a local-lvm on only one server so I can make a template of the virtual machines.
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 bug
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#1728
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?