Posts by Mathias1988

    According to the error message

    File "/usr/lib/python2.7/", line 1
    SyntaxError: invalid syntax

    you or someone else must have modified the file manually. The first line looks like a copyright to me. Seems the comments are not set correct. Fix this and it should work.

    You are right .. All files in the Python2.7 folder seems to be some kind of defect...
    I copied the Python2.7 folder from a virtual linux machine to the NAS. Now this error is gone. But now is "Samba-Tool" missing. Something strange is going on here. I hope the system ssd is not broken...
    Is there a command to check/rebuild all OMV dependencies / tools ?

    What is the output of

    ls -al /usr/lib/python2.7/


    tail -10 /usr/lib/python2.7/

    Sorry for my late response, i was in vaccation. The output of the two commands is:

    Hello guys, im not able to enable samba share anymore. Maybe anybody can give me a hint what to do ...

    Best regards, Mathias

    Zeile 2: 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 --no-color samba 2>&1' with exit code '1': debian:
    Zeile 265: Comment: One or more requisite failed: omv.deploy.samba.default.test_samba_service_config
    Zeile 274: Comment: One or more requisite failed: omv.deploy.samba.default.start_samba_service
    Zeile 291: Failed: 3

    Good evening together,
    since a few days i get error messages when changing something in the configuration. After reading through the forum / internet it must be something with the disk quota i think. But in my point of view quota is not active and i also dont use it. Got anybody a hint for me ? Maybe the quota thing is misleading me...

    You can find the error message in the attachment.

    Best regards,

    It seems that the ISO9660 thing was the issue.
    After doing the steps described here: i was able to resize the partition.
    After resizing the system booted normally. So now i try to copy the disk via DD to a smaller HDD.
    I still dont know how the hdd filesystem was formated to ISO9660 ?

    I was able to reduce the size of the OMV HDD and create a backup on a small usb stick,
    Thank you for your support :-)

    I just started Kali-Linux with a bootable USB stick and started GParted. And there is only one partition on the OMV Hdd . I was sure that there was at least a swap partition after the OMV one.... Maybe some setting deactivated it..
    Before i try to change the partition size i do a complete copy on a bigger HDD via DD. Not to crash everything.

    I will try to resize the partition tomorrow.

    I have one more question at the moment, why is the filesystem format ISO9660 and can i change it if needed ? Thank you and night (iam from germany).

    What you can try to do is use dd to copy the disk to a smaller one

    Good idea, but i already tried that, too. But booting from the "new"-HDD failed.
    I think it failed because on the source HDD are 3 Partitions and the third one will not be copied because "out of HDD space" on destination.

    Reducing the size of the partitions does not reduce the size of the disk

    You are right. So i have to reduce the main partition, but i cant. Its in the middle of two others...

    I think i could try to use gparted directly on NAS. Maybe there is only a problem with partitioning via laptop. I will give it a try and report.

    Hi together,

    OMV is running on a 256 GB SSD. I only use 20 GB of the HDD memory and want to make a cyclic backup via dd. ( And also want to use a smaller OMV HDD )

    My destination USB for the backup only got 32 GB.

    Is it possible to reduce the size of the OMV partitions ?

    I already tried GPARTED, AOMEI Partition assistant . Both with a bootable USB stick on a windows 10 PC . Without success.

    Would be great if anybody got a hint for me :-).

    Best regards,


    I just installed OMV5 on my QNAP TS253B (on USB SSD). There are only two things what are a little bit annoying to me.
    - Cannot control the FAN ( no pwm sensors found ) --> Bios settings to set it from "automatic" to "manual" leads to FAN running 100%
    - The front display is only showing "Booting" all the time

    I tried to install "qcontrol" what is - regarding to another post in the "Qnap Community" Forum - the tool used with QNAP OS for controlling these two things. But iam not able to execute it successfully.

    Has anyone a idea to fix this issues ? At least the FAN thing...

    Update: The fan can be controlled via this package:

    Best regards,


    That thread must have been old. by-label is no longer used. If you need an easy to read mountpoint, install the symlinks plugin and make a symlink.

    Thank you, i give the plugin a try. --> Already tried and it´s perfect to me :)
    The thing is, the screenshot in the first picture is from my OMV. I do not understand why "WD30" is mounted by uuid and "WD40" by label :/

    But iam new to OMV so maybe i have done somthing wrong during init...

    Hi together,

    i do not really understand why the mountpoints of my 2 HDDs are handled in different ways. As i read in another thread, since omv5 the mountpoint should be "by-uuid" by default.
    For me it would be enjoyable if i could set both mountpoints to "by-label".

    Best regards,