So i had installed proxmox back in February. All was well running TrueNas as a VM until i lost power for an expended period when the power company was replacing lines without anyone getting notice (i would have just shut it down). So it’s been a few months before i had time to boot it up again and just tried. I had to get a monitor plugged in and find the wired keyboard and mouse. I was greeted with a login prompt and was able to login and am now at a root@TruNasBoi prompt. No clue what to do from here. Sorry for the super basic question.
Can’t figure out how to get to the point where i can login from the bowser
- Thread starter mathematics28
- Start date
What are the output of
Check with
ip a and cat /etc/network/interfaces? A decent photograph will do. That will help figure out if there's a network connection and what the IP address is.Check with
systemctl --failed which services have failed, in order to find possible reasons why you are not provided with a web GUI when you connect from another computer on the local network. Did you change things in your local network in the past months?Thanks for the reply. Here are the screen shots from those commands. Also, network has stayed the same. I see it’s still pulling the same static ip it always had.
Last edited:
Your network configuration looks fine and you could probably reach the system via SSH. But the PVE services have failed and that's why you don't have a web GUI to login to.
Can you please try SSH and use it to gather information from the system? It'll be much easier to read copy-pasted text than pictures.
What is the output of
Can you please try SSH and use it to gather information from the system? It'll be much easier to read copy-pasted text than pictures.
What is the output of
systemctl status pve-cluster.service? Are there error messages in journalctl -b that might give a hint why all PVE services have failed?root@truenasboi:~# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2023-08-20 09:26:59 EDT; 1h 20min ago
Process: 2287 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
CPU: 3ms
Aug 20 09:26:59 truenasboi systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Aug 20 09:26:59 truenasboi systemd[1]: Stopped The Proxmox VE cluster filesystem.
Aug 20 09:26:59 truenasboi systemd[1]: pve-cluster.service: Start request repeated too quickly.
Aug 20 09:26:59 truenasboi systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Aug 20 09:26:59 truenasboi systemd[1]: Failed to start The Proxmox VE cluster filesystem.
root@truenasboi:~# journalctl -b
-- Journal begins at Thu 2023-07-27 08:04:32 EDT, ends at Sun 2023-08-20 10:49:48 EDT. --
Aug 20 09:01:59 truenasboi kernel: Linux version 5.15.74-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 202>
Aug 20 09:01:59 truenasboi kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.74-1-pve root=/dev/mapper/pve-roo>
Aug 20 09:01:59 truenasboi kernel: KERNEL supported cpus:
Aug 20 09:01:59 truenasboi kernel: Intel GenuineIntel
Aug 20 09:01:59 truenasboi kernel: AMD AuthenticAMD
Aug 20 09:01:59 truenasboi kernel: Hygon HygonGenuine
Aug 20 09:01:59 truenasboi kernel: Centaur CentaurHauls
Aug 20 09:01:59 truenasboi kernel: zhaoxin Shanghai
Aug 20 09:01:59 truenasboi kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and >
Aug 20 09:01:59 truenasboi kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Aug 20 09:01:59 truenasboi kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Aug 20 09:01:59 truenasboi kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Aug 20 09:01:59 truenasboi kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
Aug 20 09:01:59 truenasboi kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Aug 20 09:01:59 truenasboi kernel: x86/fpu: xstate_offset[9]: 832, xstate_sizes[9]: 8
Aug 20 09:01:59 truenasboi kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'com>
Aug 20 09:01:59 truenasboi kernel: signal: max sigframe size: 3632
Aug 20 09:01:59 truenasboi kernel: BIOS-provided physical RAM map:
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000041d01fff] usable
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000041d02000-0x0000000043501fff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000043502000-0x0000000043601fff] ACPI data
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000043602000-0x0000000043801fff] ACPI NVS
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000043802000-0x0000000044b3efff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000044b3f000-0x0000000044bfefff] type 20
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000044bff000-0x0000000044bfffff] usable
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000044c00000-0x0000000048ffffff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000049e00000-0x000000004f7fffff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Aug 20 09:01:59 truenasboi kernel: BIOS-e820: [mem 0x0000000100000000-0x00000010b07fffff] usable
Aug 20 09:01:59 truenasboi kernel: NX (Execute Disable) protection: active
Aug 20 09:01:59 truenasboi kernel: efi: EFI v2.80 by American Megatrends
Aug 20 09:01:59 truenasboi kernel: efi: ACPI=0x4379e000 ACPI 2.0=0x4379e014 SMBIOS=0x44679000 SMBIOS 3.0=0x44678>
Aug 20 09:01:59 truenasboi kernel: secureboot: Secure boot disabled
Aug 20 09:01:59 truenasboi kernel: SMBIOS 3.5.0 present.
Aug 20 09:01:59 truenasboi kernel: DMI: Micro-Star International Co., Ltd. MS-7D25/PRO Z690-A WIFI DDR4(MS-7D25)>
Aug 20 09:01:59 truenasboi kernel: tsc: Detected 2500.000 MHz processor
Aug 20 09:01:59 truenasboi kernel: tsc: Detected 2496.000 MHz TSC
Aug 20 09:01:59 truenasboi kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Aug 20 09:01:59 truenasboi kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Aug 20 09:01:59 truenasboi kernel: last_pfn = 0x10b0800 max_arch_pfn = 0x400000000
Aug 20 09:01:59 truenasboi kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
lines 1-52
root@truenasboi:~# journalctl -xe
Aug 20 11:29:03 truenasboi pveproxy[1178]: starting 2 worker(s)
Aug 20 11:29:03 truenasboi pveproxy[1178]: worker 7466 started
Aug 20 11:29:03 truenasboi pveproxy[1178]: worker 7467 started
Aug 20 11:29:03 truenasboi pveproxy[7466]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:03 truenasboi pveproxy[7467]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:08 truenasboi pveproxy[7465]: worker exit
Aug 20 11:29:08 truenasboi pveproxy[1178]: worker 7465 finished
Aug 20 11:29:08 truenasboi pveproxy[1178]: starting 1 worker(s)
Aug 20 11:29:08 truenasboi pveproxy[1178]: worker 7468 started
Aug 20 11:29:08 truenasboi pveproxy[7468]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:08 truenasboi pveproxy[7466]: worker exit
Aug 20 11:29:08 truenasboi pveproxy[7467]: worker exit
Aug 20 11:29:08 truenasboi pveproxy[1178]: worker 7466 finished
Aug 20 11:29:08 truenasboi pveproxy[1178]: worker 7467 finished
Aug 20 11:29:08 truenasboi pveproxy[1178]: starting 2 worker(s)
Aug 20 11:29:08 truenasboi pveproxy[1178]: worker 7469 started
Aug 20 11:29:08 truenasboi pveproxy[1178]: worker 7470 started
Aug 20 11:29:08 truenasboi pveproxy[7469]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:08 truenasboi pveproxy[7470]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:13 truenasboi pveproxy[7468]: worker exit
Aug 20 11:29:13 truenasboi pveproxy[1178]: worker 7468 finished
Aug 20 11:29:13 truenasboi pveproxy[1178]: starting 1 worker(s)
Aug 20 11:29:13 truenasboi pveproxy[1178]: worker 7471 started
Aug 20 11:29:13 truenasboi pveproxy[7471]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:13 truenasboi pveproxy[7469]: worker exit
Aug 20 11:29:13 truenasboi pveproxy[7470]: worker exit
Aug 20 11:29:13 truenasboi pveproxy[1178]: worker 7469 finished
Aug 20 11:29:13 truenasboi pveproxy[1178]: worker 7470 finished
Aug 20 11:29:13 truenasboi pveproxy[1178]: starting 2 worker(s)
Aug 20 11:29:13 truenasboi pveproxy[1178]: worker 7472 started
Aug 20 11:29:13 truenasboi pveproxy[1178]: worker 7473 started
Aug 20 11:29:13 truenasboi pveproxy[7472]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:13 truenasboi pveproxy[7473]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:18 truenasboi pveproxy[7471]: worker exit
Aug 20 11:29:18 truenasboi pveproxy[1178]: worker 7471 finished
Aug 20 11:29:18 truenasboi pveproxy[1178]: starting 1 worker(s)
Aug 20 11:29:18 truenasboi pveproxy[1178]: worker 7474 started
Aug 20 11:29:18 truenasboi pveproxy[7474]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:18 truenasboi pveproxy[7472]: worker exit
Aug 20 11:29:18 truenasboi pveproxy[7473]: worker exit
Aug 20 11:29:18 truenasboi pveproxy[1178]: worker 7472 finished
Aug 20 11:29:18 truenasboi pveproxy[1178]: worker 7473 finished
Aug 20 11:29:18 truenasboi pveproxy[1178]: starting 2 worker(s)
Aug 20 11:29:18 truenasboi pveproxy[1178]: worker 7475 started
Aug 20 11:29:18 truenasboi pveproxy[1178]: worker 7476 started
Aug 20 11:29:18 truenasboi pveproxy[7475]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:18 truenasboi pveproxy[7476]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Aug 20 11:29:23 truenasboi pveproxy[7474]: worker exit
Aug 20 11:29:23 truenasboi pveproxy[1178]: worker 7474 finished
Aug 20 11:29:23 truenasboi pveproxy[1178]: starting 1 worker(s)
Aug 20 11:29:23 truenasboi pveproxy[1178]: worker 7477 started
Aug 20 11:29:23 truenasboi pveproxy[7477]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_fil>
Please use the arrow keys to scroll through the log messages instead of showing just the beginning and the end. Search for messages that indicate problems, but I don't know what.
Unless someone here recognizes the problem, maybe reinstalling and restoring VMs from backup might be quicker.
/etc/pve/local/pve-ssl.key: failed to load local private key might indicate a disk corruption or maybe the file is just missing? Unless someone here recognizes the problem, maybe reinstalling and restoring VMs from backup might be quicker.
I looked up one of the errors and followed some of the steps here https://web-wilke.de/fix-proxmox-error-after-hostname-ip-change/
And i got the web GUI back up and was able to get the VMs started. Something to do with the host name even though i never changed it. Not sure why this worked. My TrueNAS is up and no disk errors.
