Search Results

Search results 1-20 of 23.

  • OMV not accessible after a few days

    Frepke - - General

    Post

    Quote from tkaiser: “Hmm... no idea. Could be related to undervoltage (PSUs getting older) and without a serial console it's close to impossible to really get a clue what's going on. AFAIK on the XU4 you can not use those cheap $1 USB serial dongles from Aliexpress or eBay but need the official one from Hardkernel (due to different voltage levels -- but I might be wrong so better check Hardkernel's wiki for information) ” Okay, Thank you for your time/help anyways I think I do a fresh OMV-4 inst…

  • OMV not accessible after a few days

    Frepke - - General

    Post

    Quote from tkaiser: “Quote from Frepke: “RPi-Monitor was installed ” Well, you could now have a look whether there's high load on the system prior to it not being available any more. RPi-Monitor logs load and temperatures so it should give a clue whether a crash/freeze is related to high activity or to something else. But looking into logs especially /var/log/syslog (or providing them via pastebin.com) might be more interesting. ” Thanks tkaiser, Yesterday, 17:00u. the HC1 was accessible and wor…

  • OMV not accessible after a few days

    Frepke - - General

    Post

    Now my system wasn't accessible, couldn't ping also. RPi-Monitor was installed, what now

  • OMV not accessible after a few days

    Frepke - - General

    Post

    Quote from tkaiser: “Quote from Frepke: “armbianmonitor -r doesn't do anything ” Well, then if you want RPi-Monitor you need to follow the manual installation instructions you'll find on the net. ” RPi-Monitor is running, now we wait Armbianmonitor is also working again.

  • OMV not accessible after a few days

    Frepke - - General

    Post

    Quote from Frepke: “Quote from tkaiser: “Quote from Frepke: “I think I understand everything you wrote, except the sync option. Is this also in the fstab? ” Yep, but I forgot that the image you're using relies on btrfs for the rootfs so simply remove the commit=600 entry there and reboot after disabling folder2ram.Another possibility is to install RPi-Monitor to get a clue whether there is high load prior to the device becoming unavailable. On the ARM OMV images it's a simple 'armbianmonitor -r'…

  • OMV not accessible after a few days

    Frepke - - General

    Post

    Quote from tkaiser: “Quote from Frepke: “I think I understand everything you wrote, except the sync option. Is this also in the fstab? ” Yep, but I forgot that the image you're using relies on btrfs for the rootfs so simply remove the commit=600 entry there and reboot after disabling folder2ram. Another possibility is to install RPi-Monitor to get a clue whether there is high load prior to the device becoming unavailable. On the ARM OMV images it's a simple 'armbianmonitor -r' (details). But thi…

  • OMV not accessible after a few days

    Frepke - - General

    Post

    Quote from tkaiser: “Quote from DHGE: “look at the files in /var/log ” Useless on OMV installations with enabled flashmemory plugin Logs remain in RAM and with an unsafe shutdown everything is lost. @Frepke you need to execute /sbin/folder2ram once to get the options then disable folder2ram and check using 'df' prior and after. Then to really get something into the logs which might show a root cause you need to also edit /etc/fstab, remove the commit=600 option and use the sync option (check car…

  • OMV not accessible after a few days

    Frepke - - General

    Post

    Quote from DHGE: “look at the files in /var/log use mc for this if working via ssh you can also view the log files via the web gui but this is more time consuming IMO ” Thanks DHGE, I'll look into the log-files tonight. Is there something specific to look at, or is this too early to say?

  • OMV not accessible after a few days

    Frepke - - General

    Post

    Hello, I've OMV-4 (updated to the latest version) running on my Odroid HC1, but since a few weeks my system disappears from my network after a few days. I can no longer reach OMV's GUI and not by SSH. Unplug and replug the power-cord is the only option for me. Is there a way to find out what causes this problem? kr., Frepke

  • Call for testers: OMV4 for ARM boards

    Frepke - - General

    Post

    Quote from tkaiser: “@Frepke: I just created an OMV 4 image for Espressobin (untested). In case you want to give it a try: OMV_4_Espressobin.img.xz And Tinkerboard image (also untested) is uploading also: OMV_4_Tinkerboard.img.xz ” Thanks Thomas, That's very nice, unfortunately I sold my Espressobin and bought an HC1. The Espressobin wasn't stable enough for daily use, the HC1 runs without problems OMV4 for months now I tried to make an backup image/clone from the SD-card I currently use so I ca…

  • Docker GUI plugin now stable

    Frepke - - Plugins

    Post

    Quote from Frepke: “Quote from ryecoaaron: “Quote from Frepke: “What am I doing wrong? ” You are trying to use an x86/amd64 docker image on an arm board... This will not work and you must use arm images. ” Thanks ryecoaaron, I'm new on Docker, but how could I've missed that kr., Frepke ” Thanks guys for pointing me in the right direction. Now I've Plex running in a docker on my ESPRESSObin by pulling the following image "lsioarmhf/plex". Still a lot to learn but there's progress

  • Docker GUI plugin now stable

    Frepke - - Plugins

    Post

    Quote from ryecoaaron: “Quote from Frepke: “What am I doing wrong? ” You are trying to use an x86/amd64 docker image on an arm board... This will not work and you must use arm images. ” Thanks ryecoaaron, I'm new on Docker, but how could I've missed that kr., Frepke

  • Docker GUI plugin now stable

    Frepke - - Plugins

    Post

    Hello, I've enabled the Docker CE plugin in OMV4 and installed Docker. Installed the plex and emby image, but when I run those images and the container is running, the log is filled with errors standard_init_linux.go:195: exec user process caused "exec format error" What am I doing wrong? Try to run it on an ESPRESSObin (ARMBIAN 5.37.171231 nightly Debian GNU/Linux 9 (stretch) 4.4.107-mvebu64)

  • Quote from tkaiser: “Quote from Frepke: “have a couple of ERRORS ” Thank you for the report. Installation routine was buggy and I tried to fix it: github.com/armbian/config/comm…4a2ca78944a2e4683085f0238 So the best idea is to start over again but this time with Debian_stretch_default.7z (kernel 4.4), then replace the whole contents of /usr/sbin/softy with raw.githubusercontent.com/armbian/config/dev/softy and then try the installation again. Why switching from next branch to default? Since with…

  • Quote from tkaiser: “Quote from Frepke: “Is this also applicable to the Espressobin? ” Today I found my EspressoBin, loaded Armbian's Debian_stretch_next.7z image, installed it and let OMV being installed: Source Code (1 line)Took 15 minutes (pretty fast SD card) and now I'm at OMV 4.0.15-1. But not that impressed since with the settings currently active idle consumption with a sleeping disk is at 5.4W (that's 0.5W above ODROID HC2 with same disk connected and also sleeping). But hopefully DVFS …

  • Thanks, I'll ban Tapatalk Kr., Frepke

  • Quote from tkaiser: “@ryecoaaron kaiser-edv.de/tmp/NumpU8/ Source Code (7 lines)The Pine64 and SoPine images currently based on kernel 3.10.107 should be replaced since 3.10 is EOL now. Most probably the last ARM images since it makes no sense any more (since all the necessary performance tweaks are now understood and documented and part of armbian-config). In a few weeks there will be a new major Armbian release available and then it's just downloading Jessie or Stretch Armbian images, running …

  • Quote from tkaiser: “Quote from Frepke: “I'm curious about the performance of the EspressoBin running OMV ” Read performance is excellent, write performance not that great but yet reasons unknown. I did not play with EspressoBin for a while since it seems we lack vendor support (GlobalScale / Marvell). You might want to check the last pages of this thread: forum.armbian.com/index.php?/t…port-development-efforts/ ” Okay thanks tkaiser, Then there's only one option for me... ...waiting Verzonden v…

  • Quote from tkaiser: “@ryecoaaron May I ask to replace all 'other arm images'? At Armbian we investigated about BTRFS (resizing, compression, performance, swap vs. zram) and here we go: kaiser-edv.de/tmp/NumpU8/ (Hidden Content)Currently Pine64/SoPine images will disappear but that's good since we're close to getting mainline kernel support for these devices. Other interesting devices (ROCK64, EspressoBin and others) will follow soon, same with some ODROID images (kernel updates applied, some u-b…

  • Quote from tkaiser: “Quote from Frepke: “I hope there's a stable build available soon, but in the mean time I follow the Armbian forum. ” Here you go: OMV_3_0_86_Espressobin_4.4.79.7z But I wouldn't call this stable atm -- quite the opposite to be honest. Starting with this release no SSH login as root is possible by default so you have to login through the web UI first, access the SSH service and allow root login. I already talked to @ryecoaaron about a mandatory password change on first login …