Beiträge von mick_d

  • Help needed with Docker Compose Files

    Hi chente and ryecoaaron,


    Thanks for all the help. The server is now cleaned up.


    What I might do is set up a toy server and run through a clean install and learn Docker without pressure to get my sister's server back to her. That way I can get all the steps clear in my mind and then look at putting Docker and miniDLNA on her machine.


    I'll mark this thread as resolved. If I have issues with the toy server, I might be back ! ;)


    BR


    Mick

  • Help needed with Docker Compose Files

    Hi again,


    The server belongs to my sister who lives about 30 km away, so support for me is a pain.


    I have struggled to configure Docker so far and have yet to try to get miniDLNA installed, so I'm going to cut my losses and not go ahead with Docker and miniDLNA.


    How do I uninstall Docker?


    I can clean up the unneeded shares, but I don't see any options to uninstall Docker.


    It's a shame that miniDLNA is no longer a plugin. It would be much simpler (for the user, if not the implementers/maintainers)


    BR


    Mick

  • Help needed with Docker Compose Files

    OK,


    I created shares like the file tree diagram, so I now have the shared folders "system", "system/appdata", "system/backup_compose", "system/docker", "data" and "data/media".


    I looked at global environment variables and see they are a shorthand way of referring to long path definitions e.g.


    Code
    MEDIA=/srv/dev-disk-by-uuid-384444bb-f020-4492-acd2-5997e908f49f/data/media


    This still doesn't address how I can get this "data/media" share to point to my two exisiting folders or their SMB shares.


    From the tree diagam it seems that exposing "data/media" to Docker will automatically expose folders below it, but how do I get "/data/media" to point to my existing shared folders that I use for SMB.


    Thanking you for your patient assistance.


    Mick

  • Help needed with Docker Compose Files

    Hi Chente,


    Thanks for the response. I've just reloaded that document and it shows you last editied this evening at 18:50'ish, so I have the up to date version.


    As you clarified the "/dev/vde1" vs "/srv/dev/disk-by-uuid..." issue, I can cope with that problem.


    However, my confusion with the Docker files being stored under a folder "system" which doesn't appear to be defined still stands.


    The same applies to the share "data", as I have 2 individual shared folders I wish to "attach" to Docker. How to do that? Is it possible to define (in OMV) a share called "data" which encompasses these two existing shares?


    BR


    Mick

  • Help needed with Docker Compose Files

    Hi All,


    I want to install miniDNLA on my OMV 7 machine which previously had the service under OMV 5. The system disk failed, so I fitted a new disk, did a fresh OMV 7 install and from my research, it indicates that Docker is the way to go to install miniDLNA. I've never used Docker before, so I'm trying to follow the online guidance, mainly "Docker in OMV" from OMV-extras.org.


    I activated the OMV-extras repo and installed Docker successfully and am now at the point of creating the plugin settings. There is a diagram showing two alternatives; the one where Docker is put on the same disk as the data looks most suitable.


    I find the screenshot and the associated file tree drawing a little hard to reconcile:-


    1) The folder"docker" is shown connected to "/srv/dev/disk-by-uuid..." and the folders "appdata" and "backup-compose" are shown connected to "/dev/vde1" in the screenshot, but the diagram shows them all under a folder called "system" on "/srv/dev/disk-by-uuid...". Nowhere is "system" defined and whilst "/srv/dev/disk-by-uuid..." is what I understand from normal file share creation in OMV, "/dev/vde1" (looks like a direct linux device) is not something I've encountered.


    2) The user data is shown in a shared folder "data" on the "/srv/dev/disk-by-uuid..." as I might expect. However, my wanted data currently exists as individual shares already defined in OMV e.g.

    Code
    Music        /dev/md0        music/        srv/dev/disk-by-uuid....

    and

    Code
    Photos        /dev/md0        photos/        srv/dev/disk-by-uuid....


    How can I attach these separate shares to the Docker settings.


    I am just afraid of doing something that might mess up the existing shares which are successfully being accessed over the network using SMB.


    Sorry if this is a bit newbie, but with Docker, I am.


    BR


    Mick

  • Problem with RAID not seen on installation

    Hi Macom,


    OK, that plugin has added a "Multiple Devices" option to "Storage" and I was able to add the Filesystem.


    I must admit it was a bit counter-intuitive to have to add the plugin. I don't seem to recall doing that before, but Hey-ho!, it's workling now.


    Thanks for the prompt info.


    BR


    Mick

  • Problem with RAID not seen on installation

    Hi all,


    I am reinstalling OMV (latest version) onto an existing machine that was running an older version of OMV (version 5 or 6, not sure).


    It is an HP Microserver Gen 7 which boots off a 2.5 inch SSD mounted in the ODD bay and has 2 x 2TB SATA hard drives in a RAID 1 in the first two caddy slots.


    The machine was running fine but suffered a failure of the SSD and (obviously) stopped functioning, so I inserted a new SSD and installed OMV 7 to it.


    Initially, I left the RAID drives out for safety until I had the installation complete and could prove the system functionality. Once that was done, I shut the machine down, inserted the RAID drives and rebooted.


    After the system came up, the RAID did not appear in the dashboard. However, using a directly attached keyboard and screen I could see the RAID was there. I could manually mount it to /mnt and the contents were visible, so they RAID was not corrupted.


    I thought it might be because the RAID was not detected at installation time, so I did the installation again, but with the RAID disks installed. During the partitioning selection process it offered a RAID1 array as a possible target, so the detection was successful. However, after the initial boot, the RAID manaagement option was still missing from the dashboard.


    I researched this issue in the forum with no success, so I am embedding some printouts which seemed relevant in other cases


    BR


    Mick


    Code
    root@odysseus:~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb1[1] sdc1[0]
      1953382400 blocks super 1.2 [2/2] [UU]
      bitmap: 0/15 pages [0KB], 65536KB chunk

unused devices: <none>


    Code
    root@odysseus:~# mdadm --detail --scan --verbose
ARRAY /dev/md/0 level=raid1 num-devices=2 metadata=1.2 name=odysseus.internal.net:0 UUID=270a3820:d7386050:f7eaaaa7:d41c577a
   devices=/dev/sdb1,/dev/sdc1


    The following mdadm.conf is unmodifed from the fresh install


  • Problem installing OMV 7.0.32

    Hi all,


    I am trying to repair a failed OMV 5 machine (HP Gen 7 microserver) which appears to have a corrupted/damaged boot SSD.


    I downloaded the latest ISO "openmediavault_7.0-32-amd64.iso" onto a USB stick and when I boot from it, the process stops after:-


    Code
    GRUB loading.
Welcome to GRUB!


    The error is

    Code
    error: file '/boot/grub/i386-pc/normal.mod' not found.
Entering rescue mode...
grub rescue>


    From what I can gather, this seems to imply that a non-UEFI version is trying to boot. This is sensible, as the HP Gen 7 is a legacy boot machine. However, if I check the contents of the iso file on my Windows machine, the "/boot/grub" directory does not contain an "i386-pc" directory. There are directories called "i386-efi" and "x86_64-efi" which both contain (among other files) the "normal.mod" file.


    What am I doing wrong? I was able to install OMV 5 ages ago and don't recall any issues. I have disconnected all the other drives (SSD boot and 2 HHDs which are a RAID mirror), so only the USB stick is involved.


    Thanks


    Mick