Search results

Today I ran in to a similar issue where Proxmox hang at during boot. Syslog statet: Since this is a supermicro server-board with IPMI, sr0 is the remote-media virtual drive where I forgot to unmount the image. I had mounted the remote media from a temporary cifs server wich wasn't reachable...

This is obviously not a Proxmox issue alone but general design issue of cifs and nfs implementation. https://stackoverflow.com/questions/18085868/attempt-to-access-remote-folder-mounted-with-cifs-hangs-when-disconnected/19101647

Not only does this bug hang just this backup, this bug slowly kills the host kernel until after a while the entire host is dead because the cifs module somehow stops execution of the kernel itself. I also reported here...

Have the same trouble with my lab servers doing offsite-backups via unreliable connections. If cifs sees fluctuations the kernel is blocked by the hung cifs module entirely. Leaving the server alone a while it doesn't even respond to network traffic anymore. CIFS totally locks up the kernel...

I had to go back to the e1000. In my case under FreeBSD and years later, virtio does not function properly. See proto://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 Neither pfSense nor Kali Linux. VirtIO cost me weeks in debuggig webservers, analyzing tcp packets in deep and ping. Sadly the...

I had the same issue recently when i reinstalled a slave node. It was then not possible to ssh-copy-id the key from the new node to the cluster master. When executing on the new node: wich is the error pvecm add complained internaly. I got it working with the following steps on the cluster...