Posts by raulfg3

I use photoshow in a docker too, and for same reason ( respect folder structure)

probably not work, ZFS need to be same or great that ZFS used on BSD used by TrueNAS.

You need to know what version are used on both O.S. to be sure that can work.

https://www.reddit.com/r/zfs/c…ch_version_of_zfs_i_have/

Please post your steps to help other user to migrate if finally works for you.

I'm sorry, it's a forgetfulness on my part.

I mark this post SOLVED, and sorry again because of my mistake.

I notice in OMV6 that if you have a huge amount of disk, this do not appear in

Storage->S.M.A.R.T.->Scheduled Tasks to select it for test.

works for me on a NAS with 5 disk, do not work on a NAS with 14 Disk.

my 14 disk:

as you can see Disk-> SMART show disk and good state, but i can't add to run schedule test because i can't select it on drop menu.

Quote from jDoll

Hallo Forum,

installed the OMV-Extras by the install-script described on the github page. I also got a subitem within the webinterface which says: "omv-extras". But when clicking on it i only got a 404 with a "Software Failure Press left mouse button …" message. Any ideas?

Omv6 was post-installed on a Debian11.

wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash

works for me on several installations of OMV6 from ISO, not tested on post-installed on debian 11

Quote from ryecoaaron

. I could release the plugin with no interface but with the backend pretty easily.

Really good news for ZFS users.

you need to install ZFS plugin to use zpool & ZFS commands.

see my signature

Quote from batikiotis

i have HPE ProLiant ML310e Gen8 v2 Server. the HDDs are docked on slot 1 & 2 of the four provided. The connection is SATA.

i did some tests from HP insight diagnostics prior to boot in windows server 2019t. The test stated for a faulty probably HDD. It says that i need to format and/or replace the disk. The error code was F2.

ok, no doubt to replace disk in that case.

only a sugest, for better use of disk in ZFS & OMV, is better that internal controller are on IT mode, please read about IT mode on google.

Is because IT mode show disk to Base OS as SATA disk, and SMART works fine, if not disk are show as logical volumen that are not really good for ZFS.

how the disk are connected to your NAS? ( USB, SATA, etc..).

And please provide more info about your MOBO.

info provided until now indicate a defective disk, but not totally sure until a SMART test is passed.

PD: SMART test only works on SATA devices not on USB or simmilar, so please post more info

Quote from batikiotis

I know this is old but i would like to ask how to command in a shell if you only have openmediavault and gui?

use putty to connect by SSH to your NAS and you can use the shell.

you must first enable SSH service in OMV WebGUI.

Quote from batikiotis

where can i do the smart test? i can't do something from openmediavault.

from webGUI, revise your webGUI to find the SMART section

i gess too , but no garantee

identify disk: scsi-3600508b1001c708e7e846b76d45b51f0 and revise the SMART TEST, probably bad .

if the disk is in bad state, you need to replace the disk in the mirror as soon as possible.

PD: Revise SATA cables too, sometimes , the error is on the cable not in the disk, and unplug and replug the disk solve the problem.

Quote from STUKguy

one last question before i mark this post as resolvd when you are on the Portainer/Container list and you have the published ports section in the middle is there away to make the links actually work?

you need to go to enviroment -> Local.

and put the NAS IP on the public IP label:

MacVLAN mode assign the piholee docker a new virtual NIC, so:

ipv4_address: 192.168.68.115 must be the NEW ip for your pihole, I suggest to use 192.168.1.2 because 192.168.1.1 is the router in most homes.

mac_address: 00:12:90:90:19:09 is a ramdon MAC ( but be sure tat donot exist on your LAN) for this new virtual NIC

ip_range : put a range that cover your new iphole IP.

PD: Please readmy pihole [HOWTO] in my signature to better understand .

ok, tested today ,and patch 6.0-27 works, I confirm that BTRFS Filesystem survive upon reboots:

Thanks a lot for the efforts.

OMV6 is enought stable now, only problem is that not all pluggings are ported, but if you use dockers , is a good decission to use OMV6.

use macvlan to avoid bind problem.

this is my working stack on IP:192.168.1.3

# Note: 192.168.1.xxx is an example network, you must update all these to match your own.
version: "2.1"
services:
  adguard:
    container_name: adguard
    image: adguard/adguardhome:latest
    mac_address: 00:12:90:90:19:09           # <-- Update
    cap_add:
      - NET_ADMIN
    networks:
      macvlan_NET:                      # <-- MACVlan Name no need to change, but do not exist previosly.
        ipv4_address: 192.168.1.3       # <-- Update
    volumes:
      - /srv/dev-disk-by-label-DATA/Data/dockers/adguard/Work:/opt/adguardhome/work
      - /srv/dev-disk-by-label-DATA/Data/dockers/adguard:/opt/adguardhome/conf
    restart: unless-stopped

networks:
  macvlan_NET:
    driver: macvlan
    driver_opts:
      parent: enp3s4f0                       # <- Update to match your NIC see your OMV WebGUI
    ipam:
      config:
        - subnet: 192.168.1.0/24            # <-- Update
          gateway: 192.168.1.1              # <-- Update
          ip_range: 192.168.1.2/28          # <-- Update

Quote from votdev

It is planned to fully support BTRFS in OMV7.

Sorry know it, I hope that will be available on OMV6.

Perhaps when you have more time?

but at all, I thanks you for your work.

trick is no use pluggins because not all where ported to OMV5, and cause problem in upgrade if still alive in OMV4