Search results

I had some quite good results with just adding 2 SSDs as l2arc. That dropped GC and other tasks by some magnitudes. Only problem left is the "not so perfect" read/write-rate to the tape device (around 150mb/s, with tops up to 180mb/s and some dips) The l2arc - in contrast to special devices -...

It seems like PBS doesn't like RAID-controllers, even when they pass-trough the drive entirely. Maybe it relies on some exotic commands that aren't 100% emulated / passed to the drive which linux and other backup tools don't use.

I see you're from .AT ... can you please contact me via PM if you're interested in such a controller? (gerne deutschsprachig!) Unfortunately, i wasn't able to contact you directly.

The controller itself never has been a problem. It passes trough tape-devices. Neither via mt/tar/dd-stuff directly on linux, nor via iscsi or esos talking to a windows-server-vm with veritas backup - everything was fine. So at first, it was not logical to search there. But because i got one on...

After changing the controller from an Adaptec ASR-5805 to a dumb LSI one, at least the labeling works. Right now i've started a backup job, drive is idling: 2022-03-29T09:09:11+02:00: update media online status 2022-03-29T09:09:11+02:00: media set uuid: 548b060a-9dc0-4750-9f41-e1a115063440...

Sorry, didn't notice that. The lto8 is factory new, the lto7 worked for veritas and linux (dd) for several years. no encryption or any extraordinary stuff. dmesg stays silent during the error. Is there a way to dump the communication while doing a task? Maybe that way we can get any further...

➜ ~ sg_raw -r 1k /dev/tape/by-id/scsi-10WT124396-sg 12 00 00 00 60 00 SCSI Status: Good Received 96 bytes of data: 00 01 80 06 12 41 01 10 02 49 42 4d 20 20 20 20 20 ....A...IBM 10 55 4c 54 52 49 55 4d 2d 48 48 38 20 20 20 20 20 ULTRIUM-HH8 20 4e 39 4d 31 00 00 6a 00 00...

Same error: ➜ ~ proxmox-tape scan --drive LTO8 rewinding tape Error: read failed - scsi command failed: transport error ➜ ~ proxmox-tape scan --drive LTO7 rewinding tape Error: read failed - scsi command failed: transport error ➜ ~ Are there some other low-level logs i can provide?

Same thing on the LTO7-drive which. "2022-03-22T11:23:51+01:00: TASK ERROR: read failed - scsi command failed: transport error" Formating went fine!

➜ ~ proxmox-tape label --label-text full --drive LTO8 TASK ERROR: media read error - read failed - scsi command failed: transport error

Thank you very much in advance! The drive is a plain standard LTO8, freshly bought. Vendordiagnostics don't show any problems. The media is nothing special, proxmox-tape status shows some written data: ┌──────────────────────────────────────────── │ Name │ Value │...

proxmox-backup 2.1-1 running kernel: 5.13.19-6-pve proxmox-backup-server 2.1.5-1 running version: 2.1.5 pve-kernel-helper 7.1-13 pve-kernel-5.13 7.1-9 pve-kernel-5.13.19-6-pve 5.13.19-14 pve-kernel-5.13.19-1-pve 5.13.19-3 ifupdown2...

Hello, i freshly connected a new LTO8-drive to my PBS. The drive gets detected. Eject, Erase, Format etc works fine. But i'm unable to label the media. I only get the following error: "media read error - read failed - scsi command failed: transport error" The tape itself is a brand new sony...

Thanks, shouldn't be to hard to script something via python or php... I'll post my result here, if i get it right.

Inside the PBS-gui i am able to change the note of the complete node, not only its items. That way, even if the folder isn't open, i am able to see which VM is contained. I wasn't able to find a command to do this via shell, thus i'm not able to extend the script to do this. Does anyone know how...

nevermind, update AND reboot fixed the problem!

Update: Added it on my private pve via vpn, working. So problem is located at pve, not pbs! My versions are some weeks newer but i can't just restart the customerserver now. proxmox-ve: 7.1-1 (running kernel: 5.11.22-5-pve) pve-manager: 7.1-5 (running version: 7.1-5/6fe299a0) pve-kernel-5.13...

Hello, i freshly installed pbs on the customer site. Unfortunately, the file-restore isn't working as qemu doesn't want to start with a strange errormessage. On my personal installation, everything is working fine. I already updated proxmox-backup-file-restore and proxmox-backup-client, no...