Any suggestions

  • Thread starter Thread starter zaazz
  • Start date Start date
Z

zaazz

Guest
I seem to have fubar'd my box. I know there isn't a ton of "good" information in this post but given my explanation, however bad it is and given how little experience I have with this software, I truly hope someone will read this and think they have an idea about what I may have done.

I added a new hard drive and was reading up on LVM group creation stuff. I went into the web interface before I did anything else and tried to add a new LVM there. I'm not sure exactly what I did but when I hit save, all default options left as is, it created a new group and it was full, the allocated space was almost completely filled. Thinking I just created something that I haven't set up to use yet I disabled it and rebooted. I got a few errors even trying to disable it. But after the reboot I can no longer get a network connection to that box. Also, none of my servers come up. It's going to be hard to copy paste any outputs here to the forum but I do have access to the command line and I can log into it but nothing else seems to work.

The new drive is set to /dev/sdb but its not configured at all. PE=0, total PE=0, Free PE =0, Allocated PE=0
I also did this to the new drive right before rebooting:

proxmox-ve:~# pvcreate /dev/sdb
Physical volume "/dev/sdb" successfully created
proxmox-ve:~#

Second, create a volume group (vg):

proxmox-ve:~# vgcreate usb-stick /dev/sdb
Volume group "seconddrive" successfully created
proxmox-ve:~#
 
I suggest you ask a simple question, without any details no one will be able to help. also choose a meaning full subject to your posts. So far I just can see that you created a physical LVM volume to the whole disk, you should not never do this. create a partition first (e.g. /dev/sdb1)
 
tom said:
I suggest you ask a simple question, without any details no one will be able to help. also choose a meaning full subject to your posts. So far I just can see that you created a physical LVM volume to the whole disk, you should not never do this. create a partition first (e.g. /dev/sdb1)
Click to expand...

Tom, thanks for replying so quickly. It would make sense if I created a physical LVM to the whole disk and then disabled it. If I did this it was on accident. Can I reverse it?
I tried to indicate that I don't have a network connection, so while I don't really want to manually type out log files into this forum I can if there is no other way to help solve this.

Short of starting over from scratch I'm looking for possible ideas on how to fix it. While it's not impossible for me to reinstal everything do to my error I thought I'd come here first to see if anyone had any suggestions on how to fix what I did.

Please be specific about the information I can provide that may help troubleshoot this. I wish I had screenshots of what it is I saw on the web interface but after the reboot everything is gone and I can't even get a network connection on that box any longer.

With the above stated. I will accept the answer, "you F@#%'ed up so reinstall" but I had hoped someone might have some suggestions to salvage this.
 
zaazz said:
Tom, thanks for replying so quickly. It would make sense if I created a physical LVM to the whole disk and then disabled it. If I did this it was on accident. Can I reverse it?
I tried to indicate that I don't have a network connection, so while I don't really want to manually type out log files into this forum I can if there is no other way to help solve this.

Short of starting over from scratch I'm looking for possible ideas on how to fix it. While it's not impossible for me to reinstal everything do to my error I thought I'd come here first to see if anyone had any suggestions on how to fix what I did.

Please be specific about the information I can provide that may help troubleshoot this. I wish I had screenshots of what it is I saw on the web interface but after the reboot everything is gone and I can't even get a network connection on that box any longer.

With the above stated. I will accept the answer, "you F@#%'ed up so reinstall" but I had hoped someone might have some suggestions to salvage this.
Click to expand...
Hi,
pve is linux not windows - you don't have to reinstall it every few month ;)
You have two things - a second disk and no network connection.
I assume your network is more urgent - handle this first.
without network you can't log in via ssh to use copy/paste for information... but we will see what we can do without this things.

use "ifconfig -a | more" (the |more is only for a large output (and small consolewindow)) to see all network-devices.
Do you see eth0 (also with TX and RX bytes)? Also eth1/eth2?
Look for all eth-info during boot:
Code: 
dmesg | grep eth
Look at your network-config: cat /etc/network/interfaces
You use eth0 as device in vmbr0? is eth0 active or another nic?
In case of a renaming of your nic you can add the right nic to the bridge like this:
Code: 
ifconfig eth1 up
brctl addif vmbr0 eth1
Have also a look at "/etc/udev/rules.d/70-persistent-net.rules" and post the output if you can't help yourself.

Udo
 
udo said:
Hi,
pve is linux not windows - you don't have to reinstall it every few month ;)
You have two things - a second disk and no network connection.
I assume your network is more urgent - handle this first.
without network you can't log in via ssh to use copy/paste for information... but we will see what we can do without this things.

use "ifconfig -a | more" (the |more is only for a large output (and small consolewindow)) to see all network-devices.
Do you see eth0 (also with TX and RX bytes)? Also eth1/eth2?
Look for all eth-info during boot:
Code: 
dmesg | grep eth
Look at your network-config: cat /etc/network/interfaces
You use eth0 as device in vmbr0? is eth0 active or another nic?
In case of a renaming of your nic you can add the right nic to the bridge like this:
Code: 
ifconfig eth1 up
brctl addif vmbr0 eth1
Have also a look at "/etc/udev/rules.d/70-persistent-net.rules" and post the output if you can't help yourself.

Udo
Click to expand...

First off, thanks for helping out a noob. I'm trying to learn and with each problem I retain a lot of information from the troubleshooting and resolution. :)

In /etc/network/interfaces my eth0 and eth2 are set to manual. In a normal ifconfig neither show up at all. Using your suggestion with a infconfig -a |more
eth0, eth2, lo, venet0-00, and veth104.0 are listed as well.

Upon booting up I see this (i'm hand typing this please disregard any typos):
device tap101i0d0 entered promiscuous mode
bridge vmbr0 does not exist!
can't add interface bridge
/var/lib/qemu-server/bridge-vlan:could not launch network script
kvm: -netdev type=tap, id=vlean0d0, ifname=tap101i0d0, script=/var/lib/qemu-server/bridge-vlan: Device 'tap' could not be initalized
start failed: command 'usr/bin/kvm -monitor unix:/var/run/qemu-server/101.mon,server,nowait -vnc unix:/var/run/qemu-server/101.vnc,password -pidfile /var.run.qemu-server/101.pid -daemonize -usbdevice tablet -name PBXINAFLASH -smp sockets=1, cores=1 -nodefaults -boot menu=on, order=dac, -vga cirrus -tdf -k en-us -drive file=/var/lib/vzimages/101-disk-1.raw, if=ide, index=0, caches=none, boot=on -drive file=dev/cdrom, if=ide, index=2, media=cdrom -m 512 -netdev type=tap, id=vlan0d0, ifname=tap101i0d0, script=/var/lib/qemu-server/bridge-vlan -device rt18139, romfile=,mac=62:DF51:c7:81:40, netdev=vlan0d0 -id 101 -cpuunites 1000' failed with excit code 1



no inet address on eth0 and eth2. I've checked all connections and they even get green lights on the nic at the back of the tower and at the switch.
I ran
ifconfig eth0 up
then
ifconfig eth2 up

then
brctl addif vmbr0 eth0

bridge vmbr0 does not exist!

Error ^^

:(
 
zaazz said:
First off, thanks for helping out a noob. I'm trying to learn and with each problem I retain a lot of information from the troubleshooting and resolution. :)

In /etc/network/interfaces my eth0 and eth2 are set to manual. In a normal ifconfig neither show up at all. Using your suggestion with a infconfig -a |more
eth0, eth2, lo, venet0-00, and veth104.0 are listed as well.

Upon booting up I see this (i'm hand typing this please disregard any typos):
device tap101i0d0 entered promiscuous mode
bridge vmbr0 does not exist!
can't add interface bridge
/var/lib/qemu-server/bridge-vlan:could not launch network script
kvm: -netdev type=tap, id=vlean0d0, ifname=tap101i0d0, script=/var/lib/qemu-server/bridge-vlan: Device 'tap' could not be initalized
start failed: command 'usr/bin/kvm -monitor unix:/var/run/qemu-server/101.mon,server,nowait -vnc unix:/var/run/qemu-server/101.vnc,password -pidfile /var.run.qemu-server/101.pid -daemonize -usbdevice tablet -name PBXINAFLASH -smp sockets=1, cores=1 -nodefaults -boot menu=on, order=dac, -vga cirrus -tdf -k en-us -drive file=/var/lib/vzimages/101-disk-1.raw, if=ide, index=0, caches=none, boot=on -drive file=dev/cdrom, if=ide, index=2, media=cdrom -m 512 -netdev type=tap, id=vlan0d0, ifname=tap101i0d0, script=/var/lib/qemu-server/bridge-vlan -device rt18139, romfile=,mac=62:DF51:c7:81:40, netdev=vlan0d0 -id 101 -cpuunites 1000' failed with excit code 1



no inet address on eth0 and eth2. I've checked all connections and they even get green lights on the nic at the back of the tower and at the switch.
I ran
ifconfig eth0 up
then
ifconfig eth2 up

then
brctl addif vmbr0 eth0

bridge vmbr0 does not exist!

Error ^^

:(
Click to expand...
Hi,
something wrong in /etc/network/interfeces?

Try this (change to the right ip-address):
Code: 
brctl addbr vmbr0
brctl addif vmbr0 eth0
ifconfig eth0 up
ifconfig vmbr0 192.168.10.10 netmask 255.255.255.0 up
any error messages?
can you ping your gateway?

Udo
 
network interface settings

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto eth2
iface eth2 inet manual

auto vmbr0
iface vmbro0 inet static
bridge_ports none
bridge_stp off
bridge_fd 0

********************

running commands:
~#brctl addbr vambr0
Bridge firewalling registered

~#brctl addif vmbr0 eth0
device eth0 entered promiscuous mode

~#ifconfig eth0 up
~#

~#ifconfig vmbr0 192.168.88.145 netmask 255.255.255.0 up
vmbr0: port 1(eth0) entering forwarding state

blinking cursor here...


but hey I got the network connection back up. Thanks for that. Now it will be much easier for me to post logs of whatever here if you have more suggestions. Thanks again.
 
I've rebooting the virtual servers and they are coming back up fine now. I'm not sure what broke. I did add a new NIC while i had it opened up and was adding the hard drive but I didn't think that would break everything. ><
 
zaazz said:
I did add a new NIC while i had it opened up and was adding the hard drive but I didn't think that would break everything. ><
Click to expand...

Might have helped diagnose the issue if you'd have said this first :)

Looks like it may have affected your NIC naming...
 
zaazz said:
I've rebooting the virtual servers and they are coming back up fine now. I'm not sure what broke. I did add a new NIC while i had it opened up and was adding the hard drive but I didn't think that would break everything. ><
Click to expand...
Hi,
now you can post
Code: 
/etc/network/interfaces,
/etc/udev/rules.d/70-persistent-net.rules
dmesg | grep eth
brctl show
ifconfig -a
running commands:
~#brctl addbr vambr0
Bridge firewalling registered
Click to expand...
hmm, what kind of firewall do you have running?
Perhaps this is the problem (is the firewall starting in the right order? with the right rules?)

Udo
 
# network interface settings
auto lo
iface lo inet loopback


auto eth0
iface eth0 inet manual


auto eth2
iface eth2 inet manual




auto vmbr0
iface vmbr0 inet static
bridge_ports none
bridge_stp off
bridge_fd 0


~
~
~
~
~
~
"/etc/network/interfaces" 17 lines, 215 characters

# 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.


# PCI device 0x10b7:0x9200 (3c59x)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:01:02:68:08:a0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"


# PCI device 0x1969:0x1026 (ATL1E)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:d9:e3:c8", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"


# PCI device 0x10ec:0x8169 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="c8:3a:35:d6:f0:ff", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
~
~
~
~
~
~
~
"/etc/udev/rules.d/70-persistent-net.rules" 13 lines, 766 characters




~# dmesg | grep eth
eth1: RTL8169sb/8110sb at 0xffffc900050a6c00, c8:3a:35:d6:f0:ff, XID 10000000 IRQ 20
udev: renamed network interface eth1 to eth2
veth104.0: no IPv6 routers present
eth0: no IPv6 routers present
ADDRCONF(NETDEV_UP): eth0: link is not ready
ATL1E 0000:01:00.0: ATL1E: eth0 NIC Link is Up<1000 Mbps Full Duplex>
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
r8169 0000:03:01.0: eth2: link up
r8169 0000:03:01.0: eth2: link up
eth2: no IPv6 routers present
device eth0 entered promiscuous mode
vmbr0: port 1(eth0) entering learning state
vmbr0: port 1(eth0) entering forwarding state
device veth104.0 entered promiscuous mode
vmbr0: port 3(veth104.0) entering learning state
veth104.0: no IPv6 routers present
eth0: no IPv6 routers present
vmbr0: port 3(veth104.0) entering forwarding state


:~# brctl show
bridge name bridge id STP enabled interfaces
vmbr0 8000.bcaec5d9e3c8 no eth0
tap101i0d0
veth104.0






eth0 Link encap:Ethernet HWaddr bc:ae:c5:d9:e3:c8
inet6 addr: fe80::beae:c5ff:fed9:e3c8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5904545 errors:0 dropped:0 overruns:0 frame:0
TX packets:5938813 errors:0 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:6166029458 (5.7 GiB) TX bytes:1706179343 (1.5 GiB)
Interrupt:25


eth2 Link encap:Ethernet HWaddr c8:3a:35:d6:f0:ff
inet6 addr: fe80::ca3a:35ff:fed6:f0ff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37192 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2483824 (2.3 MiB) TX bytes:468 (468.0 B)
Interrupt:20 Base address:0x6c00


lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:20211 errors:0 dropped:0 overruns:0 frame:0
TX packets:20211 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6564283 (6.2 MiB) TX bytes:6564283 (6.2 MiB)


tap101i0d0 Link encap:Ethernet HWaddr 46:1a:36:84:31:1a
inet6 addr: fe80::441a:36ff:fe84:311a/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:35567 errors:0 dropped:0 overruns:0 frame:0
TX packets:46495 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:8418132 (8.0 MiB) TX bytes:8384097 (7.9 MiB)


venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::1/128 Scope:Link
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


veth104.0 Link encap:Ethernet HWaddr 00:18:51:4a:2d:cc
inet6 addr: fe80::218:51ff:fe4a:2dcc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5884095 errors:0 dropped:0 overruns:0 frame:0
TX packets:5819078 errors:0 dropped:3 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1609937852 (1.4 GiB) TX bytes:6069463029 (5.6 GiB)


vmbr0 Link encap:Ethernet HWaddr bc:ae:c5:d9:e3:c8
inet addr:192.168.88.145 Bcast:192.168.88.255 Mask:255.255.255.0
inet6 addr: fe80::beae:c5ff:fed9:e3c8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:32905 errors:0 dropped:0 overruns:0 frame:0
TX packets:18796 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3372104 (3.2 MiB) TX bytes:4780757 (4.5 MiB)



I haven't configured a firewall on this proxmox box so unless it's running one by default I'm not sure. Otherwise my router is my network firewall.
 
zaazz said:
# network interface settings
...
auto vmbr0
iface vmbr0 inet static
bridge_ports none
bridge_stp off
bridge_fd 0
...
Click to expand...
Hi,
with "bridge_ports eth0" you should able to create the right bridge but you ip-address is missing. Try an interface-file like this:
Code: 
# network interface settings
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto eth2
iface eth2 inet manual


auto vmbr0
iface vmbr0 inet static
    address 192.168.88.145
    netmask 255.255.255.0
    gateway 192.168.88.1
    bridge_ports eth0
    bridge_stp off
    bridge_fd 0
Udo

PS: not the device-renaming has changed your config - you must do some strange things in the network-section of the gui
 
I hope to get time to look at this tonight. Finals week. :(

I am pretty sure I didn't do anything in the network section of the gui. I just took out an old nic and replaced it with a gig nic.

Last question, will the above settings also bridge the new nic so i can use them both? In the future I may look into assigning either my voip server (on the proxmox) or the file server to its own interface...if that's even possible.
 
You must log in or register to reply here.
Top Bottom