PVE 4.1 Emergency Mode on fresh install, slow no-subscription mirror

M

mackhax0r

Renowned Member
Jul 2, 2015
11
1
68
Hello,

I performed a fresh installation of proxmox 4.1 (redownloaded it twice, via torrent and the ISO from the site). After installation, it boots up without issue. Once reboot the system, it immediately falls back to Emergency Mode. I'm seeing the errors:

Code: 
Mar 18 23:11:11 prox-home01 systemd[1]: Timed out waiting for device dev-pve-data.device.
-- Subject: Unit dev-pve-data.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-pve-data.device has failed.
--
-- The result is timeout.
Mar 18 23:11:11 prox-home01 systemd[1]: Dependency failed for /var/lib/vz.
-- Subject: Unit var-lib-vz.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-lib-vz.mount has failed.
--
-- The result is dependency.
Mar 18 23:11:11 prox-home01 systemd[1]: Dependency failed for Local File Systems.
-- Subject: Unit local-fs.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit local-fs.target has failed.
--
-- The result is dependency.
Mar 18 23:11:11 prox-home01 systemd[1]: Dependency failed for File System Check on /dev/pve/data.
-- Subject: Unit systemd-fsck@dev-pve-data.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-fsck@dev-pve-data.service has failed.
--
-- The result is dependency.
Mar 18 23:11:11 prox-home01 systemd[1]: Job dev-pve-swap.device/start timed out.
Mar 18 23:11:11 prox-home01 systemd[1]: Timed out waiting for device dev-pve-swap.device.
-- Subject: Unit dev-pve-swap.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
lines 929-960
-- Unit dev-pve-data.device has failed.
--
-- The result is timeout.
Mar 18 23:11:11 prox-home01 systemd[1]: Dependency failed for /var/lib/vz.
-- Subject: Unit var-lib-vz.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-lib-vz.mount has failed.
--
-- The result is dependency.
Mar 18 23:11:11 prox-home01 systemd[1]: Dependency failed for Local File Systems.
-- Subject: Unit local-fs.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit local-fs.target has failed.
--
-- The result is dependency.
Mar 18 23:11:11 prox-home01 systemd[1]: Dependency failed for File System Check on /dev/pve/data.
-- Subject: Unit systemd-fsck@dev-pve-data.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-fsck@dev-pve-data.service has failed.
--
-- The result is dependency.
Mar 18 23:11:11 prox-home01 systemd[1]: Job dev-pve-swap.device/start timed out.
Mar 18 23:11:11 prox-home01 systemd[1]: Timed out waiting for device dev-pve-swap.device.
-- Subject: Unit dev-pve-swap.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-pve-swap.device has failed.
--
-- The result is timeout.
Mar 18 23:11:11 prox-home01 systemd[1]: Dependency failed for /dev/pve/swap.
-- Subject: Unit dev-pve-swap.swap has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-pve-swap.swap has failed.
--
-- The result is dependency.
Mar 18 23:11:11 prox-home01 systemd[1]: Dependency failed for Swap.
-- Subject: Unit swap.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit swap.target has failed.
--

(here's the full output: http://pastebin.com/bJrPnp5a)

One thing I am noticing, and I'm not sure why, but my ethernet adapter is being renamed from eth0 to rename2:

Code: 
root@prox-home01:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: rename2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether c0:4a:00:02:83:42 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether c0:4a:00:02:83:42 brd ff:ff:ff:ff:ff:ff
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default
    link/ether c0:4a:00:02:83:42 brd ff:ff:ff:ff:ff:ff
root@prox-home01:~#
I have two ethernet adapters in the computer (it's an gaming machine turned into a server). I have two because I bond the connections.

Here's some other info:

http://pastebin.com/bR5ptrE1

Code: 
root@prox-home01:~# lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to PCI bridge (external gfx0 port A)
00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD790 PCI to PCI bridge (PCI express gpp port A)
00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RX780/RD790 PCI to PCI bridge (PCI express gpp port D)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c)
00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770]
04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Juniper HDMI Audio [Radeon HD 5700 Series]


And finally, are there mirrors for no-subscription? The download.proxmox.com is EXTREMELY slow on my connection (20KBps). Not sure why exactly...
 
Update: If I edit /etc/fstab and comment out this line:

Code: 
/dev/pve/data /var/lib/vz ext4 defaults 0 1

It boots without issue. Could this be a device issue?

Code: 
root@prox-home01:/# fdisk -l

Disk /dev/ram0: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram8: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram9: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram10: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram11: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram12: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram13: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram14: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram15: 64 MiB, 67108864 bytes, 131072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sda: 139.8 GiB, 150039945216 bytes, 293046768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F238F8D7-ADCC-4B72-826A-A6867FB17EA2

Device      Start       End   Sectors   Size Type
/dev/sda1      34      2047      2014  1007K BIOS boot
/dev/sda2    2048    262143    260096   127M EFI System
/dev/sda3  262144 293046734 292784591 139.6G Linux LVM

Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x7a51eb13

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdb1        2048 1953525167 1953523120 931.5G 83 Linux

Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xb7c212e7

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdc1        2048 1953525167 1953523120 931.5G 83 Linux

Disk /dev/mapper/pve-root: 34.8 GiB, 37312528384 bytes, 72876032 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/pve-swap: 11 GiB, 11811160064 bytes, 23068672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/pve-data: 77.9 GiB, 83605061632 bytes, 163291136 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

root@prox-home01:/# df
Filesystem           1K-blocks    Used Available Use% Mounted on
udev                     10240       0     10240   0% /dev
tmpfs                  2460380    9088   2451292   1% /run
/dev/dm-0             35735184 1615500  32281400   5% /
tmpfs                  6150948   31200   6119748   1% /dev/shm
tmpfs                     5120       0      5120   0% /run/lock
tmpfs                  6150948       0   6150948   0% /sys/fs/cgroup
/dev/mapper/pve-data  80233296   53044  80163868   1% /var/lib/vz
/dev/fuse                30720      12     30708   1% /etc/pve
tmpfs                      100       0       100   0% /run/lxcfs/controllers
cgmfs                      100       0       100   0% /run/cgmanager/fs
 
  • Like
Reactions: josegb
Hi,

we had the same problem after changing the motherboard of a system.
Proxmox cannot mount some logical volumes during boot, it comes up in maintenance mode. The strange thing was, that all "failed" volumes are mounted and working after login into the maintenance mode. There are also some NICs with names like "RENAMED", "RENAMED2".

Code: 
# everything mounted
mount | grep mapper
/dev/mapper/pve-root on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
/dev/mapper/pve-data on /var/lib/vz type ext4 (rw,relatime,data=ordered)

# search for failed
journalctl -xb |less
-- Subject: Unit dev-pve-data.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-pve-data.device has failed.
--
-- The result is timeout.
Aug 09 18:31:32 pxnc systemd[1]: Dependency failed for /var/lib/vz.
-- Subject: Unit var-lib-vz.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var-lib-vz.mount has failed.
--
-- The result is dependency.
...

After hours of searching we found the solution:
There are entries for nonexisting NICs (of the old Hardware) in /etc/udev/rules.d/70-persistent-net.rules. After removing/commenting out these lines the system boots normally.
Code: 
vi /etc/udev/rules.d/70-persistent-net.rules

# PCI device 0x8086:0x1533 (igb)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="XX:XX:66:a4:06:61", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x1533 (igb)
#SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="XX:XX:66:a4:06:60", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
...
 
Hi! I have the same issue.
After edit "/etc/udev/rules.d/70-persistent-net.rules" and removing/commenting out these lines the system boots normally.
But if I reboot again, The lines are regenerated below and the name of the interface change :(
 
kapi2454,

1. comments all fines presents in 70-persistent-net.rules, and reboot
2. after reboot, if the interfeces are present again, edit the same file and change your intergaces names as you need(if ethX is switch with ethY - replace only "eth0" with "eth1" as a example) and reboot
3. after the switch, the names will be what you want
 
Last edited:
Doen't work but I found a solution.
The script /lib/udev/write_net_rules regenerate the lines that I comment. Soo in the top of that script I put "exit 0".
Then I comment again all in /etc/udev/rules.d/70_persistant-network.rules.

I reboot a cup of time, late I shutdown and all work great and fast.
I see eth0 (192.168.1.11) and eth1(10.10.10.11). All work fine, no more renames :)
Thank you for all, I hope that my post help some one else.
 
  • Like
Reactions: James Crook
kapi2454 said:
Doen't work but I found a solution.
The script /lib/udev/write_net_rules regenerate the lines that I comment. Soo in the top of that script I put "exit 0".
Then I comment again all in /etc/udev/rules.d/70_persistant-network.rules.

I reboot a cup of time, late I shutdown and all work great and fast.
I see eth0 (192.168.1.11) and eth1(10.10.10.11). All work fine, no more renames :)
Thank you for all, I hope that my post help some one else.
Click to expand...

After half a day of thinking i was knocking a cable after swapping out the network card....
This looks like it solved my issue !!
 
James Crook said:
After half a day of thinking i was knocking a cable after swapping out the network card....
This looks like it solved my issue !!
Click to expand...

Only half day? lucky men ... :)
I was working on that fail for about 4 days.
I think that is an linux error, because it happend the same in other distros. And in some machines like IBM 3550 this problems doesn't exist whith the same installation iso.
 
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
Back