I am not sure how they were killed off but I tried to restart them and its a no go. Suggestions? I need to be able to backup the containers. This is my first experience with Proxmox and I hate it. It is going to drive me to insanity.
I understand. I would like to get updated. I started this new admin job and found that proxmox 3.x running on only one node and I have a rather large ZFS file system. Will I be able to preserve this ZFS during the upgrade? Right now, it is looking dim because I cannot get the pve services...
I noticed this as well:
root@ilsbnode2:~# dmesg | grep -E 'SPL:|ZFS:'
SPL: Loaded module v0.6.5.7-3_g8455153
ZFS: Loaded module v0.6.5.7-8_gf1b07c5, ZFS pool version 5000, ZFS filesystem version 5
root@ilsbnode2:~#
I am having the same issue.
root@ilsbnode2:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
ceph-common glusterfs-client glusterfs-common librados2 librbd1 python-ceph tar
The following...
I recently started working at a location that uses Proxmox 3.x with kernel Linux ilsbnode2 2.6.32-48-pve #1 SMP Fri Nov 25 06:28:35 CET 2016 x86_64 GNU/Linux. There are several openVZ containers. There is just one node. There is a ZFS filesystem. Since the system was built, the ZFS file system...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.