Differences

This shows you the differences between two versions of the page.

--- installing_omv6_armbian_bullseye [2022/02/14 01:31] – [Donate] crashtest
+++ installing_omv6_armbian_bullseye [2022/02/15 15:05] – [The First Boot] crashtest
@@ Line 1: / Line 1: @@
-{{ :underconstruction.jpg?400 |}}
-<html><center><strong>This document is not up to date or complete.</strong></center></html>
-{{ :divider2.png?800 |}}
 ====== Installing OMV6 on Armbian Bullseye ======
@@ Line 28: / Line 17: @@
 Due to the lack of the numerous Single Board Computers (SBC's) required for testing and integration, providing images for all Armbian supported SBC's, with Openmediavault (OMV) pre-installed, will not be possible.
-However, installing OMV5 on Armbian supported SBC's is a relatively easy task.  This document is a guide for that purpose.
+However, installing OMV6 on Armbian supported SBC's is a relatively easy task.  This document is a guide for that purpose.
@@ Line 68: / Line 57: @@
 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.  Users will need the [[https://www.7-zip.org/|7-Zip]]  utility to decompress the image.  7-Zip is installable on a Windows client.
   * To check the decompressed image, an [[https://md5-sha-checksum-utility.en.lo4d.com/windows|MD5 – SHA Checksum utility]] is needed.  This utility is portable, meaning it's not necessary to install it, but it may require support files.  Simply run the executable.
   * [[https://www.sdcard.org/downloads/formatter/index.html|SDformatter]] is a utility for formatting SD-cards, that does a trim operation on flash media to clear remnants of old files. SDformatter is installable on a Windows client.
@@ Line 104: / Line 92: @@
 MD5 and SHA hashes check for image corruption that may have occurred during the download.
-**Beginners Note - DO NOT SKIP THIS STEP.**
+<html>
+<body>
+  <table width="100%" border="0">
+    <tr>
+      <td colspan="2" style="background-color:#69A5FF;height:30px;">
+        <b><span style="color:#FFFFFF;font-size:110%;">&#160; Beginners Note - DO NOT SKIP THIS STEP</span></b>
+      </td>
+    </tr>
+    <tr>
+      <td style="background-color:#E6FEFF;height:25px;width:380px;">
+        <p>The chance of image corruption is highest when downloading and it's pointless to build a server with flawed software.  Even the slightest corruption of the image may ruin your installation and the effects may not be noticed until well after your server is built and in use.  Headaches can be avoided by checking the image.
+</p>
+    </tr>
+  </table>
+</body>
+</html>
-The chance of image corruption is highest when downloading and it's pointless to build a server with flawed software.  Even the slightest corruption of the image may ruin your installation and the effects may not be noticed until well after your server is built and in use.  Headaches can be avoided by checking the image.
 {{ :divider2.png?800 |}}
 Verify the image file, for your SBC, with the [[https://md5-sha-checksum-utility.en.lo4d.com/windows|MD5 & SHA checksum utility]].
@@ Line 112: / Line 114: @@
 (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.)
-{{ ::omv6-arm-01.jpg?600 |}}
+{{ ::omv6-arm-01.jpg?700 |}}
 \\
@@ Line 213: / Line 215: @@
 {{ ::omv6-arm-06.jpg?400 |}}
-\\
-\\
-\\
 {{ :divider2.png?600 |}}
-\\
 ===== The First Boot =====
@@ Line 244: / Line 242: @@
   * In the event that an IP address is not issued to your SBC, check the wired Ethernet connection and reboot the device.  In some cases this will mean unplugging and plugging the power supply back in.  Allow time for boot up (5 minutes or so) and check the DHCP server again.
   * If an address is not issued, or if the user doesn't know how to find the ARM device's IP address on their DHCP server, connect a monitor and keyboard to watch the boot process until it completes.  If the IP address is not displayed at the end of the boot cycle, login with the user **root** and password **1234**
-Unfortunately, this first time logon may kick off a mandatory root user password change and the addition of a non-root user.  Once these processes are complete, type ''ip add'' on the command line.  Note the IP address of the Ethernet interface, in the output, and proceed to First Time Login.
+Unfortunately, this first time logon will start a mandatory root user password change and the addition of a non-root user.  Once these processes are complete, type ''ip add'' on the command line.  Note the IP address of the Ethernet interface, in the output, and proceed to First Time Login.
 {{ :divider2.png?600 |}}
@@ Line 318: / Line 316: @@
 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.  Minimizing PuTTY is OK, but it must be running.
+**Note: Do Not Close PuTTY** – that will terminate the root session.  Minimizing PuTTY is OK, but it must be running.
 Depending on several factors, running this script may take up to 30 minutes.
@@ Line 341: / Line 339: @@
 ===== Finishing Up =====
+  * **To add an existing or add-on Wireless Interface** to openmediavault, see [[https://wiki.omv-extras.org/doku.php?id=installing_omv6_armbian_bullseye#final_notes|Final Notes]] below.
   * New users can continue with the setup of OMV using the [[https://wiki.omv-extras.org/doku.php?id=omv6_new_user_guide|Getting Started with Openmediavault 6]] guide, starting in the section titled → [[https://wiki.omv-extras.org/doku.php?id=omv6_new_user_guide#initial_configuration|Initial Configuration]].
   * All users are encouraged to review this resource → [[https://openmediavault.readthedocs.io/en/5.x/new_user_guide/newuserguide.html#operating-system-backup|Operating System Backup]] for an easy process to clone your SBC's SD-Card.
 ((Redirect to OMV6 maintenance guide when complete.))
-**Adding a Wireless Interface:**
-To add a Wireless Interface see Final Notes below.  (Unless absolutely required, devices used in a server role should **avoid** wireless networking.)
 {{ :divider2.png?800 |}}
@@ Line 384: / Line 377: @@
 ==== 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.
+The decision was made to depreciate NetworkManager in SBC's running OMV.  The primary reason for this decision
-Supporting Portainer, to allow easy use of Dockers, was a priority add-on for OMV5.  Unfortunately, NetworkManager wreaks networking for Dockers and Portainer.
+was to better support the installation and use of Dockers.
+Supporting Portainer, to allow easy use of Dockers, was a priority add-on for OMV6.  Unfortunately,
+NetworkManager wrecks networking for Dockers and Portainer.
 ==== 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, bandwidth contention issues with clients, etc., a server should be connected to the **wired** LAN ports of a router or a network switch.  However it is understood that, in some cases, wired connections may not be an option.
+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, bandwidth contention issues with clients, etc., a server should be
+connected to the **wired** LAN ports of a router or a network switch.  However it is understood that, in some
+cases, wired connections may not be an option.
-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.
+If your SBC is equipped with a wireless interface, by default, OMV will not show it in the GUI but it can 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.*)
+<html><center>Under <b>Network</b>, in the <b>Interfaces</b> tab, click on the <b>+ Add</b> button.  From the pop up, select <b>Wi-Fi</b>.</center></html>
+\\
-Under **System**, **Network**, in the **Interfaces** tab, click on the **+ Add** button.  Select **Wi-Fi**.
+{{ ::omv6-arm-11.jpg?800 |}}
-{{ ::armbian16_omv_wireless_int.jpg?600 |}}
 \\
-\\
+----
+\\
-When the **Add Wi-Fi** dialog box pops up, select the drop down arrow next to **Device**.  The on-board or add-on  wireless interface will be the only interface in the list.  Select it.
+<html><center>In the <b>Create window</b>, select the drop down arrow next to the <b>Device</b> field.</center></html>
+<html><center>The on-board or add-on wireless interface will be the only interface in the list. Select it.</center></html>
+\\
+<html><center>In the <b>SSID</b> field, enter the SSID for the wireless network.</center></html>
+<html><center>In the <b>Password</b> field, enter the WiFi encryption password.</center></html>
+<html><center>Under <b>IPv4</b>, in the <b>Method</b> field, click on the drop down arrow and select <b>DHCP</b>.</center></html>
+\\
-In the **Wi-Fi** section, add the **SSID** for the wireless network and the encryption **Password**.
+{{ :omv6-arm-12.jpg?800 |}}
-{{ ::armbian17_omv_wireless_dialog.jpg?300 |}}
+<html><center>Scroll down and click, <strong>Save</strong>.</center></html>
+\\
-\\
+At this point, the wireless interface will appear under **Network**, in the **Interfaces** window.
+Further configuration can be done, as needed, by clicking on the interface line and the edit button (pencil).
 \\
-Using the right scroll bar, scroll down to **IPv4**.  Next to **Method**, click the drop down arrow and make the appropriate selection.  (DHCP is recommended for beginners.)
+{{ :divider2.png?800 |}}
-{{ ::armbian18_omv_wireless_dialog2.jpg?300 |}}
-<html><center>Click, <strong>Save</strong>.</center></html>
-\\
-At this point, the wireless interface will appear under **System**, **Network**, in the **Interfaces** tab.  Further configuration can be done, as needed, by editing the interface in the Interfaces tab.
-\\
-To further configure the SBC; refer to the [[https://openmediavault.readthedocs.io/en/5.x/new_user_guide/newuserguide.html#initial-configuration|Getting Started with Openmediavault 5 guide]] - [[https://github.com/OpenMediaVault-Plugin-Developers/docs/blob/master/Getting_Started-OMV5.pdf|or PDF]], starting in the section titled [[https://openmediavault.readthedocs.io/en/5.x/new_user_guide/newuserguide.html#initial-configuration|Initial Configuration]].
+To further configure the SBC; refer to the [[https://wiki.omv-extras.org/doku.php?id=omv6_new_user_guide|Getting Started with Openmediavault 6]], starting in the section titled [[https://wiki.omv-extras.org/doku.php?id=omv6_new_user_guide#initial_configuration|Initial Configuration]].