Recent content by stark

Looks like the Intel ixgbe has been updated to support kernels through 5.6: https://sourceforge.net/projects/e1000/files/ixgbe%20stable/5.7.1/

Thanks for that. I have certbot already running on a separate host grabbing wildcard certs and was manually copying them over to my proxmox nodes. With ACME running now on proxmox, I don't have to do that any longer. I'll just stick to regular certs for my proxmox nodes.

Perhaps it’s having trouble with the spaces after the equal sign?

That's a pretty amazing increase. I did a quick iperf2 test before and after and the results were similar ~ 9.86Gb/sec for each one. No massive increase for me.. :( :)

Thanks for the patch! I'm going to give it a whirl.

Try removing any quotes and just use DO_API_KEY=123456. I had to do that to get it to work with he.net.

You mean that it doesn't build with Proxmox 6.2? Yeah, that's unfortunate but we'll have to wait on Intel to update their driver to work with kernel 5.4. I'm hoping that it won't be too long. Until then I'm going to force myself to put up with the errors.

Just set up ACME using DNS and it's easy mode! Looking forward to not having to copy my wildcard certs to each proxmox node when the old ones expired.

I hand out ipv6 dns servers via radvd.

I would install the latest version of Proxmox. I run a small cluster at home with intel X56xx processors and everything runs really well. Personally, if I had your gear, I would take the 3 or 5 of the newest machines and build out a cluster - maximizing ram and drives per host. Unless your...

To display a list of messages: ceph crash ls If you want to read the message: ceph crash info <id> then: ceph crash archive <id> or: ceph crash archive-all

I see the same thing - Proxmox dash showing all memory used but when I go into the VM, I see that only 2GB is used but the rest is used for caching which I would totally expect. So from the Proxmox host's perspective, all ram is indeed being used. Seems at least on my setup, it's working as...

You're looking for: To display a list of messages: ceph crash ls If you want to read the message: ceph crash info <id> then: ceph crash archive <id> or: ceph crash archive-all

you should be able to use vgs to see what free space there is for the pve volume group. If there's free space, you would use lvextend to grow root the desired amount and then use resize2fs to resize it. use lvdisplay to see what the path is for your logical volumes. man lvextend man resize2fs...

A lot of times a simple "dd if=/dev/sdg of=/dev/null" can help narrow down which drive it is. Even if a failed drive has been deleted by the OS, working drives will still help narrow down the bad drive.