mir's latest activity
-
mir replied to the thread Upgrading to pve-9.1: apparmor.service.Hi, This is the result: # find /etc/apparmor.d/ /etc/apparmor.d/lxc -maxdepth 1 -type f -exec /sbin/apparmor_parser -N {} \; ch-run /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/connman/scripts/dhclient-script... -
mir replied to the thread Upgrading to pve-9.1: apparmor.service.Reported on the bug tracker: https://bugzilla.proxmox.com/show_bug.cgi?id=7203
-
mir replied to the thread [SOLVED] Connecting a Open Media Vault Server as storage.If you check the Advanced box what version of NFS do you see? I guess you see 'Default' which is NFS version 3. I am pretty sure OMV uses NFS >= 4.0
-
mir replied to the thread Upgrading to pve-9.1: apparmor.service.apt reinstall apparmor libapparmor1:amd64 Summary: Upgrading: 0, Installing: 0, Reinstalling: 2, Removing: 0, Not Upgrading: 0 Download size: 755 kB Space needed: 0 B / 3,915 MB available Get:1...
-
mir replied to the thread Upgrading to pve-9.1: apparmor.service.Thanks. Got this result: conflicting flag values = nvidia_modprobe 4097nvidia_modprobe//kmod , 1 conflicting flags in the rule Running the command a second time: conflicting flag values = notepadqq 4097, 1 conflicting flags in the rule Each...
-
mir replied to the thread Upgrading to pve-9.1: apparmor.service.pct start 103 --debug Has this interesting info:
-
mir replied to the thread Upgrading to pve-9.1: apparmor.service.Could it be related to this old bug? LXC container fails to start without any reason
-
mir replied to the thread Upgrading to pve-9.1: apparmor.service.It seems the problem is a lxc container with a mount point which is causing the problems. Attached is the debug log from starting the container like this: lxc-start -n 103 -F -lDEBUG -o /tmp/103.log
-
mir posted the thread Upgrading to pve-9.1: apparmor.service in Proxmox VE: Installation and configuration.What does the following mean? $ sudo systemctl status apparmor.service × apparmor.service - Load AppArmor profiles Loaded: loaded (/usr/lib/systemd/system/apparmor.service; enabled; preset: enabled) Active: failed (Result: exit-code)...
-
mir replied to the thread [solved] upgrade from pve 8.4.16 to pve 9.1 failed.The devil surely is in the details ;) The little pin which made the castle crumple was the following: A mount flag on the root partition which apparently triggers a regression in systemd-remount-fs.service. It fails if the following mount flag is...
-
mir replied to the thread [solved] upgrade from pve 8.4.16 to pve 9.1 failed.Pinning 6.8.12-17-pve for now until hopefully someone finds a solution. proxmox-boot-tool kernel pin 6.8.12-17-pve
-
mir replied to the thread [solved] upgrade from pve 8.4.16 to pve 9.1 failed.I have tried these kernel also with same poor result: proxmox-kernel-6.14.8-2-pve-signed proxmox-kernel-6.14.11-5-pve-signed proxmox-kernel-6.17.2-1-pve-signed BTW. AMD Opteron(tm) Processor 3365 does support aes: lscpu |grep aes Flags...
-
mir posted the thread [solved] upgrade from pve 8.4.16 to pve 9.1 failed in Proxmox VE: Installation and configuration.Hi all, Trying upgrading my server from 8.4 to 9.1 but after the upgrade the server fails somehow and starts the server with root in ro mode. Starting same server with the 8.4 kernel and everything works as expected. Old...