Recent content by gothbert

Thank you for considering my suggestion regarding the error message! Actually, yesterday, I was tempted to clear or format the tape. Though, last week, I initiated what I thought was a short erase but clearing the tape lasted hours. So fiddling with the first block was my quick fix for the size...

I finally solved it. The parameter MaxRecvDataSegmentLength was 8192. set parameter MaxRecvDataSegmentLength=262144 in targetcli did not fix the issue. The reason was the small tar archive previously written to the tape for testing purposes. It created a 10k block whereas proxmox-tape label...

Upgraded to PBS 4.2.7, rebooted. Can get the status of the tape library and can read the test data I have previously written to the tape from PBS, but now labeling the tape fails immediately in another way: root@pbs:~# proxmox-tape label --drive drive --label-text BN0001L8 -pool bn-continue...

It's ISCSI/LIO. Here is the relevant part in the log (repeating) after issuing the label command: [ +0.000006] Known ACL iqn.1993-08.org.debian:01:eac885df5da1 is trying to connect [ +0.000008] Entering iscsi_target_restore_sock_callbacks: conn: 00000000ccd18d91 [ +0.000008] Sending Login...

That sounds promising, so let's go. I choose a systematic reproducible approach. *** 1 Power on the Quantum Superloader 3 (QSL3) and wait until it settles into "System Ready" state. *** 2 Power on the target host (Debian 13.7) and wait until it has fully booted. Log in as root and check...

Thanks for the tips. I already got quite deep into these things recently. The drive and the library on the target are referenced by-id because the generic device names /dev/sg0 /dev/sg1 ... are randomly assigned after a restart of the machine. The devices on the pbs server are correct, as far as...

I run PBS 4.2.6. A Quantum Superloader 3 is connected via iSCSI. The iSCSI target is a Debian 13.7. PBS web interface shows the library slots and drives. I have a LTO-8 cartridge in the drive which is labeled BN0001L8. proxmox-tape barcode-label -pool bn-continue --drive drive gives...

Dear all, after updating VM guest to Windows 11 Pro 24H2 and changing some settings, the host (Xeon E3-1230 v3) had a 100 % load on all cores assigned to the VM. There are quite a lot of similar reports on that issue in this and other forums. I managed to solve the issue as follows: Turn off...

It has been a while since the last activity in this thread. Though, I would like to conclude with what I did in the end. I decided against virtualizing the NAS due to the dependencies it would create between storage and VMs and hosts on the local net. I also decided against switching to...

Lösung siehe hier: Forum-Thread

I am quite sure I found the reason for the aforementioned behavior. As mentioned in another, previously unrelated thread, I have issues with a blocking ZFS on RAID10 on consumer grade SSDs, which hosts the VMs. I moved the VMs to LVM over ISCSI (disks on a separate NAS). From thereon...

I downgraded the guest tools and drivers from 0.1.240 to 0.1.204 but no change in behavior. Plus (both with the most recent and the older guest tools and drivers): the VMs sponteneously goes to pause mode soon after start and cannot resumed - I need to stop and start again.

Thanks for your reply. The latest guest tools are installed and running when the VM is in normal running state. When hibernating, the VM is left in a kind of zombie state: no display, no access to the guest tools, just a spike of CPU activity now and then.

(this is a cross-post from the German forum - I try my luck here again) For a few days now, my VMs with Windows 11 as the guest operating system no longer switch off completely after going into sleep mode (Hibernate). It looks like this in the user interface: I cannot reach the console...

Hallo, seit einigen Tagen schalten sich meine VMs mit Windows 11 als Gastbetriebssystem nach Übergang in den Ruhemodus (Hibernate) nicht mehr ganz aus. Das sieht in der Oberfläche so aus: Die Konsole lässt sich nicht per NoVNC oder Spice erreichen. Ein Reset ist nicht möglich, es kommt die...