Situation
My proxmox (v. 7.1-4) was running last night and the power cutoff while it was on and VM's were running.
Problems
1.How do I fix this?
I have no idea what to do.
Under normal circumstances it looks like a GPU passthrough issue, but if the poweroff and shutdown commands aren't even working, I'm guessing there's something else that's broken.
2. So it looks like my nvme drive has broken. Some of my VM's are attached to a external Hard Drive, so will re-installing proxmox on my nvme hard drive and then re-attaching those HDD bring back my VM's to use?
Updates
1. Running the following commands gave the following error that might be hints:
2. Ran
3. So I plugged in an HDMI to the machine on boot up and got this error message:
4. Looks like the Hard Drive is broken?
5. OK, so I think my nvme drive is just dead (hardware failure). Running
My proxmox (v. 7.1-4) was running last night and the power cutoff while it was on and VM's were running.
Problems
- Upon restarting my machine, only the VM's without GPU passthrough turned on, while the VM's with GPU passthrough does not turn on. The error code related to this says:
TASK ERROR: Cannot bind 0000:01:00.0 to vfiowhich is weird since it was working before the power cutoff. - I cannot even restart the machine from the command line. Running
# shutdown noworpoweroff -fin the terminal nothing happens (command either returns right away or just hangs).
1.
I have no idea what to do.
Under normal circumstances it looks like a GPU passthrough issue, but if the poweroff and shutdown commands aren't even working, I'm guessing there's something else that's broken.
2. So it looks like my nvme drive has broken. Some of my VM's are attached to a external Hard Drive, so will re-installing proxmox on my nvme hard drive and then re-attaching those HDD bring back my VM's to use?
Updates
1. Running the following commands gave the following error that might be hints:
Code:
root@host:~# shutdown -P
Failed to set wall message, ignoring: Transport endpoint is not connected
Failed to call ScheduleShutdown in logind, no action will be taken: Transport endpoint is not connected2. Ran
# reboot, # reboot now, nothing happened so I forced machines shutoff again (held power button for 5 seconds), now on machine start up, no connection can be made - no GUI, no SSH...3. So I plugged in an HDMI to the machine on boot up and got this error message:
Failed fsck check in the initramfs stage4. Looks like the Hard Drive is broken?
5. OK, so I think my nvme drive is just dead (hardware failure). Running
smartctl -a /dev/nvme0n1 returns the following:
Last edited: