Hello Everyone I've run into quiet an interesting problem. I recently wanted to rename my Proxmox to match my homes Networking Naming scheme. I made the change in the Web GUI Shell on Proxmox and simply did the reboot command from the terminal. The Server rebooted and I verified it was turned on as I have a keyboard and monitor attached to it currently. I am presented with black screen with just Proxmox login: with a blinking cursor. I didn't see the usual Welcome screen you'd get which displays the management IP along with the port.
I am unable to ping the Proxmox on its Statically assigned IP (10.0.0.11) on the Proxmox itself I am able to ping out to 8.8.8.8, my homes gateway @ 10.0.0.1 and ping numerous other hosts. But no single host on my network is able to ping the Proxmox. I have posted the results of m troubleshooting please let me know if there is anything I should change. The Proxmox was working fine for the last 5 months without issues, this is the first reboot I had done since the 5 months of it being up. I would hate to have to rebuild this all over again as I have a lot of projects in the works on this server.
System Specs:
Dell Optiplex 3080
Intel i5 3.2 ghz Quad Core
16GB Ram
1 250gb Sandisk SSD
1 256gb Samsung Evo SSD
The NIC is the onboard NIC on this device
-----------------------------------------
results of nano /etc/network/interfaces
auto lo
iface lo inet loopback
iface enp2s0 inet manual
auto vmbr0
iface vmbr0 inet static
address 10.0.0.11/24
gateway 10.0.0.1
bridge-ports enp2s0
bridge-stp off
bridge-fd 0
--------------------------------------
Results of ip a command:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether c8:1f:66:29:35:da brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c8:1f:66:29:35:da brd ff:ff:ff:ff:ff:ff
inet 10.0.0.11/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80:ca1f:66ff:fe29:35da/64 scope link
valid_lft forever preferred_lft forever
--------------------------------------------------------------------
ping results from Proxmox Server (10.0.0.11)
Pinging to Default Gateway @ 10.0.0.1
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rat min/avg/max/mdev = 2.035/2.295/2.535/0.179ms
Pinging to Google DNS @ 8.8.8.8
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rat min/avg/max/mdev = 18.285/19.073/20.190/0.665ms
Pinging MacBook Pro @ 10.0.0.31 (on Wireless)
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rat min/avg/max/mdev = 1.926/44.504/103.660/34.443ms
--------------------------------------------------------------------
ping results from MacBook to Proxmox Server
--- 10.0.0.11 ping statistics ---
1517 packets transmitted, 10 packets received, 99.3% packet loss
round-trip min/avg/max/stddev = 2.514/7.622/40.864/11.138 ms
--------------------------------------------------------------------
The only time I am able to ping the 10.0.0.11 is literally 1 second after I type in the reboot command into Proxmox, it will show alive for a split second, system will reboot and will boot right into Proxmox but it goes right back to being like if the IP is dead. This IP is available I have my DHCP pool setup to not assign the first 20 IPs of my network. I have tried other IPs rebooting in-between with no luck.
Here's a capture of me trying to ping while the server is rebooting. Where you see the replies(bold) is when Proxmox is going through its reboot this is right before the system reboots.
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
64 bytes from 10.0.0.11: icmp_seq=15 ttl=64 time=3.372 ms
64 bytes from 10.0.0.11: icmp_seq=16 ttl=64 time=4.358 ms
64 bytes from 10.0.0.11: icmp_seq=17 ttl=64 time=3.273 ms
64 bytes from 10.0.0.11: icmp_seq=18 ttl=64 time=3.600 ms
64 bytes from 10.0.0.11: icmp_seq=19 ttl=64 time=2.036 ms
64 bytes from 10.0.0.11: icmp_seq=20 ttl=64 time=2.690 ms
64 bytes from 10.0.0.11: icmp_seq=21 ttl=64 time=2.756 ms
I am unable to ping the Proxmox on its Statically assigned IP (10.0.0.11) on the Proxmox itself I am able to ping out to 8.8.8.8, my homes gateway @ 10.0.0.1 and ping numerous other hosts. But no single host on my network is able to ping the Proxmox. I have posted the results of m troubleshooting please let me know if there is anything I should change. The Proxmox was working fine for the last 5 months without issues, this is the first reboot I had done since the 5 months of it being up. I would hate to have to rebuild this all over again as I have a lot of projects in the works on this server.
System Specs:
Dell Optiplex 3080
Intel i5 3.2 ghz Quad Core
16GB Ram
1 250gb Sandisk SSD
1 256gb Samsung Evo SSD
The NIC is the onboard NIC on this device
-----------------------------------------
results of nano /etc/network/interfaces
auto lo
iface lo inet loopback
iface enp2s0 inet manual
auto vmbr0
iface vmbr0 inet static
address 10.0.0.11/24
gateway 10.0.0.1
bridge-ports enp2s0
bridge-stp off
bridge-fd 0
--------------------------------------
Results of ip a command:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether c8:1f:66:29:35:da brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c8:1f:66:29:35:da brd ff:ff:ff:ff:ff:ff
inet 10.0.0.11/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80:ca1f:66ff:fe29:35da/64 scope link
valid_lft forever preferred_lft forever
--------------------------------------------------------------------
ping results from Proxmox Server (10.0.0.11)
Pinging to Default Gateway @ 10.0.0.1
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rat min/avg/max/mdev = 2.035/2.295/2.535/0.179ms
Pinging to Google DNS @ 8.8.8.8
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rat min/avg/max/mdev = 18.285/19.073/20.190/0.665ms
Pinging MacBook Pro @ 10.0.0.31 (on Wireless)
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rat min/avg/max/mdev = 1.926/44.504/103.660/34.443ms
--------------------------------------------------------------------
ping results from MacBook to Proxmox Server
--- 10.0.0.11 ping statistics ---
1517 packets transmitted, 10 packets received, 99.3% packet loss
round-trip min/avg/max/stddev = 2.514/7.622/40.864/11.138 ms
--------------------------------------------------------------------
The only time I am able to ping the 10.0.0.11 is literally 1 second after I type in the reboot command into Proxmox, it will show alive for a split second, system will reboot and will boot right into Proxmox but it goes right back to being like if the IP is dead. This IP is available I have my DHCP pool setup to not assign the first 20 IPs of my network. I have tried other IPs rebooting in-between with no luck.
Here's a capture of me trying to ping while the server is rebooting. Where you see the replies(bold) is when Proxmox is going through its reboot this is right before the system reboots.
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
64 bytes from 10.0.0.11: icmp_seq=15 ttl=64 time=3.372 ms
64 bytes from 10.0.0.11: icmp_seq=16 ttl=64 time=4.358 ms
64 bytes from 10.0.0.11: icmp_seq=17 ttl=64 time=3.273 ms
64 bytes from 10.0.0.11: icmp_seq=18 ttl=64 time=3.600 ms
64 bytes from 10.0.0.11: icmp_seq=19 ttl=64 time=2.036 ms
64 bytes from 10.0.0.11: icmp_seq=20 ttl=64 time=2.690 ms
64 bytes from 10.0.0.11: icmp_seq=21 ttl=64 time=2.756 ms
Last edited:
