Posts by vatoDETH

  • openmediavault 7 installation - network autoconfiguration failed - an error occurred and the network configuration process has been aborted

    I ran the omv-upgrade command:



    Is everything good with the output?

  • openmediavault 7 installation - network autoconfiguration failed - an error occurred and the network configuration process has been aborted

    I see the sources on the Debian site (https://wiki.debian.org/SourcesList):


  • openmediavault 7 installation - network autoconfiguration failed - an error occurred and the network configuration process has been aborted

    Ran the command:

    Code
    grep -r sandworm /etc/apt/*



    Output is below:

    Code
    =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2025.03.16 12:56:48 =~=~=~=~=~=~=~=~=~=~=~=
[7mgrep -r sandworm /etc/apt/*[27m
[C[C[C[C[C[C[C[C[C[C[C[C[C[Cgrep -r sandworm /etc/apt/*
[?2004l
/etc/apt/sources.list.d/openmediavault.list:deb [signed-by=/usr/share/keyrings/openmediavault-archive-keyring.gpg] http://packages.openmediavault.org/public/ sandworm main
/etc/apt/sources.list.d/openmediavault.list:deb [signed-by=/usr/share/keyrings/openmediavault-archive-keyring.gpg] https://openmediavault.github.io/packages/ sandworm main
/etc/apt/sources.list.d/openmediavault.list:# deb [signed-by=/usr/share/keyrings/openmediavault-archive-keyring.gpg] http://downloads.sourceforge.net/project/openmediavault/packages/ sandworm main
[?2004hroot@nas02:~#

  • openmediavault 7 installation - network autoconfiguration failed - an error occurred and the network configuration process has been aborted

    Sorry, I did not know what a Code Box is. Thank you for showing me.


    Here is the output in Code Box:

  • openmediavault 7 installation - network autoconfiguration failed - an error occurred and the network configuration process has been aborted

    =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2025.03.15 15:00:03 =~=~=~=~=~=~=~=~=~=~=~=

    [7mdpkg -l | grep openme[27m

    [C[C[C[C[C[C[C[C[C[C[C[C[C[Cdpkg -l | grep openme

    [?2004l

    ii openmediavault 7.7.1-3 all openmediavault - The open network attached storage solution

    ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive


    [?2004hroot@nas02:~# [7mgrep -r bullseye /etc/apt/*[27m

    [C[C[C[C[C[C[C[C[C[C[C[C[C[Cgrep -r bullseye /etc/apt/*

    [?2004l

    /etc/apt/sources.list:deb http://deb.debian.org/debian/ bullseye main

    /etc/apt/sources.list:deb-src http://deb.debian.org/debian/ bullseye main

    /etc/apt/sources.list:# bullseye-updates, to get updates before a point release is made;

    /etc/apt/sources.list:deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free

    /etc/apt/sources.list:deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free


    [?2004hroot@nas02:~# [7mgrep -r bookworm /etc/apt/*[27m

    [C[C[C[C[C[C[C[C[C[C[C[C[C[Cgrep -r bookworm /etc/apt/*

    [?2004l

    /etc/apt/listchanges.conf.d/95openmediavault.conf:# https://manpages.debian.org/bo…apt-listchanges.1.en.html

    /etc/apt/preferences.d/openmediavault-kernel-backports.pref:Pin: release n=bookworm-backports

    /etc/apt/preferences.d/openmediavault-kernel-backports.pref:Pin: release n=bookworm-backports

    /etc/apt/preferences.d/openmediavault-kernel-backports.pref:Pin: release n=bookworm-backports

    /etc/apt/preferences.d/openmediavault-kernel-backports.pref:Pin: release n=bookworm-backports

    /etc/apt/sources.list.d/openmediavault-kernel-backports.list:deb [signed-by=/usr/share/keyrings/debian-archive-bookworm-automatic.gpg] http://httpredir.debian.org/debian bookworm-backports main contrib non-free non-free-firmware

    /etc/apt/sources.list.d/openmediavault-os-security.list:deb [signed-by=/usr/share/keyrings/debian-archive-bookworm-security-automatic.gpg] http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

    /etc/apt/sources.list.d/openmediavault-os-security.list:deb-src [signed-by=/usr/share/keyrings/debian-archive-bookworm-security-automatic.gpg] http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware


    [?2004hroot@nas02:~# [7mcat /etc/os-release[27m

    [C[C[C[C[C[C[C[C[C[C[C[C[C[Ccat /etc/os-release

    [?2004l

    PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"

    NAME="Debian GNU/Linux"

    VERSION_ID="12"

    VERSION="12 (bookworm)"

    VERSION_CODENAME=bookworm

    ID=debian

    HOME_URL="https://www.debian.org/"

    SUPPORT_URL="https://www.debian.org/support"

    BUG_REPORT_URL="https://bugs.debian.org/"


    [?2004hroot@nas02:~# [7muname -a[27muname -a

    [?2004l

    Linux nas02 6.12.12+bpo-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.12-1~bpo12+1 (2025-02-23) x86_64 GNU/Linux

    [?2004hroot@nas02:~#

  • openmediavault 7 installation - network autoconfiguration failed - an error occurred and the network configuration process has been aborted

    I ran omv-salt deploy run apt.


    The output pertaining to the sources.list is below:

    ----------

    ID: remove_cdrom_apt_sources_list

    Function: file.line

    Name: /etc/apt/sources.list

    Result: True

    Comment: No changes needed to be made

    Started: 12:20:50.102044

    Duration: 1.556 ms

    Changes:

    ----------


    Running the command did not change the data in the sources.list file.


    I see Bullseye was the previous release of Debian and Bookworm is the latest release. Do I just need to change the sources to one for Bookworm?

  • openmediavault 7 installation - network autoconfiguration failed - an error occurred and the network configuration process has been aborted

    I downloaded the Latest Stable Re;ease of OMV7 and it did not work properly on my Dell T710. I had to use omv-firstaid to configure the NICs afterwards. It worked after I did this.


    My other NAS is an older OMV box is running 6.9.16-1 (Shaitan). This is where I copied the sources from. The updates and plug-ins are working.


    If there are new repositories, what are their names? If you can provide the "/etc/apt/sources.list" it would be appreciated.


    Thank You

  • Robocopy from OMV to OMV - Working Command

    I could not Robocopy, experiencing the commonly reported security errors when I ran the command:


    robocopy \\<sourceserver>\<sourceshare> \\<targetserver>\<targetshare> /ETA /MIR /ZB /MT:25 /COPYALL /SECFIX /R:1 /W:1 /log+:c:\FileCOPY.log

    Source: https://portal.nutanix.com/pag…ion-example-robocopy.html


    I have used this command in many successful migrations but it reported security issues on the destination side.



    The issue was researched. Others had success with running /copy:DATSOU and /copy:DAT.


    I eventually ended up using /SEC and /SECFIX. /SEC copies files with the security equivalent of /copy:DATS.

    Reference: https://learn.microsoft.com/en…windows-commands/robocopy



    The command I eventually used successfully is:

    robocopy \\nas01\share\documents \\nas02\share\documents /ETA /MIR /ZB /MT:128 /SEC /SECFIX /R:1 /W:1 /log+:"c:\RoboCopyLogs\documents.log"


    I suspect there are issues with NTFS permissions on 2 different boxes. They can not match, since they are not on the same domain like an Active Directory scenario. If you have specific permissions that need to be carried over, you can manually reapply them to the destination after the file migration.

  • openmediavault 7 installation - network autoconfiguration failed - an error occurred and the network configuration process has been aborted

    I ran an openmediavault 7 installation on a Dell T710.


    Experienced a "network autoconfiguration failed" error during the installation. Configured a static IP, but encountered "an error occurred and the network configuration process has been aborted" later on in the process. Repositories could not be assigned without network access.


    I read in articles to run omv-firstaid in terminal. This allowed me to resolve the network issue.


    The next issue was configuring the Repository Sources. I was able to copy them on my other OMV box to new one. The repositories are in sources.list at "nano /etc/apt/sources.list".



    All of the text for my Repository Sources is listed below if anyone needs it:


    # deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Official Snapshot amd64 LIVE/INSTALL Binary 20230724-12:07]/ bullseye contrib main non-free


    #deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Official Snapshot amd64 LIVE/INSTALL Binary 20230724-12:07]/ bullseye contrib main non-free


    deb http://deb.debian.org/debian/ bullseye main

    deb-src http://deb.debian.org/debian/ bullseye main



    # bullseye-updates, to get updates before a point release is made;

    # see https://www.debian.org/doc/man…ml#_updates_and_backports

    deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free

    deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free


    # This system was installed using small removable media

    # (e.g. netinst, live or single CD). The matching "deb cdrom"

    # entries were disabled at the end of the installation process.

    # For information about how to configure apt package sources,

    # see the sources.list(5) manual.

  • Scan to Folder Stopped Working - How to enable SMB1

    I have daily cloud backups so I am not super concerned about security (aka crypto). A future side project might be a Tunrkey Linux VM (small footprint) to exclusively for a scan folder then I can revert these changes on my main NAS.


    Open Source Support has been great, as always! Thanks again so very much!

  • Scan to Folder Stopped Working - How to enable SMB1

    Instructional for configuring SMB1
    It is working now with the following steps detailed below.


    *******************************
    STEP 1: Reviewed configuration using CLI


    Command 1:
    testparm -s -v | grep protocol


    Output 1:
    client ipc max protocol = default
    client ipc min protocol = default
    client max protocol = default
    client min protocol = CORE
    server max protocol = SMB3
    server min protocol = LANMAN1



    Command 2:
    testparm -s -v | grep ntlm


    Output 2:
    ntlm auth = No



    *******************************
    Step 2: Modified the configuration under SMB/CIFS> Settings> Extra Options


    client min protocol = NT1
    ntlm auth = yes



    Misstep:
    I originally tried SMB/CIFS> Shares> Edit Share> Extra Option.
    I was thinking the setting could be modified per share but I was wrong.
    Enabling SMB1 must be a global setting.


    The system would not accept the ntlm auth = ntlmv1-permitted config change in Extra Options. This was not required.



    RESOLUTION:
    Scan to folder is working properly now. Thank you for the assistance!

  • Scan to Folder Stopped Working - How to enable SMB1

    Saw the NT1 and NTLM syntax when I did some research. Have not tried applying those yet.


    I was trying SMB1 which I now realize is incorrect syntax. NT1 is the correct syntax for SMB1.


    I will try editing the smb.conf file when I get home. I cracked it open in Nano before work but ran out of time.


    Thanks for the grep! That will help. I am not usually navigating Linux, so I forgot about the power of GREP!


    *******************************************
    Do you know if I can modify the SMB for an individual share, or does it have to be global?


    This is only a scan folder so I don't care too much about security on this one folder. I know that SMB1 has been deprecated because crypto malware can traverse SMB1 shares and infect everything. I would like to avoid SMB on the main share to keep it secure and protected. And yes, I do back up everything to cloud but still would like to practice best security. :)


    Thanks for the input and assistance. I will post results when I play with it again tonight.

  • Scan to Folder Stopped Working - How to enable SMB1

    testparm does not show output the global or individual share SMB version. I already had tried adding 'client max protocol = SMB1' to Extra Options on the share but that did not work.


    I was hoping for an answer on how to configure the Extra Options field of the individual share to get it working. I will review the smb.conf and how to configure it. Once I have that figured out, then i will try using the Extra Options field in the GUI.

  • Scan to Folder Stopped Working - How to enable SMB1

    An SMB share on Windows 10 with SMBv1 enabled has been setup for the interim. It is working properly w/o any issues. I would prefer to scan to the OMV NAS, as that is the centralized file server.


    The following actions have been performed to troubleshoot:
    OMV NAS has been restarted.
    Credentials were tested by accessing with Windows file explorer; creds were even reapplied to be sure.
    MFP printer was restarted and unplugged.
    IP address of host was used.
    Created a new test share with no permissions.


    I have been fairly thorough and nothing is working. I work in IT so I know the tricks on the printer side of things to get it working but still no luck.