Posts by vcp_ai

YES to both questions

Just two minor errors (From all versions). Hope can be easily corrected on OMV 5.x...

-On Mail SMPTport you put as example .....25 o 578. Should be .... 25 o 587 ??

.On every week day list (Crons and similars) 5th day says Miercoles and should be Viernes

Regards

@shazster
curl is installed on mi line #4
The shared folder is created , from OMV, as any other shared folder of the system. In my case is a ZFS fileSystem (does not have a limit on its size). Actually, after one month, is using 490MB..

The install script is downloaded and run from root account (step #7). it makes all the job. Docker UI is not used.

Dockeu UI is only used to test tthat all containers are installed and running....

This is a copy of my steps:
The are executed in an OMV Shell .

### create workspace for hassio
# mkdir /sharedfolders
# mkdir /sharedfolders/hassio
#apt-get install apt-transport-https  ca-certificates  curl gnupg-agent software-properties-common 
#apt-get install apparmor-utils   apt-transport-https    avahi-daemon    ca-certificates    curl    dbus    jq     socat  software-properties-common   network-manager


# curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | bash -s --  -d "/sharedfolders/hassio"


### Instalation take some time as most of packages(container) are installed after....

HI, I've just got it working on OMV 4.1, following the instructions on https://www.home-assistant.io/hassio/installation/ (last steps, general install on UBUNTU).

Steps I've done are in the attached text file forum.openmediavault.org/wsc/index.php?attachment/14215/,

Also attached a copy of the result working dockercontainers.
Docker Images Created.jpgDocker runing containers.jpg
Home assistant is accesed via: http://OMV_IP:8123


Tested add-ons (MQTT, SSH, Config) are installed as usual and they work ...

Regards

@grusu
Finally I've got it to work using your suggestion.
I tested this before, without success. It seems that mount point /srv/dev-disk-by.... should be empty for owncloud to use it.

After starting a new installation, it worked as expected.

Thanks again

I have that working. Mounted as /ownclouddata

What I need is a way to tell owncloud to use thata mount for its data.....

Thanks Mike.

Not sure if I can understand what you say...

From inside OMV shell, I can see docker(Owncloud) data nder /var/lib/docker/volumes.
-that means that owncloud data is filling mi OMV main disk.

I've shared (from OMV) another disk/filesystem and passed it to docker mount as /ownclouddata
- from inside docker shell I can access this mountpoint and write to it.

From inside docker shell on /var/www/html I only have index.html

Regards

HI, I've installed owncloud under docker using the 'official source' :
https://hub.docker.com/r/owncloud/server/
It works as expected, but I've not been able to use a OMV shared folder as a storage path for owncloud.

All data seems to be in (omv path) /var/lib/docker/volumes

I've passed a shared folder to the container and mount it as /ownclouddata and it is there, but I can not find the way to say owncloud to use that mountpoint for its data.

Can anybody point me how to change it ??

Regards

Do not know about services way. Have you tested it ?

/etc/rc.local solution works. Mine:

#!/bin/sh -e
##send an email when system starts
/root/emailarranque
# Change level
/root/changelevelkeyb.sh
#exit 0

As it does not exist, remember to make it executable ( chmod +x /etc/rc.local )

Quote from richprim

........ each time i typed a letter it would output a line of code.

I also have this behavior, and seems is related to debug level of keyboard. Yo can find more info here:
https://forum.pine64.org/archive/index.php?thread-6121.html

As a resume, you must reduce keyboard log level from 7 to 4 by isuing :
echo 4 > /proc/sys/kernel/printk

This will make problem dissapear , until a new reboot.....

You can add this command to /etc.rc.local to be executed on every reboot.

Quote from test011a

I am not trying to use 0.6.57, but I am just worrying about the faulty hardware (various dots all over the screen may mean screen memory is overwritten by bug or may be a hardware failure) Is this normal output with 0.6.57 pre-release?

I had similar 'screen symptoms' with 0.6.57 ...

HI,
I have rock64 2GB board.
I´m using stretch-openmediavault-rock64-0.6.44-239-armhf.img.xz image. It installed omv 4.xx
It works, and I've succesfully updated via GUI to 4.1.8.2-1

I've not tested any more....

Sorry for the late reply....

I also spent three days testing Beta versions (0.6.57) and omv image does not work.
I tested stretch-minimal-rock64-0.6.57-270-arm64.img and it worked...
Then I realized that I was using a Pre-release version, and I scroll down the page until found First STABLE Version 0.6.44 and it works.

Now waiting to have spare time for real tests....

Quote from ryecoaaron

The 4.1.7 version of omv-extras has buttons to hold/unhold the current kernel/headers (linux-image-$arch and linux-headers-$arch) and disable/enable the backports repo.

How can I know if current kernel is in Hold status or not ?
Ther is no visual indication on GUI.

May be you can disable the button that is not applied. I.E:
- If kernel is in hold status, only Unhold button is enabled, and opposite...
Regards

@ryecoaaron
Thanks, In my case, marking 4.14 as default, and rebooting, worked. Everything is there...

Quote from ryecoaaron

You might run into issue if you upgrade other packages that use a compiled kernel module though.

Not sure what you state here. Can you give some example of what I should not have to do/upgrade ?

HI, I've installed 4.16 (I'm using ZFS). I've just seen this post.
Fortunately I've not rebooted the system, and I' m still running 4.14.

Can anybody point me how to 'downgrade' to 4.14 ?

Regards

Just to be sure, I've just performed following tests:

I have a test OMV 4.1. running on a 8GB SATA SDD.
I've 'clonezilled' it to a 16GB SSD conected with a USB to SATA adapter.
I've connected this USB to SATA + SSD to a DL380-G7
And it started/worked with no problem.

Quote from blindguy

Yes I installed to one of the 8 hard drives and that is fine. I event tried using clonezilla and cloning a working copy and then put it on a SSD connected via USB and that failed to boot as well.

That probably shoul not work due to the overhead that Proliant Raid Cards introduces in partitioning schema.

Iwould recommend install OMV to USB on a standard PC and then use this USB on Proliant (I´ve done that with a Debian netinstall distribution).

Quote from blindguy

I am trying to install the OMV OS onto a USB device. I am using the iLO and that allows me to select a image file and use it as a boot device. So I boot using the OMV and I am able to install OMV and it gets all the way to the end of the installer and then complains about GRUB and asks me to chose which device to install GRUB, I select the device and it appears to work fine but then after reboot I get to the grub rescuse screen and can't boot.

Yes I installed to one of the 8 hard drives and that is fine. I event tried using clonezilla and cloning a working copy and then put it on a SSD connected via USB and that failed to boot as well.

Any assistance is appreciated. Thanks in advance.

Display More

I've had that problem sometime ago, and as far as I can remember it pointed to a problem with grub, that was installing to a wrong drive.
May be you are install from an USB (iso with OMV) to another USB ?
If so , I would recommend to use another media for the OMV-ISO (CD/DVD) and test.