From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 0D00A1FF380 for ; Fri, 19 Apr 2024 12:51:44 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 31EF26B1D; Fri, 19 Apr 2024 12:51:42 +0200 (CEST) Message-ID: Date: Fri, 19 Apr 2024 12:51:07 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Proxmox VE development discussion , Christoph Heiss References: <20240419090519.291775-1-c.heiss@proxmox.com> <20240419090519.291775-2-c.heiss@proxmox.com> Content-Language: en-US From: Aaron Lauterer In-Reply-To: <20240419090519.291775-2-c.heiss@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.495 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 URIBL_SBL_A 0.1 Contains URL's A record listed in the Spamhaus SBL blocklist [185.199.111.153, 185.199.109.153, 185.199.108.153, 185.199.110.153] Subject: Re: [pve-devel] [RFC PATCH docs-common 01/13] installation-media: move page from pve-docs here 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On 2024-04-19 11:05, Christoph Heiss wrote: > Small adaptions were necessary; mostly a s/{pve}/{product}/g and > replacing the ISO URL with the {iso-url} variable. except there are still plenty of `{pve}`s in there? another thing looking at this patch, how do we handle product specifics? having a ton of variables that are set according to the product, might be cumbersome. Most likely something like `ifdef:product-pve` and so forth would be useful. some situations I spotted where we would probably need it in this patched marked below: > > Signed-off-by: Christoph Heiss > --- > installation-media.adoc | 132 ++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 132 insertions(+) > create mode 100644 installation-media.adoc > > diff --git a/installation-media.adoc b/installation-media.adoc > new file mode 100644 > index 0000000..a1c9402 > --- /dev/null > +++ b/installation-media.adoc > @@ -0,0 +1,132 @@ > +[[installation_prepare_media]] > +Prepare Installation Media > +-------------------------- > +ifdef::wiki[] > +:pve-toplevel: > +endif::wiki[] > + > +Download the installer ISO image from: {website}en/downloads/proxmox-virtual-environment/iso ^actual download link for each product > + > +The {pve} installation media is a hybrid ISO image. It works in two ways: > + > +* An ISO image file ready to burn to a CD or DVD. > + > +* A raw sector (IMG) image file ready to copy to a USB flash drive (USB stick). > + > +Using a USB flash drive to install {pve} is the recommended way because it is > +the faster option. > + > +Prepare a USB Flash Drive as Installation Medium > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +The flash drive needs to have at least 1 GB of storage available. > + > +NOTE: Do not use UNetbootin. It does not work with the {pve} installation image. > + > +IMPORTANT: Make sure that the USB flash drive is not mounted and does not > +contain any important data. > + > + > +Instructions for GNU/Linux > +~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +On Unix-like operating system use the `dd` command to copy the ISO image to the > +USB flash drive. First find the correct device name of the USB flash drive (see > +below). Then run the `dd` command. > + > +---- > +# dd bs=1M conv=fdatasync if=./proxmox-ve_*.iso of=/dev/XYZ ^ useful example, though this one could also be helped with by putting the 've_' part into the glob as well > +---- > + > +NOTE: Be sure to replace /dev/XYZ with the correct device name and adapt the > +input filename ('if') path. > + > +CAUTION: Be very careful, and do not overwrite the wrong disk! > + > + > +Find the Correct USB Device Name > +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > +There are two ways to find out the name of the USB flash drive. The first one is > +to compare the last lines of the `dmesg` command output before and after > +plugging in the flash drive. The second way is to compare the output of the > +`lsblk` command. Open a terminal and run: > + > +---- > +# lsblk > +---- > + > +Then plug in your USB flash drive and run the command again: > + > +---- > +# lsblk > +---- > + > +A new device will appear. This is the one you want to use. To be on the extra > +safe side check if the reported size matches your USB flash drive. > + > + > +Instructions for macOS > +~~~~~~~~~~~~~~~~~~~~~~ > + > +Open the terminal (query Terminal in Spotlight). > + > +Convert the `.iso` file to `.dmg` format using the convert option of `hdiutil`, > +for example: > + > +---- > +# hdiutil convert proxmox-ve_*.iso -format UDRW -o proxmox-ve_*.dmg > +---- > + > +TIP: macOS tends to automatically add '.dmg' to the output file name. > + > +To get the current list of devices run the command: > + > +---- > +# diskutil list > +---- > + > +Now insert the USB flash drive and run this command again to determine which > +device node has been assigned to it. (e.g., /dev/diskX). > + > +---- > +# diskutil list > +# diskutil unmountDisk /dev/diskX > +---- > + > +NOTE: replace X with the disk number from the last command. > + > +---- > +# sudo dd if=proxmox-ve_*.dmg bs=1M of=/dev/rdiskX > +---- > + > +NOTE: 'rdiskX', instead of 'diskX', in the last command is intended. It will > +increase the write speed. > + > +Instructions for Windows > +~~~~~~~~~~~~~~~~~~~~~~~~ > + > +Using Etcher > +^^^^^^^^^^^^ > + > +Etcher works out of the box. Download Etcher from https://etcher.io. It will > +guide you through the process of selecting the ISO and your USB flash drive. > + > +Using Rufus > +^^^^^^^^^^^ > + > +Rufus is a more lightweight alternative, but you need to use the *DD mode* to > +make it work. Download Rufus from https://rufus.ie/. Either install it or use > +the portable version. Select the destination drive and the {pve} ISO file. > + > +IMPORTANT: Once you 'Start' you have to click 'No' on the dialog asking to > +download a different version of GRUB. In the next dialog select the 'DD' mode. > + > +ifdef::wiki[] > +Boot your Server from the USB Flash Drive > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +Connect the USB flash drive to your server and make sure that booting from USB > +is enabled (check your servers firmware settings). Then follow the steps in the > +xref:chapter_installation[installation wizard]. Aligning chapter references will also be some work, especially if we want to keep old direct links still working. > + > +endif::wiki[] > -- > 2.44.0 > > > > _______________________________________________ > pve-devel mailing list > pve-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > > _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel