Proxmox VE no connection
- Thread starter TKL
- Start date
My apologies, the hostname above gave me the wrong impression that you are running inside fritz.box hosting provider.
If you are sure that the IPs and subnet are correct, it still continues to be local networking issue. With properly reachable gateway you should see at least one more hop, ie.
traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 172.16.202.1 (172.16.202.1) 0.175 ms 1.223 ms 1.216 ms
2 172.16.255.2 (172.16.255.2) 0.144 ms 1.203 ms 1.197 ms
It is possible that ICMP ping can be functional but other traffic is being blocked. If you are absolutely sure that all the settings are correct, my next step would be a network trace.
To address your question - these are temporary settings. Your boot sequence indicates presence of either slow/defective USB disks, or USB bus issues. You may want to disconnect all unnecessary device and reboot.
Good luck.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Having skimmed through this thread + the biggest graphics album on these forums - I'm betting this is HW related.
My first suspicion is on this:
My first suspicion is on this:
- What is this drives history? Has it been successfully tested/used in another environment?
- More importantly is this m.2 the
sdadrive mentioned in the logs? (Maybe providelsblkoutput, great for more art!) - How is this connected to the server? Is it using some m.2 adapter dangling on a USB cable?
- Have you successfully installed & run any OS with this EXACT HW?
no worries fritz.box is my router. i am no genius in networking (passed my uni course with a 3.0) but i do know the basics and am pretty sure that everything is correct.
.1 definitly is the router and therefore the gateway (?)
i set .32 as the static IP for the Server
i can ping the Router, but can't get past that
alright i'll try that tomorrow
hm ok weird. i forgot to take out the boot stick and havent changed the boot order yet. maybe thats what you are refering to?
with random i just meant i dont know the brand. its been in my old PC for maybe 5-6 Years (windows). i ran a crystaldisc ( i believe thats what its called) a few months ago and everything was fine.
the only thing i did was wipe the old os of the drive and install proxmox onto it. so yes this HW has been running in this config for several years.
the M.2 is in the M.2 slot of the motherboard.
Code:
root@pve:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sdb 8:16 1 0B 0 disk
sr0 11:0 1 1024M 0 rom
nvme0n1 259:0 0 465.8G 0 disk
├─nvme0n1p1 259:1 0 1007K 0 part
├─nvme0n1p2 259:2 0 1G 0 part
└─nvme0n1p3 259:3 0 464.8G 0 part
├─pve-swap 252:0 0 8G 0 lvm [SWAP]
├─pve-root 252:1 0 96G 0 lvm /
├─pve-data_tmeta 252:2 0 3.4G 0 lvm
│ └─pve-data 252:4 0 337.9G 0 lvm
└─pve-data_tdata 252:3 0 337.9G 0 lvm
└─pve-data 252:4 0 337.9G 0 lvm
Some routers block traffic from IP addresses that are within the DHCP range but do not use DHCP to get the IP address. Can you make sure the Proxmox IP address is not inside the router's DHCP range?
oh that is a very good idea havent thought of that. i'll check in the morning thanks!
ok this seamed to be one of the frontpanel usbs (although there was nothing plugged into them). i have unplugged them for now.
this seemed to be the issue. i can now ping 8.8.8.8. i think the only issue i still have, is that i have to setup the bridge everytime i boot the system. although it is configured here:
Code:
GNU nano 7.2 /etc/network/interfaces
auto lo
iface lo inet loopback
iface enp6s0 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.178.3/24
gateway 192.168.178.1
bridge-ports enp6s0
bridge-stp off
bridge-fd 0
source /etc/network/interfaces.d/*any ideas?
Code:
root@pve:~# ip a
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether f8:32:e4:bb:72:4f 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 f8:32:e4:bb:72:4f brd ff:ff:ff:ff:ff:ff
inet 192.168.178.3/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::fa32:e4ff:febb:724f/64 scope link
valid_lft forever preferred_lft foreverThanks for all the Help, you guys are legends!