Posts by raulfg3

    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 - | bash

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

    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

    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.

    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: must be the NEW ip for your pihole, I suggest to use because 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 .

    use macvlan to avoid bind problem.

    this is my working stack on IP: