Search results

HDDs werden nie ansatzweise so schnell sein wie SSDs...egal was du da tust. Will man es performant haben ersetzt man die HDDs durch SSDs. Nicht vergessen, dass da eine schnelle HDD vielleicht 200 IOPS schafft und eine schnelle SSD 2,5 Mio IOPS. Selbst eine lahme SATA SSD ist da 400x schneller...

Correct Use "ls -la /dev/disk/by-id" instead of your "cd /dev/disk/by-id; ls". An SSD could have multiple IDs pointing to the same SSD. Yes. It will clone the partition table and both disks will have the same partitions. So you might want to install PVE to the smaller one so cloning won'T fail...

As I already said, its the same as replacing a failed disk of a mirror, you just don't replace a disk but add a new one. See the article linked above. So:

Ich würde den SLOG nie auf eine Platte mit Daten, die du nicht verlieren willst, packen. SLOG auf Systemdisk ist also eine ganz schlechte Idee. SLOG ist ja gerade das, was dir in Null-Komma-Nichts die SSDs killt und die Systemdisk möchte man ja im Normalfall nicht verlieren ;) Dann bitte was...

Jup, da muss man dann warten bis sowohl PVE als auch PBS auf die neue Major-Version aktualisiert wurden. Daher eher unschön. Auch kann man ein Bare Metal PBS nicht so leicht sichern. Aber LXC sind noch unschöner, weil PBS nie ausgelegt wurde um in einem LXC zu laufen und auch niemand vor dem...

You can't add a disk without formating it first and cloning the bootloader. And thats partition 3 of your physical disk because partition 1+2 are needed for the bootloader. See chapter "Replacing a failed bootable device" but instead of the "zpool replace..." you use a "zpool attach" for a...

Würde ich nicht machen. Performance ist echt nicht toll wenn deine VMs/LXCs von HDDs laufen. Auch nicht vergessen, dass ein Raid5 echt nicht toll für VMs/LXCs ist. 6 Disks im Raid5 sind von den IOPS her so lahm wie eine einzelne Disk und bei ZFS wärst du auch gezwungen deine Blockgröße...

Yes, and the great thing about it is that you can adjust to a newer PVE version or new hardware. Where a deploy script made for PVE 8 maybe won't work with PVE9 anymore without spending a lot of time keeping your redeploy scripts always updated. I've got a DokuWiki container for this where I...

TrueNAS got a minimum RAM requirement of 8GB. PVE 2GB. So with that single VM alone you should have like 11+GB of RAM. And TrueNAS uses ZFS, so consumer SSDs aren't great and I would bet you didn't bought a proper SSD with power-loss protection. ZFS also benefits from ECC RAM your MiniPC...

Wüsste ich jetzt nicht. Du musst dir halt überlegen was ein VLAN Interface macht und wie da die einzelnen Pakete durch den PVE laufen. Also wann da an welchem Schritt die Pakete getaggt werden und wann der Tag wieder entfernt wird.

Nein, du mischt das. Entweder VLAN interface unterhalb einer vlan-unaware Bridge oder ein VLAN interface oberhalb einer vlan-aware Bridge. Also entweder... auto lo iface lo inet loopback auto eno1 iface eno1 inet manual auto eno1.3 iface eno1.3 inet manual auto vmbr0 iface vmbr0 inet manual...

I like all my disks mirrored via software raid and with checksumming. The only other supported option would be btrfs and thats still in "feature preview" state, less mature and got other problems. The unsupported mdadm works but got problems too (like the bug you linked above). Encryption on PVE...

But that's a very advanced topic. Debian Installer isn't supporting ZFS and PVE installer insn't supporting LUKS. From what I've read so far full system encryption using ZFS on LUKS is full of pittfalls and has all to be done manually via CLI from a Live Linux after installing an unencrypted...

You could install a Debian 12 using the installer of the Debian 12 ISO. That installer supports LUKS while the PVE installer does not. For the raid0 you could use mdadm + LVM that the Debian installer is supporting. You then could install the PVE packages on top of that encrypted Debian 12...

You only need a single vlan-aware bridge. For a VM in multi vlans you got two options: 1.) a single vNIC and you don't set a "VLAN Tag" in the vNICs settings. In this case the guestOS got access to all vlans on that bridge and vlan config has to be done inside the guestOS. 2.) you create one...

There is an example: https://pve.proxmox.com/wiki/Network_Configuration#sysadmin_network_vlan I would use a single vlan-aware bridge. Then add a vlan interface on top of that bridge for your management. VLANs for VMs are tagged in the "hardware" section of your VM config when editing the...

You know that your "Min RAM: 4 GiB" config could force TrueNAS down to 4GiB of RAM and that TrueNAS got a minimum hardware requirement of 8GB?

It gets especially bad when a scrub is running in parallel. Not that unusual here that a weekly re-verify task will then run for 10 hours to verify a fraction of the 2TB datastore on a 4-HDD raidz1 + special device SSD mirror. Don't want to know how slow that would be scrubbing and re-verifying...

Also keep the time, needed for resilvering, in mind. Once one of those 8x8TB disks in a raidz1 dies you will have to replace it and resilvering might take some days where your other disks are tortured 24/7 with 100% IO. In that state ZFS can't fix any errors any longer and it is very likely that...

It's one of the few backup solutions that makes heavy use of deduplication instead of more classic approaches like differential backups. With those differential or full backups the IO is pretty sequential but deduplication causes stuff to be scattered across the disk with lots of references...