Search results

Thanks!

Hi, Continuing testing of Dell TL4000 tape library with PBS 3.1.2 : - I made a few tape backup with an encryption key. - I removed all the files in /var/lib/proxmox-backup/tape/ (inventory.json and the UUID.log and .index) - I removed the media pool and encryption key - (the two step above...

In this case I loaded the tape in the drive to label it to expand the media pool so that the next backup job would have a media to use. I guess I have to remember to unload when I do format and label tapes (the nice thing about having multiple drives is that you can work while a backup job is...

Hi, Using PBS 3.1.2 with Dell TL-4000 library with 3 drives, when the next available tape in the media pool for a job is already loaded in a drive but not the drive set for the job it seems that PBS doesn't unload by itself but rather asks for the user to do it. Here the job is set up for...

Hi, for the record we have a Dell TL4000 tape library with three drives (internally IBM 3573-TL + 3 ULT3580-HH7 drives) and with PBS 3.1.2 root@r730xd:~# proxmox-backup-manager versions proxmox-backup-server 3.1.2-1 running version: 3.1.2 Everything seem to work fine, PBS web UI and pmtx...

Hi, We have one old hdd where the column "Type" in the "Disks" node view shows as "unknown" (instead of "SSD" or "Hard Disk") Our proxmox version is 7.4 up to date kernel 5.15.108-1-pve on this server. Here is smartctl of the disk : === START OF INFORMATION SECTION === Model Family...

Hi, Running a PVE 7.4.15 cluster with 5 nodes and PVE ceph pool replica 3 "ceph1" When I detach a "ceph1:" disk from a VM "vm1" on node "node1" and I then go to disk action / reassign owner on the now unused disk the proposed target VM list are only the VM running on "node1". Is there a...

Hi, During the upgrade PVE 7 to 8 on my test system I get to validate change or not on /etc/lvm/lvm.conf with lots of change. Most of them seem to be to comment a default value setting: --- /etc/lvm/lvm.conf 2021-07-19 16:01:37.893450177 +0200 +++ /etc/lvm/lvm.conf.dpkg-new 2022-10-19...

Just hit this issue on our proxmox, applied the patch from the mail thread. root@pve:/usr/share/proxmox-acme# diff -u dns-challenge-schema.json~ dns-challenge-schema.json --- dns-challenge-schema.json~ 2022-12-07 13:20:49.000000000 +0100 +++ dns-challenge-schema.json 2023-01-19...

Indeed host is PVE 7.3 with kernel Linux version 6.1.0-1-pve and root filesystem is on 2 disk ZFS mirror, and /tmp on it.

After setting snapdir=visible on the zpool I redid a backup, "file restore" on it shows .zfs/snashot/ but when I try to click on "+" on one of the snapshot I get an "Error" popup with the following message: Tried a few things but still got the above Error popup from "file restore", may be...

Yes indeed snapdir is set to hidden (default value). I will try zfs set snapdir=visible Thanks!

Hi, When I backup a VM disk formatted in ZFS in PVE 7.3 to a PBS 2.3 datastore, I can use "file restore" to see files on the various ZFS dataset. But I couldn't find a ".zfs/snapshot/" on the file restore interface, is it possible to browse the dataset snapshots in some way in PVE/PBS ...

One blocking issue has been fixed recently about the upload of small files via the API: https://bugzilla.proxmox.com/show_bug.cgi?id=3990 Upload of small iso fails with error 501 upload failed So nothing blocks the snippet yaml patch technically now.

Note: it didn't last long and even with latest 5.15.64-1-pve I had an issue of losing connection to disks with ASM1062 startech 8P6G-PCIE-SATA-CARD has 4xASM1062 inside and shows the issue too. Looking for recommandations for a PCIe 8 port SATA or 2xminiSAS PCIe non RAId card that doesn't have...

Thanks! I tested updating the trunk list via qm set NNN -net0 and it worked as expected without having to reboot the VM.

Hi, I have a proxmox VM with the following network configuration: net0: virtio=xx,bridge=vmbr0,trunks=2;3;4 I wanted to add VLAN 5 to the trunk without having to reboot the VM. I first added ";5" to the configuration line. But I ended up doing on the hypervisor where the VM is running...

Patch but not working yet, help welcomed! https://lists.proxmox.com/pipermail/pve-devel/2022-April/052548.html

For reference it has been opened: https://bugzilla.proxmox.com/show_bug.cgi?id=2208 Bumped multiple times

No issue after two weeks with 5.4.157. I see that PVE 7.1 has now 5.13.19-2 which should have the fix too.