Search results

# pmtx status --changer msl2024 using device /dev/tape/by-id/scsi-DEC80205XR Transport Element (Griper) 0: Empty Data Transfer Element (Drive) 0: Empty, Serial: HUE08455BM Storage Element 1: VolumeTag("PBS001L4") Storage Element 2: VolumeTag("PBS002L4") Storage Element 3...

thanks! i suspected, that i was doing something wrong or have not fullfilled all needed dependencies. so i removed all rustc and dependencies which i installed previously, then recompiled exactly as in the documentation and build notes you posted above. still got same error. now i have seen...

task log 2021-07-22T20:24:56+02:00: Starting tape backup job 'ait:dailyfull:lto4:daily' 2021-07-22T20:24:56+02:00: update media online status 2021-07-22T20:24:56+02:00: starting new media set - reason: policy is AlwaysCreate 2021-07-22T20:24:56+02:00: media set uuid...

the panic happens less often, than the buffer error before. in the changer menu clicking reload it was previously 3-4 times error, one successful. now 1-2 succesfull, one panic. i will run a backup job now, and see, if will finish successfully. could take a while (12TB, LTO-4...) are those...

Package built and installed. Now i have for the first time a successfull job (cleaning drive). But, there is now this error instead: 2021-07-22T20:04:58+02:00: TASK ERROR: worker panicked: unknown type. This error happens now with ~same frequency, as the one before, while before i could not run...

never mind, downgraded rustc to 1.52.1, now compilation is was successfull. building a package now. rustup install 1.52.1 export RUSTUP_TOOLCHAIN=1.52.1 source "$HOME/.cargo/env"

i am failing to build the package from git master branch (including all your todays commits). do i need an older lexical-core library to build successfully? not a dev here and especially rust is new for me :) Debian 11, Kernel 5.11.22-4 PBS devel sorurce, updated + installed all dependencies

Thank you Dominik! there is no such file on installation, do i need to compile from source? or will the patch be packaged in the testing repository?

Are you sure it is just after restart, or is it after shutdown + start? The fast PBS backups are based on Qemu dirty bitmap, witch tracks the changes on virtual disk, if you stop your VM the bitmap is reset, so backup needs to reread the whole disk image again. Still backup does write only...

Hello, got a used HP MSL2024 changer with an LTO-4 drive and try to setup it up with PBS. PBS is installed on a HP DL380g8 (2x Xeon 2660v3, 192GB DDR3 ECC, ZFS/Datastore on SSDs). Following error happens on every occasion. It happens while try to load or unload a tape, starting a backup and...

Hi @blanco, is the additional ip from the same subnet or different? if its in same subnet as the main ip, you could just assign the main ip to your vmbr0 instead of enp4s0 (leave enp4s0 all fields empty) and the additional ip configure as wan ip in the pfsense. obviously, if you assigned your...

Hi, PVE7.x Linux Bridge does not work currently on Hetzner. You could fix your installation following way: remove vmbr (all vmbrs) from /etc/network/interfaces. leave only the physical interface. name might be different for you (to list all available interfaces try ls -d /sys/class/net/*) auto...

Oh, most users are just quiet and waiting patiently. I would add my "+1" on Mac and Windows clients then :)

get current postfwd3 download link from https://postfwd.org you might also need to install some perl modules, if missing (see documentation https://postfwd.org) wget https://postfwd.org/postfwd-2.03.tar.gz tar -xzvf postfwd-2.03.tar.gz cp ./postfwd/sbin/postfwd3 /usr/local/bin/postfwd3 mkdir...

Hallo zusammen, ich habe genau das selbe bemerkt nach dem Upgrade auf PVE 6.4). Finde es sehr gut, dass man dies in der GUI sieht. Bin aber unerwartet verwundert gewesen und bin via SUFU genau hier gelandet... ...nach dem ich angefangen habe die OSDs, eine nach der anderen, zu konvertieren...

you could give the opns vm more cores and ram + set cpu to "host" instead of kvm64, maybe that will help

hm... strange, i am out of ideas. maybe you could search or ask in opnsese forum. i am running opnsendse since a few years on proxmox and had same issues at the begining. disabling hardwareoffloading helped instantly: 100+ vlans, inter-vlan routing is 550-600Mbits (cpu is the limiting factor...

suppress ARP too, won't hurt :)

https://docs.opnsense.org/manual/interfaces_settings.html interfaces / settings