Proxmox not starting from drive

T

Tuckerdog

Well-Known Member
Aug 17, 2011
67
0
46
I have been reading on my problem with the update to my server. I have been reading everything I can for 2 weeks now, and I must finally ask for help.

was updating a running, stand alone server when it would not reboot. I can reboot from the install USB, but it would seem I can't repair to boot on it's own.

I have tried rescatux, supergrub2, GRML, debian live cd, systemrescue, the Proxmox install and several others, but I don't seem to have enough of a grasp to get on the right track. Could someone out there point me in the direction I need?

I am looking at a 'root@proxmox:~#' prompt. The system is set to static IP, but won't ping to anything outside the box...it will ping loopback and its own static IP. As the USB boots, FSCK reports fsck.ext3: no such file or directory while trying to open /dev/pve/data etc.

Thank-you ,
 
Tuckerdog said:
I have been reading on my problem with the update to my server. I have been reading everything I can for 2 weeks now, and I must finally ask for help.

was updating a running, stand alone server when it would not reboot. I can reboot from the install USB, but it would seem I can't repair to boot on it's own.

I have tried rescatux, supergrub2, GRML, debian live cd, systemrescue, the Proxmox install and several others, but I don't seem to have enough of a grasp to get on the right track. Could someone out there point me in the direction I need?

I am looking at a 'root@proxmox:~#' prompt. The system is set to static IP, but won't ping to anything outside the box...it will ping loopback and its own static IP. As the USB boots, FSCK reports fsck.ext3: no such file or directory while trying to open /dev/pve/data etc.

Thank-you ,
Click to expand...
Hi,
it's looks that you discibed different issues.
When you at the root@proxmox:~# prompt, you are in the normal runlevel, or in single user mode?

The missing network connection can be happen due an different networkinterface name. I guess your bridge is not connected to the right network-interface.

Can you post the output of following commands (first the network related, because after that it's easier with copy/paste on an ssh session.
Code: 
brctl show
cat /etc/network/interfaces
ifconfig -a
cat /etc/udev/rules.d/70-persistent-net.rules
Udo
 
Hi,

Here is my best copying over...hopefully I have no mistakes.

root@proxmox:/# brctl show
bridge name bridge id STP enabled interfaces
vmbr0 8000.000000000000 no

root@proxmox:/#cat /etc/network/interfaces
# network interface settings
auto lo
iface lo inet loopback

iface eth2 inet manual

iface eth3 inet manual

iface eth0 inet manual

auto vmbr0
iface vmbr0 inet static
address 10.0.0.10
netmask 255.255.252.0
gateway 10.0.0.1
bridge_ports eth0
bridge_stp off
bridge_fd 0
root@proxmox:/# ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU: Metric:1
RX packets:1284 errors:0 dropped:0 overruns:0 frame:0
TX packets:1284 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:129616 (126.5 KiB) TX bytes:12616 (126.5 KiB)

vmbr0 Link encap:Ethernet HWaddr c2:14:31:39:46:a5
inet addr:10.0.0.10 Bcast:10.0.3.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3840 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:161280 (157.5 KiB)
root@proxmox:/# cat /etc/udev/rules.d/70-persistent-net.rules
# 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 0x11ab:0x4364 (sky2)
SUBSYSTEM=="NET", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:50:8a:34", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="NET", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:50:8a:aa", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="NET", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:50:89:ff", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="NET", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:50:8a:72", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

Hope this will get the internet online, cause that was some typing over from the terminal.. :^)
 
Tuckerdog said:
Hi,

Here is my best copying over...hopefully I have no mistakes.

root@proxmox:/# brctl show
bridge name bridge id STP enabled interfaces
vmbr0 8000.000000000000 no

root@proxmox:/#cat /etc/network/interfaces
# network interface settings
auto lo
iface lo inet loopback

iface eth2 inet manual

iface eth3 inet manual

iface eth0 inet manual

auto vmbr0
iface vmbr0 inet static
address 10.0.0.10
netmask 255.255.252.0
gateway 10.0.0.1
bridge_ports eth0
bridge_stp off
bridge_fd 0
root@proxmox:/# ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU: Metric:1
RX packets:1284 errors:0 dropped:0 overruns:0 frame:0
TX packets:1284 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:129616 (126.5 KiB) TX bytes:12616 (126.5 KiB)

vmbr0 Link encap:Ethernet HWaddr c2:14:31:39:46:a5
inet addr:10.0.0.10 Bcast:10.0.3.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3840 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:161280 (157.5 KiB)
root@proxmox:/# cat /etc/udev/rules.d/70-persistent-net.rules
# 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 0x11ab:0x4364 (sky2)
SUBSYSTEM=="NET", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:50:8a:34", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="NET", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:50:8a:aa", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="NET", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:50:89:ff", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="NET", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:ae:c5:50:8a:72", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

Hope this will get the internet online, cause that was some typing over from the terminal.. :^)
Click to expand...
Hi,
your kernel module for the nic isn't loaded. so you don't have any nic...

What happens if you try to load the module?
Code: 
lsmod | grep sky
modprobe sky2
lsmod | grep sky


# which kernel is running?
uname -a

# is the driver there?
find /lib/modules/ | grep sky
If you see eth0 after modprobe, you can add the interface to the bridge with
Code: 
brctl addif vmbr0 eth0
ifconfig eth0 up
Udo
 
Hi,

This was booted from a usb key with proxmox 3.3 on it...came to the boot: prompt and entered pveboot...came to the cntl-d and did that.

lsmod | grep sky came back to the prompt with no reply.
modprobe sky2 came back with libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/2.6.32-32-pve/modules.dep.bin'
uname -a Linux promox 2.6.32-32-pve #1 SMP Thu Aug 21 08:50:19 cest 2014 x86_64 GNU/Linux
find /lib/modules/ | grep sky find: '/lib/modules/' : No such file or directory
 
Tuckerdog said:
Hi,

This was booted from a usb key with proxmox 3.3 on it...came to the boot: prompt and entered pveboot...came to the cntl-d and did that.

lsmod | grep sky came back to the prompt with no reply.
modprobe sky2 came back with libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/2.6.32-32-pve/modules.dep.bin'
uname -a Linux promox 2.6.32-32-pve #1 SMP Thu Aug 21 08:50:19 cest 2014 x86_64 GNU/Linux
find /lib/modules/ | grep sky find: '/lib/modules/' : No such file or directory
Click to expand...
Hi,
ok - then we must first try to fix the booting.

What is the output of following commands?
Code: 
pvs
vgs
lvs
mount
Udo
 
pvs
-bash: pvs: command not found
vgs
-bash: pvs: command not found
lvs
-bash: pvs: command not found
mount
/dev/mapper/pve-boot on / type ext4 (rw,relatime,errors=remount-ro,barrier=1,data=ordered
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1641948k,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
proc on /proc type proc (rw,nosuid.nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=10240,mode=755)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3283880k)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5.mode=620,ptmxmode=000)
 
unless I'm doing something wrong, they are all displaying -bash: xxdisplay: command not found
 
Hi,
can you boot an live-distro like grml? http://grml.org/
Boot the 64bit version.

Then do something like:
Code: 
mkdir /mnt/pve
pvs
vgs
lvs
vgchange -a y pve
mount /dev/pve/root /mnt/pve
mount /dev/sdX1 /mnt/pve/boot     # X is the device numer which showed by pvs
mount -o loop /proc /mnt/pve/proc
mount -o loop /sys /mnt/pve/sys
mount -o loop /dev /mnt/pve/dev
chroot /mnt/pve /bin/bash
which version of pve do you have installed?
Code: 
dpkg -l | grep pve
Udo
 
i just booted with sysresccd 64 and now I am at root@sysresccd /root %

I just put in pvdisplay and got

--- Physical volume ---
PV Name /dev/sda2
VG Name pve
PV size 931.01 GiB / not usable 0
Allocatable yes
PE size 4.00 MiB
Total PE 238339
Free PE 4095
Allocated PE 234244
PV UUID PKfmsQ-V1Ln-mvAR-CmBg-YDQT-4aPY-oz31HC
 
all commands giving expected results until mount -o loop /proc /mnt/pve/proc came back with mount: /proc: failed to setup loop device: Is a directory
 
the rescue cd (USB) also pulled an IP address from the pool and I am able to ping 8.8.8.8, etc.
 
Sorry...was using the sysrescue OK?...I didn't mean to not follow your instructions, but I had GRML on a key, but couldn't figure how to land at the command prompt instead of the GUI. I can load up a key with that, if need be..?
 
that gave dpkg-query: error: failed to open package info '/var/lib/dpkg/status' for reading: No such file or directory
 
and the pvs lvs and vgs all give info now....the mount is far to much to type over...scrolls the screen by. :)
 
after the mount error, I didn't put the rest of the mount commands (or the chroot) in...should I?
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom