36 36
gprovost

Helios4 Support

Recommended Posts

There seems to be a lot of PSU options with regular 2.1mm DC jack. Has anyone tried using (or soldering their own) a Mini DIN to DC jack adapter?

Share this post


Link to post
Share on other sites

@Janne Actually pretty straight forward. If you cut the DC side of power adapter cable you will see inside there are only 2 wire. One black and one red.

Red : +12Vdc

Black : GND

 

So you can easily repurposed the 4-Pin Mini Din cable with a ATX PSU (P4 connector) or any AC/DC 12V Adapter (need 8A output at least).

 

 

Share this post


Link to post
Share on other sites

@Janne Yes that is a correct pinout. But it's quite expensive.

 

Maybe check on amazon first for Synology power adapter replacement since we use the same exact 4-pin pinout and connector.

 

image.thumb.png.7399507adcae4abc21daaa4031264c3b.png

 

Share this post


Link to post
Share on other sites

Here is my guide to upgrade omv4to5. Hopefully this will help out others looking to do the same.

 

Was able to upgrade omv4 to 5. Here is my posts and the github bash script from the omv site: I downloaded the scripts then changed to executable.

https://forum.openmediavault.org/index.php?thread/27909-omv-5-0-finally-out/&pageNo=2  
https://forum.openmediavault.org/index.php?thread/27909-omv-5-0-finally-out/&pageNo=22
https://github.com/OpenMediaVault-Plugin-Developers/installScript/blob/master/upgrade4to5
https://forum.openmediavault.org/index.php?thread/33219-upgrade-to-5-x-failure/&pageNo=1
 
Steps to reproduce:

1. Remove incompatible plugins
2. Switch over to dockers that are incompatible
3. Download the two bash scripts:
wget https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/upgrade4to5
wget https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install
4. chmod +x the upgrade4to5 chmod +x install
5. Run the upgrade4to5 as root
6. omv and plugins will fail. as describes here: https://forum.openmediavault.org/index.php?thread/33219-upgrade-to-5-x-failure/&pageNo=1
7. Remove failed packages not purge since we want config files from omv They should print out.
8. Reinstall openmediavault only
9. Reboot
10. Run this command : apt-get purge openmediavault-omvextrasorg resolvconf
11. Reboot again
12. Run the install script as root. this will install omv extras.
13. apt update
14. apt dist-upgrade
15. omv-salt deploy run nginx

16. omv-salt deploy run phpfpm

17. But remove or move upsschedule-cmd from usr/bin and bin then run  apt-get install usrmerge
18. apt install docker
19. https://forums.docker.com/t/fa…te-nat-chain-docker/78269

The docker installer uses iptables for nat. Unfortunately Debian uses nftables. You can convert the entries over to nftables or just setup Debian to use the legacy iptables.

sudo update-alternatives --set iptables /usr/sbin/iptables-legacy

sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy

dockerd, should start fine after switching to iptables-legacy.

sudo service docker start

20. Switch to 5.4 kernel using armbian-config refer to kobol blog: 

https://blog.kobol.io/2020/03/13/armbian-new-release/

Hopefully this helps others out.

Thanks 
 

Share this post


Link to post
Share on other sites
On 6/28/2020 at 1:38 AM, DavidGF said:

Are we supposed to upgrade our PSU? Are they all failing or was it a bad batch?

 

Honestly hard to say since capacitor failure is something not to be unexpected on such appliance PSU (you can check for other NAS brand, it's quite common). However clearly these occurrences experiences by some users are premature capacitor failure. For instance on our side we have yet to experience these capacitors failure, even though we have some setup that have been running non stop for more than 2 years now.

 

As mentioned previous we are changing PSU supplier for Helios64. Supplier which gives us more control on the capacitor brand and model. We will be using Rubycon capacitor.

Share this post


Link to post
Share on other sites

No Text on OLED-Display (Logo is ok)

 

Today I assembled my spare Helios 4 from batch 3 (which came with the bonus OLED display) and installed Armbian_20.05.2_Helios4_buster_current_5.4.43.img - nothing else yet.

 

Nearly the first thing I did was to install sys-oled, which works well with everything left at defaults, with the exception of text display: Every line of text is just a solid block of pixels . The graphical logo displays well, so cabling and OLED type (sh1106) seem to be correct.

 

 

Share this post


Link to post
Share on other sites

@Harvey I just updated sys-oled repo to fix the issue since the code wasn't aligned with latest luma.core changes.

 

Pull the git repo and reinstall (sudo ./install.sh). Let me know if it works.

Share this post


Link to post
Share on other sites
4 hours ago, gprovost said:

@Harvey I just updated sys-oled repo to fix the issue since the code wasn't aligned with latest luma.core changes.

 

Pull the git repo and reinstall (sudo ./install.sh). Let me know if it works.

Yes, it's working now, thanks a lot for the quick fix!

Share this post


Link to post
Share on other sites

Hello,

my installation omv crashed the other day. The SD card was corrupted and fsck was not able to get the thing back. Ok, I said, not a problem, I will reinstall the system from the last version.
I downloaded the last version Armbian_20.05.1_Helios4_buster_current_5.4.43 and thought that I will be good in an hour.
Now it is two days later and it doesn't work and I don't know how to get it to work. Here just a little description of what happens.
1. write the image on the µSD

2. put in Helios4. Start.

3. connect over serial. login roor, change root password, add sudo user.

4. apt update+upgrade. ok.

5. (optionally) Set fixed IP-address with armbian-config (DHCP doesn't change the issue).

6. enter armbian-config install OMV. Installation takes some time, the nas reboots.

7. login with root or the user

8. No network anymore. OMV took over the system, the eth0: device is no more. OMV is not usable because there's no GUI, one cannot connect externally to it.
Here the result of ifconfig

root@helios4:~# ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 2129  bytes 878522 (857.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2129  bytes 878522 (857.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@helios4:~#

What can I do to at least set an interface. The options are annoying as I don't want to read a treatise on systemd and having to lear what the f.  yaml is, or in what format I have to invoke beelzebuth to get that interface to show up.
 

Share this post


Link to post
Share on other sites
15 hours ago, gprovost said:

@Patrick Schlüter You mean the interface disappeared ?

 

Have you try a full power cycle ? unplug / plug DC plug.

Yes, the interface eth0 is missing

 

Quote

 

What do you get if you do the following commands ?

 

sudo ethtool eth0

 

dmesg | grep mvneta

root@helios4:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP AUI BNC MII FIBRE Backplane ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                1000baseX/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Advertised FEC modes: Not reported
        Speed: Unknown!
        Duplex: Half
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: d
        Wake-on: d
        Link detected: no

root@helios4:~# dmesg | grep mvneta
[    1.731952] mvneta_bm f10c8000.bm: Buffer Manager for network controller enabled
[    1.734625] mvneta f1070000.ethernet eth0: Using device tree mac address 06:69:ed:96:0b:b2

 

 

So I simply set the interface by hand with ifconfig as in older times
 

ifconfig eth0 up
ifconfig eth0 inet 192.168.1.201/24

 

Now I can connect with OMV. I will see if I can make the change so that it is permanent.
and now I can connect.
 

After reboot the adress I set is still set. Ok, my immediate problem is fixed. Thank you.

Edited by Patrick Schlüter

Share this post


Link to post
Share on other sites
(edited)
On 6/25/2020 at 9:53 AM, PEW said:

Here is my guide to upgrade omv4to5. Hopefully this will help out others looking to do the same.

Test a backup/restore procedure: How to restore from an omv-backup?

Was able to upgrade omv4 to 5. Here is my posts and the github bash script from the omv site: I downloaded the scripts then changed to executable.

https://forum.openmediavault.org/index.php?thread/27909-omv-5-0-finally-out/&pageNo=2  
https://forum.openmediavault.org/index.php?thread/27909-omv-5-0-finally-out/&pageNo=22
https://github.com/OpenMediaVault-Plugin-Developers/installScript/blob/master/upgrade4to5
https://forum.openmediavault.org/index.php?thread/33219-upgrade-to-5-x-failure/&pageNo=1
 
Steps to reproduce:

1. Remove incompatible plugins
2. Switch over to dockers where there are incompatible plugins
3. Download the two bash scripts:
wget https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/upgrade4to5
wget https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install
4. chmod +x the upgrade4to5 chmod +x install
5. Run the upgrade4to5 as root
6. omv and plugins will fail. as describes here: https://forum.openmediavault.org/index.php?thread/33219-upgrade-to-5-x-failure/&pageNo=1
7. Remove failed packages not purge since we want config files from omv They should print out.
8. Reinstall openmediavault only
9. Reboot
10. Run this command : apt-get purge openmediavault-omvextrasorg resolvconf
11. Reboot again
12. Run the install script as root. this will install omv extras.
13. apt update
14. apt dist-upgrade
15. omv-salt deploy run nginx

16. omv-salt deploy run phpfpm

17. But remove or move upsschedule-cmd from usr/bin and bin then run  apt-get install usrmerge
18. apt install docker
19. https://forums.docker.com/t/fa…te-nat-chain-docker/78269

The docker installer uses iptables for nat. Unfortunately Debian uses nftables. You can convert the entries over to nftables or just setup Debian to use the legacy iptables.

sudo update-alternatives --set iptables /usr/sbin/iptables-legacy

sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy

dockerd, should start fine after switching to iptables-legacy.

sudo service docker start

20. Switch to 5.4 kernel using armbian-config refer to kobol blog: 

https://blog.kobol.io/2020/03/13/armbian-new-release/

Hopefully this helps others out.

Thanks 
 

 

Edited by PEW

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
36 36