[2022] NAS Image OpenMediaVault 6 CloudShell2 + KODI 19.4

[AreaScout]

@all

NAS OpenMediaVault 6 + KODI 19.4

OpenMediaVault 6 Logon Screen:

OMV6.gif (8.43 MiB) Viewed 3402 times

Boot Logo:

Boot_Logo_NAS.png (98.82 KiB) Viewed 3364 times

NEW Armbian 22.08 Yapok

Download Link -> CloudShell2 NAS Image

MD5: 1c3e08b9d10bc7fc602feea55283c0af Armbian_22.08.0-trunk_XU4_CS2_NAS_OMV6_bullseye_current_5.4.208_minimal.img.xz
SHA1: 22456e3ef535831ea2b5a6e668da33198bd07d07 Armbian_22.08.0-trunk_XU4_CS2_NAS_OMV6_bullseye_current_5.4.208_minimal.img.xz
SHA256: 27436508718056664afea5a7296f06bdf9c60b1b0685521bc44f980639fa5fbc Armbian_22.08.0-trunk_XU4_CS2_NAS_OMV6_bullseye_current_5.4.208_minimal.img.xz

User: root
Password: 1234

This is my newest custom SD Image for the CloudShell2 (446mb xz compressed), it uses Armbian 22.08 Debian bullseye as a base install, it has OpenMediaVault 6.0.34-1 (Shaitan) as well as my cloudshell2-monitoring tool 1.0.23 pre-installed, KODI is auto started when you connect a TV to your CloudShell2 and stopped if you disconnect or turn off the TV, KODI has to be installed optionally (see below)

! I was trying to build this Image with the newest Kernel 5.19 and Panfrost but the hktft32 LCD driver module seems to have a problem with 5.19 and 5.18, so I was stuck to 5.4 and proprietary Mali blobs !

After download the NAS Image, please follow this detailed instruction on how to write the Image on SD card Write OMV6 Image on SD Card

First things first !! Before you proceed with the configure process you have to logon once via SSH and change the password, there also will be a user created, please have a password and username ready, it is needed for KODI, if you want the same user to be used for network shares (SMB) you must re-create the same user under SMB once with smbpasswd -a YourChosenUserName command, on all other users added/created via web GUI you don't need to do that

To start with the first steps of the configuration of your NAS please follow this excellent Documentation

OpenMediaVault 6 Documentation

First Login to the Web UI with this user and password:

Web-Interface:
http://your_cs2_ip
User: admin
Password: openmediavault

KODI:

kodi_ani_small.gif (2.2 MiB) Viewed 3402 times

Install KODI form a terminal with:

Code: Select all

apt install kodi kodi-bin

To start KODI connect a HDMI Cable !

Need more Add-ons ? Just apt install them

Code: Select all

kodi-screensaver-rsxs-sundancer2
kodi-screensaver-rsxs-spirographx
kodi-screensaver-rsxs-solarwinds
kodi-screensaver-rsxs-flocks
kodi-screensaver-rsxs-lorenz
kodi-screensaver-rsxs-fieldlines
kodi-screensaver-rsxs-feedback
kodi-screensaver-rsxs-euphoria
kodi-screensaver-rsxs-lattice
kodi-screensaver-rsxs-skyrocket
kodi-screensaver-rsxs-hyperspace
kodi-screensaver-rsxs-drempels
kodi-screensaver-rsxs-hufotunnel
kodi-screensaver-rsxs-plasma
kodi-screensaver-rsxs-hufosmoke
kodi-screensaver-rsxs-microcosm
kodi-screensaver-rsxs-cyclone
kodi-screensaver-rsxs-helios
kodi-screensaver-rsxs-colorfire
kodi-screensaver-rsxs-matrixview
kodi-screensaver-rsxs-flux
kodi-screensaver-rsxs-busyspheres
kodi-pvr-hts
kodi-pvr-vuplus
kodi-screensaver-stars
kodi-screensaver-asteroids
kodi-screensaver-cpblobs
kodi-screensaver-matrixtrails
kodi-screensaver-shadertoy
kodi-visualization-shadertoy
kodi-visualization-matrix
kodi-visualization-waveform
kodi-visualization-starburst
kodi-imagedecoder-heif
kodi-imagedecoder-raw
kodi-imagedecoder-mpo
kodi-peripheral-joystick

screensaver_KODI.png (249.1 KiB) Viewed 3401 times

How to connect your Apple iPad / iPhone / Mac to Kodi:

• From within Kodi select Settings -> Services -> AirPlay -> Enable AirPlay Support
• Follow this instructions from within your device https://support.apple.com/en-us/HT202809

cloudshell2-monitoring tool:

Have a look how to configure this tool here viewtopic.php?f=147&t=33860#p246480

That's all, have fun !

P.S.: Please feel free to ask any questions

Regards,
Daniel

[mstumpel]

Hi I am using your image to get familiar with OMV 6. The standard things work fine however I can not get portainer up and running. also if I manually install from the console. Same issue with sabnzbd.
Both give me the following errors:

sudo docker start sabnzbd

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: bpf_prog_query(BPF_CGROUP_DEVICE) failed: invalid argument: unknown
Error: failed to start containers: sabnzbd

Any idea what can be wrong?

[AreaScout]

Any idea what can be wrong?

Yes, please edit the file /boot/boot.ini and add on line number 288 this kernel parameter systemd.unified_cgroup_hierarchy=0, then reboot your CS2, or re-download the image tomorrow, I will let you know when I updated it -> thanks for reporting !

Regards,
Daniel

[fabiobrolo]

Hi. I´ve tried this new image in my XU4, however OMV was not applying any changes (timeout) that I was doing and neither detecting my existing file system (1 HD only).
Is there something that I have to config?

[AreaScout]

Hi. I´ve tried this new image in my XU4, however OMV was not applying any changes (timeout) that I was doing and neither detecting my existing file system (1 HD only).
Is there something that I have to config?

I did a extra test for you, flashed the image on a SD card, bootet, tested to install some packages, installed docker, installed apttool plugin, everything except that missing kernel command line argument from the posts above is working, so what you can do !?

• Install the image on a different SD card, and retry it
• If you had OMV5 or 6 running on the same browser before from a different installation, delete the internet cache for this site completely, it can safe you from some big headage ! stored cookies can confuse OpenMediaVault
• If you boot for the first time, first create a new password for the root user via SSH and then immediately update OpenMediaVault to it's latest version from within the WebUI under System -> Update Management

Regards,
Daniel

[AreaScout]

@mstumpel

Uploaded the new image with the kernel command line added systemd.unified_cgroup_hierarchy=0, that will make Portainer work

Regards,
Daniel

[mstumpel]

thx for the support. I will give it a try later this week

[mstumpel]

Checked the image and portainer and sabnzbd can be installed and run in docker. Thx

[fabiobrolo]

Is the download link down?

[AreaScout]

It's working again

[BigNorm]

Firstly, @AreaScout - Thanks so much for this build! After a long break, I restarted my CloudShell (1) and without any hassles configured the NAS device I've been promising myself for a long time - Fantastic Work!!! I really like the stunning LCD display as well:-)

The question I have is with regards to getting some guidance to take this further. I'd really like to have an XU4/CloudShell(1) "desktop" machine running uBuntu Mate, and offering a "Dual Head" configuration where the server status is shown on the LCD display (using your beautiful configuration:-)) while at the same time offering a Mate Desktop as a regular development machine. Can you advise whether this has been done, how much work (and/or knowledge:-)) it would take, and if you consider it feasible?

I do not consider myself very knowledgeable with regards to Linux development, but am able to follow instructions:-)

Thanks again for your fantastic contribution! It's also been a great learning experience getting it configured and operating:-)

Norm

EDIT: So far I've gone through installing Cloudshell2-monitoring (1.0.23) on uBuntu Mate 22.04 but can't get the LCD to display anything.

[AreaScout]

I'd really like to have an XU4/CloudShell(1) "desktop" machine

I don't get it, does that (1) mean you are running a CloudShell1 or do you have a CloudShell2 ? If you have a CloudShell2 you could download Jammy Desktop image from here https://www.armbian.com/odroid-xu4/ enable the display inside the /boot/boot.ini by set cs2enable to "true", download my cloudshell2-monitoring tool and install it.

If you own a CloudShell1 you must use a 4.14 Kernel iirc, load the LCD kernel driver manually and use an older cloudshell2-monitoring tool from here https://area.mdrjr.net/tools/Cloudshell2/ I think 1.0.7 should work with a CS1

Regards,
Daniel

[Frettchen]

after 5 years of operation my XU4-cloudshell2 with OMV4 it was time to upgrade to OMV6. Upgrading with the script did not work for me, so i reimaged the eMMC with your OMV6 image. It is working so far besides the LCD and Fan. I tried all kind of things descripted in the forum but did not work. All updates are installed, OMV6 is running o.k.

Version 6.1.3-1 (Shaitan)
Processor ARMv7 Processor rev 3 (v7l)
Kernel Linux 5.4.225-odroidxu4


root@borkenas:~# systemctl status cloudshell2-monitoring
● cloudshell2-monitoring.service - "ODROID Cloudshell2 Monitoring"
Loaded: loaded (/lib/systemd/system/cloudshell2-monitoring.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2022-12-28 07:57:59 CET; 5min ago
Process: 18268 ExecStart=/usr/bin/start-lcd (code=exited, status=134)
Main PID: 18268 (code=exited, status=134)
CPU: 41ms

Dec 28 07:57:59 borkenas systemd[1]: Started "ODROID Cloudshell2 Monitoring".
Dec 28 07:57:59 borkenas start-lcd[18272]: Can't open /dev/fb0 device node
Dec 28 07:57:59 borkenas start-lcd[18268]: /usr/bin/start-lcd: line 87: 18272 Aborted /usr/bin/cloudshell2-monitoring
Dec 28 07:57:59 borkenas systemd[1]: cloudshell2-monitoring.service: Main process exited, code=exited, status=134/n/a
Dec 28 07:57:59 borkenas systemd[1]: cloudshell2-monitoring.service: Failed with result 'exit-code'.

there is no fb0 file in /dev

What do i missed here to get at least the fan running?

thanks for yout help in advance.

[Frettchen]

issue fixed after updating the u-boot with armbian-config.

Thanks for the neat system setup.

[df5cl]

Hi Daniel,
Dear CS2 aficionados,

Just changed from OMV4 CS2 to this NAS image.
But the CS2 display stays off and the web interface is kind of empty. - There is a homepage with new design, but Dashboard and Settings don't have any content.


Here you can see my attempts to verify 'cloudshell2 monitoring' is working:

Code: Select all

root@odroidxu4:~# systemctl status cloudshell2-monitoring
● cloudshell2-monitoring.service - "ODROID Cloudshell2 Monitoring"
     Loaded: loaded (/lib/systemd/system/cloudshell2-monitoring.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2023-05-12 15:19:15 CEST; 3min 38s ago
    Process: 584 ExecStart=/usr/bin/start-lcd (code=exited, status=134)
   Main PID: 584 (code=exited, status=134)

May 12 15:19:10 odroidxu4 systemd[1]: Started "ODROID Cloudshell2 Monitoring".
May 12 15:19:15 odroidxu4 start-lcd[1565]: Can't open /dev/fb0 device node
May 12 15:19:15 odroidxu4 start-lcd[584]: /usr/bin/start-lcd: line 87:  1565 Aborted                 /usr/bin/cloudshell2-monitoring
May 12 15:19:15 odroidxu4 systemd[1]: cloudshell2-monitoring.service: Main process exited, code=exited, status=134/n/a
May 12 15:19:15 odroidxu4 systemd[1]: cloudshell2-monitoring.service: Failed with result 'exit-code'.
root@odroidxu4:~# nano /etc/cloudshell2-monitoring/cloudshell2-monitoring.conf
root@odroidxu4:~# systemctl start cloudshell2-monitoring
root@odroidxu4:~# nano /etc/cloudshell2-monitoring/cloudshell2-monitoring.conf
root@odroidxu4:~# systemctl status cloudshell2-monitoring
● cloudshell2-monitoring.service - "ODROID Cloudshell2 Monitoring"
     Loaded: loaded (/lib/systemd/system/cloudshell2-monitoring.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2023-05-12 15:24:30 CEST; 10s ago
   Main PID: 6177 (start-lcd)
      Tasks: 2 (limit: 4441)
     Memory: 1.2M
     CGroup: /system.slice/cloudshell2-monitoring.service
             ├─6177 /bin/bash /usr/bin/start-lcd
             └─6181 /usr/bin/cloudshell2-monitoring

May 12 15:24:30 odroidxu4 systemd[1]: Started "ODROID Cloudshell2 Monitoring".
root@odroidxu4:~# systemctl status cloudshell2-monitoring
● cloudshell2-monitoring.service - "ODROID Cloudshell2 Monitoring"
     Loaded: loaded (/lib/systemd/system/cloudshell2-monitoring.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2023-05-12 15:25:04 CEST; 21s ago
    Process: 6177 ExecStart=/usr/bin/start-lcd (code=exited, status=134)
   Main PID: 6177 (code=exited, status=134)

May 12 15:24:30 odroidxu4 systemd[1]: Started "ODROID Cloudshell2 Monitoring".
May 12 15:25:04 odroidxu4 start-lcd[6181]: Can't open /dev/fb0 device node
May 12 15:25:04 odroidxu4 start-lcd[6177]: /usr/bin/start-lcd: line 87:  6181 Aborted                 /usr/bin/cloudshell2-monitoring
May 12 15:25:04 odroidxu4 systemd[1]: cloudshell2-monitoring.service: Main process exited, code=exited, status=134/n/a
May 12 15:25:04 odroidxu4 systemd[1]: cloudshell2-monitoring.service: Failed with result 'exit-code'.
root@odroidxu4:~# 

Any idea? Do I also need to flash UBoot seperately?

UPDATE: Followed Daniel's advice below from previous OMV4 posts and now the display became active.

Code: Select all

fdtoverlay -v -i /boot/dtb/exynos5422-odroidxu4.dtb -o /boot/dtb/exynos5422-odroidxu4.dtb /boot/dtb/overlays/hktft-cs-ogst.dtbo /boot/dtb/overlays/i2c0.dtbo /boot/dtb/overlays/i2c1.dtbo

Empty web Interface >> admin, openmediavault! - I did try with the terminal assigned users and that results in an empty page...

Happy hackin',
-Pete

[AreaScout]

Any idea? Do I also need to flash UBoot seperately?

UPDATE: Followed Daniel's advice below from previous OMV4 posts and now the display became active.

Empty web Interface >> admin, openmediavault! - I did try with the terminal assigned users and that results in an empty page...

Happy hackin',
-Pete

Just to clarify, the Image works on SD cards without patching the device tree files, if you use a EMMC you have to have the newest uboot on EMMC (stored in a special area on the media, SD use's a different method for booting), just update uboot on EMMC with armbian-config tool and reboot or patch the device tree files, but note that a kernel update may overwrite this files so update uboot on EMMC is the way to go.

For the web interface, are you login in with this credentials User: admin Password: openmediavault and the web interface stays empty ? If so you have to look at the openmediavault log files what's going wrong, update OMV6 to the latest version, check file system, normally you login with user admin and openemdiavault and then add some more user from within the web interface

Regards,
Daniel