omv6:armbian_bullseye_install

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
omv6:armbian_bullseye_install [2023/07/06 03:42] – [Prerequisites] crashtestomv6:armbian_bullseye_install [2024/03/29 15:13] (current) – [Prerequisites] crashtest
Line 4: Line 4:
 \\ \\
 \\ \\
 +**Note:**\\ 
 +OMV6 is a legacy version of Openmediavault.  While it is still possible to build OMV6, it is recommended that users build the latest version, -> 
 +[[https://wiki.omv-extras.org/doku.php?id=omv7:armbian_bookworm_install|OMV7]]. 
  
  
Line 34: Line 36:
  
  
-**OMV6** will install on most SBC devices with **Official** Armbian support and a **Debian __Bullseye__** image.+**OMV6** will install on most SBC devices with Armbian support and a **Debian __Bullseye__** image.
  
-To see if an SBC of interest is supported by Armbianvisit the [[https://www.armbian.com/download/|Armbian Download Page]]:\\ +A list of imagesfor your particular SBC can be found in the -> [[https://armbian.lv.auroradev.org/archive/|Armbian Archive]].   Find your SBC on the archive page, select it and drill down to the images page.  Scroll to the bottom of the images page, looking for the latest, small, Bullseye image.  (Typically the smaller sized image files are "CLI" or "Minimal" This may be difficult to see as image names are shorted.  Verify "CLI" or "Minimal" as the image is downloading.)
-A list of images, for your particular SBC can be found by scrolling to the bottom of the SBC's download page, under Other Supported Varients+
 \\ \\
-  * Focal, Hirsute, Jammy, and other variants are **not** supported. +  * Focal, Hirsute, Jammy, other variants, and Bullseye images with desktops are **not** supported.
-  * **Suitable For Testing** , “**WIP**” (Work in Progress), and **No Official Support** Bullseye images may work, but things may be broken.  Use of these images is at the user's risk.  These images could be considered to be in “BETA” state.  Problems are to be expected.   +
-  Use of **End of Support (EOS)** images is discouraged.  The state of the OS is undetermined and it may not update normally. The install process may fail or, if the installation is successful, OMV may be (or become) unstable.  Again, use of **EOS** images is at the user's risk. +
-  * Use of any of the above image classes is not supported. +
  
 ===== Prerequisites ===== ===== Prerequisites =====
Line 64: Line 61:
  
 {{ :armbian1_sd-card.jpg?80 |}} {{ :armbian1_sd-card.jpg?80 |}}
 +\\
  
-**Important** +**Important - The location for image downloads has been moved to Armbian's Archive.** 
-  * On the [[https://www.armbian.com/download/|Armbian device page]], select the appropriate SBC and scroll down to the **Other Supported Variants** section for your device+  * On the [[http://xogium.performanceservers.nl/archive/|The Armbian Image Archive Page]], scroll down through the page.  Open the folder for the appropriate model of SBC and select a **Bullseye Current Minimal** image. Older Bullseye images are fine.  They will be updated in processes following
-  * For best possible compatibilitywhen selecting an [[https://www.armbian.com/download/|Armbian image to download]], select an Armbian **Bullseye** image that's branded "CLI" or **Bullseye** Minimal image for your device+  * While image names may be appended in the archivethe smaller of the available __image__ files tend to be "Minimal" or "CLI" Look for Minimal or CLI in the image name as it downloads.  If a mistake is made, cancel the download and try again
-  * To find the appropriate image, it may be necessary to scroll to the bottom of the Armbian device page and click on the link to **Archived Versions**.  (Scroll to the bottom of the archived images page and select the latest Bullseye Minimal or CLI version.)+  * In a similar manner, directly under the downloaded image, look for a file with a **sha** file extension.  The sha hash withing that file will be used to verify the image as noted below 
  
-(Due to the potential for package conflicts, an image with **a desktop is __not__ supported**. Lastly, Bionic, Focal, Jammy, Bookworm etc., images will not work with OMV6.)+(Due to the potential for package conflicts, an image with **a desktop is __not__ supported**. Lastly, Bionic, Focal, Jammy, Bookworm etc., images will not work with **OMV6**.)
  
 {{ :divider2.png?800 |}} {{ :divider2.png?800 |}}
Line 298: Line 296:
  
 ''reboot'' ''reboot''
- +\\ 
-In a few minutes, open a new PuTTY/SSH window for the installation of OMV. +**Note:**\\ 
 +Some devices may require a hard power off and on.  In those cases, shutdown now, would be appropriate.  Remove and reconnect power.\\ 
 +\\ 
 +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, look at your DHCP server again to see if a “new” IP address has been assigned.* *In the event that the SSH client does not respond to the IP address used for the Armbian installation, look at your DHCP server again to see if a “new” IP address has been assigned.*
  
Line 380: Line 381:
  
 The decision was made to depreciate NetworkManager in SBC's running OMV.  The primary reason for this decision  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+was to better support the installation and use of Dockers.  Unfortunately,  
-Supporting Portainer, to allow easy use of Dockers, was a priority add-on for OMV6.  Unfortunately,  +NetworkManager wrecks networking for Dockers. 
-NetworkManager wrecks networking for Dockers and Portainer+
  
  
  • omv6/armbian_bullseye_install.1688614969.txt.gz
  • Last modified: 2023/07/06 03:42
  • by crashtest