Can't Access OMV After Attempting Update

    Do what is written on screen:


    systemctl status srv-5f...


    Another way would be to re-create the mergerfs wit the UI

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    It tells that the directory /srv/5f... is not empty so it can not mount anything there.

    Can you veryfiy what is in there with ls -la /srv/5ff.../Elle


    Is this what you expect to be there?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Quote from Zoki

    It tells that the directory /srv/5f... is not empty so it can not mount anything there.

    Can you veryfiy what is in there with ls -la /srv/5ff.../Elle


    Is this what you expect to be there?

    Will check tomorrow evening. Have to log off now. Thanks for your help and patience. You're an example of why the OMV community is so great.

    Your Problem is with the mergerfs. As I do not use it, I can only guess what is wrong.

    Eigther only half of the volumes in the mergefs is mounted or something copied parts of your files into the mountpoint.


    Can yoiu disable the mergerfs again and check the directory again.

    If it is still not empty, move the files out of the directory into a save place and re-enable the mergerfs

    If this does not help, ask a specific question regarding mergerfs in a different thread.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    After commenting out mergerfs and rebooting, I see the same list of folders on the mount point. So you're right, it seems to be a mergerfs issue. I'll raise a separate thread. Thanks for all your help, support and patience

    • Official Post
    Quote from claredad

    I see the same list of folders on the mount point.


    Quote from Zoki

    If it is still not empty, move the files out of the directory into a save place and re-enable the mergerfs

    I would suggest as Zoki recommended.

    • Official Post
    Quote from claredad

    If i recreate the mergerfs, do I risk losing info?

    If you can somehow clear the mergerfs references from the system, you should be able to recreate them. You would not lose data on your drives by doing this.

    If the mountpoint is empty my guess is the mergerfs is mounted correctly. mount only complained about a non-empty mountpoint.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    • Official Post
    Quote from claredad

    After commenting out mergerfs and rebooting, I see the same list of folders on the mount point.

    I guess this means, the mount point is not empty (when the filesystem is not mounted)

    Quote from macom

    I guess this means, the mount point is not empty (when the filesystem is not mounted)

    Below are the folders I see in the mount, even though the MergerFS is commented out. They all should have subfolders, but the only ones that do are the ones that are data folders related to dockers I have running on the OS (Nextcloud & Calibre). Does that mean anything?


    this means you are in danger to loose some data:

    While the mergerfs was not mounted the docker containers wrote some data to the location where there used to be the mergerfs. So you have the data which shoild be in one place in twi places.


    What you need to do now is to move the files out of the srv/5ff directory (make it empty), restoee the mergerfs and merge the files back into the mergerfs.


    Make shure the containers are stopped while you do the above.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    • Official Post
    Quote from Zoki

    the docker containers wrote some data to the location where there used to be the mergerfs

    I haven't read the whole thread, but I hope he doesn't have any config folder or volume inside mergerfs. A container that writes data to mergerfs is fine, but volumes or config will be problematic.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login