#error500

  1. R

    Nod3 HS - Cluster : Hostname lookup 'nod3' failled

    In my test simulations, I intentionally crashed the nod3 on a 3-node cluster to simulate the definitive death of node 3. I completely reinstalled the nod3 so that it is like "new" and virgin. With the new name 'nod3b' and a new IP address. My VMs have their disk on CEPH. The goal of the game is...
  2. C

    [SOLVED] Node 1 Down in Cluster Can't turn on VMs on others

    Hi Proxmox community, Still new to Proxmox but was wondering why it is that if I am adding multiple nodes into a cluster they start acting like a legitimate chain and that if one goes down the entire chain breaks. I am working on two nodes for testing different filesystems and virtual machine...
  3. P

    [SOLVED] Peer/Cluster Communication not Working

    Hi, I've setted up two Proxmox Servers in my home lab, each one running in a distinct physical server, but can't ping each other, neither join the same cluster. Both PVE can: Ping the gateway (192.168.15.1); Ping outside ips (8.8.8.8) Ping other devices in lan; Receives pings from my own...
  4. D

    ZFS Pool Not Found Error 500

    Last year create ZFS pool - local-hdd 2021-09-10.19:57:15 zpool create -o ashift=12 local-hdd /dev/disk/by-id/ata-ST500LM021-1KJ152_W62BB0MS 2021-09-10.19:57:20 zfs set compression=on local-hdd 2021-09-10.20:18:06 zpool import -c /etc/zfs/zpool.cache -aN 2021-09-10.20:35:11 zfs create -V...
  5. D

    zfs error: cannot import 'raid1': no such pool available (500)

    Many months agao created a zfs-pool `local-hdd` 2021-09-10.19:57:15 zpool create -o ashift=12 local-hdd /dev/disk/by-id/ata-ST500LM021-1KJ152_W62BB0MS 2021-09-10.19:57:20 zfs set compression=on local-hdd 2021-09-10.20:18:06 zpool import -c /etc/zfs/zpool.cache -aN This is the output of zpool...
  6. M

    [SOLVED] New Proxmox - NFS Error 500

    I just installed Proxmox 7.1 I access the web, I add NFS storage, when I put the IP of the NAS (Synology) the shared folder appears. Adding gives a 500 error. All that appears on many websites is that this error is a permission error on the NAS. I have checked the Synology NAS several times...