hard drive swap failure to access PVE 2.0

P

Peter712

Member
Oct 25, 2009
16
0
21
so I have two servers that I use, dev, and production, they are both the same mobo, proc, raid card, the only thing different about them is the amount of ram.
I have been running 1.9 on production and 2.0 on dev. and now that 2.0 is stable I moved all VE's over pulled one of the drives and installed it into the production box powered it back on and went to verify that all was well in the webui. it was unable to connect. and when I logged on to the box found that I was unable to ping anything outside the box. putting it back into the dev box it works just fine. so now I'm lost and dont know where to look to correct the issue.

any help would be most appreciated
Peter.
 
Peter712 said:
so I have two servers that I use, dev, and production, they are both the same mobo, proc, raid card, the only thing different about them is the amount of ram.
I have been running 1.9 on production and 2.0 on dev. and now that 2.0 is stable I moved all VE's over pulled one of the drives and installed it into the production box powered it back on and went to verify that all was well in the webui. it was unable to connect. and when I logged on to the box found that I was unable to ping anything outside the box. putting it back into the dev box it works just fine. so now I'm lost and dont know where to look to correct the issue.

any help would be most appreciated
Peter.
Click to expand...
Hi Peter,
you install pve2 on an different system? Then your udev-rule for eth0 is wrong on the new system. Simply remove the entry before you boot on the new system (or change it after this).
With the right eth0 you should able to ping.

The file is /etc/udev/rules.d/70-persistent-net.rules

Udo
 
Udo,
Thank you for this!! (even though its delayed) this has helped me alot, and also has helped me prepare for hardware failing.

again thank you!
Peter.
 
You must log in or register to reply here.
Top Bottom
Back