Recent content by gothbert

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...

Thank you for your replies. I certainly cannot ignore two people blaming the SanDisk SSDs, with cwt reporting similar symptoms as mine. What's nagging in my head is that I remember the same issue with a 3 enterprise HDDs in a RAID Z3, which led to the upgrade to 4 consumer SSDs in a RAID 10. I...

Thanks for the swift reply. The 4 SSDs are SanDisk SSD Plus 1000 GB. Wearout is not reported. Here the SMART data for the fourth device (the others have similar readings with less bad blocks): smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.11-7-pve] (local build) Copyright (C) 2002-22, Bruce...

Dear community, I run PVE on a Supermicro X10SLM+-LN4F board with 8 x Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz CPU and 32 GB ECC DDR3 RAM in a Supermicro Chassis with 4 x 1 TB SATA SSDs in a ZFS RAID10 array (as per recommendation in this forum a few years ago). Although the hardware is now...

Well, that it explains it all. The user did not have any permissions on the datastore because I did not understand the dependency. I now carefully reread the docs and it actually says "The resulting permission set on a given path is then intersected with that of the corresponding user." about...

Thank you for the reply! With token permission: 1) I deleted the sync-user@pbs!token1 on the Local PBS and started from scratch, assigning sync-user@pbs!token1 the DatastorePowerUser role on datastore/nas-backup-1 (just to be sure, but DatastoreReader would be the appropriate role, I suppose)...

Still holiday season. Interestingly there is no one with a working remote backup who would like to help. Changed the title of the thread to grab some attention.

I ran into the same issue today. All recent backups were flawed. Looks like the first bytes of the disk were zeroed. This is a severe issue as it goes undetected for a long time until the server is rebooted. It took me hours to investigate and repair. I used testdisk to recreate the root partion...

Comforting that I am not the only one. Hopefully someone from the Proxmox team will pick this up and either enlighten us on how to do it right or confirm an issue in the current version. Or maybe a user who managed to implement the offsite backup can provide the right hint.

Dear all, I am struggling with configuring an offsite backup from Local PBS to Offsite PBS. This is what I have done so far: Local PBS has Datastore /datastore/nas-backup-1 with fully functional backups. Created user sync-user@pbs and API token sync-user@pbs!token1 on Local PBS...