Janne Posted June 23, 2020 Posted June 23, 2020 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?
gprovost Posted June 24, 2020 Author Posted June 24, 2020 @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).
Janne Posted June 24, 2020 Posted June 24, 2020 Would this https://www.mouser.fi/datasheet/2/942/SF_VES90-1508671.pdf power supply work? The 2 "upper" pins (pins 1 and 2) next to the notch are positive and pins 3 and 4 (as well as the sleeve) are negative.
gprovost Posted June 25, 2020 Author Posted June 25, 2020 @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.
PEW Posted June 25, 2020 Posted June 25, 2020 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=22https://github.com/OpenMediaVault-Plugin-Developers/installScript/blob/master/upgrade4to5https://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 1
DavidGF Posted June 27, 2020 Posted June 27, 2020 Are we supposed to upgrade our PSU? Are they all failing or was it a bad batch? Thanks!
gprovost Posted June 29, 2020 Author Posted June 29, 2020 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.
Harvey Posted June 30, 2020 Posted June 30, 2020 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.
gprovost Posted July 1, 2020 Author Posted July 1, 2020 @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.
Harvey Posted July 1, 2020 Posted July 1, 2020 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!
Patrick Schlüter Posted July 5, 2020 Posted July 5, 2020 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.
gprovost Posted July 6, 2020 Author Posted July 6, 2020 @Patrick Schlüter You mean the interface disappeared ? Have you try a full power cycle ? unplug / plug DC plug. What do you get if you do the following commands ? sudo ethtool eth0 dmesg | grep mvneta
Patrick Schlüter Posted July 6, 2020 Posted July 6, 2020 (edited) 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 July 6, 2020 by Patrick Schlüter
PEW Posted July 7, 2020 Posted July 7, 2020 (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=22https://github.com/OpenMediaVault-Plugin-Developers/installScript/blob/master/upgrade4to5https://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 July 7, 2020 by PEW
bigbrovar Posted July 8, 2020 Posted July 8, 2020 Hi everyone. Been running my helios4 since last year. Runs like clock work. I currently have 2 WD Red 4 terabyte drives and I am looking to add an additional 2 1tb ssd drives (using a 2.5 to 3.5 adapter) the SSD are meant to be a storage for VMs I would be running on my laptops but shared via NFS. This got me wondering if having SSD shared over NFS through a Gigabit ethernet would bring any added advantage. If the ethernet card would limit my maximising the potential of the ssd drives (in write shd read speeds) Can can I get a second ethernet (over usb 3) and have a bond interface with the onboard nic.. Would appreciate insight on this.
Heisath Posted July 8, 2020 Posted July 8, 2020 Regarding SSD performance in general: 1Gbit/s Ethernet would limit your data rates to about 120MB/s, which normal drives are also capable of doing. But an SSD also has the big advantage of faster (nearly instant) access times (to any sector/block) which is definitely noticable when running VMs (as their data is more random access than serial). Bonding several eth links together is no problem (regardless wether they are directly attached or via USB3 / whatever). See the Linux Bonding package for more info https://help.ubuntu.com/community/UbuntuBonding (for example). If have tried this on a board similar to helios4 and it works. But keep in mind, the other side of your dual network cables also has to be able to detect and bond the links.
Aldoz Posted July 10, 2020 Posted July 10, 2020 My Helios4 stopped working. Here is what I've tried so far: Removed all HDD, full power cycle, re-flashed the same sdcard. It was doing some high pitch sound not coming from HDD since it still happened after removing all HDD but then suddenly all gone. No sound and not booting. It stops here in the serial console: U-Boot SPL 2019.04-armbian (Jun 03 2020 - 10:05:36 +0200) High speed PHY - Version: 2.0 Detected Device ID 6828 board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 6 | SATA0 | | 1 | 5 | USB3 HOST0 | | 2 | 6 | SATA1 | | 3 | 6 | SATA3 | | 4 | 6 | SATA2 | | 5 | 5 | USB3 HOST1 | -------------------------------- High speed PHY - Ended Successfully mv_ddr: mv_ddr-armada-18.09.2 Is there anything else I can do? Thanks
gprovost Posted July 13, 2020 Author Posted July 13, 2020 @Aldoz Are you able to measure the following voltage with a voltmeter ? Expected measured value, on 5V rail: 4.90 V - 5.20 V on 12V rail: 11.90 V - 12.5 V If 12V is outside that range, that means the power supply is faulty. Is the high pitch noise come from the board or the power adapter ?
Aldoz Posted July 13, 2020 Posted July 13, 2020 (edited) @gprovost I don't have a voltmeter, but I'll try and get one. The sound feels like it's coming from the board. It's not doing it anymore since it stopped booting. I tried it again after being unplugged for a day and it just keeps looping after the mv_ddr line. Edited July 13, 2020 by Aldoz Added info.
gprovost Posted July 14, 2020 Author Posted July 14, 2020 12 hours ago, Aldoz said: The sound feels like it's coming from the board. It's not doing it anymore since it stopped booting. I tried it again after being unplugged for a day and it just keeps looping after the mv_ddr line. Well actually it's still a good sign the system can boot up even though it hangs at very early stage. Yes could be a dying power adapter. To confirm, need to measure the voltage point I posted previously.
bigbrovar Posted July 20, 2020 Posted July 20, 2020 Hi guys, what do I need to do to setup the Helios4 as a iscsi target and allow other computers connect to it. I am running latest armbian (buster) Also would I be able to connect the Helios4 target to a 64b OS or it is doesn't matter.
gprovost Posted July 21, 2020 Author Posted July 21, 2020 @bigbrovar You are asking a general Linux question, this is not hardware specific. Search for 'linux iscsi server' and you will find plenty of tutorial online. It doesn't matter that the client is a different architecture.
bigbrovar Posted July 21, 2020 Posted July 21, 2020 4 minutes ago, gprovost said: @bigbrovar You are asking a general Linux question, this is not hardware specific. Search for 'linux iscsi server' and you will find plenty of tutorial online. It doesn't matter that the client is a different architecture. Thanks. Just wanted to be sure.
bigbrovar Posted July 21, 2020 Posted July 21, 2020 Please I noticed the USB 3 interface on my helios4 does not detect an external drive. When I plug in a 2.5 inch drive through an orico sata to USB 3 device. Nothing happens, even lsusb shows nothing. Same drive is detected on my (Ubuntu 18.04) laptop. Interestingly, the Helios4 detect a USB mouse, I could see it via lsusb and the mouse led lights up when connected.
gprovost Posted July 21, 2020 Author Posted July 21, 2020 1 minute ago, bigbrovar said: Please I noticed the USB 3 interface on my helios4 does not detect an external drive. When I plug in a 2.5 inch drive through an orico sata to USB 3 device. Nothing happens, even lsusb shows nothing. Could be that the power used from all USB devices exceed the max power budget of the USB power rail. Do you have more than one device connected ? What Orico model you are referring to ?
bigbrovar Posted July 21, 2020 Posted July 21, 2020 49 minutes ago, gprovost said: Could be that the power used from all USB devices exceed the max power budget of the USB power rail. Do you have more than one device connected ? What Orico model you are referring to ? I used it with this https://www.amazon.com/gp/product/B01LY97QE8/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 The drive is a 1tb mechanical drive. No other device is connected. what is the max power budget and is it possible to increase it?
gprovost Posted July 21, 2020 Author Posted July 21, 2020 3A Max budget. Budget is both ports. So if one draw 2A, only 1A remains for the other one. Do you have another USB device connected ? If not, then there is no reason it doesn't work. What's the HDD model you are using ?
bigbrovar Posted July 21, 2020 Posted July 21, 2020 2 minutes ago, gprovost said: 3A Max budget. Budget is both ports. So if one draw 2A, only 1A remains for the other one. Do you have another USB device connected ? If not, then there is no reason it doesn't work. What's the HDD model you are using ? I am using it with a 2.5 WD slim 5v 0.55A drive. 1tb capacity. I am really confused. I could make a video. It works on my laptop and it is not even detected on via lsusb and the device led stays off. My mouse is detected right away though. Could this be a power supply issue I have been reading about issue some people had with the power supply that came with the Helios4.
gprovost Posted July 21, 2020 Author Posted July 21, 2020 Any chance you have a USB3.0 Flash dongle around, to check if at least you can detect. Mouse is only USB2.0.
bigbrovar Posted July 21, 2020 Posted July 21, 2020 13 minutes ago, gprovost said: Any chance you have a USB3.0 Flash dongle around, to check if at least you can detect. Mouse is only USB2.0. I happen to have a USB 3 device. An odroid emmc writer. When I plugged it to my laptop and ran a lsusb -D here is what I got lsusb -D /dev/bus/usb/002/004 Device: ID 05e3:0749 Genesys Logic, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.20 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x05e3 Genesys Logic, Inc. idProduct 0x0749 bcdDevice 15.38 iManufacturer 3 Generic iProduct 4 USB3.0 Flash Disk iSerial 2 000000001538 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 224mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 4 Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 22 bNumDeviceCaps 2 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType 16 bDevCapabilityType 2 bmAttributes 0x00000f0e Link Power Management (LPM) Supported SuperSpeed USB Device Capability: bLength 10 bDescriptorType 16 bDevCapabilityType 3 bmAttributes 0x00 wSpeedsSupported 0x000e Device can operate at Full Speed (12Mbps) Device can operate at High Speed (480Mbps) Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 1 Lowest fully-functional device speed is Full Speed (12Mbps) bU1DevExitLat 10 micro seconds bU2DevExitLat 2047 micro seconds Device Status: 0x000c (Bus Powered) U1 Enabled U2 Enabled When I plugged it in the helios it seem to be detected as a usb2 device. It is however detected. Just wondering why it is not seen as a usb3 device on the helios. root@helios4:~# lsusb -D /dev/bus/usb/004/004 Device: ID 05e3:0749 Genesys Logic, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x05e3 Genesys Logic, Inc. idProduct 0x0749 bcdDevice 15.38 iManufacturer 3 Generic iProduct 4 USB3.0 Flash Disk iSerial 2 000000001538 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0020 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 0x0016 bNumDeviceCaps 2 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType 16 bDevCapabilityType 2 bmAttributes 0x00000f0e BESL Link Power Management (LPM) Supported BESL value 3840 us SuperSpeed USB Device Capability: bLength 10 bDescriptorType 16 bDevCapabilityType 3 bmAttributes 0x00 wSpeedsSupported 0x000e Device can operate at Full Speed (12Mbps) Device can operate at High Speed (480Mbps) Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 1 Lowest fully-functional device speed is Full Speed (12Mbps) bU1DevExitLat 10 micro seconds bU2DevExitLat 2047 micro seconds can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0000 (Bus Powered)
Recommended Posts