Old server died moved NVME to a alt machine now cant access

[michaeljkent090]

Hello looking for help.

I reccently had a lenovo mini pc that was my homelab with a quite a few vms and cts die.

In my attempt to save all my unbacked up vms and cts i put the nvme into a laptop and hooked it up where the mini pc was.

Now I cannot access the proxmox console at all. I have checked the ip on the login banner, as well in the interfaces file and host file. according to those three points I have it correct.

Im sure im missing something hoping someone will help.

 

[marcush70]

I re-read your post and see that maybe you're saying you checked that they match already; as you say interface file, ?

try this first if you have network ip and the system was in a machine that died suddenly.
none of these should effect yo v.m.s.

---Look for a file called 'config.db.lock'. If this exists after a sudden power failure, it can prevent Proxmox from starting properly. We can safely remove it:
rm /var/lib/pve-cluster/config.db.lock

verify the integrity of the Proxmox configuration database:
pmxcfs -l
see any errors, remove the database, and let it rebuild:
systemctl stop pve-cluster
rm /var/lib/pve-cluster/config.db
systemctl start pve-cluster

restart the key Proxmox services:
systemctl restart pvedaemon
systemctl restart pveproxy
systemctl restart pvestatd

remove any stale locks:
find /var/lock/ -type f -delete

reboot



ip addr show
1-This will show you the actual interface names on the new hardware.
then;
cat /etc/network/interfaces
the interface name in this file match as it binds to the name, not necessarily the ip.
if they do not match
nano /etc/network/interfaces

update the interface name to match what you saw in ip addr show

save the file
then
systemctl restart networking

try now.

if not then

Verify your network configuration
ip route show
check default gateway, i imagine this isn't messed up though.

next
network service
systemctl status networking
systemctl restart networking

systemctl status pveproxy
systemctl restart pveproxy

netstat -tuln | grep 8006
if it's no listed, check

 

[michaeljkent090]

ip addr show
1-This will show you the actual interface names on the new hardware.
then;
cat /etc/network/interfaces
the interface name in this file match as it binds to the name, not necessarily the ip.
if they do not match
nano /etc/network/interfaces

update the interface name to match what you saw in ip addr show

save the file
then
systemctl restart networking

try now.

interface name shows as vmbr0 which matches the other three spots, so does the IP address matches across the board yet i still have zero access.....

 

[Kingneutron]

https://github.com/kneutron/ansitest/blob/master/proxmox/proxmox-fix-vmbr0-nic.sh

Try this - copy the script to server with usb thumbdrive; if it fails then you need to hand-edit /etc/network/interfaces or reinstall PVE