Search results

no, I am unable to import by name. I'll try setting the rootdelay to 30 seconds.. it's at 20 seconds now.

Order of things: * Blue PMX Screen * Loading Ramdisk * (clear screen) * Loading, please wait... Let me know which logs you need me to pull, etc.. I've posted hardware info above. root@pmx1:~# zfs list -t all NAME USED AVAIL REFER MOUNTPOINT rpool...

Sorry if I was unclear. This happens upon first boot after initial install. Continues to happen after upgrade to latest versions of everything. If you'd like to give me logs to collect after a fresh install, let me know what files, I'll grab & post them.

PVE installer. 4.3, then upgraded. FWIW, first boot after install won't boot without assistance. There's something missing here....

^^ Worked like a charm, thank you @tdonkers

on apt-get upgrade, some packages were held back, so I force updated them all, which seems to include the bpo80 fix. proxmox-ve: 4.3-71 (running kernel: 4.4.21-1-pve) pve-manager: 4.3-9 (running version: 4.3-9/f7c6f0cd) pve-kernel-4.4.21-1-pve: 4.4.21-71 pve-kernel-4.4.19-1-pve: 4.4.19-66...

I'm running a couple sets of older supermicro (Opteron 2xxx/8xxx series) motherboard, and they're all having this issue, even on a completely clean new install. Tried all the options listed here, still can't get a clean boot. this works. can then boot cleanly. also works hasn't...

+1 - this worked for me. Would be nifty to have a few items like this added to the GUI options

I suspected it had something to do with open-vswitch, so I'd removed it yesterday, hadn't rebooted yet.. Put it back to grab the output.

Works fine now in PMX 4.x

Still happening under latest version: pve-manager/4.3-1/e7cdc165 (running kernel: 4.4.19-1-pve) [ 21.074621] systemd[1]: Breaking ordering cycle by deleting job networking.service/start [ 21.074625] systemd[1]: Job networking.service/start deleted to break ordering cycle starting with...

Wondering if anyone has been able to make nvidia-smi/cuda/etc work in an LXC container. Feels like I'm close...configs added correctly in LXC: lxc.mount.entry = /dev/nvidia0 dev/nvidia0 none bind,optional,create=file,uid=65534,gid=65534 lxc.mount.entry = /dev/nvidiactl dev/nvidiactl none...

stood up a new machine side-by-side with my existing 3.x PMX installation, slowing learning the new. Oddly the PMX4 box isn't starting networking on boot. "service networking start" brings everything up. .and this is in the log. Ideas? 22.219739] systemd[1]: Cannot add dependency job for...

Had this happen as well under 4.4.15-1-pve.. added a cache drive to rpool, same exact symptoms. Imported rpool, removed cache, rebooted, all good. Bug

So @tom - any suggestions?

dist-upgrade PVE (4.4.15-1-pve), seems to have solved it, no other changes root@pmx8:~# grep c_max /proc/spl/kstat/zfs/arcstats c_max 4 68719476736 ARC Size: 1.93% 1.24 GiB Target Size: (Adaptive) 100.00% 64.00 GiB Min Size (Hard Limit): 6.25% 4.00 GiB Max Size (High Water)...

Tom: Updated as requested, didn't change behavior in the least. root@pmx8:~# pveversion -v proxmox-ve: 4.2-60 (running kernel: 4.4.15-1-pve) pve-manager: 4.2-17 (running version: 4.2-17/e1400248) pve-kernel-4.4.6-1-pve: 4.4.6-48 pve-kernel-4.4.15-1-pve: 4.4.15-60 lvm2: 2.02.116-pve2...

This was a fresh install from ISO, then update && upgrade && reboot. Which ones need updated?

apt-get update'd yesterday, should be recent enough? root@pmx8:~# pveversion -v proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve) pve-manager: 4.2-2 (running version: 4.2-2/725d76f0) pve-kernel-4.4.6-1-pve: 4.4.6-48 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1 pve-cluster: 4.0-39...

New install of PMX4 (4.4.6-1-pve) - backup/restored my containers from pmx3, imported my ZFS pools, and (almost) everything is peachy.. New machine has 4x the RAM, so I'm looking to increase the amount of ram ZFS is allowed to use.. Worked out the math, and increased zfs_arc_max to 64G, by...