Search results

If you have server-grade hardware, you will have /dev/watchdog* interfaces. They even exist on low-end intel chipsets, most servers feature an integration to IPMI. A software watchdog would not make much sense, as they won't fire for most cases (but they exist). Try these: root@vm2021 ~ # dmesg...

Thats why I never use predictive network interfaces and switched to the old behavior (params: biosdevname=0 net.ifnames=0). I know why they are called predictive but actually, most automation tools work better with the old naming scheme. :cool:

I'm not exactly sure but can you edit the title? There should be a drop-down for that.

Die Config sieht in der Tat gut aus. Ob die Infos in der /etc/hosts sich damit decken, hast du aber noch nicht bestätigt. Sollte dort die IP und / oder der Hostname abweichen oder gar fehlen, werden keine Proxmox-Cluster-Dienste starten. Meldet "systemctl status" mehrere failed services?

Sure, no problem ;)

Depends. I don't generally recommend a change in hardware, just because there are problems with unknown cause. On the other hand, it might take weeks / months to understand whats happening there, which might resolve on it's own when switching hardware. IMHO I had lot's of broken HW RAIDs, card...

You can use iSCSI, SMB/CIFS, NFS, etc. - plenty options to choose from. It depends on what you want to do. If you want to use it for backups, NFS/SMB works perfectly fine.

That's also a safe solution. ESXi does not support mdraid or lvm, there you are forced to use a HW RAID controller. On most other solutions, software based solutions are available and most of them are equally or even better from performance perspective. You can also check if an update for...

LVM is very mature and light on ressources which is a requirement in this scenario. If you have a larger machine where you have some spare RAM, give ZFS a go. It's resilency is great but it needs to communicate directly with the devices (that's why a RAID controller is not suitable). Also, ZFS...

Yes, never use ZFS with RAID controllers, only with HBA.

Ok, you definitely lost access to your storage backend which holds the OS. Did you install directly to disk or did you install proxmox to a flash drive which the server boots?

But both in a proxmox cluster and add a third node (old pc also running proxmox, no vm's). This way you get a fully working HA cluster and you can backup/recover/replicate between them very easy.

What do you mean? I operate lots of ceph clusters, ZFS pools and LVMs. I like ZFS a lot but if the owner runs a raid controller, ZFS actually is a very bad idea, as it is supposed to break on such setups.

Das bedeutet nicht das die frei ist, sondern nur das nichts auf ICMP reagiert. Das ist quasi die Standard-Sperrregel jeglicher Firewalls. In den meisten Fällen kann man von Linux besser arp-scan / arping verwenden - auf ARP antworten nämlich die meisten Geräte trotz Firewall. Stell doch zum...

You can try "dmesg" on your console (might work) when this happens.

ZFS is not much different to mdraid/LVM in that case, as both are no cluster-optimized filesystems. I would go with LVM if it's a RAID controller and ZFS if it's just an HBA. ZFS has send/receive to clone data which is cool.

Ok, I am confused, you miss the "auto" directives and have your IP duplicated, that can't work. According to your log, eno1 is your mlx adapter.

Are you sure it works this way with /32? I would expect a small subnet or the "pointopoint" (no typo) directive pointing to the other node.

Da du dich im lokalen Netzwerk befindest, findet dein Router gar keine Anwendung. Wie hast du das zuvor nachgesehen? Zufällig nur mit "normalem" ping?

Do you run one or multiple hosts?