Just to be clear, the steps would then be:
# set disk offline
zpool offline rpool /dev/WRONG_PARTITION_DISK
# force-remove all possibly remaining data-fragments
dd if=/dev/zero of=/dev/WRONG_PARTITION_DISK
# copy partition table from healthy disk and write new UUIDs
sgdisk...
Would these be the next correct steps?
Is there something I missed?
# set disk offline
zpool offline rpool /dev/WRONG_PARTITION_DISK
# copy partition layout and erase UUID + label (thanks ubu)
sfdisk -d /dev/SOME_WORKING_DISK | sed 's/, uuid.*//; /label-id/d;' | sfdisk...
Ok, the last resilvering is done and it, again, resulted in there being no boot partition.
This is the current setup:
# lsblk -o +FSTYPE,PARTTYPENAME
sda 8:0 0 14.6T 0 disk
├─sda1 8:1 0 1007K 0 part BIOS boot
├─sda2 8:2 0 512M 0 part...
So, after checking with cfdisk, I can see that /dev/disk/by-id/ata-ST16000NM001J-2TW113_ZRS1QMPT still has only 2 partitions instead of 3 and there's no BIOS boot partition in sight.
But what else am I to do?
I took a healthy disk, gave its partition table to the unhealthy disk (using sgdisk)...
Thank you for your answer.
Seeing as I am replacing a disk with itself, I did the following:
# the wrongly partitioned disk: /dev/disk/by-id/ata-ST16000NM001J-2TW113_ZRS1QMPT-part1
# removing the disk
zpool offline rpool /dev/disk/by-id/ata-ST16000NM001J-2TW113_ZRS1QMPT-part1
zpool labelclear...
Hello dear Proxmox Backup users!
One of our 4 HDDs failed in our Proxmox Backup Server.
We replaced this with a new HDD and then re-silvered the whole pool.
Now, after resilvering, I realised I may have made a mistake.
See this screenshot:
You can see here that every HDD has the following...
Thank you for clearing things up. I will wait until pve-qemu-kvm v8.0.2-4 hits the enterprise-repo and report back after that :)
Best regards,
pixelpoint
Dear Proxmox Users and Maintainers / Developers,
I cannot seem to roll back (maybe only some) VMs.
The full rollback log is:
Logical volume "vm-196-disk-0" successfully removed.
WARNING: You have not turned on protection against thin pools running out of space.
WARNING: Set...
I actually didn't do anything different then the last time I tested.
I just set the environment variables for the Repo and Password and execute proxmox-backup-client benchmark
I just assumed the change in number of chunks sent is automatic and probably rises and falls with available bandwidth...
Ok, we found the "culprit": One of our employees uploaded a full-backup (2 TB) to the cloud, which took ~6 days to complete.
That's why the sync was limited in speed.
Regarding the iperf3 retries:
I tested again today (the full-backup upload has conclued already) and got this:
cloud server ->...
Dear Proxmox Forum Community,
I have encountered a problem with the sync between local PBS and remote PBS.
The Setup
We run a Proxmox Backup Server internally for backing up Proxmox VE VMs (+ proxmox-backup-client for 2 smaller workstation hosts).
The internal PBS is of course behind a...
I enabled the following Repository:
deb http://download.proxmox.com/debian/pbs bullseye pbs-no-subscription
After seeing that the new client does not work on Ubuntu 18, I re-enabled the "old" repository (for Ubuntu 18 hosts).
deb http://download.proxmox.com/debian/pbs buster pbs-no-subscription...
Dear Proxmox Community,
we have been running Proxmox VE + Proxmox BS and are quite happy with it.
Just this morning, I needed to restore a single file from an old backup and it's been as easy and fast as it could possibly be.
So a big thank you to the proxmox team for a nice, easy and...
Dear Proxmox Community,
I deleted the VM yesterday, created a new one and booted from Windows 2012 R2 x64 ISO to restore the latest Windows Backup.
This worked and the VM is now up and running!
For the restore to work, I had to change the Disks to IDE.
Even when installing the correct drivers...
Dear Proxmox Community,
last night I had to migrate a Physical Windows Server 2012 R2 x64 UEFI/GPT Server to Proxmxo VE 7 (for a customer, we already use Proxmox VE Enterprise).
I tried many different things but in the end the virtual Windows did not start.
Here's what I tried
Installed...
Hallo liebe Proxmox Community,
wir haben ein Problem mit APT Updates und den Proxmox Repositories.
Beschreibung der Umstände
Wir sichern unsere Ubuntu Root-Server (18.04 und 20.04) mittels Proxmox Backup Client auf unseren Proxmox Backup Server (Root-Server Hetzner).
Das Proxmox Backup Repo...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.