Jump to content

Patrick Schlüter

Validating
  • Posts

    3
  • Joined

  • Last visited

  1. Yes, the interface eth0 is missing 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.
  2. 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.
  3. 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.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines