SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Abend during installation of Home Assistant OS (VM) #1048

New Issue
Closed
opened 2025-11-20 04:58:48 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 04:58:48 -05:00
Owner
Copy Link

Originally created by @haseat on GitHub (May 7, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Home Assistant OS

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

Installation abends with following message:

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

🔄 Steps to reproduce the issue.

run the command below in the Proxmox VE Shell:

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

❌ Paste the full error output (if available).

    __  __                        ___              _      __              __     ____  _____
   / / / /___  ____ ___  ___     /   |  __________(_)____/ /_____ _____  / /_   / __ \/ ___/
  / /_/ / __ \/ __ `__ \/ _ \   / /| | / ___/ ___/ / ___/ __/ __ `/ __ \/ __/  / / / /\__ \
 / __  / /_/ / / / / / /  __/  / ___ |(__  |__  ) (__  ) /_/ /_/ / / / / /_   / /_/ /___/ /
/_/ /_/\____/_/ /_/ /_/\___/  /_/  |_/____/____/_/____/\__/\__,_/_/ /_/\__/   \____//____/

Using Default Settings
Using HAOS Version: 15.2
Using Virtual Machine ID: 102
Using Machine Type: i440fx
Using Disk Cache: Write Through
Using Hostname: haos15.2
Using CPU Model: Host
Allocated Cores: 2
Allocated RAM: 4096
Using Bridge: vmbr0
Using MAC Address: 02:36:D2:8B:8F:8F
Using VLAN: Default
Using Interface MTU Size: Default
Start VM when completed: yes
Creating a HAOS VM using the above default settings
 ✓ Using local-lvm for Storage Location.
 ✓ Virtual Machine ID is 102.
 ✓ https://os-artifacts.home-assistant.io/15.2/haos_ova-15.2.qcow2.xz
######################################################################################################################################################################################################################################################### 100.0%#=#=-  #       #                                                                                                                                                                                                                                               #-=#=-    #        #                                                                                                                                                                                                                                            #=O=-#      #          #    
 ✓ Downloaded haos_ova-15.2.qcow2.xz
 ✓ Extracted KVM Disk Image
 | Creating HAOS VM   
[ERROR] in line 466: exit code 0: while executing command pvesm alloc $STORAGE $VMID $DISK0 4M >&/dev/null

🖼️ Additional context (optional).

No response

Originally created by @haseat on GitHub (May 7, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Home Assistant OS ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/haos-vm.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. Installation abends with following message: `[ERROR] in line 466: exit code 0: while executing command pvesm alloc $STORAGE $VMID $DISK0 4M >&/dev/null` ### 🔄 Steps to reproduce the issue. run the command below in the Proxmox VE Shell: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/haos-vm.sh)" ### ❌ Paste the full error output (if available). ``` __ __ ___ _ __ __ ____ _____ / / / /___ ____ ___ ___ / | __________(_)____/ /_____ _____ / /_ / __ \/ ___/ / /_/ / __ \/ __ `__ \/ _ \ / /| | / ___/ ___/ / ___/ __/ __ `/ __ \/ __/ / / / /\__ \ / __ / /_/ / / / / / / __/ / ___ |(__ |__ ) (__ ) /_/ /_/ / / / / /_ / /_/ /___/ / /_/ /_/\____/_/ /_/ /_/\___/ /_/ |_/____/____/_/____/\__/\__,_/_/ /_/\__/ \____//____/ Using Default Settings Using HAOS Version: 15.2 Using Virtual Machine ID: 102 Using Machine Type: i440fx Using Disk Cache: Write Through Using Hostname: haos15.2 Using CPU Model: Host Allocated Cores: 2 Allocated RAM: 4096 Using Bridge: vmbr0 Using MAC Address: 02:36:D2:8B:8F:8F Using VLAN: Default Using Interface MTU Size: Default Start VM when completed: yes Creating a HAOS VM using the above default settings ✓ Using local-lvm for Storage Location. ✓ Virtual Machine ID is 102. ✓ https://os-artifacts.home-assistant.io/15.2/haos_ova-15.2.qcow2.xz ######################################################################################################################################################################################################################################################### 100.0%#=#=- # # #-=#=- # # #=O=-# # # ✓ Downloaded haos_ova-15.2.qcow2.xz ✓ Extracted KVM Disk Image | Creating HAOS VM [ERROR] in line 466: exit code 0: while executing command pvesm alloc $STORAGE $VMID $DISK0 4M >&/dev/null ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 04:58:48 -05:00
saavagebueno commented 2025-11-20 04:58:48 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 7, 2025):

work fine here:

Image

can you execute:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/clean-orphaned-lvm.sh)"
@MickLesk commented on GitHub (May 7, 2025): work fine here: <img width="619" alt="Image" src="https://github.com/user-attachments/assets/e3a0bfd6-b9e9-4ef8-b9d4-f73aee00006f" /> can you execute: ```bash bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/pve/clean-orphaned-lvm.sh)" ```
saavagebueno commented 2025-11-20 04:58:49 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 7, 2025):

you can clear orphaned lvm with the bash above, otherwise its fixed after #4292 merged

@MickLesk commented on GitHub (May 7, 2025): you can clear orphaned lvm with the bash above, otherwise its fixed after #4292 merged
saavagebueno commented 2025-11-20 04:58:49 -05:00
Author
Owner
Copy Link

@haseat commented on GitHub (May 7, 2025):

I ran the bash to clean the orphaned lvms, tried again with vmid 102, similar result (line number is now 482 instead of 466):

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

Same result with vmid 107 (which would be next in line), 108, 109, 110, 111 ...

Also the same result after a reboot and trying out various vmids.

This is the output of lvs:

root@box0:~# lvs
  LV                              VG  Attr       LSize    Pool Origin        Data%  Meta%  Move Log Cpy%Sync Convert
  data                            pve twi-cotzM- <816.21g                    9.24   0.94                            
  root                            pve -wi-ao----   96.00g                                                           
  snap_vm-100-disk-0_works        pve Vri---tz-k    2.00g data vm-100-disk-0                                        
  snap_vm-101-disk-0_beforeUpdate pve Vri---tz-k    2.00g data vm-101-disk-0                                        
  snap_vm-101-disk-0_works        pve Vri---tz-k    2.00g data vm-101-disk-0                                        
  snap_vm-103-disk-0_works        pve Vri---tz-k    2.00g data vm-103-disk-0                                        
  snap_vm-104-disk-0_beforeUpdate pve Vri---tz-k   10.00g data vm-104-disk-0                                        
  snap_vm-105-disk-0_beforeUpdate pve Vri---tz-k    2.00g data vm-105-disk-0                                        
  snap_vm-105-disk-0_works        pve Vri---tz-k    2.00g data vm-105-disk-0                                        
  swap                            pve -wi-ao----    8.00g                                                           
  vm-100-disk-0                   pve Vwi-aotz--    2.00g data               57.04                                  
  vm-101-disk-0                   pve Vwi-aotz--    2.00g data               98.31                                  
  vm-103-disk-0                   pve Vwi-aotz--    2.00g data               27.51                                  
  vm-104-disk-0                   pve Vwi-a-tz--   10.00g data               86.02                                  
  vm-105-disk-0                   pve Vwi-aotz--    2.00g data               67.95                                  
root@box0:~#
@haseat commented on GitHub (May 7, 2025): I ran the bash to clean the orphaned lvms, tried again with vmid 102, similar result (line number is now 482 instead of 466): `[ERROR] in line 482: exit code 0: while executing command pvesm alloc $STORAGE $VMID $DISK0 4M >&/dev/null` Same result with vmid 107 (which would be next in line), 108, 109, 110, 111 ... Also the same result after a reboot and trying out various vmids. This is the output of lvs: ``` root@box0:~# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert data pve twi-cotzM- <816.21g 9.24 0.94 root pve -wi-ao---- 96.00g snap_vm-100-disk-0_works pve Vri---tz-k 2.00g data vm-100-disk-0 snap_vm-101-disk-0_beforeUpdate pve Vri---tz-k 2.00g data vm-101-disk-0 snap_vm-101-disk-0_works pve Vri---tz-k 2.00g data vm-101-disk-0 snap_vm-103-disk-0_works pve Vri---tz-k 2.00g data vm-103-disk-0 snap_vm-104-disk-0_beforeUpdate pve Vri---tz-k 10.00g data vm-104-disk-0 snap_vm-105-disk-0_beforeUpdate pve Vri---tz-k 2.00g data vm-105-disk-0 snap_vm-105-disk-0_works pve Vri---tz-k 2.00g data vm-105-disk-0 swap pve -wi-ao---- 8.00g vm-100-disk-0 pve Vwi-aotz-- 2.00g data 57.04 vm-101-disk-0 pve Vwi-aotz-- 2.00g data 98.31 vm-103-disk-0 pve Vwi-aotz-- 2.00g data 27.51 vm-104-disk-0 pve Vwi-a-tz-- 10.00g data 86.02 vm-105-disk-0 pve Vwi-aotz-- 2.00g data 67.95 root@box0:~# ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1048
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?