ACPI error. Booting does not start daemons. reinstalled with the issue persisting

[soloash]

I have been trying to fix this for days. I hope someone can help as I love proxmox and this is my only system.
I was up and running for almost a year with this machine. It is HP z440 - Xeon e5-2650v4, 64gb ram, amd GPU (w5100). BIOs is on the newest version.

I have tried pretty much every setting in Bios. I have tried Proxmox version 6.2 and up with no luck.I figured it was the latest proxmox update and I just hadn't power down since then but it does not work with older versions either. I had GPU pass through to a VM, and it worked great for months.I read some ACPI error threads that this could cause the issue but It was fine for almost a year. I had a power failure and when rebooted I had the ACPI errors.
Proxmox will reinstall and it will boot but no networking or daemons started. Just goes to login. I have tried all the combinations of ACPI=off,ACPI= strict with no luck either.
I have changed ssds and tried a different video card with no luck either. I am out of ideas except to try xcp-ng and I really do not want to as I love proxmox.
I am booted and logged into proxmox just no services work. No networking or anything. I do not see the green checklist of services starting at boot either.
I have tried a lot of different things from pretty much any ACPI error thread I could find. I am just a home user but this proxmox is very important to me. I get a lot of enjoyment from learning Linux even though I am still a beginner. It also ran my home assistant with frigate. The photo show after I added ACPI=off to grub.
If anyone can help me It would mean so much.
Thanks
Soloash

 

[cheiss]

Hi,

since the core issue seems to be that services fail to start and you do have shell access - can you provide the output of e.g. journalctl -b -u pvedaemon?
Also, since you do mention ACPI - dmesg | grep -i acpi returns all messages from the ACPI subsystem, which again would be useful to see and debug this further.

Some messages like

[    6.685429] ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade (0x1001)

are (unfortunately) rather common and can normally be safely ignored, as more often than not the vendor's firmware is just buggy, esp. on consumer hardware.

You can also scroll through the log (journalctl -b, then scroll using e.g. the arrow keys if there are any errors that might hint at the root cause.