Done.
Building OMV automatically for a bunch of different ARM dev boards
-
-
@ryecoaaron last three images to upload:
- OMV_3_0_91_Helios4_4.4.96.img.xz (MD5: 1063fd0381b18dcbeea9f8372ba5f7b7)
- OMV_3_0_91_Nanopim1plus_4.13.12.img.xz (MD5: de65c3ef2c9ba69f82e83bdd39b6e7c1)
- OMV_3_0_91_Nanopim1plus2_4.13.12.img.xz (MD5: b2fb6855dc2fda667e4d16dbc078752f)
That's now all the GbE enabled boards Armbian currently supports in a stable branch...
Browsing through the forum, I haven't found an explanation on why 3_0_91 isn't available for the Odroid line. Any plans for that or a link to a thread that explains what the issue might be?
Thanks in advance.
-
Browsing through the forum, I haven't found an explanation on why 3_0_91 isn't available for the Odroid line. Any plans for that or a link to a thread that explains what the issue might be?
Just install the 3.0.88 image and update from the Updates tab. Then you will have 3.0.91.
-
Just install the 3.0.88 image and update from the Updates tab. Then you will have 3.0.91.
As my signature shows, I'm already at 3.0.91. I'm still interested in knowing whether there is some issue with Odroid/XU4 going forward... I'm a simple minded guy who just likes knowing there's a (current) iso image to reload should things really go south at some point.
-
As my signature shows, I'm already at 3.0.91. I'm still interested in knowing whether there is some issue with Odroid/XU4 going forward... I'm a simple minded guy who just likes knowing there's a (current) iso image to reload should things really go south at some point.
No, there is no issue. We don't release a new image every time a new revision of OMV is released because there is no need. Sometimes there are improvements for some boards that justifies a new image. If you based things going south on the revision available, then 24 of the 28 arm images available would be going south since they aren't on 3.0.91.
-
Just as a referene the summary what makes these OMV SBC images generated with Armbian's build system somewhat special: https://forum.armbian.com/topi…findComment&comment=44097
Edit: almost forgot to mention: All of ayufan's OMV images for ROCK64 also contain those relevant performance stuff (we added that a while ago already) so it's fine to choose his OMV images too
-
Big thank's for every contributor to extend the base for openmediavault to all these nice arm boards!
I have big troubles to get the image OMV_3_0_90_Orangepipc2_4.13.10.img.xz running on my Orange Pi PC 2.
Right now the system is running an armbian without problems with original power supply and a shiny evo+ micro sd card.
Just to be sure I did the following steps (more than one time):
- Downloading the image + md5 / checking checksum manually (2+)
- Checking the shiny evo+ micro sd card with f3 for errors (2+)
- Writing & Verifying the image (using etcher) to micro sd (5+)
- booting the image with network-cable attached and let it settle (5+)
And from here the result is always not nice. Often the device doesn't come up in my network. When it's available sometimes there is no webserver delivering the OMV-frontend. The other is that it's accessible but immediately starts throwing errors in the web interface (lost connection or something) and goes "offline" quite quickly.
I did this today again - as I did this a couple of weeks ago already. The results are the same and I never get the system running. Never able to access the system via ssh or get any logs out.
I wanted to try the way to use the armbian-debian base and converting it to OMV. But sadly there is only armbian-ubuntu based images available and I don't have resources to build my own armbian images.
Just to be sure I also downloaded the new OMV image for the Raspberry Pi 3 to try on this device... and it works directly
I just want somebody to confirm that OMV_3_0_90_Orangepipc2_4.13.10.img.xz is working out of the box - because I'm running out of knowledge?
Thank's!
---
Access denied. You are not authorized to view this page. -
Big thank's for every contributor to extend the base for openmediavault to all these nice arm boards!
I have big troubles to get the image OMV_3_0_90_Orangepipc2_4.13.10.img.xz running on my Orange Pi PC 2.
Right now the system is running an armbian without problems with original power supply and a shiny evo+ micro sd card.
Just to be sure I did the following steps (more than one time):
- Downloading the image + md5 / checking checksum manually (2+)
- Checking the shiny evo+ micro sd card with f3 for errors (2+)
- Writing & Verifying the image (using etcher) to micro sd (5+)
- booting the image with network-cable attached and let it settle (5+)
And from here the result is always not nice. Often the device doesn't come up in my network. When it's available sometimes there is no webserver delivering the OMV-frontend. The other is that it's accessible but immediately starts throwing errors in the web interface (lost connection or something) and goes "offline" quite quickly.
I did this today again - as I did this a couple of weeks ago already. The results are the same and I never get the system running. Never able to access the system via ssh or get any logs out.
I wanted to try the way to use the armbian-debian base and converting it to OMV. But sadly there is only armbian-ubuntu based images available and I don't have resources to build my own armbian images.
Just to be sure I also downloaded the new OMV image for the Raspberry Pi 3 to try on this device... and it works directly
I just want somebody to confirm that OMV_3_0_90_Orangepipc2_4.13.10.img.xz is working out of the box - because I'm running out of knowledge?
Thank's!
---
Access denied. You are not authorized to view this page.Just to be sure I did the whole process with a diffrent sd card. I have the same results in the web-gui. communication erros -> offline.
I just wonder because there are a couple of downloads for the Orange Pi PC 2 and nobody complained?
-
I downloaded the image, burned it on SD card with Etcher, inserted it into Orange Pi Zero Plus (I donated my PC2 already last year to another dev so can' t test on the hardware), booted, then 'apt update' followed by 'apt upgrade' followed by the mandatory reboot: sudo armbianmonitor -u
Works as expected, in a few weeks there will be a small performance bump via an update (cpufreq scaling and DVFS support then with 4.14 kernel)
-
I downloaded the image, burned it on SD card with Etcher, inserted it into Orange Pi Zero Plus (I donated my PC2 already last year to another dev so can' t test on the hardware), booted, then 'apt update' followed by 'apt upgrade' followed by the mandatory reboot: sudo armbianmonitor -u
Works as expected, in a few weeks there will be a small performance bump via an update (cpufreq scaling and DVFS support then with 4.14 kernel)
Thank's tkaiser for your reply. Was your test performed with a display attached and did you manually executed 'apt update' & 'apt upgrade'?
I did it unattended and just waited till the web gui came up. This is the way I used to.... but I think I will find a display and some keyboard for my next run!
BTW: DVFS and kernel 4.14 sounds great!
-
Was your test performed with a display attached and did you manually executed 'apt update' & 'apt upgrade'?
No display (there's not even HDMI on the board I tested with). I waited 3 minutes for the automatic reboot, then accessed OMV's web UI to enable SSH and did the next step through network/SSH.
I've really no idea whether these OMV builds for H5 boards (or any Allwinner 64-bit boards) currently display anything via HDMI or not. They should be fully useable via network and if this doesn't work you need serial console anyway (but this is a bit out of OMV scope and more something for Armbian forum)
-
No display (there's not even HDMI on the board I tested with). I waited 3 minutes for the automatic reboot, then accessed OMV's web UI to enable SSH and did the next step through network/SSH.
I've really no idea whether these OMV builds for H5 boards (or any Allwinner 64-bit boards) currently display anything via HDMI or not. They should be fully useable via network and if this doesn't work you need serial console anyway (but this is a bit out of OMV scope and more something for Armbian forum)I didn't tried with a display attached but I gave a couple of more shots to track the source of failure.
What I can say at this point: the network goes (completely) down in any state (no matter of the web gui or ssh is used or not) after a short period when the device is powered. I also changed the network cables and position in the network (from switch to router) just to be sure there is no poison from there.
One time I was fast enough to enter the web-gui and add a ssh user (half way, because while applying the configuration connection was lost). And after a hard reset (taking off the power supply) I was even able to enter via ssh for half a second (before I was kicked/the host went down)
Bash
Alles anzeigenuser@orangepipc2 password: ___ ____ _ ____ ____ ____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) | _ \ / ___|___ \ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | |_) | | __) | | |_| | | | (_| | | | | (_| | __/ | __/| | | __/| |___ / __/ \___/|_| \__,_|_| |_|\__, |\___| |_| |_| |_| \____|_____| |___/ Welcome to ARMBIAN 5.35 user-built Debian GNU/Linux 8 (jessie) 4.13.10-sunxi64 System load: 1.26 0.71 0.28 Up time: 1 min Memory usage: 12 % of 994MB IP: 192.168.XXX.XXX CPU temp: 21°C Usage of /: 9% of 7.4G New to Armbian? Check the documentation first: https://docs.armbian.com Could not chdir to home directory /home/user: No such file or directory $ Connection to orangepipc2 closed by remote host. Connection to orangepipc2 closed.
In the next step I will build a dedicated network to see if the failure is reproducible.Are there by change any logs written to sd card which I could recover to get some information why the system goes offline?
-
I don't know how and why but after a power circuit I was able to enter the system via ssh without getting kicked right away:
I did a 'sudo apt update' followed by a 'sudo apt upgrade' and there are some not that nice looking messages from syslogd@orangepipc2:
Bash
Alles anzeigenFetched 2056 kB in 12s (158 kB/s) W: Failed to fetch https://dl.bintray.com/openmediavault-plugin-developers/erasmus/dists/jessie/main/binary-arm64/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none W: Failed to fetch https://dl.bintray.com/openmediavault-plugin-developers/erasmus/dists/jessie/main/binary-armhf/Packages server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none E: Some index files failed to download. They have been ignored, or old ones used instead. $ sudo apt upgrade Reading package lists... Done Building dependency tree... 72% Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.058985] Internal error: Oops: 96000006 [#1] SMP Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.221257] Process php5-fpm (pid: 1788, stack limit = 0xffff80001760c000) Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.232413] Stack: (0xffff80001760fd20 to 0xffff800017610000) Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.242451] fd20: 0000000000000000 ffff0000081e4458 ffff000008c38000 0000000000000005 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.254621] fd40: 00000000ffffff9c ffff800016dcb000 0000000080000000 ffff0000081ec850 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.266768] fd60: ffff80001760fde0 ffff000008208af8 0000000000000005 ffff80002d948300 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.278882] fd80: ffff80001760fda0 ffff80002d948328 0000000000009eb0 00000001000081a4 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.290962] fda0: 0000000000000000 0000000000000000 ffff80001760fdb8 ffff0000081f79f0 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.303081] fdc0: ffff000008c38000 0000ffff89da7640 ffff80001760fde0 0000000000040d00 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.315221] fde0: ffff80001760fe30 ffff000008208cac ffff000008c38000 0000000000020000 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.327336] fe00: 00000000ffffff9c ffff800016dcb000 0000000080000000 ffff800016dcb000 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.339439] fe20: 0000000000000124 000080002f358000 ffffff9c00000000 0000000000040d00 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.351517] fe40: ffff80001760feb0 ffff0000081e4540 0000000000000000 000080002f358000 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.363583] fe60: ffffffffffffffff 0000ffff8e4a148c 0000000059f5fff9 000000002753580d Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.375644] fe80: 00000000590baf43 0000000000000000 0000000000020000 0000010000000004 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.387774] fea0: 0000000000000001 0000000000040d00 0000000000000000 ffff000008082730 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.399856] fec0: ffffffffffffff9c 0000ffff89da7640 0000000000000000 0000000000000000 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.411917] fee0: 0000000000000008 000000003a3b52c8 0000ffff89da7680 2e636e7973722e65 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.424017] ff00: 0000000000000038 6c75617661696465 6f6d617461642f74 6e6f632f736c6564 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.436040] ff20: 6369767265732e66 2e636e7973722e65 6e6f736a2e626f6a 0000ffff8e48d588 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.447994] ff40: 0000000000c15570 0000ffff8e4a1410 0000000000000000 0000000000c13000 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.459921] ff60: 0000ffff89da7640 0000ffff89f13d10 0000000000000000 0000000000000000 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.471758] ff80: 0000000000c1d818 0000000000000000 0000000000000000 0000ffff89f13d10 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.483478] ffa0: 0000000000000000 0000ffffe261f020 000000000069bf00 0000ffffe261f020 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.495075] ffc0: 0000ffff8e4a148c 0000000080000000 ffffffffffffff9c 0000000000000038 Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.506568] ffe0: 0000000000000000 0000000000000000 296a006d29ff0008 00000830b70603ec Message from syslogd@orangepipc2 at Oct 29 16:54:40 ... kernel:[ 100.665168] Code: b90117a0 910162a2 f9004ba2 52800000 (b94012d7) Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: armbian-firmware curl hostapd libcurl3 libcurl3-gnutls libssl-dev libssl1.0.0 libwbclient0 linux-dtb-next-sunxi64 linux-image-next-sunxi64 linux-jessie-root-next-orangepipc2 openmediavault openssl python-samba samba samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules sunxi-tools 21 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 28.7 MB of archives. After this operation, 795 kB of additional disk space will be used. Do you want to continue? [Y/n]
followed by a: Y
The message is too long, must be under 10,000 characters.
-
and a couple of working upgrades it ends with this:
Bash
Alles anzeigenupdate-initramfs: Generating /boot/initrd.img-4.13.16-sunxi64 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 304.816206] Internal error: Oops: 96000004 [#2] SMP Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.091144] Process fsck (pid: 3761, stack limit = 0xffff80001e044000) Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.101622] Stack: (0xffff80001e047c00 to 0xffff80001e048000) Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.111283] 7c00: ffff80001e047c70 ffff0000080ac110 ffff80002b6eb600 ffff000008c38000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.123082] 7c20: ffff80001e047d90 0000000000000eb5 0000000000000000 ffff000008c35000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.134822] 7c40: 0000000000000010 0000000000000000 ffff000008961000 ffff800035e92880 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.146525] 7c60: 00000000001eef1b ffff800016fddc00 ffff80001e047cf0 ffff0000080ac308 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.158243] 7c80: ffff80002b6eb600 ffff80001e047d90 ffff000008c35100 ffff000008c38000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.169984] 7ca0: ffff80001e047db8 00000000fffffff6 ffff800035e92880 ffff800035e92d88 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.181760] 7cc0: ffff000008961000 ffff800035e92880 ffff000008c38000 00000000001eef1b Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.193587] 7ce0: 0000000000000000 0000000000040d00 ffff80001e047d50 ffff0000080ad468 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.205416] 7d00: ffff000008c38000 0000000000000004 0000ffffe7f75c5c 0000000000000000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.217264] 7d20: 0000000000000000 0000000000000015 0000000000000124 0000000000000104 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.229088] 7d40: 0000000000000000 0000000000040d00 ffff80001e047df0 ffff0000080ad5c8 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.240881] 7d60: ffff000008c38000 000080002f370000 ffffffffffffffff 0000ffffabb4ac28 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.252632] 7d80: 0000000060000000 0000000000000000 0000000400000003 0000000000000000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.264416] 7da0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.276131] 7dc0: ffff800035e92880 ffff0000080ab3d8 ffff8000361c8028 ffff8000361c8028 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.287849] 7de0: 0000000000000000 0000000000040d00 0000000000000000 ffff000008082730 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.299526] 7e00: 0000000000000000 0000000000000000 ffffffffffffffff 0000000000000000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.311139] 7e20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.322688] 7e40: ffff80001e047e80 ffff0000080878c8 0000000000000000 ffff000008c38000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.334235] 7e60: 0000000000000000 0000000000000002 0000000000000000 0000000000040d00 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.345666] 7e80: 0000000000000000 ffff000008082730 0000000000000000 000080002f370000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.356955] 7ea0: ffffffffffffffff 0000ffffabc216c8 0000000000000000 0000000000040d00 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.368126] 7ec0: 00000000ffffffff 0000ffffe7f75c5c 0000000000000000 0000000000000000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.379147] 7ee0: 0000000000000000 0000ffffe7f75c5c 0000000000000000 0000000000000000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.390079] 7f00: 0000000000000104 6a6e7160fefeff0e 7f7f7f7f7f7f7f7f 0101010101010101 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.400988] 7f20: 0000000000000020 0000000080000000 0000000000000021 0000ffffabbf3588 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.411899] 7f40: 0000aaaac6bd7ae8 0000ffffabb4abfc 0000ffffe7f75d70 0000aaaac6bd7000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.422812] 7f60: 0000aaaac6bdaad8 0000000000000001 0000aaaac6bd7000 0000aaaac6bd7000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.433764] 7f80: 0000aaaaf4f5f7a0 0000000000000000 0000ffffe7f75c5c 0000aaaac6bd7000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.444651] 7fa0: 0000aaaac6bdac38 0000ffffe7f75bf0 0000aaaac6bba108 0000ffffe7f75bf0 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.455514] 7fc0: 0000ffffabb4ac28 0000000060000000 00000000ffffffff 0000000000000104 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.466397] 7fe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Message from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.614130] Code: 942244ae 37f800b6 91010280 940028f3 (f94037a0) Progress: [ 90%] [##########################################################################################################################################..............]
and out...
-
One time I was fast enough to enter the web-gui and add a ssh user (half way, because while applying the configuration connection was lost). And after a hard reset (taking off the power supply) I was even able to enter via ssh for half a second (before I was kicked/the host went down)
Quoting the readme.txt at the download location:
Code- OMV installation finalizes itself at first boot (network connection needed!) Please be patient since this can take up to 15 minutes. When done the board automatically reboots once and afterwards OMV is ready to be used
That's the simple reason you 'got kicked out', the system reboots one time automatically and is ready afterwards.
What you experienced later is either SD card crappiness or insufficient powering: https://forum.armbian.com/anno…other-people-experiences/
There's nothing OMV or Armbian can do for you since software is not able to run on isufficient hardware
-
Writing & Verifying the image (using etcher) to micro sd (5+)
IMPORTANT NOTE: Etcher on Linux was broken until yesterday. The one and only feature why everyone should use Etcher (verifying after writing and therefore spotting broken SD cards that corrupt data) never worked when running the Linux version.This has been fixed yesterday so everyone wanting to use Etcher on Linux has to upgrade now!
-
Quoting the readme.txt at the download location:
Code- OMV installation finalizes itself at first boot (network connection needed!) Please be patient since this can take up to 15 minutes. When done the board automatically reboots once and afterwards OMV is ready to be used
That's the simple reason you 'got kicked out', the system reboots one time automatically and is ready afterwards.
What you experienced later is either SD card crappiness or insufficient powering: https://forum.armbian.com/anno…other-people-experiences/
There's nothing OMV or Armbian can do for you since software is not able to run on isufficient hardware
I did let it settle down before. It was already after the first restart. The SD card crappiness should be not be part of my solution (real samsung evo(+) cards recently checked for corruption with f3write/f3read). As my power supply should be more than sufficent (5V,3000mA from xunglong himself!), but I also checked with a second power supply - just to be sure.
I running a bunch of SBC and I'm knowing the typical failures. But this here is non typical - for sure
IMPORTANT NOTE: Etcher on Linux was broken until yesterday. The one and only feature why everyone should use Etcher (verifying after writing and therefore spotting broken SD cards that corrupt data) never worked when running the Linux version.
This has been fixed yesterday so everyone wanting to use Etcher on Linux has to upgrade now!
But this one here could be the show stopper! I just downloaded the most recent version (1.2.1) and give the thing a new run. Stay tuned! -
This post will remain inaccessible for others until approved by a moderator.
So everything new from scratch. Now burned the sd card with the most recent etcher (1.2.1). There (still) where no errors when doing this.
This time I provided a 'lab'-network with only a router and my client to access OMV.
Still I have exactly the same failures and errors like observed before.
This time I could capture a Error while trying to log into the web gui of OMV:
Code
Alles anzeigenFailed to connect to socket: No such file or directory Error #0: exception 'OMV\Rpc\Exception' with message 'Failed to connect to socket: No such file or directory' in /usr/share/php/openmediavault/rpc/rpc.inc:140 Stack trace: #0 /var/www/openmediavault/rpc/session.inc(56): OMV\Rpc\Rpc::call('UserMgmt', 'authUser', Array, Array, 2, true) #1 [internal function]: OMVRpcServiceSession->login(Array, Array) #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array) #3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array) #4 /usr/share/php/openmediavault/rpc/proxy/json.inc(95): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3) #5 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle() #6 {main}
And once I was able to ssh to the device (interesting that the web gui lost connection exact like the last when applying the new user) I found out that the system-load was extremely high.
Bash
Alles anzeigen___ ____ _ ____ ____ ____ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) | _ \ / ___|___ \ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | |_) | | __) | | |_| | | | (_| | | | | (_| | __/ | __/| | | __/| |___ / __/ \___/|_| \__,_|_| |_|\__, |\___| |_| |_| |_| \____|_____| |___/ Welcome to ARMBIAN 5.35 user-built Debian GNU/Linux 8 (jessie) 4.13.10-sunxi64 System load: 8.01 7.48 4.73 Up time: 15 min Memory usage: 26 % of 994MB IP: 192.168.XXX.XXX CPU temp: 28°C Usage of /: 9% of 7.4G [ General system configuration: armbian-config ] New to Armbian? Check the documentation first: https://docs.armbian.com Could not chdir to home directory /home/su: No such file or directory
Even though after login the system went away seamlessly and I couldn't enter any command...
Does anyone know by chance what these messages mean?
BashMessage from syslogd@orangepipc2 at Oct 29 16:58:04 ... kernel:[ 305.614130] Code: 942244ae 37f800b6 91010280 940028f3 (f94037a0)
Maybe it's a hardware failure? -
Quoting the readme.txt at the download location:
Code- OMV installation finalizes itself at first boot (network connection needed!) Please be patient since this can take up to 15 minutes. When done the board automatically reboots once and afterwards OMV is ready to be used
That's the simple reason you 'got kicked out', the system reboots one time automatically and is ready afterwards.
What you experienced later is either SD card crappiness or insufficient powering: https://forum.armbian.com/anno…other-people-experiences/
There's nothing OMV or Armbian can do for you since software is not able to run on isufficient hardware
So I tracked it down even more (even though a little tricky). But I think the system does not reboot successful or doesn't finish it's automatic setup.If I put the newly written image into the system and directly try to access the webgui from omv it get's direclty deliverd. I don't log in and do nothing - just wait. Then after a while (20+ minutes) the system is gone from my network. Not accessible by web nor by IP. Looks like it's was falling out of the network - even though the green light on the board is on, so maybe the system is running.
Is there any way to see if the initial setup is complete from the content from the sd card? I wonder now if the first setup is running successful...
-
And the journey goes on.
This time I was able to catch a 'sudo armbianmonitor -u' before doing a 'sudo update' followed by a 'sudo upgrade' where the system freezes while downloading.
I just see a lot's of internal errors like this one:
Bash[ 17.716488] [0000000000000060] *pgd=0000000075694003, *pud=0000000074ea3003, *pmd=0000000000000000 [ 17.716497] Internal error: Oops: 96000006 [#1] SMP
and many more...
Can't tell what it is and why it's there... hardware fault?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!