Recent content by dafydd

I've seen the same issue on a Dell R340 - it was failing to find or load megaraid_sas. So it failed to boot further and went into busybox (unfortunately I didn't get a screenshot of the errors before rebooting).

Check the wiki docs here - https://pve.proxmox.com/wiki/Host_Bootloader You can unpin with proxmox-boot-tool kernel unpin

I had the same issue with a Dell server, it couldn't boot up and complained about a missing megaraid module. You can pin the previous kernel with the following command which sets the default kernel in grub. proxmox-boot-tool kernel pin 5.13.19-6-pve

The error goes away when I remove the gateway on eth1. For some reason when I tried this before, it didn't appear to work e.g. the second IP didn't appear to be routable. But it works now anyway. Edit: Unfortuntely the MAC address flip-flopping is still happening.

I have a Proxmox v6 server (not quite ready to upgrade to 7 on this server yet). I've setup a new CT with a Debian 11 template. I then added a second IP address on eth1, using the same gateway. This all works, with the second IP working and visible. But 'networking.service' is showing as...

Thanks for that! An upgrade to 6 is my next step but the plan is to move everything off the other server so I can install v6 from scratch on that box.

P.S. Stopping one other container stopped it but it failed again after re-starting the CT. I then experimenting by stopping another container and after re-starting, it still gave this error Oct 16 18:45:00 devhost pvesr[19771]: Unable to create new inotify object: Too many open files at But a...

I have a server running 5.4-13 with the latest packages. It has 24 containers running on it. I've been migrating some older openvz containers to it, and they all are up and running and visible in the web interface. Shortly after starting up a newly transferred container. I was unable to run pct...

I had the same issue with a brand new server and new install of PVE 6 - short session timeouts and " notice: RRDC update errors" Both problems stopped as soon as I created the first CT.

I downloaded an lxc 6.10 image and did some diffs between that and my filesystem. Some of this information is documented in a few places but probably not for a openvz->lxc conversion. So here are the steps I needed to get it working: 1. Edit /etc/rc.sysinit to remove /sbin/start_udev 2. Edit...

Did anyone ever find a proper fix for this one? It's pretty annoying. The CentOS 6.3 template works fine but once you upgrade to later versions it breaks SSH logins. I'm currently on 6.10 I've tried the other suggestions e.g. commenting /sbin/start_udev but that makes no difference. This...

Yes, my option 2 would use mountpoints, but I would like to keep all the data for one container all together so they can be migrated easily or backed up in one file. In the old setup I had symlinks in /home/$user which would link to /var/lib/vz/ABC/dir but I can't get Samba 4.5 to work with...

Thanks. This probably isn't the solution for me. Having searched in various places, I think there are two solutions: 1. Create containers with directory storage (effectively size=0), as mentioned here...

I am running Proxmox 3 for our internal development and really need to upgrade to Proxmox 5 but it looks like it's going to be problematic. I'll describe how I run it and would like to know if this is even possible on version 5. Each developer gets a few containers that run different...