Search results

Hi, created a datastore zpool on attached usb disk, which at the time identified itself by /dev/sdi. Need to change that to /dev/disk/by-id. Tried https://plantroon.com/changing-disk-identifiers-in-zpool/#detach-and-attach Want to export and import -d /dev/disk/by-id...

After kernel upgrade I did a Hibernate on the VM's and a following reboot hung with the same msg as the above shown by izegd. Had to powercycle the host.

Small bump, got the same issue. Moving LV is not a preferred option. Anyone that can hint me to another solution?

No cluster here. systemctl restarted a couple of pve services, after that i could disable this Storage, and delete it. Probably a full disk was one of the cause: "unable to open file '/etc/pve/nodes/pve4/lrm_status.tmp.4655' - Input/output error" Solved.

Any thought on how to remove the beta from Storage? All I get is "delete storage failed: error during cfs-locked 'file-storage_cfg' operation: got lock request timeout (500)" and loads of errors in syslog. pvestatd[4098]: Tuxis_Backup_Beta: error fetching datastores - 500 Can't connect to...

Found this: https://forum.proxmox.com/threads/qm-monitor-and-shell-scripts.6052/#post-34338

https://blog.chrishowie.com/2019/09/19/hot-swapping-virtio-disks-on-qemu/

https://pve.proxmox.com/wiki/Physical_disk_to_kvm

https://research.kudelskisecurity.com/2017/06/07/installing-wireguard-the-modern-vpn/ don't forget the: net.ipv4.ip_forward=1 and PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o IFACE -j MASQUERADE PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t...

Web interface: select Node (not your VM!) it is one line below Datacenter. Select >_Shell stop your VM: qm stop <VMID> convert: qemu-img convert -f qcow2 /var/lib/vz/images/<VMID>/imagediskname.qcow2 -O vmdk /path/to/myNewImage.vmdk copy/move /path/to/myNewImage.vmdk destination

It happened to me too (third time...) on my testserver, HP DL120 G7. This one is running on 2 x 4TB drives. Another one runs on smaller < 2Tb drives, no problems yet. Any hint on what is the cause? Or how to create a boot USB to get it on its feet again?

Suffering from the same (using a usb serial adapter to readout some smartmeter) I created a workaround: Either Logwatch for the above and then perform a reset/reload of the USB. Google for billauer.co.il usb-reset-ehci-uhci-linux Or cron it every 5 minutes... Works for me...