Posts by ShamusLit

    Yes of course as MDADM cannot create a file system, where is the file system indicator coming from? I have only used OMV7 GUI and all prior steps completed perfectly until I got to the File System step and then ended up with this situation. This was on a completely clean OMV7 install with wiped drives.


    I have resorted to the CLI and just added an EXT4 file system to the md0 array and now have got it working but I was really trying to do the whole thing through the GUI.

    When I attempt to create the filesystem (Create and Mount a File System) on the Raid using the GUI it does not find the Raid. But gives me the option to mount an existing File System. When I select that, it actually shows the Raid as being /dev/md0 [EXT4, 3.63 TiB]. (I may have falsely assumed that when the Array was established it was created as an EXT4?) When I select that it then ultimately gives me the error above.


    BTW here are the details for the RAID 6 array:

    I'm attempting to rebuild an OMV server that had a disk failure. The disk was replaced and while I did that I decided to upgrade from OMV5 to OMV7. The configuration is an AMD64, 32 GB System Disk & four 2 TB HDDs.


    This is what I've done (twice now):

    1. install OMV7 on the 32 GB SSD with four HDDs disconnected
    2. Shutdown and add back the four HDDs
    3. Add OMV Extras
    4. Activate the OMV Multi Disk plugin
    5. Wipe all four HDDs
    6. Add the four disk to the SMART monitoring. All showing "Good".
    7. Group all of the four HDDs into a single RAID 6 configuration (took 8 hours) finished fine.
    8. Attempt to add a EXT4 file system to the newly created MD0 using Create and Mount a File System

    I get the following error when this is attempted:


    I see something failed about line 15 but I do not have enough knowledge on how to resolve the issue. Can anyone suggest a possible course of action?


    Thanks,

    I'm attempting to get ZFS running on OMV 6 (new install AMD64) and have been advised to install above plugin. Doing so from the Plugins manager gives me the following error:

    Can someone point me in a direction to fix this issue?

    should not create shared folders directly on top of the pool.

    chente , I did not know that! Is it documented somewhere in OMV? Also if that is the case then why would OMV offer the Pool as an option for shared Folders? Seems counterintuitive to me.


    So if I go to Storage, Filesystems, + and then create a new filesystem on top of the Pool how would I do that inside OMV? It's not clear to me how that can be done since when you go to Select A Device only the actual disks show up as options.


    I read through your first reference and could not find anything that seemed to be relevant to the OMV GUI. Perhaps you might point it out. The second reference has a number of dead links on subjects that might be relevant e.g. "ZFS Best Practices Guide".

    Perhaps you could suggest a step 6.2 that would improve my process above?

    Quote

    raulfg3 install previosly Promox kernel

    raulfg3 how would one do that in OMV? Using the plugin reference in this post showed a plugin titled "openmediavault-kernel 6.0.2" but that plugin does not appear in my plugins.


    What does appear is a plugin titled "openmediavault-kernel" but I assume that is not correct as when I run it I get a resounding failure. Or do I need to back out all of my ZFS work to get this plugin to install?


    What is the correct plugin to use? Could you suggest a step 5 (Install OMV Extras (and ZFS))for the above install guide?

    While I understand that raulfg3 was trying to be brief and helpful, his primary link refers to OMV 1 so it was not relevant for me to follow it. Flare I just went through this yesterday and here is what I did. I am using OMV 6 so I am assuming you are doing the same. Here goes:

    Install OMV Extras (and ZFS)

    1. From the Navigation menu select System, Plugins and in the search bar enter omvextra and then hit the Reload circle
    2. Select the plugin named openmediavault-omvextrasorg
    3. In the upper left select the downward arrow, Install
    4. Ensure that the plugin installs without error.

    Setting Up ZFS & Shares

    Then after the you have installed your drives,

    1. At the Navigation menu select Storage, Disks
    2. Select your data disk(s) **NOT your system disk**
    3. Select Wipe from the upper left menu (looks like pathetic eraser)
    4. Once you've wiped all the disks you are planning to use select Storage,ZFS, Pools
    5. Enter the pool data and select the drives you want to use. (Be cautious about naming your pool, I used an underscore [which apparently is allowed] in a pool name and got an endless string of errors in later config attempts. Also you should read about ZFS RAID alternatives to ensure you understand what devices are required and what type of RAID you need. It's too long to explain here.
    6. Let ZFS do its thing.
    7. Then select Storage, Shared Folders, +
    8. Add your shares by selecting the ZFS pool and naming the shared folders
    9. You will then need to link any services you plan to use to your shares.

    It may take a few minutes before these shares appear in your network.

    Hope that helps,

    macom Thanks for the list. However your 8 steps only gets to the first step of Clonezilla - then need to complete the next 8 to actually get a backup.

    I had already done your steps, at least up to 7, and after getting Clonezilla Live started I ran into the problem of not finding my backup drive listed in the available options.

    So now that I have at least one good backup of the OS drive I will follow your steps to see if I can also do the same from Clonezilla Live. More to follow...

    gderf - Thanks for your reminder about dd.

    OK so as I'm somewhat of a Linux noob i reread the dd man page and paid attention this time. The process ended up being:

    1. Attach the target drive to OMV (in my case a USB drive toaster)
    2. SSH into OMV root
    3. lsblk to see what drives are there and they were if=/dev/sdc & of=/dev/sdg
    4. sudo dd if=/dev/sdc of=/dev/sdg status=progress
    5. Receive completion status (took about an hour but my USB toaster is slow)

    I have read through the support forum and also read Headless backup. The Headless backup seems dated as it was done in 2015 and consists of 22 steps and ends up with the image on a data drive. You then have a number of additional steps to burn that image to an external SSD.


    I run OMV5 from a 32GB SSD and have recently purchased 2 identical SSDs. I would like to clone the system SSD to each of the backup SSDs. Having read the Clonezilla Live Doc for this disk-to-disk process (consists of 11 steps) I am unable to see how to do it in OMV using the built in version of Clonezilla?


    Any advice on how to do this? It seems to me that it would be a lot simpler than the existing directions provided. I'd be happy to document the process if I can get it to actually work.

    Methy By default Portainer installed itself with a Restart Policy of Unless Stopped. I've changed it to Always. I'll monitor the next week or so for the effect of that as the occurrence was random and it will take a while to see if it pops up again. Thankyou.


    macom I'll wait to see what changing the Restart Policy does before moving to a more direct approach but thanks for your suggestions.

    On my OMV installation I shut down the server at night and restart it in the morning. Randomly Portainer is not started. I can go for days with it running correctly and then again it might not be started. It can always be properly started by restarting Docker in the GUI.


    I am guessing this might be a random timing issue upon startup but I am at a loss to find a way to resolve it.

    1. Is there a way to delay the startup of Portainer within Docker?
    2. Or should there be a delay in Docker startup?
    3. Where are Docker log files stored?

    ...your UPS is not supported directly.

    chente In reading your referenced link a bit further it seems that there is an indication that this UPS is supported using usbhid--ups though it does not provide any detail.

    ...experience using apcupsd instead of NUT.

    gderf is there any way to achieve the same thing by entering information into the OMV-UPS field titled "Driver Configuration Directives"? I'd really like to stick to plain vanilla OMV services (& plug-ins) if I could.


    If I am going to have to use a separate install of apcupsd  how do I learn what to edit in the config so that I can set the shutdown time threshold (As this is missing from the link you provided).

    I had successfully used an APC Back-UPS ES 350 with OMV and NUT. Today that UPS was swapped out for a APC Back-UPS ES 550 to allow for a bit more time on the battery. Now the UPS log and the Syslog are overflowing with UPS related messages. Basically the error message is Poll UPS [borg-ups] failed - Driver not connected.


    I've noticed in reading for UPS Config it mentions a specific driver apcsmart for APC devices. Should I be using this driver as it seems when turning on NUT it uses a driver called usbhid-iups?


    I've attached the UPS log but as I am a bit green on the whole UPS monitoring process I'd appreciate any advice or direction to resolve these issues.

    I've recently installed Portainer 2.1.1 on my OMV 5 platform. I was interested in using the templates from SelfhostedPro. The instruction say to Enable External Templates under the Portainer Settings . In my installation of Portainer there is no entry on the Settings page for Enabling External Templates. The Portainer documentation that I've been able to review does not even mention this option. There is an option on the Settings page for "You can specify the URL to your own template definitions file here...". Do I overwrite that JSON file or can I somehow append the second location to it?


    Can someone please point me in the right direction on this issue?

    cubemin  KM0201  kenboyer-kb I really appreciate all of your help so far and it seems that Docker is now installed and running BUT I am a little leery about further steps until I am able to determine just how stable this whole thing is. This is on a working system so I don't want to break basic OMV functions.

    1. Is there a way to check Docker to make sure that it is in fact a good install?
    2. Does it seem strange to anyone that by apt install docker-ce it would reinstall the whole ball of wax without me touching the GUI?
    3. Once step 1 above is done will it be OK to install Portainer.
    4. Also when other changes are made to OMV via the GUI you get the banner asking you to confirm changes but in the above case that did not happen. Is this normal for Docker installs ( I cant recall what occurred when I originally installed it).

    The command docker run hello-world provides me with the following outupt:

    So does that tell me that all is well in Docker land?