Beiträge von magarity

    I have my Samba share set up for 'guest only' because I don't need to restrict any permissions. When I use a Windows 10 client, I can see the existing folders and add new files to existing folders. However, creating a new folder (simple right-click then create folder) makes 4 at a time, New Folder (1-4). Which cannot be renamed or anything put in them. So, I SSH to the server, navigate to the /srv/dev-disk-by-label-shared to delete 3 of them, chmod them to 'root' instead of 'nobody' and then I can use it from the Win 10 client. What might I have set incorrectly in the OMV SMB configuration that causes this behavior?

    thanks for any help

    magarity

    Thanks, unfortunately this seems to be a problem with the Win 10 client. I found and deleted the directory on the OMV server and it stayed gone until I opened recycle bin on the client. Then it suddenly reappeared on the server while the client popped up its complain that it is corrupt. Argh!

    I searched the registry on the client but can't find an entry. Recycle bin itself has no option to delete that particular bin.

    For x86 based hardware the OMV images include the Linux OS but for ARM systems like RPi you must install some Linux first then the OMV package. Raspian, Debian server, whatever. Raspian makes the most sense and is easiest. The people who told you that must not be RPi owners if they think the OMV people maintain an image for ARM including the OS.

    My use is about the same as your except only 3 cameras instead of 5. My ancient AMD A6-3500 tri-core stays around 20% load. I suggest you get as low power a CPU as they offer since any new model will be able to keep up. I think AMD has quad cores that take a mere 35 watts for the AM4 socket. Saves a lot of electric bill over time.

    If your system will be "headless" (no monitor) there is no need for the 'G' model CPU.

    I toggled on the 'enable recycle bin' option on an SMB share. Now my Windows 10 client complains that the recycle bin on that share is corrupted. I tried just removing it by un-toggling in the OMV setting, which saved the change and shows not enabled. Yet the Windows client still insists it is corrupted. Honestly I don't care about keeping it on, I just want the Windows client to stop complaining about this. Any suggestions?

    (Yes, OMV 5 is completely up to date on patches so is the Win 10 client)

    The docker run, docker compose, and docker create commands that you will see in the documentation pages of images are in almost every case examples, not working configurations that anyone and everyone can just run as is. You need to examine every line in such examples and decide for yourself if it can be used as is or must be modified to match your specific use case. To do this you need to have at least a basic understanding of docker and Linux principles. This knowledge is assumed, and this assumption is not mentioned anywhere.

    OK, I've gone over the example settings again and I think I see where to put the path. However, where has OMV 5 put it? So, using the OMV management page I've created a volume called 'zonemindernas' on a dedicated disk. However, it is not neatly under /mnt/ on the filesystem and the management page gives no hints as to where it might really be. "find zonemindernas -type d" did not locate it. I assume these are aliased somehow?

    thanks for the help and patience so far.

    Started it up as is doesn't say anything.


    The docker run command provided in the image documentation provides what you need to configure the container. You do need to select proper values for the various variables to fit your use case.

    Sorry, Zoneminder's website seems to be having issues and I can't get at those details. I just pasted in what they had as a default.

    docker exec -i <container_name> sh -c printenv

    Code
    ZM_DIR_EVENTS=/full/path/to/the/events/folder

    https://zoneminder.readthedocs…guide/dedicateddrive.html


    In my understanding and unless it's a real bug, if that variable is set to your path with permissions, it should work.

    I don't think I can do that without first setting up the docker image to know about the mount, which is what I'm having trouble doing.

    You might be better off using Bind mounts. Also it is difficult to help when you haven't provided any information about how you configured the container, not even the image name and where you got it.


    Oh, sorry, it's the one linked from Zoneminder's site as the somewhat official version. It is called dlandon/zoneminder.master:latest

    As for how I configured it, I just started it up as is. This is the first time I tried Docker so all I'm still fumbling about.


    Can you give me some direction for how to set up the bind type mount? I ssh'd to my OMV and poked around the filesystem but I can't figure out where it was put.

    Click on the container name. Then click on the Duplicate / Edit button.

    Thanks! I found all that and 'zonemindernas' appears to be added OK. I selected it from the menu of local volumes and after saving the volume details appear correct. Zoneminder in the revised container starts up, but then the ZM 'storage' option refuses to accept it. I put the path as copied from what Portainer says is "path in container' but upon saving ZM lists it as the original default location! It even renames it to 'Default'. I tried several times and now have 7 identical 'Default' storage locations, all identical. :/ Kinda weird! Adding it to the Volumes section will do all the necessary mounting behind the scenes for the container or is there some additional step for that I missed?

    I have the zoneminder docker image running under OMV5 just fine with 3 cameras. Except that the default storage mount is the same as OMV, which is not a very large drive. I have a drive to dedicate to ZM installed and set up on OMV and am able to access it both with NFS and SMB. I added it in the 'volumes' section of Portainer. But how the heck do I add it to the ZM container??

    I get the following when trying to turn on SMB service on a version 5 install. Also, the Dashboard's system info is just a blank box, so I'm not sure what subversion of 5 it is on.


    The SMB shares are set up without any problem, it's just that this is what I get when trying to enable the actual service:

    what exactly do I need to edit to fix this?

    Internal Server Error

    {"response":null,"error":{"code":0,"message":"The property 'localmaster' does not exist in the model 'conf.service.smb'.","trace":"OMV\\AssertException: The property 'localmaster' does not exist in the model 'conf.service.smb'. in \/usr\/share\/php\/openmediavault\/config\/configobject.inc:71\nStack trace:\n#0 \/usr\/share\/php\/openmediavault\/config\/configobject.inc(186): OMV\\Config\\ConfigObject->assertExists('localmaster')\n#1 \/usr\/share\/php\/openmediavault\/config\/configobject.inc(271): OMV\\Config\\ConfigObject->set('localmaster', true, true)\n#2 \/usr\/share\/php\/openmediavault\/config\/configobject.inc(233): OMV\\Config\\ConfigObject->setFlatAssoc(Array, true, false)\n#3 \/usr\/share\/openmediavault\/engined\/rpc\/smb.inc(81): OMV\\Config\\ConfigObject->setAssoc(Array)\n#4 [internal function]: Engined\\Rpc\\Smb->setSettings(Array, Array)\n#5 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(123): call_user_func_array(Array, Array)\n#6 \/usr\/share\/php\/openmediavault\/rpc\/rpc.inc(86): OMV\\Rpc\\ServiceAbstract->callMethod('setSettings', Array, Array)\n#7 \/usr\/sbin\/omv-engined(537): OMV\\Rpc\\Rpc::call('SMB', 'setSettings', Array, Array, 1)\n#8 {main}"}}