moved proxmox hard drive to new computer of same

P

pdpurvis

New Member
Jul 27, 2011
4
1
1
I moved the hard drive from one computer that was not working to another of the same.
Proxmox boots and has same ip address as before, but not able to connect to network.

background:
I had rebooted on a machine running proxmox into windows 7 to update the bios.
I had unplugged the hard drive which proxmox was installed on.
The bios update did not compete, there by likely bricking my computer.

I have identical computers stored on the shelf. I pulled one and placed the proxmox hard drive into the newer computer.
Proxmox boots, shows the current ip address.
The hardware is suppose to be exactly the same except naturally the MAC address of the hard wired network card.
Networking connection is not working. Doing simple ping to other equipment does not work.
Ifconfig does report proper ip address and subnet, etc.

I installed two other operating systems on other hard drives to test and see if the network card of the new computer might be broke.
The other two operating systems did operate properly on networking, so the network card should be good.

This is sort of disappointing. I was hoping I could always remove the hard drive and place it in another computer like the one it came out of.
Do i need to reinitialize the network in some way?

Thanks for responding.
 
Last edited:
Seems I have it working, i will post back shortly of what is happening and what i have done.
 
When I put the working hard drive that had proxmox on it into another exact computer after
bricking a computer that proxmox was on by attempting bios update with windows 7.
(I RELEARNED MY LESSON OF BIOS UPDATING.)


My networking did not work.
There was only one wired network card in the old computer and only one in the new computer

I am only guessing here what happened and how I fixed my networking.
I made a backup of the file /etc/udev/rules.d/70-persistent-net.rules


Proxmox updated the file /etc/udev/rules.d/70-persistent-net.rules
Apparently Proxmox found the new network card and added it and created a "eth1" network connection
adding the 2 lines
--------------------------------------------------
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:9c:dc:f5:b5:e7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
--------------------------------------------------

c8:9c:dc:f5:b5:e7 was the new MAC address of network card in the new computer

so now the whole file /etc/udev/rules.d/70-persistent-net.rules looked like this
-----------------------------------------------------------------------------------
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:9c:dc:e8:03:d4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:9c:dc:f5:b5:e7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
-----------------------------------------------------------------------------------


The file /etc/network/interfaces looked like this
-----------------------------------------------------
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
address 192.168.1.9
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_stp off
bridge_fd 0
-----------------------------------------------------


When ran "ifconfig -a"
eth1 showed in the listing using the MAC address c8:9c:dc:f5:b5:e7
There was listing of eth0
As you can see in the file /etc/network/interfaces that the bridge_ports pointed to eth0
I could have just changed the eth0 in /etc/network/interfaces to eth1
But I do not know what is going to happen in the future.
So I left the file /etc/network/interfaces as it was and
edited /etc/udev/rules.d/70-persistent-net.rules instead to create a eth0 newtwork device


so

i removed the two lines in the file /etc/udev/rules.d/70-persistent-net.rules
-----------------------------------------------------
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:9c:dc:e8:03:d4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
-----------------------------------------------------



then i changed the line from
-----------------------------------------------------
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:9c:dc:f5:b5:e7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
-----------------------------------------------------
to
-----------------------------------------------------
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:9c:dc:f5:b5:e7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
-----------------------------------------------------




now the file /etc/udev/rules.d/70-persistent-net.rules looks like this
-----------------------------------------------------
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:9c:dc:f5:b5:e7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
-----------------------------------------------------


For many other experience users of proxmox, this would have been easy to do and figure out, perhaps it is a debian thing. I do no know.

But hopefully this will help out another users of proxmox that has simple needs or installs a network card or replaces one.
 
Last edited:
  • Like
Reactions: borekon
You must log in or register to reply here.
Top Bottom