Search results

But through the GUI the error still occurs?

And /usr/sbin/pvesm status --storage nfs-iso tells you what?

So the nfs issue is solved, then? I suggest to open a new thread for the OS issues since people tend to not look in long threads after a while.

There's no „easy“ way to share folders between a VM and the host in the way it's possible with CTs. You have to provide the folders via NFS or CIFS (don't mix!), or maybe iSCSI to the host in order to grant the CTs access to it.

Did you open the vdmk file in VMware like suggested?

You can just replace the node. Maybe set the OSD flags to noout, nobackfill before but Ceph will handle the rest. There's enough documentation on how to detach and destroy OSDs, but it doesn't matter if you do this while they're in or out. Same goes for the node itself.

You're learning it the hard way, then. That's very honorable. Hope you don't loose too many years with it. :D I guess it wasn't you who decided to switch to Proxmox? ;) But back to topic: Please execute the problematic command on pro07 and see if there are further information on the command...

Ich würd halt kein Consumer-Zeug für nen Server kaufen, aber das ist deine Sache. Welchen CPU-Typ hast du bei deinen VMs eingestellt? Falls da nicht „host“ steht, ist es schonmal überhaupt kein Problem. Falls doch, kann es dennoch funktionieren, die Maschinen einfach so zu starten...

Auf welchem Wege wurde iobroker gebackupt? Vermutlich kann proxmox damit nix anfangen, aber evtl. lässt sich etwas konvertieren.

Maybe it has to do with Administrative Native VLAN tagging: enabled? I don't see an Operative Native VLAN tagging stanza, so maybe this is a problem for vmbr0.

I really much would like to help you further, but I don't see an error in the proxmox files, since this is exactly the way it works for me. I still guess that this is a configuration issue.

I don't, I'm trying to help objectively as possible. Otoh, as one calls into the canyon, so it echoes back. There are a lot of Proxmox fan boys here (including me). Ranting (yeah, you might call it differently) about their beloved hypervisor when the error seems to be on the user side, is a bit...

And Dell pays for corrupt data if SHTF? The disk surely won't report errors because it's bored. If this is a production server there's no way that anyone should gamble on the drive failing or not. It started to die, it gets replaced, it's that simple. Could be a good day to not invest 1.000...

Getting this ssh stuff right was definitely important, but maybe the real culprit is yet to be found ... Please execute the problematic command on pro07 and see if there are further information on the command line as well as in journalctl. /usr/sbin/pvesm status --storage nfs-iso

My interfaces file looks exactly like yours, the only thing I added is bond-lacp-rate fast in the bond, but I doubt that this would break the vlans. Are the vlans also on the trunk to pfsense in order for the VMs to get an address?

Since you ranted about proxmox I was wondering if you never encountered problems with vmware. Every system has its quirks.

Some stuff in the GUI actually uses ssh that's why it's important that every node can access every other node through ssh. If you're in doubt you can even add every id_rsa.pub to known_hosts once again. But after that your issues with the storage in the GUI will most certainly be gone.

Okay, so that's 99.9% not a problem on the proxmox side. Unfortunately, I'm no Cisco expert either but if it works with a single nic it should also work with a bond, especially since we checked your config, which looks fine (probably even with bridge-pvid!).

If you rebuilt the node then probably the ssh keys did change. Enter that in one of the other nodes: ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R pro07 ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R "10.0.0.76 and that on pro07: echo ~/.ssh/id_rsa.pub >> /etc/pve/priv/authorized_keys in order to get...

Does the VM on vlan 5 get an address from dhcp? Do you try to reach it from a computer on vlan 5 or from the proxmox host? Did a reboot of the host solve it?