Posts by Cezi_86

    Great work with omv-regen! I really admire your hard work.


    I just wonder, why it requires to have exactly the same disks set instead of just the same file system with particular UUID. I tried to disable it, but I do not speak Spanish and it was hard for me go understand the script. I tried to comment few lines in "if" at around 1074-1078 line, but failed. It would be great to be able migrate config to another system, or prepare system with omv-regen but without data drives and swap os disk to minimalize downtime.

    @zarrath I think something strange is happening with your OS drive. Is it new? Did you try in different USB port? Looks like it is loosing connection?

    Remember to install flashmemory plugin after OMV installation . Without this flashdrives die fast when OMV uses them as root partition. I forgot once to install it once long time ago and SLC flashdrive died in a week or something like that...

    I did install from the USB first, in order to install onto the hard drive.


    All 6 drives are connected in the hot swap bays. Why would this not work?

    I am not sure if you got it right. You can install OMV on a pendrive at least 8GB capacity and run OMV from it. If this would be what you choose to do, remember to install openmediavault-flashmemory. Otherwise you will kill the flashdrive.

    KM0201 is not wrong about RAID not beeing a backup. RAID 5 is fault tolerant (n-1 - one drive can die and the data is "safe"); RAID6 is more fault tolerant n-2 - two disks can die and the data is still available. There is still that ugly "but...". RAID is still a pain in the ass to recover data from it. When something goes terribly wrong, like file system get corrupted, accidental sync with not zeroed disk when upgrading array, etc... Personally I use RAID5 since the very beginning of OMV and NEVER got any problems. Unlike my fancy QNAP RAID array that has broken because of not genuine WD disk still waiting since 2019 for a miracle. Well, that for sure taught me a lesson.

    I thing with this config save solution would be RAID5 (5x500 in RAID5 =2000) and sync it with that single 2000 once in a while. You would have to configure RAID5 and JBOD for the 2TB single disk on that controller. BTRFS can be useful here. I use it on all my systems and data takes noticeable less space. You can even make w script that copy data from RAID 5 to that single disk at night and have versions of those files.

    REMEMBER to check the disks before using it.

    And one more thing - use an UPS. I buy used and replace battery/batteries, so this is quite cheep solution. Connect its data interface to the server and configure NUT plugin in OMV to safely shutdown your server when the power goes out.

    If you are using it just as NAS to backup your primary NAS and as a plex server then in my opinion you have way much free resources. I use MobaXterm as SSH client and constantly I see how much power and memory is needed for OMV to run in different use cases when I do something over SSH. For years I use Thin Clients to run OMV with 2,5" 7-9 mm disks in RAID 5. It is very cost efficient and I mean not only building those, but electricity efficient. 2x 1,65GHz or 4x 1,5 GHz 2-4GB of DDR3 10600, 3x 2TB, 8-16 GB SLC/TLC SSD for OS.

    flashmemory plugin is definitely a must-have when OS is running on flash drive. Otherwise you can kill the SSD/flashdrive really fast. Once I did that. :saint:

    @macom in this wiki article there is not mentioned about additional attributes in "noatime" and "nodiratime" that needed to be add by hand in /etc/fstab. Is this not needed anymore? I still add them and nothing bad happens to my systems, but maybe I have missed the memo that it is not required anymore? :/

    Make sure you have ntfs-3g, fuse installed to support NTFS.

    Then try (physically, with WeTTY or connecting to SSH server) shell command mount /dev/sdc1 /srv/some_folder

    You need to replace some_folder with folder for mounting partition

    If this is going to be permanent, you need to add it to /etc/fstab and run:

    omv-salt deploy run fstab

    Non the less, it should work out of the box. Is your system updated?

    Hi!

    Is there any particular reason that you are using "dd", instead of "dd full disk"?

    "dd" method is writing parts of disk separately, when "dd full disk" has all you really need in one file.

    ryecoaaron (the creator of this great plugin) explained those parts of "dd" backup in this post.

    When restoring to a new drive, you need to

    Code
    # !!! in case of use, remember to change disks and file name accordingly!!!
    
    dd if=/mnt/backup-omv-15-May-2022_20-46-32.grubparts of=/dev/sda bs=512 count=1
    partprobe /dev/sda
    gunzip -c /mnt/backup-omv-15-May-2022_20-46-32.gz | dd of=/dev/sda1 bs=1M status=progress

    "dd full disk" restores image with

    Code
    # !!! in case of use, remember to change disks and file name accordingly!!!
    
    gunzip -c /media/sdc1/restore-omv/backup-omv-15-May-2022_20-46-32.ddfull.gz | dd of=/dev/sda bs=1M status=progress

    If you want to backup only the OS partition, I recommend openmediavault-backup plugin with "dd full disk" method. Very easy to setup and easy to restore. Tested it many times, and never had any problems. Every time new major version of OMV/Debian is released, I download from remote servers its backups, restore it on local machine and test if it is safe to upgrade remotely.

    I am using BTRFS as single partition without swap on six installations and no problems found. Thanks to macom I installed snapper and snapshots work fine too.


    My preseed configuration (partitioning part)

    REMEMBER to disconnect all other drives when installing


    ### Partitioning 4 legacy

    d-i partman-auto/method string regular

    d-i partman-auto/disk string /dev/sda

    d-i openmediavault-installer/partman/multiple_target_devices select continue

    d-i partman-auto/expert_recipe string \

    no-swp :: \

    500 5000 100% btrfs \

    $primary{ } \

    $bootable{ } \

    method{ format } \

    format{ } \

    use_filesystem{ } \

    filesystem{ btrfs } \

    mountpoint{ / } \

    .

    d-i partman/confirm boolean true

    d-i partman-basicfilesystems/no_swap select no

    d-i partman-partitioning/confirm_write_new_label boolean true

    d-i partman/choose_partition select finish

    d-i partman/confirm boolean true

    d-i partman/confirm_nooverwrite boolean true


    After unattended installation I run script that includes installing and configuring snapper with command

    Code
    snapper -c root create-config /

    After some time I see snapshots in /.snapshots/1 or something like that with all files of root file system.

    I need to do separate file for EFI installation, but I do not have time.

    I have read somewhere that even booting to a snapshot is possible, but did not test it. I wonder, if it is possible to do automatic fallback to earlier snapshot if starting system fails like three times.

    I have tried to apply some values to OMV using shell. In general omv-confdbadm update works, but with this one particulat it drives my crazy. For example the simpliest job...


    config.xml example:

    <crontab>

    <!--

    <job>

    <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>

    <enable>0|1</enable>

    <execution>exactly|hourly|daily|weekly|monthly|yearly|reboot</execution>

    <sendemail>0|1<sendemail>

    <type>reboot|shutdown|standby|userdefined</type>

    <comment>xxx</comment>

    <minute>[00-59|*]</minute>

    <everynminute>0|1</everynminute>

    <hour>[00-23|*]</hour>

    <everynhour>0|1</everynhour>

    <dayofmonth>[01-31|*]</dayofmonth>

    <everyndayofmonth>0|1</everyndayofmonth>

    <month>[01-12|*]</month>

    <dayofweek>[1-7|*]</dayofweek>

    <username>xxx</username>

    <command>xxx</command>

    </job>

    -->

    </crontab>


    in config.xml:

    <job>

    <uuid>32664b22-5a9d-11ec-8834-6f00f75b23ee</uuid>

    <enable>1</enable>

    <execution>exactly</execution>

    <sendemail>1</sendemail>

    <comment>Monthly backup</comment>

    <type>userdefined</type>

    <minute>30</minute>

    <everynminute>0</everynminute>

    <hour>4</hour>

    <everynhour>0</everynhour>

    <month>*</month>

    <dayofmonth>1</dayofmonth>

    <everyndayofmonth>0</everyndayofmonth>

    <dayofweek>*</dayofweek>

    <username>root</username>

    <command>/usr/sbin/omv-backup</command>

    </job>


    #omv-confdbadm read --prettify conf.system.cron.job


    [

    {

    "command": "/usr/sbin/omv-backup",

    "comment": "Monthly backup",

    "dayofmonth": "1",

    "dayofweek": "*",

    "enable": true,

    "everyndayofmonth": false,

    "everynhour": false,

    "everynminute": false,

    "execution": "exactly",

    "hour": "4",

    "minute": "30",

    "month": "*",

    "sendemail": true,

    "type": "userdefined",

    "username": "root",

    "uuid": "32664b22-5a9d-11ec-8834-6f00f75b23ee"

    }

    ]


    #omv-confdbadm read conf.system.cron.job

    [{"uuid": "32664b22-5a9d-11ec-8834-6f00f75b23ee", "enable": true, "execution": "exactly", "sendemail": true, "comment": "Comiesi\u0119czna kopia systemu", "type": "userdefined", "minute": "30", "everynminute": false, "hour": "4", "everynhour": false, "month": "*", "dayofmonth": "1", "everyndayofmonth": false, "dayofweek": "*", "username": "root", "command": "/usr/sbin/omv-backup"}]



    and update command I use:

    omv-confdbadm update conf.system.cron.job '{"uuid":"32664b22-5a9d-11ec-8834-6f00f75b23ee","enable":false,"execution":"exactly","sendemail":true,"comment":"","type":"userdefined","minute":"30","everynminute":false,"hour":"1","everynhour":false,"month":"*","dayofmonth":"*","everyndayofmonth":false,"dayofweek":"7","username":"root","command":"/usr/sbin/omv-backup"}'


    After this command, I get:

    Traceback (most recent call last):

    File "/usr/sbin/omv-confdbadm", line 76, in <module>

    sys.exit(main())

    File "/usr/sbin/omv-confdbadm", line 72, in main

    return cmd_inst.execute(*sys.argv)

    File "/usr/share/openmediavault/confdbadm/commands.d/update.py", line 57, in execute

    obj.set_dict(cmd_args.data)

    File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 208, in set_dict

    self.set(key, value, validate)

    File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 184, in set

    self.model.property_validate(name, value)

    File "/usr/lib/python3/dist-packages/openmediavault/config/datamodel.py", line 272, in property_validate

    self.schema.validate(value, name)

    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 175, in validate

    self._validate_type(value, schema, name)

    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 229, in _validate_type

    raise last_exception

    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 209, in _validate_type

    self._validate_string(value, schema, name)

    File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 275, in _validate_string

    raise SchemaValidationException(

    openmediavault.json.schema.SchemaValidationException: minute: The value '30' is not a string.


    I run and applied successfully so far: conf.webadmin, conf.system.time, conf.system.notification.email, conf.system.notification.notification (each separately), conf.system.powermngmnt, conf.service.smartmontools, conf.service.ssh, conf.system.monitoring.perfstats, but the most wanted cron job entries remains mistry to me. After some modifications I get this error about dayofmonth. I would not post question about it if it would not give me terrible headake. There is very little info in manual section about "omv-confdbadm update". There is not even mentioned that applying requires particular salt command. And there is no information wich omv-confdbadm command is connected to salt command. I still try to figure out, what salt command applies conf.system.monitoring.perfstats settings. Those commands are not even searchable in google. I get one or two hits per "omv-confdbadm update conf.***". Or am I missing something?

    Hi! I have noticed, that preseed file in installation media of omv 6.0.24 tells Debian installer to create EXT4 as root fs. Is there any particular reason for that? I have installed it with changed option d-i partman/default_filesystem string to btrfs as root and it works so far. I wonder if this was good idea or not. Any thouths?

    Hi!
    Although I am using OMV since the very beginning in 2009, Docker is very new to me. I almost always managed to work thing out without bothering people on this forum. I have sticked to traditional plugins as long as it was possible, because I like OMV as it was, with one, great interface. Volker really did awesome job. With Docker, Portainer, Cockpit and Heimdall it feels like OMV was just a plugin. Depricating UrBackup as a traditional plugin in OMV 5 forced me to move to Docker and right away I encountered a problem that is repeating itself in two of four stacks. Nonetheless I see big advantages of using Docker.


    About my installation
    OMV 5.3.3-1 (Usul)
    Debian 10.3
    kernel: 5.4.0-0.bpo.3-amd64
    sda: 4GB SSD for / (27% free)
    sdb: 99% of dev-disk-by-label-SpareNDFS is free (for data)
    no swap with openmediavault-flashmemory (swap off, commented out in fstab and in /etc/initramfs-tools/conf.d/resume, swap partition removed, sda1 resized to full disk, no efi partition)
    /var/lib/docker in my case is moved to /srv/dev-disk-by-label-SpareNDFS/docker (ln -s srv/dev-disk-by-label-SpareNDFS/docker /var/lib/docker).


    Portainer 1.23.1 installed form OMV-Extras

    Docker installed form OMV-Extras

    dpkg -l | grep docker
    ii docker-ce 5:19.03.6~3-0~debian-buster amd64 Docker: the open-source application container engine
    ii docker-ce-cli 5:19.03.6~3-0~debian-buster amd64 Docker CLI: the open-source application container engine
    ii docker-compose 1.21.0-3 all Punctual, lightweight development environments using Docker
    ii golang-docker-credential-helpers 0.6.1-2 amd64 native stores to safeguard Docker credentials
    ii python3-docker 3.4.1-4 all Python 3 wrapper to access docker.io's control socket
    ii python3-dockerpty 0.4.1-1 all Pseudo-tty handler for docker Python client (Python 3.x)
    ii python3-dockerpycreds 0.3.0-1 all Python3 bindings for the docker credentials store API


    What I do, is copy docker-compose configuration text to a stack, correct PUID, PGID, TZ, and paths in section "volumes". For every stack I use the same absolute path to folder on the data drive where I want them to be, with separate folders for each container. Half of them gave me the same error:
    "Deployment error
    yaml: unmarshal errors: line 15: cannot unmarshal !!seq into map[string]interface {}".


    Error message always is pointing the first path in section "volumes:"


    I know that containers can be created with command line, but I like this method better - I can see everything here in great order and I can comment out lines I do not want at the time.


    Here is the configuration text I used for transmission:


    and for UrBackup from uroni github:

    Here I get the same error with line number 13.
    Tried with different folders in /srv/dev-disk-by-label-SpareNDFS, but with no luck. Once I event tried it with path to shared folders /sharedfolders but with no luck either.

    Hi!
    Try to install TeamViwer HOST within XFCE. Just had it done with TV 13.2 for Debian amd64. Despite TeamViwer's GUI never showed up in XFCE, it worked after using teamviewer info for ID and teamviewer passwd xxxxxxxxxx to add password.

    OMG!!! You wil not believe it... I was connecting with TeamViewer to a computer in the network where this NAS is to access OMV's Web Interface. Never had any need to connect to any other sites despite router's wb page, switch etc. I was so focused on not working OMV's Web interface and had no need to go any other place in the network or Internet that I did not think of one more thing... It was never about OMV. I think it was working whole the time. It turned out, that fu**ing Norton Internet Security was screwing with access to web pages... :cursing: Wrrrr...
    Sorry 4 wasting your and my time.

    In first massage I wrote everything that I tried. This solution was recommended in some post here. I did quite a lot of research before starting new thread.
    Did it again just to make sure and nothing.
    Honestly I do not understand what is happening with this NAS.
    Some people at least get "It works", or "Welcome to nginx", but here is nothing at all. :(
    Maybe in nginx configuration something is wrong, like path to OMV's files?


    EDIT: By the way, first time when I sow this command, I did look at this folder before executing it. It was empty. Is it normal? One more thing - when I try to apt-get dist-upgrade or apt-get upgrade after confirming upgrade I get "aborted" or something like that. Forgive me writing those system massages starting with "something like that", but it is translated form Polish. :P

    Just in case it changes anything, it runs 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u3 x86_64.
    I have one more NAS running OMV and there is 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u2~bpo70+1 (2015-07-22) x86_64. This one works fine on 2.1.7 (recently updated from 1.17).
    I have no access to Web interface at all. Only access via SSH. SMB works fine, but I need to add one user and I am unable to do it. :-/

    Sorry for second post in a row, but I am getting some access error when I try to edit my post. :(


    So here it is, what I wanted to add:
    Can cause such a problem wrong kernel version? Maybe something in config files?