Differences

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

--- omv7:armbian_bookworm_install [2024/02/11 21:32] – [Finishing the Armbian Install] crashtest
+++ omv7:armbian_bookworm_install [2025/06/10 21:55] (current) – crashtest
@@ Line 13: / Line 13: @@
 \\
 \\
+Revisions:\\
+June, 10th, 2025 - "Do not deviated" FOREWORD added.\\
@@ Line 21: / Line 22: @@
 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 OMV6 on Armbian supported SBC's is a relatively easy task.  This document is a guide for that purpose.
+However, installing OMV7 on Armbian supported SBC's is a relatively easy task.  This document is a guide for that purpose.
@@ Line 30: / Line 31: @@
   * This guide contains links to external sources of information and software.  It's best used on an Internet connected PC.
   * This is a community document and a work in progress.  Input and feedback are welcome and can be sent to: [[omvguide@gmail.com]]
+\\
+<html>
+<body>
+  <table width="100%" border="0">
+    <tr>
+      <td colspan="2" style="background-color:#69A5FF;height:30px;">
+        <strong><span style="color:#FFFFFF;font-size:110%;">&#160; FOREWORD</span></strong>
+      </td>
+    </tr>
+    <tr>
+      <td style="background-color:#E6FEFF;height:25px;width:380px;">
+        This guide was written to avoid as many installation pitfalls as is possible to anticipate or predict.  With that in mind, please adhere to this guide without deviating in any significant way.  Specifically, that means DO NOT preconfigure wireless networking (that will be covered later - after OMV is installed), or use armbian-config prior to the installation of OMV.  Once the OMV installation is complete, and after backing the OS' SD-card → <a href="https://wiki.omv-extras.org/doku.php?id=omv7:utilities_maint_backup#cloning_flash_media" target="_blank">Cloning Flash Media</a>, additional configuration or experimentation will be possible without losing the install, if something goes awry.
+    </tr>
+  </table>
+</body>
+</html>
@@ Line 40: / Line 58: @@
 Given the wide variety of Armbian supported devices, and the images available for these devices, it's important to understand what will and will not work with an Openmediavault 7 installation.\\
 \\
-**OMV7** will install on most SBC devices with Armbian support and a **Debian 12 __Bookworm__** image.\\
+**OMV7** will install on most SBC devices with Armbian support __AND__ a **Debian 12 __Bookworm__** image.\\
 \\
 Further, before selecting a Bookworm image, note that Armbian supports devices with differing levels of support.  See -> [[https://docs.armbian.com/User-Guide_Board-Support-Rules/|this page]] for an explanation of the different support levels.  Devices with "Standard support" or "Community support" images are acceptable.  While **Staging - Work in progress** images may work, they are not supported and are used at the users risk.
@@ Line 54: / Line 72: @@
   * **Bookworm** images **with desktops** are **not** supported.
   * **Jammy**, **Trixie** and other non-Bookworm variants are **not** supported.
-  * Images at the bottom of some device pages under the heading of "**Rolling releases from CI pipeline**" are **not** supported.
+  * Images at the bottom of some device pages under the heading of "**Rolling releases from CI pipeline**" are **not supported**.
-  * Images at the very bottom of some device pages with the warning "**Made with official Armbian build framework but untested by Armbian team**" are **not to be used**.  (These images are built nightly -   usually the date will be the current day or the day before.)  They're auto generated for test purposes only, for software developers. Typically, **Auto generated images** have **login warnings** as noted below.\\
+  * **Bookworm** images at the very bottom of some device pages, with the warning "**Made with official Armbian build framework but untested by the Armbian team**", are not supported.  While these images usually work, they're auto generated for test purposes, for software developers.
+(These images are built nightly.  Usually their date will be the current day or a few days before.   Typically, **Auto generated images** have **login warnings** as noted below.  **Read and heed the warning**.  If user's install one of these development images, -> [[https://wiki.omv-extras.org/doku.php?id=omv7:utilities_maint_backup#cloning_flash_media|Cloning the OS SD-card]], before OS updates, is highly recommended.)\\
 \\
 {{ :omv7-arm_02-dev_only_image.jpg?nolink&800 |}}
@@ Line 63: / Line 82: @@
 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).
+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).\\
+\\
+<html>
+<body>
+  <table width="100%" border="0">
+    <tr>
+      <td colspan="2" style="background-color:#69A5FF;height:30px;">
+        <strong><span style="color:#FFFFFF;font-size:110%;">&#160; Note</span></strong>
+      </td>
+    </tr>
+    <tr>
+      <td style="background-color:#E6FEFF;height:25px;width:380px;">
+For best results, please <b>DO NOT</b> vary from the process outlined.<br>
+Examples of variation would be "preconfiguring wireless networking" or the installation of extra packages <i><b>before</b></i> running the installation script.<br>
+    </tr>
+  </table>
+</body>
+</html>
+\\
 To get started, a few utilities are needed to expand, check, and work with an Armbian image.
@@ Line 299: / Line 335: @@
-On the command line, copy and paste the following command into the SSH window:
+On the command line, copy and paste the following commands, one at a time, into the SSH window:
 ''apt-get update''
-When the command prompt returns copy and paste the following command into the SSH window:
 ''apt-get upgrade -y''
-(This process with take a few to several minutes.)
+(The above command may take a few to several minutes to complete.)
+''wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/preinstall | sudo bash''
 Finally, reboot the SBC with the following command:
@@ Line 314: / Line 350: @@
 \\
 **Note:**\\
-Some devices may require a hard power off and on.  In those cases, shutdown now, would be appropriate.  Remove and reconnect power.\\
+Some devices may require a hard power off and on, to reboot.  In such cases, physically remove and reconnect power.\\
 \\
 In a few minutes, open a new PuTTY/SSH window for the installation of OMV.\\
@@ Line 397: / Line 433: @@
 <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>
+<html><center>Under <b>IPv4</b>, in the <b>Method</b> field, click on the drop down arrow and select <b>DHCP</b> or statically address as needed.</center></html>
 \\