- after kernel update pve doesn't come up
- whe I login to the console and try zpool status I get:
/dev/zfs and /proc/self/mounts are required
- when I try modprobe zfs I get
"module zfs not found in directory /lib/modules/5.15.60-2-pve"
how can I fix this error?
During bootup it shows "failed to insert module autofs4" and following that then a couple of other error messages. All that leads to a non working system.
When I boot the older 5.4 kernel the system boots normally, but my vm won't start, showing only the PROXMOX logo in the console.
I need...
Same problem here:
Linux sv-pve 5.3.18-2-pve #1 SMP PVE 5.3.18-2 (Sat, 15 Feb 2020 15:11:52 +0100) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright...
I have a similar issue here (without Ceph involved) between our PVE host and a FreeNAS nfs share (1GB connection):
()
INFO: starting new backup job: vzdump 104 --mailto admin@imedos.de --compress lzo --mailnotification failure --mode snapshot --storage NFSFreeNAS --quiet 1
INFO: Starting Backup...
I have two PVE systems which are not connected, both have a valid subscription and the same apt sources settings, but I get different results on running package update while both claiming that no updates are available:
proxmox-ve: 5.1-40 (running kernel: 4.13.13-4-pve)
pve-manager: 5.1-46...
Hello,
at the headquarter of our facility is currently running a PVE server (v5.1), on which several virtual servers are operated. We will soon get another location and the network there will be connected to the main site via VPN. The line capacity for the VPN is extremely limited (about 1 ~ 2...
Same here:
qm start 100
WARNING: Image format was not specified for '/dev/zvol/rz2pool/vm/vm-100-disk-1' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format explicitly...
OK - I tried this, but without luck - still get error code 43 in device manager.
Here is my config:
xyz@pve:~# cat /etc/pve/qemu-server/100.conf
agent: 1
args: -cpu host,kvm=off
balloon: 2048
bios: ovmf
bootdisk: scsi0
cores: 4
cpu: host
efidisk0: local-zfs-vms:vm-100-disk-1,size=128K
hostpci0...
@futiless
did you get this to work finally? I'm stuck at the same place: successfully managed to passthrough a Nvidia Quadro P400 to my Win10VM, but Driver hangs with Error 43
OK - so now I installed an Intel Octane 16GB module, reconfigured the zpool to use this as zlog and run those tests again - here are the results for those who are interested:
Test with Samsung EVO960 nvme as cache and Intel OPTANE 16GB as zlog
root@sv-pve01:/dev/disk/by-id# fio...
I'm trying to setup another PVE on an old Intel S5500BC with an SSD and a couple of SATA drives connected to the onboard SATA (AHCI mode in BIOS)
The Mainboard BIOS is the last available from 2014.
I'm trying to setup proxmox on the SSD and the data will be located on an zfs pool on the 4 6TB...
Windows 2008 64bit server
balloon driver version: 08/11/2016,60.73.104.12600 from virtio-win 0.1.126
after installing it with blnsvr -i I get:
Service not started.
Current State: 1
Exit Code: 1008
Service Specific Exit Code: 0
Check Point: 0
Wait Hint: 0
Starting it inside services...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.