Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
installing_omv5_armbian_buster [2021/11/24 19:56] – [Prerequisites] crashtest | installing_omv5_armbian_buster [2022/07/31 17:16] (current) – removed crashtest | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | < | ||
- | |||
- | {{ :: | ||
- | |||
- | ====== Installing OMV5 on Armbian Buster ====== | ||
- | \\ | ||
- | \\ | ||
- | This document can be converted to a PDF file, in the user's language of choice (see the following), on Windows, Mac's and popular Linux desktop platforms. Simply select the printer icon on the upper right corner of this web page. When prompted at the client, select “print to PDF”, name and save the file.\\ | ||
- | \\ | ||
- | [[https:// | ||
- | [[https:// | ||
- | [[https:// | ||
- | [[https:// | ||
- | \\ | ||
- | |||
- | |||
- | |||
- | ===== Introduction ===== | ||
- | |||
- | Due to the lack of the numerous Single Board Computers (SBC' | ||
- | However, installing OMV5 on Armbian supported SBC's is a relatively easy task. This document is a guide for that purpose. | ||
- | |||
- | |||
- | ===== About this Guide ===== | ||
- | |||
- | The purpose and intent of this guide is to provide a walk-through to get SBC users up and running as quickly and as easily as possible. | ||
- | |||
- | * This guide contains links to external sources of information and software. | ||
- | * This is a community document and a work in progress. | ||
- | |||
- | |||
- | |||
- | ===== Not Supported ===== | ||
- | |||
- | **Desktop versions of Armbian** | ||
- | |||
- | Armbian desktop versions are not supported and are used at the user's risk. If a desktop is used, SD-card backup is recommended. | ||
- | |||
- | |||
- | ===== Supported Devices ===== | ||
- | |||
- | To see if an SBC of interest is supported by Armbian, visit the Armbian Download Page. | ||
- | |||
- | OMV5 will install on most SBC devices with **Official** Armbian support and a **Buster** image: | ||
- | * **Suitable For Testing** , “**WIP**” (Work in Progress), and **No Official Support** images may work, but things may be broken. | ||
- | * Use of **End of Support (EOS)** images is discouraged. | ||
- | * Use of any of the above image classes is not supported. | ||
- | |||
- | |||
- | ===== Prerequisites ===== | ||
- | |||
- | |||
- | This installation process __requires__ a wired Ethernet connection and Internet access. | ||
- | Typically, all that is needed to begin the installation is an Ethernet cable, an Armbian supported SBC, a power supply sufficient for the SBC model being used, and one SD-card (two are preferred for backup). | ||
- | |||
- | To get started, a few utilities are needed to expand, check, and work with an Armbian image. | ||
- | |||
- | * Armbian images are compressed with a .7z extension. | ||
- | * To check the decompressed image, an [[https:// | ||
- | * [[https:// | ||
- | * [[http:// | ||
- | * To burn an Armbian image to an SD-card, [[https:// | ||
- | * [[https:// | ||
- | * While 8GB is the minimum and will work fine, a 16GB card will provide longer life in the role of a boot drive. | ||
- | |||
- | |||
- | For the best experience, use only high quality **__new__** SD-cards, such as Samsung or SanDisk, that are rated A1 Class 10 or better. | ||
- | |||
- | {{ : | ||
- | |||
- | **Important** | ||
- | * On the [[https:// | ||
- | * When selecting an [[https:// | ||
- | * When selecting an [[https:// | ||
- | (Due to the potential for package conflicts, an image with **a desktop is __not__ recommended or supported**. Lastly, Bionic or Stretch images will not work with OMV5 or OMV6.) | ||
- | |||
- | {{ : | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | ===== Working With the Image File ===== | ||
- | |||
- | **Decompress the Image** | ||
- | Armbian images are compressed and will need to be extracted with 7-Zip. | ||
- | |||
- | {{ :: | ||
- | |||
- | \\ | ||
- | | ||
- | The result of the above action is the extraction of files into the current directory. | ||
- | |||
- | |||
- | {{ :: | ||
- | |||
- | {{ : | ||
- | |||
- | ==== Verify the image ==== | ||
- | |||
- | MD5 and SHA hashes check for image corruption that may have occurred during the download. | ||
- | |||
- | **Beginners Note - DO NOT SKIP THIS STEP.** | ||
- | |||
- | The chance of image corruption is highest when downloading and it's pointless to build a server with flawed software. | ||
- | {{ : | ||
- | Verify the image file, for your SBC, with the [[https:// | ||
- | |||
- | (Note that it's possible to “drag and drop” the file name into the utility, on the **File** line. Otherwise, use the **Browse** button and navigate to the image file.) | ||
- | |||
- | {{ : | ||
- | |||
- | \\ | ||
- | \\ | ||
- | | ||
- | Notepad can be used to open the file sha256sum.sha , with **File**, **Open**, using the **ALL Files *.* ** setting. | ||
- | |||
- | {{ :: | ||
- | |||
- | With a sha-256 match, the downloaded image is verified. | ||
- | |||
- | \\ | ||
- | | ||
- | ==== Format and Test Flash Media ==== | ||
- | |||
- | |||
- | Using SDFormatter, | ||
- | |||
- | (Note that SDFormatter does a trim operation on the card which cleans up remnants of deleted or previously existing files.) | ||
- | |||
- | In most cases, SDFormatter will detect the SD-card or thumb-drive. | ||
- | |||
- | {{ :: | ||
- | |||
- | \\ | ||
- | \\ | ||
- | |||
- | |||
- | < | ||
- | < | ||
- | |||
- | {{ :: | ||
- | |||
- | \\ | ||
- | \\ | ||
- | |||
- | |||
- | < | ||
- | |||
- | {{ :: | ||
- | |||
- | \\ | ||
- | \\ | ||
- | |||
- | | ||
- | < | ||
- | |||
- | {{ :: | ||
- | |||
- | \\ | ||
- | \\ | ||
- | |||
- | < | ||
- | |||
- | {{ :: | ||
- | |||
- | \\ | ||
- | \\ | ||
- | |||
- | |||
- | < | ||
- | |||
- | {{ :: | ||
- | |||
- | |||
- | After H2testw verifies the SD-card; **do one more clean format**, using **SDFormatter**, | ||
- | |||
- | \\ | ||
- | \\ | ||
- | | ||
- | ==== Flashing Armbian onto an SD-card ==== | ||
- | |||
- | < | ||
- | |||
- | Etcher, in most cases, will auto detect the SD-card or a USB thumb-drive. | ||
- | |||
- | * A windows confirmation dialog may pop up. (Click on OK.) | ||
- | * Etcher will write the image, then verify it in one operation. | ||
- | |||
- | {{ :: | ||
- | |||
- | A “**Success**” flag will pop up when the job is finished and the Etcher window will display “Flash Another? | ||
- | The flash operation is complete. | ||
- | |||
- | \\ | ||
- | |||
- | ===== The First Boot ===== | ||
- | |||
- | *At this point, a wired Ethernet connection is required to connect to the SBC with PuTTY and to install OMV in a later process.* | ||
- | |||
- | * Insure the SBC is connect to wired Ethernet. | ||
- | * Insert the SD-card, into the SBC, and apply power. | ||
- | * Wait 3 to 5 minutes. | ||
- | |||
- | The IP address to use for logging into the console is available from your DHCP server. | ||
- | |||
- | (The following is an example.) | ||
- | |||
- | {{ :: | ||
- | |||
- | With the IP address noted, proceed to **First Time Login**. | ||
- | |||
- | {{ : | ||
- | |||
- | < | ||
- | |||
- | * In the event that an IP address is not issued to your SBC, check the wired Ethernet connection and reboot the device. | ||
- | * If an address is not issued, or if the user doesn' | ||
- | Unfortunately, | ||
- | |||
- | {{ : | ||
- | |||
- | ===== Armbian - First Time Logon ===== | ||
- | |||
- | < | ||
- | |||
- | {{ :: | ||
- | |||
- | |||
- | < | ||
- | < | ||
- | |||
- | \\ | ||
- | \\ | ||
- | |||
- | |||
- | When the SSH window opens: | ||
- | Login as: root The Armbian default password is: 1234 | ||
- | |||
- | {{ :: | ||
- | |||
- | After logging in with the default password, you'll be required to change the root password. | ||
- | Re-enter the current password **1234**, then follow the prompts to enter and confirm a new root password. | ||
- | When the root password change is complete, Armbian will prompt to create a non-root user, with “sudo” admin abilities. | ||
- | |||
- | {{ : | ||
- | \\ | ||
- | |||
- | |||
- | ===== Finishing the Armbian Install ===== | ||
- | |||
- | |||
- | On the command line, copy and paste the following command into the SSH window: | ||
- | |||
- | '' | ||
- | |||
- | When the command prompt returns copy and paste the following command into the SSH window: | ||
- | |||
- | '' | ||
- | |||
- | (This process with take a few to several minutes.) | ||
- | |||
- | Finally, reboot the SBC with the following command: | ||
- | |||
- | '' | ||
- | |||
- | In a few minutes, open a new PuTTY/SSH window for the installation of OMV. | ||
- | |||
- | *In the event that the SSH client does not respond to the IP address used for the Armbian installation, | ||
- | |||
- | \\ | ||
- | | ||
- | ===== Install OMV ===== | ||
- | |||
- | |||
- | Installing OMV on Armbian is very easy, thanks to Arron Murray (ryecoaaron on the [[https:// | ||
- | |||
- | Highlight and copy the following line complete (**Ctrl+C**) and paste it into PuTTY' | ||
- | |||
- | '' | ||
- | |||
- | |||
- | Once the script is running, click out of the SSH window so the script will not be interrupted. | ||
- | **Note: Do Not close PuTTY** – that will terminate the root session. | ||
- | |||
- | Depending on several factors, running this script may take up to 30 minutes. | ||
- | |||
- | When the script is complete, the SBC will automatically reboot. | ||
- | |||
- | \\ | ||
- | | ||
- | ==== First Time GUI Logon ==== | ||
- | |||
- | After 3 to 5 minutes, OMV can be logged in using the same IP address that was used for the SSH client, entered in a web browser address bar. The web GUI user is **admin** and the default password is **openmediavault** | ||
- | |||
- | \\ | ||
- | **Note** - after the completion of the script: | ||
- | |||
- | In the rare event that the OMV console or SSH client does not respond to the IP address used during the installation, | ||
- | |||
- | (Typically, consumer router DHCP leases last at least 24 hours. | ||
- | |||
- | \\ | ||
- | | ||
- | ===== Finishing Up ===== | ||
- | |||
- | |||
- | New users can continue with the setup of OMV using the [[https:// | ||
- | |||
- | All users are encouraged to review the section titled Operating System Backup for an easy process to clone your SBC's SD-Card. | ||
- | |||
- | |||
- | **Adding a Wireless Interface: | ||
- | |||
- | To add a Wireless Interface see Final Notes below. | ||
- | |||
- | \\ | ||
- | ===== Donate ===== | ||
- | |||
- | |||
- | If you found this guide to be helpful and OMV on Armbian SBC's to be useful; please consider a modest [[https:// | ||
- | \\ | ||
- | < | ||
- | <form action=" | ||
- | <input type=" | ||
- | <input type=" | ||
- | <input type=" | ||
- | <img alt="" | ||
- | </ | ||
- | </ | ||
- | \\ | ||
- | | ||
- | ===== Final Notes: ===== | ||
- | |||
- | |||
- | ==== Networking - General ==== | ||
- | |||
- | The decision was made to depreciate NetworkManager in SBC's running OMV. The primary reason for this decision was to better support the installation and use of Dockers. | ||
- | Supporting Portainer, to allow easy use of Dockers, was a priority add-on for OMV5. Unfortunately, | ||
- | |||
- | |||
- | ==== Wireless Networking ==== | ||
- | |||
- | First it should be noted that using a wireless interface, with a server, is not the best idea. To prevent a number of issues such as interference, | ||
- | |||
- | If your SBC is equipped with a wireless interface, by default OMV will not show it in the GUI but it can easily be added. | ||
- | * An existing interface can be added as noted in the following. | ||
- | * After plugging it in, a compatible add-on USB wireless interface can be added in the same manner. | ||
- | |||
- | (*In the example below, a wireless USB adapter is being added to a Rock64 without an onboard interface.*) | ||
- | |||
- | Under **System**, **Network**, | ||
- | |||
- | {{ :: | ||
- | |||
- | \\ | ||
- | \\ | ||
- | | ||
- | When the **Add Wi-Fi** dialog box pops up, select the drop down arrow next to **Device**. | ||
- | |||
- | In the **Wi-Fi** section, add the **SSID** for the wireless network and the encryption **Password**. | ||
- | |||
- | {{ :: | ||
- | |||
- | \\ | ||
- | \\ | ||
- | |||
- | Using the right scroll bar, scroll down to **IPv4**. | ||
- | |||
- | {{ :: | ||
- | |||
- | < | ||
- | |||
- | \\ | ||
- | |||
- | |||
- | At this point, the wireless interface will appear under **System**, **Network**, | ||
- | |||
- | \\ | ||
- | |||
- | |||
- | To further configure the SBC; refer to the [[https:// |