Recent content by bmcgonag

Ok. I'll see what i can do.

I have a few VMs that are setup with a ZFS Pool, or part of one as external storage (USB Drive Bay). I'm trying to migrate the VMs to a new server in my cluster, but when I did this using Backup / Restore, it did allocate the storage, but to the same physical drive. I'd really like to put the...

Anyone have anything else I might check? I have now set both Proxmox VE servers up to be exactly the same as far as /etc/network/interfaces (except IP Address of course), and set their /etc/resolv.conf to be the same, and ensured other than their hostname itself, that /etc/hosts and...

Yes, they all use the same gateway. No, also can't ping the router from inside the guests, but I can ping external sites like google.com and 1.1.1.1 from inside the guests. I have pulled the `ip route` information from this host (aria) and my other proxmox machine host (bia) to compare. I've...

No, I can't - odd. Yes, and have now double checked all rules, None for outgoing, only for incoming, and only to port forward to my NGinX Proxy on a completely different machine. The Node Firewall showed 'Yes', but no rules were setup, so I turned it to 'No' in the web ui, and also ran the...

Yes, just a copy/paste mistake, it is "search" New order: search mcghome.localdomain nameserver 1.1.1.1 nameserver 1.0.0.1 nameserver 192.168.10.1 Ping Results after change: root@aria:~# ping 192.168.10.34 # separate machine PING 192.168.10.34 (192.168.10.34) 56(84) bytes of data. 64 bytes...

I'm not sure when this happened, but I've noticed that in attempting to update my host, it couldn't reach the repos. I then found that it simply can't reach the internet at all, but all of my VMs / CTs can. I can reach the host internally on my network via SSH and the Web UI. I have checked...

Having the same issue. # If you want to manage parts of the network configuration manually, # please utilize the 'source' or 'source-directory' directives to do # so. # PVE will preserve these directives, but will NOT read its network # configuration from sourced files, so do not attempt to...

I now have 2 CTs that I want to remove, but have gotten this error on. I'm not sure why I'm getting it. 1. I had VM 103 (LXC container) on a SSD Logical Volume called "CTs". I got this error, and through a bunch of forum threads, just got nowhere, and ended up trying to simply remove the CT...

Wow, ok. Good to know, and thanks for the great information. I'll look for a better drive in the future for sure.

I moved it to a USB3 for certain. It shows read speed 120 MiB/s, and Write 35 MiB/s - still seems quite slow to me.

=== START OF INFORMATION SECTION === Model Family: Seagate BarraCuda 3.5 Device Model: ST8000DM004-2U9188 Serial Number: ZR11XF45 LU WWN Device Id: 5 000c50 0dc66b8a8 Add. Product Id: DELL(tm) Firmware Version: 0001 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes...

I was noticing it was seeming very slow. Not sure why actually. Maybe, it wasn't an overly expensive drive by any means. I thought the same for the USB port, I'll double check it and see if it makes any difference.

Just bumping this, wondering if there is any thought on why it would be failing every time? Additionally, wondering if I can manually backup the VM(s) with something like rsync and 7Zip?

Good day. I have a couple of VMs up and running, and one of them backs up fine, but one has failed every time. I have an 8 TB drive connected via USB to the Proxmox Server install itself, and added as storage in DataCenter. I have setup a backup job of a VM (101) which is Ubuntu 20.04...