Search results

Hi there, i am running proxmox 6.2-10 with ceph 14.2.9 i also installed the ceph-manager-dashboard (to get the alert module) via apt install ceph-mgr-dashboard and then configured the alerts module like this: ceph mgr module enable alerts ceph config set mgr mgr/alerts/smtp_host...

@dcsapak classic regexp bug with greediness ;-) thought as much Thanks for the quick fix! :-)

Hi there, i am currently on proxmox 6.1-8 and have a Samsung 970 Evo NVME SSD. The Smart values differ quite alot from other SSDs i had: root@pve:~# smartctl -a /dev/nvme0 smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.3.18-3-pve] (local build) Copyright (C) 2002-19, Bruce Allen, Christian...

but you could try to run proxmox 5.x to see if the problem disappears.

Sorry, but as i wrote earlier, i switched the platform altogether. so no, i think this was never fixed.

but something did change with proxmox 6 as the issue is no longer present on my microsoft surface pro (5). On my other cluster (running proxmox 5) the issue is still there.

yes, here it is: dir: local disable path /var/lib/vz content images,iso,rootdir,vztmpl maxfiles 0 shared 0 zfspool: zfs-data pool rpool/data content rootdir,images mountpoint /rpool/data sparse 1 dir: zfs-templates...

Ok, i think the simple explanation is like this: Proxmox depends on a matching mountpoint in reference to the pool/dataset so if the tank is called tank0 and the dataset is called test there must be a mountpoint /tank0/test/ This is where all the confusion originally came from. because i...

ok, i got this now. should have inspected the used command mount -o ro -t zfs rpool/data/subvol-100-disk-0@vzdump /mnt/vzsnap0// correctly: my pool is named tank (because that is the commonly used name for creating zfs-pools online). but proxmox had issues creating LXCs that way and i found...

Hi there, i am currently testing ZFS instead of my "old" setup (mdadm raid) and wanted to start the usual backup cycle. My Qemu-VMs will get backuped perfectly, my LXCs won't. Here is the log: Virtual Environment 6.1-3 Search Datacenter Server View Logs () INFO: starting new backup job...

@rkk2025 you can always download the corresponding header files from here: http://download.proxmox.com/debian/pve/dists/buster/pvetest/binary-amd64/ i.e.: wget "http://download.proxmox.com/debian/pve/dists/buster/pvetest/binary-amd64/pve-headers-5.3.10-1-pve_5.3.10-1_amd64.deb" dpkg -i...

Great Tip!

i switched my Hardware-Plattform from an AAEON Up-Squared (Intel N4200, 8GB RAM) to a Custom-Built ASRock Deskmini A300 (Ryzen 3400G, 32GB RAM) - using all the same USB-Devices. With the new Server, this Problem does not happen. So it is not really solved but atleast bound to some form of...

i also tried disabling autosuspend for all devices at boot time by adding splash usbcore.autosuspend=-1 to the kernel command line. but no luck here. Running Proxmox 6.0 with the "old" Linux pve 4.15.18-21-pve #1 SMP PVE 4.15.18-48 (Fri, 20 Sep 2019 11:28:30 +0200) x86_64 GNU/Linux Kernel...

just FYI: i updated to the latest testing kernel Linux pve 5.3.7-1-pve #1 SMP PVE 5.3.7-1 (Wed, 23 Oct 2019 19:00:21 +0200) x86_64 GNU/Linux but the problem still persists. switching to a 4.15.x kernel resolves the issue.

Hi Chris, thanks for your reply the output is just the same as with the previous version: root@pve:/root# cat /sys/bus/usb/devices/2-2/power/control on so, autosuspend is not allowed. The disconnect/reconnect also happens on a drive that can never be suspended because it has virtually no...

or, depeding on the use-case for the GPU you could use containers to access the card directly (hw-encoding/decoding for example)

Hi there, i just upgraded last night to Proxmox 6.0, since then i have random disconnects for my USB-attached drives. I currently have 3 HDDs connected via XHCI which worked flawlessly on Proxmox 5.x. After the upgrade i.e. the disc with the name /dev/sda gets disconnected after a short period...

Tested on proxmox 5.4-5, the bug is still there.

@oguz: i think you got me wrong. I do know how to cleanly shutdown containers, which works very well from the CLI as well as the Web-GUI: when issuing the shutdown from within the Web-GUI it sends "pct shutdown" to the selected container. But the issue is: if for whatever reason the host is...