Recent content by dw2412

Why not creating a script in /etc/networkd-dispatcher/routable.d that contains the routes. By this you're still able to update the ip adress from the gui and still have you static routes defined... I just did in Ubuntu 18.04 and it works great. Andreas

Hi Stoiko, some time passed by already - I've updated now to latest pve-manager/5.2-11/13c2da63 (running kernel: 4.15.18-9-pve). The reported issue is unfortunately still the same. If there is more info needed please tell me what you need and I will try to prepare it for you. Thanks Andreas

After last week being on holidays I got some info from my collegue about what he did and thought to have solved everything. Well actually what he did helps a bit but does not solve the issue entirely. The "solution" was to set all containers to unconfined apparmor profile. Doing a reboot and...

Is there a chance that it contains privacy related informations (passwords / ssh keys)? If so please give me another way to provide you the debug infos that does not result in releasing this info to the public... Sorry - none available... :-( Yes. I would say so... I did it in bash script 20...

Hi Even they seems to be outdated because of mentioned Proxmox Version... They way is still the same. You've plenty of options to migrate such a VM to Proxmox. Either direct by converting the image using qemu-img or by starting in both (old virtualbox vm / now proxmox vm) some boot image (i.e...

kworker according to top is at (around) 100%. But instead of zfs lvm-thin is being used. No. Just tried it, after first shutdown of container with single iptables command issued occured no other container could be started. Only thing I can say from this is that first start works (as...

Dear technicians & Proxmox devs, lets start it this way - I think I've found an issue and I'm more or less out of ideas on how to continue debugging / solving the issue at all. In use: Proxmox 5.2 details: proxmox-ve: 5.2-2 (running kernel: 4.15.18-5-pve) pve-manager: 5.2-9 (running version...

Hi Proxmox Team, it seems that the aacraid module update introduced incompatibilities with older Adaptec Controllers (namely AHA5805). I've had a look at Adaptec / Microsemi homepage and they don't mention this controller anymore being compatible with their aacraid source. Problem can be...

Hi all out there, today it happened again - I've found out some strange behaviour in Proxmox 4 with LXC Containers. Container is running Ubuntu 14.04 LTS all updates applied, Node is running Proxmox, all patches applied: proxmox-ve: 4.2-54 (running kernel: 4.4.8-1-pve) pve-manager: 4.2-15...

Without big wish to make this issue more wired... I've Proxmox 4.2-5 running on my DL180 G6 with firmware O20 build on 07/01/2013. In case raid controller might be an issue. In system Smart Array P410 with FW 6.64 is used with hpsa module. Only wired thing I experience with Proxmox 4.x is that...

Edit /etc/initramfs-tools/modules file. Add each module you need to load and run update-initramfs Works only when you have a working system. Since your system doesn't seem to boot at all you have to boot with some rescue cd, mount all your devices in some folder, chroot to the folder, do edit...

What about adding the module mentioned in your photo into initrd image? Seems that modules cannot be found in initrd that are needed to find the pve vg and start the root volume.

Re: poblem with fresh installation of proxmox 4 with adaptec maxview (can't access it Hi Vigilian, this pam_cracklib.so error is the problem why you cannot login to adaptec maxview. They ship a wbem pam.d file that contains reference to pam_cracklib. The pam_cracklib can be installed on Debian...

Re: poblem with fresh installation of proxmox 4 with adaptec maxview (can't access it Just open /etc/pam.d/wbem and comment out line with pam_cracklib. Andreas

ack... did as requested.