Beiträge von kentish

Zitat von gderf

When I upgraded ny OMV from 4 to 5 it kept deleting the /etc/resolv.conf file which broke DNS resolution. Check that file on your machine and see what's inside it. If it's empty or missing try populating it like this and see what happens:

Code

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 8.8.8.8
nameserver 4.2.2.2
nameserver 1.1.1.1
search localdomain

Alles anzeigen

Eventually after some system updates I stopped having problems, and I am unsure whether this file is even needed anymore. On my machine it exists as a symbolic link to /run/systemd/resolve/resolv.conf

Sorry to jump in on a thread - wanted to say thanks as this fixed my issue

Morning or Afternoon All

I'm looking for a bit of advice on my next upgrade as I'm not sure on the amount of hardware resources I'll need. Bit of background, been using OMV since release and the forum helped me with the last hardware purchases six years ago The NAS has been pretty much rock solid apart from a few user errors on my part, which we won't go into!!

My employer has told me I'll be working from home from the forthcoming year and I'll like to change my NAS from just being a Filestore / Media Server and a Minecraft server for the kids into a host for a couple of VM's. As I need to try and separate work from personal life and I'm hoping if I can leave work stuff on the VM I can shut it down and walk away - fingers crossed. At the moment I'm using my gaming PC as a workstation, so I tend to look at my emails and work stuff when I shouldn't it's a bad habit!!!

My current set up is

• Fractal Design R3 Case
• Intel i3-4130 @ 3.40GHz
• OMV 5.5.3-1
• RAM: 4 Gig
• ASRock Z87 PRO3
• Storage: SnapRaid
  
  • 3 x 2tb (2 Data and 1 Parity)
  • 3 x 3tb (2 Data and 1 Parity)
• Wired Gigabit Network

The NAS streams DVD, BluRay, 4k and Music content to Samsung TV's and PC's around the house and runs the following dockers

Docker

1. Minecraft Bedrock - 4 users
2. Minecraft Java - 4 users
3. Sonarr
4. NZBGet
5. Heimdell
6. Emby

Would like add two VM to this, which I'll remote desktop into from a Windows 10 PC.

Virtual Machines

1. Windows 10 - Skype, Office and general work stuff
2. Linux Mint - Development box - help me to learn some additional tech skills

So finally the questions

• As the Motherboard and CPU is quite old, is it really worth attempting to upgrade
• Should I go for a new Motherboard, CPU and RAM - budget about £100 to £200
  
  • Local PC shop has this AMD Ryzen 3 3200G 3.6GHz +8GB HyperX DDR4 Memory for £179.99 , feels bit over powered but I'm bit out of touch of specs I need for the NAS.

Cheers for any advice

Kentish

Zitat von crashtest

Good. That's what I was looking for. The extra space on your boot drive is a good location for Dockers and other utility purposes. Docker containers do not like being stored on the fused mount point of mergerfs.

Splendid, glad I'm on the right track

The boot drive is 240 Gig SSD, which I've partitioned into 40G for OpediaMediaVault and 200G for Applications - basically all of the config file for docker. I do plan to switch this back to separate drives in the future but as I only had the SSD available it will make do.

Currently running the following dockers :-

• Minecraft - 3 LAN users
• Sonarr
• Emby
• Heimdall & Organizr- finding out which one i like most
• NZBGet

Zitat von crashtest

While UnionFS and SNAPRAID can be added at any time, a formatted and mounted filesystem is assumed.

OMV configures in a layered approach:
- 1 add physical drives
- 2 format
- 3 mount
_____________________________
- 4 add-on's can be done at this stage such as UnionFS and / or SNAPRAID
____________________________
- 5 shared folders
- 6 CIF/SMB network shares
etc....

When deconfiguring, the above needs to be done in reverse order.

In essence, I would undo the UnionFS fuse mount point (as in delete the UnionFS config) before wiping drives and formatting drives.
It would make sense to do the same with SNAPRAID - delete the configuration (while keeping track of which drives you're using for Parity).

Alles anzeigen

Thanks, I suspect that at some point I did these things out of order!

Still it's a learning curve and I'm copying data back and creating the docker containers! My son is asking for a minecraft one, so at least I can do that now.

So update, thought I'd try and take the install back to as close to fresh as I could.. checking the plugins I noticed that I'd installed diskstats 5.0.2.1, so uninstalled that and tried the process again. This time everything completed with out error!

I now have a working 5.2-1.1 install

Hmmm, so wiping the drives generated this error...

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run collectd 2>&1' with exit code '1': debian:
    Data failed to compile:
----------
    Rendering SLS 'base:omv.deploy.collectd.plugins.disk' failed: Problem running salt function in Jinja template: A valid link was not specified.; line 54


---
[...]
  {% if salt['mount.is_mounted'](mountpoint.dir) %}
    {% set parent_device_file = salt['omv_utils.get_fs_parent_device_file'](mountpoint.fsname) %}
    {% if parent_device_file %}
      # Get the canonical device file to extract the device name. The collectd disk
      # plugin wants this format: https://collectd.org/wiki/index.php/Plugin:Disk
      {% set canonical_parent_device_file = salt['file.readlink'](parent_device_file, True) %}    <======================
      # Extract the device name from '/dev/xxx'.
      {% set _ = disks.append(canonical_parent_device_file[5:]) %}
    {% endif %}
  {% endif %}
{% endfor %}
[...]
--- in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(60): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusw6...', '/tmp/bgoutputLZ...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Interestingly reverting still allows the drive to be mounted and mergeFS to be created but then fails when you have to revert

Error #0:
OMV\Config\DatabaseException: Failed to execute XPath query '/config/services/unionfilesystems/filesystem[uuid='c76b3d70-c8e9-42a6-a50c-a47f7abe77e0']'. in /usr/share/php/openmediavault/config/database.inc:78
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/unionfilesystems.inc(166): OMV\Config\Database->get('conf.service.un...', 'c76b3d70-c8e9-4...')
#1 [internal function]: OMV\Engined\Rpc\UnionFilesystems->get(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('get', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('UnionFilesystem...', 'get', Array, Array, 1)
#5 {main}

So I think, it's time to drag the server from out under the stars and start again....

Zitat von crashtest

Go with EXT4.

That's a typo, meant EXT4.. too quick on the submit button

Zitat von crashtest

SNAPRAID and MergerFS (know as the UnionFS plugin) can be applied with data on storage drives, and in any order. (But it does make sense to cleanly format parity drives and use EXT4 as the file format.) Similarly, you can back out of either one and not lose any data.

Since OMV5 and it's plugins are works in progress, perhaps you might consider OMV4.
The data on your drives can stay in place, but you'll have to setup the UnionFS plugin again, and setup SNAPRAID again, being careful to reuse the correct drives for parity, so that you don't overwrite your data.

With that setup, you can reconnect to your data when setting up shared folders.

Thanks that's good to know...

I'll wipe the drives and try EXT3 rather than the current XFS and see what happens!.

If this doesn't do the trick then I think it's time to redo with OMV 4, still learnt a fair bit on this build, mainly around using cockpit and portainer.

Zitat von geaves

Sorry no, based upon the error output I'm still using OMV4, did you wipe the drives before trying MergerFS

I just purged the SNAP Raid data, didn't actually try that but can do and see if that works?

Just looked and the FSTAB and it seems that the mergeFS has created an entry

# >>> [openmediavault]
/dev/disk/by-label/Applications         /srv/dev-disk-by-label-Applications    e                                                                                                                  xt4     defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota                                                                                                                  .group,jqfmt=vfsv0,acl  0 2
/dev/disk/by-label/Data01               /srv/dev-disk-by-label-Data01   xfs    d                                                                                                                  efaults,nofail,noexec,usrquota,grpquota,inode64 0 2
/dev/disk/by-label/Data02               /srv/dev-disk-by-label-Data02   xfs    d                                                                                                                  efaults,nofail,noexec,usrquota,grpquota,inode64 0 2
/dev/disk/by-label/Data03               /srv/dev-disk-by-label-Data03   xfs    d                                                                                                                  efaults,nofail,noexec,usrquota,grpquota,inode64 0 2
/dev/disk/by-label/Data05               /srv/dev-disk-by-label-Data05   xfs    d                                                                                                                  efaults,nofail,noexec,usrquota,grpquota,inode64 0 2
/dev/disk/by-label/Data04               /srv/dev-disk-by-label-Data04   xfs    d                                                                                                                  efaults,nofail,noexec,usrquota,grpquota,inode64 0 2
/dev/disk/by-label/Data06               /srv/dev-disk-by-label-Data06   xfs    d                                                                                                                  efaults,nofail,noexec,usrquota,grpquota,inode64 0 2
/srv/dev-disk-by-label-Data01:/srv/dev-disk-by-label-Data02:/srv/dev-disk-by-lab                                                                                                                  el-Data04:/srv/dev-disk-by-label-Data05         /srv/8ba16f15-49a3-44d1-809e-6ff                                                                                                                  3cab5cbe7       fuse.mergerfs   defaults,allow_other,direct_io,use_ino,category.                                                                                                                  create=epmfs,minfreespace=4G,x-systemd.requires=/srv/dev-disk-by-label-Data01,x-                                                                                                                  systemd.requires=/srv/dev-disk-by-label-Data02,x-systemd.requires=/srv/dev-disk-                                                                                                                  by-label-Data04,x-systemd.requires=/srv/dev-disk-by-label-Data05        0 0
# <<< [openmediavault]

running mount-a gives me a non-empty error

mount -a
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option

not sure if I should try and and use the nonempty or specifically try an mount the fuse entry - just not sure on the syntax

So a little bit delayed bu the festival spirit...

Tried the following and still no joy!

• Removed SNAP Raid
• Deleted SNAP Raid data from the drives
• Uninstalled UnionFS/MergeFS
• Rebooted
• Reinstalled MergeFS

Added four of the six drives to the merge, the other two are going to be parity drives...get this error

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run collectd 2>&1' with exit code '1': debian:
    Data failed to compile:
----------
    Rendering SLS 'base:omv.deploy.collectd.plugins.disk' failed: Problem running salt function in Jinja template: A valid link was not specified.; line 54


---
[...]
  {% if salt['mount.is_mounted'](mountpoint.dir) %}
    {% set parent_device_file = salt['omv_utils.get_fs_parent_device_file'](mountpoint.fsname) %}
    {% if parent_device_file %}
      # Get the canonical device file to extract the device name. The collectd disk
      # plugin wants this format: https://collectd.org/wiki/index.php/Plugin:Disk
      {% set canonical_parent_device_file = salt['file.readlink'](parent_device_file, True) %}    <======================
      # Extract the device name from '/dev/xxx'.
      {% set _ = disks.append(canonical_parent_device_file[5:]) %}
    {% endif %}
  {% endif %}
{% endfor %}
[...]
--- in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(60): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusjQ...', '/tmp/bgoutputkF...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Any one got any ideas?

Ideally I want the data drives to be available as a single location that I can then use to store all the media on

Zitat von geaves

my understanding having set this up a few months back, MergerFS then SnapRaid not the other way round

Thanks, I'll back up the little bit of data that on the snapraid and then try again.

Morning from the UK

Just done a fresh install of OMV 5 on the NAS, previously been running OMV 3 and felt I should really clean the NAS and start a fresh as was moving all services into Docker containers. Everything has been going smoothly apart from setting up the MergeFS and this could (is?) my fault as I might of done it out of order, so to speak.

OMV is running on 256 SSD which has been partitioned into two OS and Applications then I have 3 x 2TB and 3 x 3TB Western Digital Red. The data drives are formatted as XFS.

So far I have SNAP Raid set up

All well so far, so I sync and scrubbed the SNAPRaid and then created the MergeFS using just the Data drives 01,02, 04 and 05

Here's the error message MergeFSError.txt

and the output of fstab fstab.txt

and of BLKID blikid.txt

When I try and edit the MergeFS, i get this error

Error #0:
OMV\Config\DatabaseException: Failed to execute XPath query '/config/services/unionfilesystems/filesystem[uuid='0ed06412-2810-4472-8dbd-195cda91af69']'. in /usr/share/php/openmediavault/config/database.inc:78
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/unionfilesystems.inc(166): OMV\Config\Database->get('conf.service.un...', '0ed06412-2810-4...')
#1 [internal function]: OMV\Engined\Rpc\UnionFilesystems->get(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('get', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('UnionFilesystem...', 'get', Array, Array, 1)
#5 {main}

What the best course of action here?

Should I have installed OMV 4 instead?

Did I make a mistake by setting up MergeFS on a non-empty SNAPRaid drive?

Should reboot the NAS?

Any advice will be warmly received, thanks.

Kentish

Zitat von nicjo814

If you want DLNA or similar services you should have a look at using the macvlan network driver in docker. It allows you to give a container its own ip. Support for macvlan should be coming "soon" to the docker plug-in.

Swapping the docker to host mode resolved the DLNA issue but I am interested in looking a Macvlan. I'd also consider just installing emby via apt-get but it's working now so have to resist the temptation to mess as I'll only break it

Zitat von hoppel118

25k in two weeks? Crazy, seemingly I am in the wrong job.

Greetings

me too ....

Yes I thought it was a security thing and for some reason I forgot that you could use symlinks to link to the binaries

That would be nice as I had some issues with emby in docker, DLNA only works in host mode and for some reason I can't seem to access it outside my lan. Saying that I'm not hijacking an old thread and asking for help just passing comment

Hi

I've had a similar issue and posted it on the Emby Forums, seems that Emby has a local copy of ffmpeg which needs suitable permissions to execute. If you have put the /config folder on a OMV Share then this execution is denied as the FSTAB record is set to NOEXEC.

Does that make sense?

I have an separate SSD which holds docker and all the application data, so just remove noexec from the fstab entry for that drive.

sorry about the delay, I had to go back through my history and i got it wrong.

try installing ncmpc

sudo apt-get update
sudo apt-get install ncmpc

how are you getting on, is working how you expected?

Have you added the folder and run a database up date. There is a mpd client that you can run from the terminal which is handy to check things are working.

Try apt-cache search mpd | grep client

As I forgotten it's name!

Sent from my SM-G935F using Tapatalk

Think that mpd will do that fine.

Hope it goes well

Sent from my SM-G935F using Tapatalk