u/fl4tdriven

I currently have a 12TB 2x disk mirror with a potentially failing disk. The failing disk is under warranty and will be replaced, but while I’m waiting for the replacement, I’d like to put a spare 16TB disk into the mirror as its replacement temporarily and then swap the new 12TB disk into place when I receive it.

I know it’s not possible to use a smaller disk into a pool that’s been expanded to a larger capacity, but being that I’ll be mixing a 12TB and 16TB disk, my pool will stay at 12TB. Is this possible?

First, I realize this sub is for Immich specifically, but I figured it couldn’t hurt to ask this question here anyway.

What I’m up against is trying to import my wife’s Google Photos library into Immich. I’ve already downloaded the Takeout .zip files and created an API key with specified permissions under her Immich account (non-admin).

Where I’m getting confused is in the Immich-go readme, they specify that an API key needs to be created for each user needing to use Immich-go, and a second admin-tied API key be created with the base permissions + additional to stop Immich jobs.

Where does this second key come in to play when running Immich-go? The commands only specify one API key, with no mention of the secondary admin key to stop jobs.

Any help is appreciated!

As the pictures show, I have a dataset called 'proxmox_backup' that I set a quota of 300GiB to. I noticed tonight that at the dataset level, that same dataset shows 951.09GiB/109.27GiB used/available. Additionally, I have a daily snapshot job for this dataset with a 15 day retention.

Why is this dataset showing 951GiB used when it only has an allocation of 300GiB and only 190.73GiB currently stored?

https://preview.redd.it/hguzthg4zb9h1.png?width=554&format=png&auto=webp&s=f5957e29ae1be4c357e05ad792f283f8c93da289

https://preview.redd.it/vu6fyhg4zb9h1.png?width=1140&format=png&auto=webp&s=3218423d49eb70394eef2032cc6fa54c3a5c5a47

https://preview.redd.it/bybwcig4zb9h1.png?width=920&format=png&auto=webp&s=2cff66be9e3d769cff3cf1bf39266df1a7488cd2

I've procrastinated on updating my PVE instance (non-subscription) for long enough and decided to start getting an upgrade plan in place. I decided to run the recommended 'pve8to9 --full' command and the only failure I received was this:

FAIL: systemd-boot meta-package installed. This will cause problems on upgrades of other boot-related packages. Remove 'systemd-boot' See https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#sd-boot-warning for more information.

So I, being new to Linux in any capacity before starting my homelab last year, started to do some research as to what this is and if it's safe to remove. I started with the provided Proxmox URL which specifies it's safe to remove unless it was explicitly installed, which I did not do at any point since installing PVE. I decided to do some more research to make extra sure this is safe to remove, which led me to finding this tutorial: https://www.techtutorials.tv/sections/promox/how-to-upgrade-promox-8-to-9/

This tutorial specifies to run:

[ -d /sys/firmware/efi ] && echo "UEFI" || echo "Legacy"

My two questions are:

1. What does the '-d' option do? I'm hesitant to run that command without knowing what it does and I can't find reference of it anywhere
2. Should I make changes in the BIOS to be better compatible with PVE or should I just keep BIOS as is and remove systemd-boot as suggested?

Looking for a USW-Flex-2.5G-8 (full size Flex 2.5, non PoE) shipped to PA.

Looking for a working USW-Flex shipped to PA. Let me know what you have!