Search results

I had a pve up and running with grub with gpu passthrough working without a hitch. I reinstall proxmox with a zfs mirror and get a shock when I see systemd and already now I think...bah, this is going to cause issues. A few moments later, my fears were confirmed a vm with a gpu added and romfile...

Quote: "https://pve.proxmox.com/wiki/Pci_passthrough is outdated (i ought to update this page soon)" Jul-2019 Reponse november-2020: "yes, it ought to be updated." The systemd information makes no sense on that page.

Hello, this is a non-production friendly guide to how to get proxmox to work with ZFS2.0 and persistent L2ARC cache for those of you who use GPU passthrough and use proxmox as basis for a workstation that is shutdown every day. Please read it all before you venture down this path. It can be...

What would one do if the EFI disk for a debian system was accidently deleted?

SO I aborted the process, being satisfied that at least the C drive of the backup had been restored... then what happens? It decides to remove the file it just restored to 100% :D I am so happy right now I could cry! There could be ALOT of sarcasm and anger involved in my previous...

With the latest data coming in, I multiplied the amount of seconds by 50 to get 100% progress 1% (read 21474836480 bytes, zeroes = 0% (213909504 bytes), duration 5852 sec) progress 2% (read 42949672960 bytes, zeroes = 0% (213909504 bytes), duration 12588 sec) Result is I have to wait 7.2 days...

I have the same problem. Absurd low speed. I have tried reinstalling my entire cluster and the backup server. After doing so the problem remains. Cables have been checked, not the problem. I guess I can look forward to several days of waiting to restore the 1TB of data on the next drive...

As I understand it there is no way to force it to remove these chunks? But to wait 24h5m? I guess I'll just have to advance the system time and revert it after removal then. I suspect that haxx will break something else? But I need that space, like NOW :/

What I noticed before reinstalling yesterday was that /etc/pve/nodes did not contain information for node3 on node 1+2+4. Node3 which was the one that stopped being part of the cluster after adding pve04. These files are however present now on all nodes. The files were present on node3 itself...

The cluster seems to have started existing again magically while I was sleeping... Join information is no longer greyed out. root@pve01:~# pvecm status Cluster information ------------------- Name: ALMA-MATER Config Version: 4 Transport: knet Secure auth: on Quorum...

Yes, disks were totally wiped. Config files for vms in qemu-server was saved

I had a 3 node cluster setup, then I added a 4th node and suddenly the 3rd node was not part of the cluster and the cluster seems to not exist anymore. I reinstall ALL 4 nodes fresh, joined them to a new cluster and now I have the same situation. What is going on here? The "join information"...

Thanks for the reply, will try it shortly :)

Reinstalled PBS today to try to solve some speed issues. Now I have this problem instead: Running the same backup script as before the reinstallation yields this error.. The script runs: proxmox-backup-client backup homes.pxar:/storage/homes --repository root@pam@10.0.0.7:backup --verbose...

Some fun stats I found on reddit from a user who has been using a RMS-200 quite alot of time more than I have :p 115 PB written... When he installed the card it had 49PB written. 1 year later... 115!! === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED...

Yes, works out of the box. Is visible as a standard block device/disk/ssd

If you want to save a buck or two you can obtain the previous model, the RMS-200 (many have seen 60+ PBW but since it is DRAM it does not matter. The onboard flash is only used during power outage. https://www.ebay.com/sch/i.html?_from=R40&_trksid=p2380057.m570.l1313&_nkw=rms-200&_sacat=0

Thanks, I somehow missed that in the documentation when using the search function searching for "password" odd.

I have a fileserver which house several ZFS datasets that I would like to backup periodically. I run this command on the fileserver (pve01) to do the backup manually, but it asks me for password each time. How do I implement the password into the command line so I can do a cron-job...

No, they are two different hosts. There was only 2 disk files in the /vm/images/110 dir. pve02 did not contain the disks physically. They do not share storage. I suspect I misconfigured a datastore to be avail from both hosts.