Recent content by Coffeeri

  1. C

    Server Unbootable After ZFS Mirror Failure — Missing ESP on Remaining Drive?

    Hi @leesteken, Thank you for your suggestions and the links to the documentation. Regarding adding an ESP: I double-checked the partition table on the remaining drive (nvme0n1) using sgdisk -p /dev/nvme0n1. It confirmed that there is only 1.7 MiB of total free unpartitioned space on the...
  2. C

    Server Unbootable After ZFS Mirror Failure — Missing ESP on Remaining Drive?

    Hi Proxmox Community, I'm facing an issue with a Proxmox VE server that has become unbootable after one of the drives in the boot ZFS mirror failed. I've confirmed the remaining drive lacks an ESP partition and need advice on the best recovery path. Setup: Proxmox VE (Version 8.x) installed...
  3. C

    [SOLVED] Cannot boot after Upgrade

    Hello there! I've just had a VM being weirdly locked that would not be released by its own due to a backup. The VM shut down as well. I was not able to do qm unlock ID, so I thought "lets do an dist upgrade via the web ui anyways and do a reboot". Now, my Proxmox single instance is not able to...
  4. C

    [SOLVED] No GUI nor SSH after upgrade 6.1 -> 6.3 - needs manual restart of services

    The guest additions are uninstalled https://forum.proxmox.com/threads/after-using-cloud-init-the-first-time-pve-is-messed-up-now-lxc-etc-not-working.61970/#post-284104 Sadly I do not see anything specific - I get some Ceph errors (which I do not use ... single node) and postfix (currently wrong...
  5. C

    [SOLVED] No GUI nor SSH after upgrade 6.1 -> 6.3 - needs manual restart of services

    I did. hostname --ip-address is now correct. The problem persists after a reboot just now.
  6. C

    [SOLVED] No GUI nor SSH after upgrade 6.1 -> 6.3 - needs manual restart of services

    Thank you! The log seems to be to post here. So here is it in a gist. My /etc/hosts # Your system has configured 'manage_etc_hosts' as True. # As a result, if you wish for changes to this file to persist # then you will need to either # a.) make changes to the master file in...
  7. C

    [SOLVED] No GUI nor SSH after upgrade 6.1 -> 6.3 - needs manual restart of services

    It seems short and ok root@pve:~# journalctl -u pve-cluster -- Logs begin at Thu 2020-11-26 13:30:47 CET, end at Thu 2020-11-26 13:57:00 CET. -- Nov 26 13:35:36 pve systemd[1]: Starting The Proxmox VE cluster filesystem... Nov 26 13:35:37 pve systemd[1]: Started The Proxmox VE cluster...
  8. C

    [SOLVED] No GUI nor SSH after upgrade 6.1 -> 6.3 - needs manual restart of services

    Thank you for the fast response @Moayad @Stoiko Ivanov - you rock! I've just done a fresh reboot to get the logs. pvestatd ● pvestatd.service - PVE Status Daemon Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code)...
  9. C

    [SOLVED] No GUI nor SSH after upgrade 6.1 -> 6.3 - needs manual restart of services

    Hello folks, I just upgraded my single pve node from 6.1-3 to 6.3-2. This process had me do apt upgrade twice, so I moved from 6.1-3 over 6.2-X to 6.3-2. After the reboot I had to run those commands, since GUI and SSH were not working, nor was any VM/ LXC up: systemctl restart pvestatd...
  10. C

    [SOLVED] After using cloud init the first time, pve is messed up now (LXC etc not working)

    I saw on some post the usage of 172.16.1.100 pve.proxmox.com pve pvelocalhost eventhough my fqdn i set at the installation was "leserver", it worked. I will change it though. Thank you Dominik
  11. C

    [SOLVED] After using cloud init the first time, pve is messed up now (LXC etc not working)

    I think you are correct, I ran apt-get install cloud-init on the host. I uninstalled it via apt purge install cloud-init and did a reboot. Same condition as before. I didn't ran any other host changing command regarding the network/ hosts manually. Did cloud init change something, that I have...
  12. C

    [SOLVED] After using cloud init the first time, pve is messed up now (LXC etc not working)

    Hello folks. My PVE instance was up for 19 days, during this time I did: I used cloud init the first time a couple days ago and pretty much followed this tutorial. i created like 3 vms with cloud init, including one with qm clone 9000 191 --name tpy2 notice the name of the vm - got hostname of...
  13. C

    [SOLVED] Zpools not mounting on boot

    Any idea how I am able to debug this? Edit: I guess I solved it by: root@pve:~# zpool set cachefile=/etc/zfs/zpool.cache TANK root@pve:~# zpool set cachefile=/etc/zfs/zpool.cache BLACK Great! I mark this as solved! Thanks for the help!
  14. C

    [SOLVED] Zpools not mounting on boot

    Yep, the mountpoints /TANK and /BLACK do exists, but without any content inside them ( no files, nor any folder - completely empty).
  15. C

    [SOLVED] Zpools not mounting on boot

    root@pve:~# zfs get mountpoint,mounted NAME PROPERTY VALUE SOURCE BLACK mountpoint /BLACK default BLACK mounted no...