Posts by MarcS

thanks for the link but this defeats this process seems to automatically unlock all drives after reboot.

That would defeat the whole purpose of drive encryption.

In my solution, there is a manual step, i.e. running of a shell script as root.

So I solved the problem. The issue was some confusion with the mount-points.

I have several LUKS encrypted disks which I decrypt after booting via a script but apparently that now doesn't work anymore after the OMV update. I have to manually decrypt the disks each by hand in the OMV GUI.

After doing that, the Docker path is visible again and docker works.

yes my docker storage path points to a disk that is now (surprisingly) empty. Something must have happened during the OMV upgrade...one disk is completely empty and that was the disk where my Docker path is pointing to.

Seems to be the same problem. I dont even want to re-install docker as I have so many containers up and running which took me weeks to configure. I fear they might all be gone if I re-install Docker.

Is there any one that can help on this Docker issue. Seems to be cause be a recent OMV update.

many thanks

I had Docker running nicely with Portainer and several live containers (Nginx, Nextcloud, Pihole).

After a recent OMV update I cannot get Docker up again. I am posting the output below. Maybe someone can help interpret this.

Journalctl -xe output:

A stop job for unit docker.service has finished.
--
-- The job identifier is 87250 and the job result is done.
Apr 19 21:56:41 pi3 systemd[1]: docker.service: Start request repeated too quickly.
Apr 19 21:56:41 pi3 systemd[1]: docker.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit docker.service has entered the 'failed' state with result 'exit-code'.
Apr 19 21:56:41 pi3 systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: A start job for unit docker.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit docker.service has finished with a failure.
--
-- The job identifier is 87250 and the job result is failed.
Apr 19 21:56:41 pi3 systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.

and the output of systemctl status...

root@pi3:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2021-04-19 22:01:13 BST; 16ms ago
Docs: https://docs.docker.com
Process: 11586 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=
Main PID: 11586 (code=exited, status=1/FAILURE)


Apr 19 22:01:13 pi3 systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Apr 19 22:01:13 pi3 systemd[1]: Stopped Docker Application Container Engine.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Start request repeated too quickly.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 19 22:01:13 pi3 systemd[1]: Failed to start Docker Application Container Engine.
root@pi3:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2021-04-19 22:01:13 BST; 50s ago
Docs: https://docs.docker.com
Process: 11586 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=
Main PID: 11586 (code=exited, status=1/FAILURE)


Apr 19 22:01:13 pi3 systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Apr 19 22:01:13 pi3 systemd[1]: Stopped Docker Application Container Engine.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Start request repeated too quickly.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 19 22:01:13 pi3 systemd[1]: Failed to start Docker Application Container Engine.

after a reboot it seems to have worked but docker is still not starting.

I will post a separate thread here re docker problem.

thanks

that command just runs and never stops.

I think the OMV update broke something else.

thanks - currently I see the below. Do I just type the data in clear text? How do I then restart the OMV engine so it takes effect?

<mount>

<uuid>d769a175-28d3-4046-9a37-eb31be79a77a</uuid>

<name>nfs2</name>

<mntentref>8e50a97c-1c2f-4b92-b417-dfca599360f0</mntentref>

<mounttype>nfs</mounttype>

<server>[IP]</server>

<sharename>[SHARENAME]</sharename>

<nfs4>0</nfs4>

<username></username>

<password></password>

<options>rsize=8192,wsize=8192,timeo=14,intr,nofail</options>

</mount>

Since today's update of OMV and Plugins, my Union Filesystem setup is not working anymore.

When trying to access the Pool, the error is

cd: '[Poolname]' : Transport endpoint is not connected.

My fstab looks like this:

proc            /proc           proc    defaults          0       0
PARTUUID=738a4d67-01  /boot           vfat    defaults          0       2
PARTUUID=738a4d67-02            /       ext4    noatime,nodiratime,errors=remount-ro 0 1
# /swap_file  swap  swap  defaults  0 0
# >>> [openmediavault]
/dev/disk/by-label/enc500NEW            /srv/dev-disk-by-label-enc500NEW        ext4    defaults,nofail,x-systemd.device-timeout=1,user_xattr,noexec,usrjquota=aquota.user,g$
/dev/disk/by-label/enc5N2               /srv/dev-disk-by-label-enc5N2   btrfs   defaults,nofail 0 2
/dev/disk/by-label/enc5N3               /srv/dev-disk-by-label-enc5N3   btrfs   defaults,nofail 0 2
/dev/disk/by-label/enc5N4               /srv/dev-disk-by-label-enc5N4   btrfs   defaults,nofail 0 2
/dev/disk/by-label/enc1T                /srv/dev-disk-by-label-enc1T    btrfs   defaults,nofail 0 2
/dev/disk/by-label/enc2TB               /srv/dev-disk-by-label-enc2TB   ext4    defaults,nofail,x-systemd.device-timeout=1,user_xattr,noexec,usrjquota=aquota.user,grpjquota$
/dev/disk/by-label/encKing240           /srv/dev-disk-by-label-encKing240       btrfs   defaults,nofail,ssd     0 2
/dev/disk/by-uuid/e3f54227-f3de-4f4f-bba6-ba24994fd1b1          /srv/dev-disk-by-uuid-e3f54227-f3de-4f4f-bba6-ba24994fd1b1      ext4    defaults,nofail,x-systemd.device-tim$
/dev/disk/by-label/hgst500              /srv/dev-disk-by-label-hgst500  btrfs   defaults,nofail 0 2/dev/disk/by-uuid/5e2a1221-90c5-4504-9375-65afd6c4a8cf          /srv/dev-disk-by-uuid-5e2a1221-90c5-4504-9375-65afd6c4a8cf      ext4    defaults,nofail,x-systemd.device-tim$
/srv/dev-disk-by-label-encKing240:/srv/dev-disk-by-label-enc5N3:/srv/dev-disk-by-label-enc500NEW:/srv/dev-disk-by-label-enc5N4:/srv/dev-disk-by-label-enc5N2            /srv$
192.168.1.102:/volume1/NNnfs2           /srv/d769a175-28d3-4046-9a37-eb31be79a77a       nfs     rsize=8192,wsize=8192,timeo=28,intr,nofail      0 0
# <<< [openmediavault]

I had a remote mount to a NFS share on another server setup and it worked well.

Now the other server failed and had to be re-built but now my OMV Remote Mount is failing. The Plugin screen just doesn't stop "Loading" until the web interface fails.

Where are username/password of the remote mount stored so I can amend them?

Will LUKS need the keyfiles after unlocking?

Scenario: I am running several HDs encrypted with LUKS. The OMV Plugin works well but any reboot results in a laborious manual unlocking exercise. So I decided to create a shell script to unlock all drives via keyfiles. Now it would be best to put the keyfiles onto a USB stick and only insert that during a reboot and remove once the server is running.

This of course only works if LUKS/OMV don't need the keyfiles after unlocking.

Is this so?

they are talking about an adapter

https://forum.thinkpads.com/viewtopic.php?t=130562

thank you. Yes, for Laptop. I have a MAcbook running Linux and a Lenovo X230. Not sure if those take the intel card.

I think the Lenovo needs an adaper to fit the card and the Macbook does not support it but I could be wrong.

Has anyone tried it?

Quote from mi-hol

Any cheap WiFi6 router (prices in Germany start at 35Euro) will do the trick if your client accessing the data has a WiFi6 card too

Sadly there are no WiFi6 USB cards available yet.

so has anyone compared the 2 options:

LUKS encrypted HD + ZFS on top

vs

ZFS encryption

- performance

- security

Quote from ryecoaaron

I don't know that there are any. Snapraid doesn't make a difference. Auto-unlock of LUKS might help. Maybe someday I will re-write the plugin to use systemd mount files but I don't want to do that and have it not work any better. LUKS needs to go away as an OMV option (I know LUKS works well - I use it at work a lot) in favor of a filesystem that offer encryption in one layer to avoid this double layer problem.

Doesn’t ZFS offer data at rest encryption now?

Quote from wepee

Hi everyone,

Happy new year!

I am just wondering, has anyone using this LSI 9212-4i card before?

I have completed flashed the card into Initiator Target (IT) mode with the apporpriate firmware +
also updated the latest bios on the card.

What is the maximum hard disk capacity, can card this support: 4TB or 8TB? I could not find any info. in Google.

Thank you.

2020-01-01_11-56-40.jpg

Display More

Sorry guys I have a silly question : this card has 2 internal SATA connectors. Is it still possible with the right cables to connect SAS drives internally with their full performance or does the controller only like SATA internally?

Hello- I have a mount problem.

One of my HDs disconnected temporarily. I fixed the cable and did an BTRFS check. The filesystem is OK (no errors) but OMV wont mount it.

OMV can see the disk and I see the entry under "OMV-filesystems" but the mount command just times out. Also from CLI the mount just hangs.

Can anyone help?

This is my FSTAB entry. The disk is LUKS encrypted and the unlock worked fine/

/dev/disk/by-label/EncExt3600GB /srv/dev-disk-by-label-EncExt3600GB btrfs defaults,nofail 0 2

Yes, I am using a docker container for NC, mainly for document sharing and the chat app "talk. All of that is extremely slow.

Quote from Soma

Also maybe you could see the error/access/php/ logs and see if there's mention to where/what might be the bottleneck.

What comes to mind immediately is "server reached pm.max_children"

And have you tried to see the output of this: https://scan.nextcloud.com/

The scan output shows A+, so no issues.

I cannot find error/access/logs . Do you know where this is located?

I think if you add your IP address to the field Domain it also works (with ACL verify ticked)