Search results

Hi whatishappening, I ran into that as well after configuring LE. The fingerprint is mandatory when lacking 'real' certificates. Once your nodes have LE certs, you can leave the fingerprint empty.

As for the stray 104-image of 11 GB in /var/lib/vz/images/104: I'm not allowed to delete it, as container 104 exists. It was not my intention for 104 to use it, and the config seems to back me up: # pct config 104 arch: amd64 cores: 3 cpuunits: 1201 features: nesting=1 hostname: online...

As a pointer for the next person facing this issue: https://pve.proxmox.com/pve-docs-8/pct.1.html#_restoring_container_backups details: Create volumes for storage backed mount points on the storage provided with the storage parameter (default: local). So, it would seem that I did not set...

Hi news, Thanks for the pointer. The thread discusses whether the configured tempdir is used or not, and that it is corrected by upgrading to the next minor version (all PVE 6, I'm halfway migrating from 8 to 9), with the case that resembles my situation (@agapitox) not posting back on the...

Hi news, Thank you for your reaction! The hardware I listed is PBS (1 GBit copper) , so ballpark about half the performance of your unit. I just found the culprit: besides creating an LV for the container to live in in the assigned storage, it also creates an image in /var/lib/vz/images in...

Hi all, Over an hour and a half ago I started a restore task of a 400 GB container backup. Up to now, restores have been of VMs and containers in the lower tens of GB range, which would ramble for a while and then complete. This one just 'sits there': recovering backed-up configuration...

That's a worthy cause! Yes, indeed, BTRFS is the file system. Other popular options would have been ZFS, XFS or ext4. Is this the situation: Proxmox: hostname = mediaserver one harddisk default Proxmox installation with LVM guest: hostname = Immich_VM type = VM (not container) under...

I'd boot a live distro and see whether the pool can be brought up using regular methods, before staying stuck trying it from initramfs. I presume you don't have an alternative (older) kernel to boot from where the boot configuration is not messed up?

Great that you solved it, thanks for posting back the cause of the issue and updating the thread!

Mostly things are fine, though a bit on the slower side, with HDDs. Migration to faster aggregated storage is the reason for the exercise in the first place. Unfortunately, I woke up to a failed backup, and running fsck gives quite a few suggestions for repair. As to be expected, reported...

Wohoo! The shrink-operation (crosspost for details) has completed, stats are returning, backup is running, and I'm winding down.

Solved! "DELLE", as I recall the solution is called in German :p After waiting for half a day and then fretting for hours. With help of an AI, I got some idea of the state of the process, but things were not actually moving a lot. Until they did, then all of a sudden the operation was over...

That indeed.... The screenshot shows lilliputter lettersoup without zooming, or no more than six 3 cm lettes when zooming in, I was not able to read anything on it :p For me too, good night!

Hi Boerny41, Would it be an option to netboot.xyz or a USB stick to boot a live distro and write a new GRUB? Take care of course to include ZFS if it does not come with the booted distro.

Hi digamman, Welcome to the forums! That must have been quite a scare, good that your storage survived! Some questions: Why did you need to reinstall Proxmox after losing the network? I guess your original install was on LVM on nvme0n1p3 Do you have experience with LVM? If not: run...

Hi Balcony7199, Welcome to the forums! What filesystem is your VM on, and what is the storage layout? In the mean time, how pressing is the issue? Do you still have access to the VM, or is it locked in turned off state? Do you have a backup of the photos if worst comes to worst?

Hi all, Sorry for crossposting My main container (mail, messaging, calendar, phone backup) is offline (and has been for some 10 hours) due to resizing the LV from 3,6 TB to 0,4 TB. This is an LV on a thin pool; it has previously been filled to about 3 TB before I moved most data to other...

Slight worry is setting in. The transaction is still running. It put an exclusive lock on everything LVM, and also prevents the volume from being mounted read-only. I never had trouble shrinking an LV before, but this is the first time it involves thin pools. Without any feedback from the...

@Johannes S , thanks for adding those threads. I knew they exist, but couldn't find the links immediately!

If you want to use HW RAID, ZFS is off the charts. LVM is fine, especially if your current environment is on LVM as well. People love ZFS for the ease with which advanced features are available, such as checksumming, RAID, caching, deduplication and volume management, but these can be used on...