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

Proxmox unresponsive/does not boot after running updater script #328

New Issue
Closed
opened 2026-02-04 17:59:58 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-04 17:59:58 +03:00
Owner
Copy Link

Originally created by @JesperDramsch on GitHub (Jan 14, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Proxmox VE LXC Updater

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

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

📝 Provide a clear and concise description of the issue.

I ran the script with default settings to update all LXCs. Now my Proxmox does not boot anymore.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  1. run bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-lxcs.sh)"
  2. Wonder why proxmox is acting weird
  3. Reboot
  4. "Cannot find boot image"

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

No response

Originally created by @JesperDramsch on GitHub (Jan 14, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Proxmox VE LXC Updater ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-lxcs.sh)" ### 📝 Provide a clear and concise description of the issue. I ran the script with default settings to update all LXCs. Now my Proxmox does not boot anymore. ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. 1. run `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/misc/update-lxcs.sh)"` 2. Wonder why proxmox is acting weird 3. Reboot 4. "Cannot find boot image" ### ❌ Paste the full error output (if available). - ### 🖼️ Additional context (optional). _No response_
OVERLORD commented 2026-02-04 18:00:12 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 14, 2025):

ive used this script yesterday for my new node. Work Perfectly. Are you sure thats the problem? I think maybe the update to debian12.9?

@MickLesk commented on GitHub (Jan 14, 2025): ive used this script yesterday for my new node. Work Perfectly. Are you sure thats the problem? I think maybe the update to debian12.9?
OVERLORD commented 2026-02-04 18:00:17 +03:00
Author
Owner
Copy Link

@JesperDramsch commented on GitHub (Jan 14, 2025):

I mean I didn't change anything on Proxmox, but the issue template forces me to chose one.
The causality is very direct. I ran this script with all defaults, it doesn't boot anymore,  and now I'm trying to recover my installation somehow.

@JesperDramsch commented on GitHub (Jan 14, 2025): I mean I didn't change anything on Proxmox, but the issue template forces me to chose one. The causality is very direct. I ran this script with all defaults, it doesn't boot anymore,  and now I'm trying to recover my installation somehow.
OVERLORD commented 2026-02-04 18:00:25 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Jan 14, 2025):

I also just run it on 3 of my nodes without any issue.

@michelroegl-brunner commented on GitHub (Jan 14, 2025): I also just run it on 3 of my nodes without any issue.
OVERLORD commented 2026-02-04 18:00:30 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Jan 17, 2025):

Running fine for me too.

I hardly believe the update script messed up proxmox so bad that it does not boot anymore.
I suggest looking into syslog dmesg etc and post on proxmox forums if necessary.

Edit: Didn't meant this to sound that rude in any way, english is not my primary language.

@CrazyWolf13 commented on GitHub (Jan 17, 2025): Running fine for me too. I hardly believe the update script messed up proxmox so bad that it does not boot anymore. I suggest looking into syslog dmesg etc and post on proxmox forums if necessary. Edit: Didn't meant this to sound that rude in any way, english is not my primary language.
OVERLORD commented 2026-02-04 18:00:35 +03:00
Author
Owner
Copy Link

@JesperDramsch commented on GitHub (Jan 17, 2025):

I hardly believe the update script messed up proxmox so bad that it does not boot anymore.

That's a pretty rude thing to respond. Maybe reconsider how you approach others, who have tried to contribute to the scripts here and are reporting a pretty egregious failure mode after running one of your scripts.

Here's the order of events:

  1. I ran the script
  2. Proxmox started acting funny
  3. I rebooted
  4. It doesn't find a boot disk

If I threw a cheeky rm -rf / --no-prese-root in there, I'd probably refrain from posting here :)

Not the first time I used this script. I thought it would be important to document the failure.

I have received better support from strangers on Threads than this "community", which is a bit worrying.
Anyone else that runs into a "Can't find bootdisk", I was sent to this page: https://pve.proxmox.com/wiki/Recover_From_Grub_Failure
I will try this on the weekend and hope for the best.

I will close this now, as I don't need more contributors to inform me that it worked for them.

@JesperDramsch commented on GitHub (Jan 17, 2025): > I hardly believe the update script messed up proxmox so bad that it does not boot anymore. That's a pretty rude thing to respond. Maybe reconsider how you approach others, who have tried to contribute to the scripts here and are reporting a pretty egregious failure mode after running one of your scripts. Here's the order of events: 1. I ran the script 2. Proxmox started acting funny 3. I rebooted 4. It doesn't find a boot disk If I threw a cheeky `rm -rf / --no-prese-root` in there, I'd probably refrain from posting here :) Not the first time I used this script. I thought it would be important to document the failure. I have received better support from strangers on Threads than this "community", which is a bit worrying. Anyone else that runs into a "Can't find bootdisk", I was sent to this page: https://pve.proxmox.com/wiki/Recover_From_Grub_Failure I will try this on the weekend and hope for the best. I will close this now, as I don't need more contributors to inform me that it worked for them.
OVERLORD commented 2026-02-04 18:00:42 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 17, 2025):

I might have written you exactly the same page, but I assume it has nothing to do with the update_os. Since it doesn't do anything to the main node or anything else. It looks more like a failed kernel that killed the grub.

But it's nice if others can help you ;-)

@MickLesk commented on GitHub (Jan 17, 2025): I might have written you exactly the same page, but I assume it has nothing to do with the update_os. Since it doesn't do anything to the main node or anything else. It looks more like a failed kernel that killed the grub. But it's nice if others can help you ;-)
OVERLORD commented 2026-02-04 18:00:47 +03:00
Author
Owner
Copy Link

@JesperDramsch commented on GitHub (Jan 17, 2025):

Cool ;-)

@JesperDramsch commented on GitHub (Jan 17, 2025): Cool ;-)
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
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#328
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?