From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 357171FF380 for ; Fri, 19 Apr 2024 11:06:51 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6E34336E1; Fri, 19 Apr 2024 11:06:19 +0200 (CEST) From: Christoph Heiss To: pve-devel@lists.proxmox.com Date: Fri, 19 Apr 2024 11:05:19 +0200 Message-ID: <20240419090519.291775-14-c.heiss@proxmox.com> X-Mailer: git-send-email 2.44.0 In-Reply-To: <20240419090519.291775-1-c.heiss@proxmox.com> References: <20240419090519.291775-1-c.heiss@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.397 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_ASCII_DIVIDERS 0.8 Email that uses ascii formatting dividers and possible spam tricks KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [RFC PATCH docs 13/13] installation: use new 'advanced-installation' partial from common docs X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Signed-off-by: Christoph Heiss --- pve-installation.adoc | 126 +----------------------------------------- 1 file changed, 1 insertion(+), 125 deletions(-) diff --git a/pve-installation.adoc b/pve-installation.adoc index 2f4642e..0a0dc76 100644 --- a/pve-installation.adoc +++ b/pve-installation.adoc @@ -78,131 +78,7 @@ web interface for further configuration. . Check your xref:chapter_pve_firewall[Firewall settings]. -[[advanced_lvm_options]] -Advanced LVM Configuration Options -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The installer creates a Volume Group (VG) called `pve`, and additional Logical -Volumes (LVs) called `root`, `data`, and `swap`, if `ext4` or `xfs` is used. To -control the size of these volumes use: - -`hdsize`:: - -Defines the total hard disk size to be used. This way you can reserve free space -on the hard disk for further partitioning (for example for an additional PV and -VG on the same hard disk that can be used for LVM storage). - -`swapsize`:: - -Defines the size of the `swap` volume. The default is the size of the installed -memory, minimum 4 GB and maximum 8 GB. The resulting value cannot be greater -than `hdsize/8`. -+ -NOTE: If set to `0`, no `swap` volume will be created. - -`maxroot`:: - -Defines the maximum size of the `root` volume, which stores the operation -system. The maximum limit of the `root` volume size is `hdsize/4`. - -`maxvz`:: - -Defines the maximum size of the `data` volume. The actual size of the `data` -volume is: -+ -`datasize = hdsize - rootsize - swapsize - minfree` -+ -Where `datasize` cannot be bigger than `maxvz`. -+ -NOTE: In case of LVM thin, the `data` pool will only be created if `datasize` is -bigger than 4GB. -+ -NOTE: If set to `0`, no `data` volume will be created and the storage -configuration will be adapted accordingly. - -`minfree`:: - -Defines the amount of free space that should be left in the LVM volume group -`pve`. With more than 128GB storage available, the default is 16GB, otherwise -`hdsize/8` will be used. -+ -NOTE: LVM requires free space in the VG for snapshot creation (not required for -lvmthin snapshots). - -[[advanced_zfs_options]] -Advanced ZFS Configuration Options -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The installer creates the ZFS pool `rpool`, if ZFS is used. No swap space is -created but you can reserve some unpartitioned space on the install disks for -swap. You can also create a swap zvol after the installation, although this can -lead to problems (see xref:zfs_swap[ZFS swap notes]). - -`ashift`:: - -Defines the `ashift` value for the created pool. The `ashift` needs to be set at -least to the sector-size of the underlying disks (2 to the power of `ashift` is -the sector-size), or any disk which might be put in the pool (for example the -replacement of a defective disk). - -`compress`:: - -Defines whether compression is enabled for `rpool`. - -`checksum`:: - -Defines which checksumming algorithm should be used for `rpool`. - -`copies`:: - -Defines the `copies` parameter for `rpool`. Check the `zfs(8)` manpage for the -semantics, and why this does not replace redundancy on disk-level. - -`ARC max size`:: - -Defines the maximum size the ARC can grow to and thus limits the amount of -memory ZFS will use. See also the section on -xref:sysadmin_zfs_limit_memory_usage[how to limit ZFS memory usage] for more -details. - -`hdsize`:: - -Defines the total hard disk size to be used. This is useful to save free space -on the hard disk(s) for further partitioning (for example to create a -swap-partition). `hdsize` is only honored for bootable disks, that is only the -first disk or mirror for RAID0, RAID1 or RAID10, and all disks in RAID-Z[123]. - - -ZFS Performance Tips -~~~~~~~~~~~~~~~~~~~~ - -ZFS works best with a lot of memory. If you intend to use ZFS make sure to have -enough RAM available for it. A good calculation is 4GB plus 1GB RAM for each TB -RAW disk space. - -ZFS can use a dedicated drive as write cache, called the ZFS Intent Log (ZIL). -Use a fast drive (SSD) for it. It can be added after installation with the -following command: - ----- -# zpool add log ----- - -[[nomodeset_kernel_param]] -Adding the `nomodeset` Kernel Parameter -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -Problems may arise on very old or very new hardware due to graphics drivers. If -the installation hangs during boot, you can try adding the `nomodeset` -parameter. This prevents the Linux kernel from loading any graphics drivers and -forces it to continue using the BIOS/UEFI-provided framebuffer. - -On the {pve} bootloader menu, navigate to 'Install {pve} (Terminal UI)' and -press `e` to edit the entry. Using the arrow keys, navigate to the line starting -with `linux`, move the cursor to the end of that line and add the -parameter `nomodeset`, separated by a space from the pre-existing last -parameter. - -Then press `Ctrl-X` or `F10` to boot the configuration. +include::proxmox-docs-common/partials/advanced-installation.adoc[] ifndef::wiki[] -- 2.44.0 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel