Search results

Thank you very much for your prompt and insitefull reply, you were correct esp partitions were full :) Also very sorry it took so long to post my results here, especially since i received help so quickly. However it was a very busy week and i finally got a chance to fix this issue. I mainly...

I did a dist-upgrade today and it popped up a dialog box you know the blue grey and red type it contained some information about grub2 (sadly i did not take a screenshot) and this dialog box asked if i wanted to continue of course i said yes. Then i got an error about not being able to write to...

Ok thank you very much for helping me make matter is very clear as i can see below now. So i will continue to use datasets knowing it is the same a proxmox defaults as you described. NAME PROPERTY VALUE SOURCE apool/subvol-101-disk-1 type filesystem -...

Ok thank you very much for the info guess i will keep using datasets then? Just curious seems like Proxmox uses zvol when adding a mount point to LXC containers or does it? Yes i plan to use a LXC and a mount point to do my SMB sharing was just trying to use zvol for mount point instead of...

I guess i could create a dataset, and that would be alot easier as i used to do it that way, but i think zvol is superior for speed/overhead and versatility maybe im wrong there, thinking proxmox uses zvol for good reason. The reason i would like to have it named mypool/share is i will be...

Hello again all i am interested in Proxmox way of adding a mount point to a lxc container, using the GUI works, and i a can easily add a mount point but it always creates a new zvol and gets named something like /mypool/subvol-100-1 My question is what if i want to create a zvol called...

This is what i found on some Ubuntu post somewhere, and it works for me on Ubuntu 16.04 LXC containers chown syslog:adm /var/log/syslog chmod 644 /var/log/syslog

Hello i am running ZFS here and not sure if this is ready for ZFS yet ?? noted a couple of changes along with moving the 40network file out of the way which i did have to do. during Step 1 "3. You should add a few lines into LXC container config before it first start: lxc.aa_profile...

I have updated Proxmox a couple of times see below but still cannot get spice working, does spice work in proxmox 4? pveversion --verbose proxmox-ve: 4.4-78 (running kernel: 4.4.35-2-pve) pve-manager: 4.4-5 (running version: 4.4-5/c43015a5) pve-kernel-4.4.6-1-pve: 4.4.6-48...

Hello again all i am having trouble getting spice to work Keep getting error Unable to connect to the graphic server ...some local file... socket I/O timeout I have Proxmox installed and completely up to date pveversion --verbose proxmox-ve: 4.3-72 (running kernel: 4.4.24-1-pve) pve-manager...

Ok sorry i did not realize that, could have sworn that my OpenVZ containers always got backed up correctly with all files as default. Also would like to apologize for my last post after a reread i realize i was quite frustrated and did not mean to come across quite so angry Sorry

WTF Proxmox never used to do that, this has caused me alot of problems a warning would have been nice ... Its ok now that i found out a bit late and potentially catastrophic. I am sure Proxmox has included this seriously not cool default setting for a reason? but as far as i am concerned...

This seems to have corrected itself at least for me with the latest kernel update ... i have my external USB 3.0 drives importing again

I have a similar issue, I had to do a full shutdown, and my external USB enclosure containing a couple of drives did not import or get mounted. Now every time i bootup that pool is missing and when i try to import or even zfs status the command hangs forever and the proxmox GUI goes strange...

I have upgraded to version 4.2 and still have issues with lxc backups excluding some important files, is this going to be fixed? or do i need to adjust my system to get full backups of lxc machines

Is this fixed yet, really sucks not having backup and restore function be reliable in the GUI cost me at least a couple days of my time NOTE i'm using enterprise version here

I am having a few issues with version 4 too however had not had much time to do testing or prepare a post to the forum but i will

Thanks Dietmar, and i was just reading through the v3x to v4x upgrade documentation and will be doing the upgrade ASAP

During backup i get this error, it does the same for a snapshot or suspend the only way i can get backups without error is to use the stop method ... oddly only some openvzs not all INFO: starting new backup job: vzdump 101 --remove 0 --mode snapshot --storage bpool-dir-2 --node pve-1 INFO...

Hmm this is super annoying problem, and causes me alot of grief, is there really no solution?