Search results

  1. S

    After upgrade to v8.2 black screen with blinking cursor

    I dont understand. You asked for it. :) The problem is that the server doesn't boot with the standard kernel. I have to force booting from v5
  2. S

    After upgrade to v8.2 black screen with blinking cursor

    I'm so sorry for the delay. Here you go: # pveversion -v proxmox-ve: 8.2.0 (running kernel: 5.15.149-1-pve) pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4) proxmox-kernel-helper: 8.1.0 pve-kernel-5.15: 7.4-12 pve-kernel-5.13: 7.1-9 proxmox-kernel-6.8: 6.8.4-3...
  3. S

    After upgrade to v8.2 black screen with blinking cursor

    Upgraded a r220 server that had Proxmox v7.4 installed to 8.2. Verified that pve7to8 was all green and then followed the official instructions. After the packages upgrade, checked the pve7to8 as stated that showed the following: # pve7to8 = CHECKING VERSION INFORMATION FOR PVE PACKAGES =...
  4. S

    local-lvm disabled

    Last week I added a new node to the cluster, and didn't notice it, but other node lost it's local-lvm in the process. I've made a cluster only for the convenience of managing them from the same address. When I noticed, this node had all the containers shut down and the local-lvm shows an...
  5. S

    Help! After 7.2-4 to 7.3-4 upgrade node doesn't boot

    Setting boot from grub rescue starts booting from the proxmox partition then:
  6. S

    Help! After 7.2-4 to 7.3-4 upgrade node doesn't boot

    I'm still stuck with this problem... Cloned sda1 & 2 from other working proxmox install, and logically now it complains that it can't find the os partition and goes into grub rescue. I don't know what else to do. Booting from install in debug: efiboot-tool fails:
  7. S

    Help! After 7.2-4 to 7.3-4 upgrade node doesn't boot

    After I upgraded to PVE 7.3-4 from 7.2-4 and rebooted my system now shows this error and doesn't boot. The boot partition only has a EFI folder and seems to miss a lot of things. Is there a way to recover this node? Like booting from a Proxmox ISO and doing any recovery/boot fix? Does anyone...
  8. S

    [SOLVED] Changed cluster node IP and now it's isolated

    So it finally solved by shutting down the 4th node and then rebooting the 1st node, that still hadn't been rebooted. The cluster formed again and by starting the 4th node I had it all running again.
  9. S

    [SOLVED] Changed cluster node IP and now it's isolated

    Also I'm experiencing so much lag whenever I ask for corosync restart or pvecm status. It's strange. I'm reading about IGMP Snooping on the switch, but It's not clear to me how it has to be configured. Specially the Querier part.
  10. S

    [SOLVED] Changed cluster node IP and now it's isolated

    Thanks for your help. The other three node where already on trunk configuration. It was only this node that initially all it's services where on an vlan and it was made like this. Anyways, ping works between all nodes. I had to add hosts entries for them to resolve names. Ping already worked on...
  11. S

    [SOLVED] Changed cluster node IP and now it's isolated

    I've changed the IP of one node in the cluster as instructed here, rebooted and now the node is out of the cluster and refuses to bring up any VM & CT. The steps I've done are: Backup of all VM/CT Informed the vlan tag in all the CT/VM. It was a vlan+ip change. Changed /etc/network/interfaces...
  12. S

    SSHD service disappeared from containers

    Seems that other things may be affected. I had one container that hosts a zigbee connector eating 4Gb of disk with syslog. The service had an error and It seems that is not rotating logs. Anyone?
  13. S

    SSHD service disappeared from containers

    Today, while trying to ssh login to one container, I received a connection refused message. The container was given a root password and a pub.key during creation. I accessed via tty from host and realized that the sshd service has completely disappeared. After that I inspected and found that 4...
  14. S

    After joining a cluster, internal storage is lost

    Ok, it seems after editing the config file underneath and waiting for it to sync I've managed to be able to unlock Datacenter->Storage and add the node2 storage. Still don't know if it's operative, but I'm now gonna take a nap :) Thank you very much @fabian for your help.
  15. S

    After joining a cluster, internal storage is lost

    Finally my main server storage was lost. So I installed Proxmox 7.1-8 on it, and recovered from backups. The process took hours because it was stucking installing (3% creating lvs, for example) After that, I finally understand what you told me and changed the local-lvm (and usb backup device)...
  16. S

    After joining a cluster, internal storage is lost

    I don't know what I'm supposed to do. On a brand new installation on core, that is what is shown: And I can't change anything bc they are read-only. core (node2): # cat /etc/pve/storage.cfg dir: local path /var/lib/vz content iso,vztmpl,backup lvmthin: local-lvm thinpool data vgname pve...
  17. S

    After joining a cluster, internal storage is lost

    Hi Fabian, thanks for your reply. And excuse, me for my lack of experience. I'm trying to move from another hipervisor solution and still don't know Proxmox enough. With storage.cfg files being different, what do you mean? Being on different machines aren't them supposed to be different? (I...
  18. S

    After joining a cluster, internal storage is lost

    I already have a Proxmox server. I've raised a new Proxmox server and before adding any service, I'm trying to add it as a node to the first one. So I copy the join info and launch it and it stays thinking. After some time I can see that in the background cluster info screen has appeared a...
  19. S

    Today, the server doesn't boot

    Thanks Marco. But the SSD it's mirrored to a conventional 1Tb backup disk that goes online for boot if required. (I'm not just born today ;)) Nothing changed from yesterday, it's also rainy. Isn't there any solution for repairing this without doing a livecd boot? It's nothing else possible from...