Probably the easiest (assuming this is VM and not container) is V2V conversion using clonezilla. So basically create a similar configured VM with slightly larger HD size on your target VM (in this case vsphere), boot both machines with virtual cd of clonezilla, and do disk to disk clone over...
You can also try dpkg -P (packagename) to purge old kernels:
#dpkg -P pve-kernel-4.13.13-1-pve
As for updating, I now recommend doing apt-clean first (to clear out old temp files under /var/cache/apt/archives)
#apt clean && apt update && apt dist-upgrade
Would storage replication be an alternative option?
"Replication uses snapshots to minimize traffic sent over the network. Therefore, new data is sent only incrementally after an initial full sync. In the case of a node failure, your guest data...
For some x86 configurations, USB install doesn't work. I would burn to disc and use PowerEdge 860 CD/DVD reader. If none is available, you can use external USB CD/DVD reader (about $20 U.S. on eBay or Amazon). The other option is to install Debian stretch, and Proxmox on top of that...
IIRC ProxMox is preconfigured OOB to timesync to time server. Any VM/CT created will use the same time as the ProxMox server. So make sure you set the correct timezone for your Proxmox server under Proxmox gui > datacenter > yourproxmoxservername> time...
This page should help:
Config info stored here (make sure to backup this file before changing anything)
You can also try shutting down everything, boot NAS/NFS server first and wait 15 minutes to settle down, verify you can access the...
Those of you with qcow2/NFS/Virtio combo and getting corruption, could you also test if the corruption happens with a CIFS/SMB share on the NAS? I was just curious if the type of share has any effect.
I also think it may be a hardware issue, or possibly your UPS battery may need replacing. Several years back I had an old PowerEdge T300 server rebooting with ProxMox. First thing I did was replace the power supply (and CPU/Case fans for good measure) and it's been stable since. Another time a...
Have you tried this? I noticed in the video he used "update-grub" as the last step.
I would also try running dmesg -T to check log for drive errors within last 2 days, and smartctl -H on all your drives
If you have a lot of memory (at least 16gb), another way is to create a ZFS pool. However expect 50% of your memory to be dedicated to ZFS, with the rest allocated for VM's
or you can follow my notes below:
Proxmox : Add a 2nd hard drive to ProxMox node for iso/images/templates/backups
Backup your existing VM’s/VM Data outside of the ProxMox node just in case
Install the 2nd Hard Drive...