Recent content by pookieman

Tried that too - still the same :(

No.. the card isn't plugged into a monitor as such, does it need to be?

If I set display to none I just see this in the console ‍♂️

Back again .. this forum has been super helpful. Hoping for one more win. I was attempting PCI pass through for graphics with a different card. But that doesn't support parsec. So got a new card - Nvidia GTX 650 ti boost.. followed a bunch of steps.. this is what I have so far...

OK so I moved on from this by replacing the graphics card and fixed this issue here - https://forum.proxmox.com/threads/help-proxmox-not-starting-with-a-sbin-zpool-import-n-not-found-error.96842/post-419456

OK I've discovered something but I don't understand why it would cause the issue .. I was trying to get PCIE pass through working for graphics card .. here is that thread https://forum.proxmox.com/threads/configuring-proxmox-for-pcie-passthrough-nvidia-geforce-9600.96659/#post-419368 As part...

So something is clearly up with the boot process .. are there are any commands I can run to check the health of the boot drives?

But .. I just rebooted the server .. removed the USB and back to where I started .. If there was an issue with the zfs pool .. then how could proxmox be back .. it's installed on the paired SSDs So I can boot into proxmox via the rescue option on the USB.. but not normally

Wow that actually worked .. it booted .. but .. now I'm nervous .. do i unplug the USB key and reboot again?

no .. let me try that

any suggestions what to try next?

so I type in exit .. took me back to prompt .. and I repeated a bunch of times.. then this .. Is this pretty bad? I feel like the disks are corrupt

this is what zpool status shows .. why it it only showing ... -part3 of the 2 disks

So I did some googling and found this video .. which seems to describe my situation https://www.youtube.com/watch?v=kJB6BOtKKNU&t=1s I tried the commands mentioned it didn't help. The import command runs fine. But when I type exit .. I'm back where I started.. It seems like 'rpool' is the...

starting seeing this error on reboot - this is latest version of proxmox v7