I have two servers, both with 2 drives, 1 SSD and 1 Spinning disk.
Right now I have them setup with VMs and containers running on the SSDs and the HDDs used for backups. This works fine for our needs as it's mostly stuff for our office running on them and a hour or so of downtime during...
I've modified the systemd config file so the watchdog timeout is 10 seconds. That seems to limit the delay to about 10 seconds, so I'm going to use that as a work around for now.
I'm not sure why you think I'm calling the netboot functionality and the pulling of the IP on boot the glitch. I think what I wrote is pretty clear that I now think that part is normal.
The glitch was after the first install I could not get an IP change to work. I tried changing the interfaces...
So it turns out that this server supports net booting with no os installed and the EFI is by default pulling an IP. I loaded the latest EFI update and it still does that so I think it's normal. Now why the IP set for Proxmox/Debian would not work after the machine booted I don't know. I think...
Interesting. This server had ESXi on it previously. Maybe it tweaked something in the EFI that is pulling an IP. I'll have to play around with it some more and see what happens. For now I have it set to static and also have a static lease for the same IP setup for it in the router. Seems to boot...
So I reloaded and setup the work IP during the install. I added that subnet to my home router and it does work on that IP now.
The weird thing is I still see the lease created in the router at the grub screen even though I did not setup dhcp anywhere. Once the server is up I cannot ping the...
So after a little more playing around, it seems that the server is pulling it's IP at the grub boot screen. I looked through the grub config file but there's not much there. At this point I think I may just reinstall from scratch to see what happens if I set up a static during the initial install.
I setup a new Proxmox 5 install on my home network with DHCP. After verifying I could log in to the web interface and ran updates I set the IP to static shutdown the server and took it to work.
At work I logged into the ip that was on the home network updated it to match the work network and...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.