Search results

Thanks. I did indeed have that exact latest version you linked to. I noticed that even when downgrading, the memory consumption rises again to 10GB with a VM that does nothing. Full Virus scan can back negative, its a Win10 Enterprise version 1803. This problem might not be related to the...

These are the details about the 2018 version I am having problems with: http://take.ms/8QKSh This is the old working one: http://take.ms/abeCM

I recently found a newer version as I was running an agent from 2015, have a look: http://take.ms/boW0a So after replacing the one from 2015 with the one from 2018 my memory consumption as reported within the guest (Win10) jumped straight to 10GB out of 12GB. After deisntalling and installing...

Problem solved and it had nothing to do with Proxmox. The problem was between me and the host. Basically, they provide me with a value pair of name and server and I'm supposed to figure out that the name is not the export name but the server name and the server is not the nfs server but my...

while the check_connection function was commented I tried again adding this storage via PX GUI and am getting: I just tried manually adding this NFS storage again via Proxmox GUI and am getting: create storage failed: error with cfs lock 'file-storage_cfg': mount error: mount.nfs: requested NFS...

I talked to the support from my hoster and he pointed me in the right direction. He showed me this old post from 2013 which talks about the short timeout of 2 seconds which PX checks the NFS connection for: https://forum.proxmox.com/threads/nfs-shares-storage-is-not-online-500.11121/#post-69878...

For the time being, I have mounted this NFS share via /etc/fstab like this: # mount backup storage via NFS ftpback-rbx7-XXX.ovh.net:/export/ftpbackup/ns312791.ip-188-XXX-XXX.eu /mnt/nfs-backup-storage nfs soft,retry=5,timeo=60 but I'd like to solve this mystery. I'm open for any pointers.

it feels like I have read all threads here on nfs and tried all those solutions to change from nfs 3 to nfs4 and try via udp but nothing works via PX GUI. I tried using the nfs server IP instead of the server name and I tried changing my name servers with no change.

Well, since its a new setup, I have since reinstalled PX completely to make sure I didn't screw up anything. I just checked the logs you mentioned and: syslog only keeps saying: Oct 1 11:38:32 jarvis pvestatd[2925]: storage 'local-nfs' is not online Oct 1 11:38:42 jarvis kernel: [...

anyone got an idea what else to check? I would like to add the storage via PX GUI vs mounting it manually :-(

@thomas, thanks for the elaborate answers. Everything is as it should be right now and you were spot on: I am using the provider's template because getting access to a KVM is expensive and manually mounting a custom ISO is a lot of work...

I added a NFS share that my server provider offers as backup space, via the proxmox GUI, and it worked. A few days later it shows in proxmox as offline, with error 500. If I access this proxmox server via ssh and execute: mount -t nfs...

Thanks for explaining. I have taken the following away from your explanations: - there is always a "local" storage so I'll use it for everything except my VMs which should reside on the local-zfs storage as that will enable me to do snapshot backups. - noted your comment on the node, I had...

It turns out the default profile is inside the letsencrypt staging directory so I followed the instructions to switch and forced a cert renewal and it works :-)

Brand new isntall of Proxmox, latest 5.x as of right now. Followed this guide: https://pve.proxmox.com/wiki/Certificate_Management and everything worked as detailed in that guide except when accessing my proxmox GUI via https://mysub.deomain.tld:8006 my browser still shows the old fake...

Hi there, I have used Proxmox before and I have used ZFs before but never in combination. I have read all the Proxmox Wiki pages about ZFS on Linus and storages and am even more confused now. I have installed Proxmox 5.2-9 via a Soyoustart template(64bit and ZFS) - I ended up having ZFS as my...

Today, I am getting a similar error, shall I jsut go ahead and wait for kernelcare to catch up with proxmox kernels or do I need to do anything? Unknown Kernel (debian 4.4.117-1-pve)

Thanks, you gave a lot of good pointers. I jsut wanted to quickly clarify why I mentioned a 3rd party tool: veeam agent for linux can do a full machine backup which can be restored onto completely different hardware. Hence my question if it could be used to transform LXC into KVM. On the other...

I have a SED compatible server but the hosting company can't guarantee SED capable disks. They said its highly likely I will get some when ordering but not guaranteed. Btw. is this correct: - so an SED-capable mainboard/bios + HD will do the encryption no matter what OS is running on the server?

Ok, so say I have 5 disks, I install PVE on1 disk, then create a LUKS device for each of the 4 other disks will I then be able to use ZFS to create a raid out of these 4 disks or am I losing some of ZFSs functionality since it is not accessing the underlying HDs directly? Also, am I right in...