Search results

To anyone interested: The windows guest ran fine, then the proxmox server's console started stating that there was irrecoverable data corruption in the volume and specifically the subvolume of this vm and that the file needed to be removed. I removed the subvolume, but the error persisted...

Turns out /dev/zd128 was the virtual disk of my only windows guest. Doing: gdisk -> p -> v -> w fixed the issue and eliminated the error message. Windows guest boots and runs fine.

Here is the output from gdisk p and v on zd128. Will simply writing the partition table to disk before quitting gdisk solve the problem? I'm concerned about the "Partition(s) in the protective MBR are too big for the disk!" part. root@proxmox:~# gdisk GPT fdisk (gdisk) version 1.0.6 Type...

I stumbled upon these two Error messages when examining another thing in my dmesg today: [ 39.908314] Alternate GPT is invalid, using primary GPT. [ 39.908337] zd128: p1 p2 p3 p4 [ 40.536545] Alternate GPT is invalid, using primary GPT. [ 40.536569] zd192: p1 p2 p3 First of all; what...

My MSI X470 motherboard had an "enroll" setting under the secure boot menu (actually "windows boot settings"), in which I "enrolled" all PCI storage devices (there were only PCI storage devices listed). After that I booted and it worked.

I cannot for the life of me understand what I did, I just messed around with the secure-boot/custom saettings in my bios, but I finally got it to work. My MSI X470 motherboard had an "enroll" setting under the secure boot menu (actually "windows boot settings"), in which I "enrolled" all PCI...

When running "proxmox-boot-tool init" on a new system drive, I get an error message and it doesn't finish. "Failed to create EFI Boot variable entry: Invalid argument" Anybody know what it's about? Is this an efi/bios setting around secure-boot that needs to be changed? It affects both nvme0n1...

I managed to complete the whole operation in a lab environment :) When running it on my production machine I get an error message from proxmox-boot-tool. Anybody know what its about? root@proxmox:~# proxmox-boot-tool init /dev/nvme1n1p2 Re-executing '/usr/sbin/proxmox-boot-tool' in new private...

That did the trick! Thanks!

This might be a bit off topic, but, actually, I am unable to boot into my new VM with either the 7.2 or 7.1/7.0 Proxmox VE ISOs. It leaves me with the following error at boot: ""UEFI QEMU DVD-ROM QM00003 " from PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x1,0xFFFF,0x0): Access Denied" If I load something...

That is actually very good advice :) I'll do that

Allright, then that is probably what I'll do. Is this the correct command to randomize all the GUIDs on a drive? sgdisk -G /dev/sdX Also, I'm guessing that cloning the partitions will not also clone the data to the new drives and that I will need to perform the below steps: zfs snapshot -r...

Thanks to both of you! Yes, the drives are larger, but I'm migrating from three 512GB drives in R5 to two 1024GB drives in R1. Usable pool size should be close to identical, but will it really be possible to clone the partitions if I don't have the same number of drives (and will not be...

I have one of my proxmox nodes' root filesystem on a z-pool called rpool, consisting of three 512GB SSDs in raidz. I would like to fully transfer that filesystem with name (rpool), subvolumes, settings and all, to two 1024GB M.2 nvme drives in a zfs raid-1 mirror. Then take the three SSDs out...

This is not GUI-based, but does the trick for me. I started using "cv4pve-autosnap" for the automatic snapshots of VMs. Brilliant in it's simplicity.

Thanks! The drive accepted the command from hdparm and has not gone to sleep since yesterday as far as I can see.

I recently replaced a faulty HDD in one of my RAIDZ-pools. Before, it concisted of three identical, 8TB Toshiba NAS HDDs. The replacement drive is a 8TB Toshiba NAS drive, but a slightly newer model with more cache etc. It also differs from the other two drives in that it insists on going to...

Ended up trying: "pve-zsync sync --source spool/filestor --dest 192.168.5.2:spool --verbose" It did more or less exactly what I wanted it to do; created and exact copy of the volume on the other node. What I have not figured out how to do, is set pve-zsync up to automatically sync at an...

How would I go about fully synchronizing, say at a 1hr interval, one subvolume of my rpool on node1 to node2? This subvolume does not contain any VMs, only file data created/consumed by my containers on node1 and I would just like to have a live copy of all the data on the other node. Is there a...

Two questions: 1. Is it possible to set up automatic replication of a VM between two nodes without replicating all snapshots? I. e. replicating only the current machine state, but not the snapshots taken of it before? I take daily and weekly snapshots (retain six weekly and seven daily) locally...