Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
1 of 2 tasks
JesperDramsch opened this issue Jan 14, 2025 · 7 comments
Closed
1 of 2 tasks

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

JesperDramsch opened this issue Jan 14, 2025 · 7 comments

Comments

@JesperDramsch
Copy link
Contributor

βœ… 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

@JesperDramsch JesperDramsch changed the title Proxmox unresponsive after running updater script Proxmox unresponsive/does not boot after running updater script Jan 14, 2025
@MickLesk
Copy link
Member

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?

@JesperDramsch
Copy link
Contributor Author

JesperDramsch commented Jan 14, 2025 via email

@michelroegl-brunner
Copy link
Member

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

@CrazyWolf13
Copy link
Contributor

CrazyWolf13 commented 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.

@JesperDramsch
Copy link
Contributor Author

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.

@MickLesk
Copy link
Member

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 ;-)

@JesperDramsch
Copy link
Contributor Author

Cool ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants