Beiträge von thud1

  • How do I remount a MergerFS mount point without rebooting the system?

    I followed troubleshooting steps from this thread and got it mounted without rebooting! Thank you.
    mergerfs filesystem suddenly not mounted and can't seem to find a way to get it back

    I would say journalctl did not explain why it lost mount. but i am happy to fix it without reboot. next time i lose mount again i will dig through logs immediately to see if i can find a cause.



    I get the same error. My server seems to drop mount every 2 or 3 months. I don't know the trigger. tired of reboot being the fix.

    Is there an OMV cheatsheet for digging through the logs and finding out why my mergerfs drops mount?

    If i try to refresh mergerfs mount in the gui i get the error below.

    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; systemctl restart srv-ae0f5928\x2d3495\x2d4ef8\x2d9e08\x2d3cfa3665428d.mount' with exit code '5': 

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; export LANGUAGE=; systemctl restart srv-ae0f5928\x2d3495\x2d4ef8\x2d9e08\x2d3cfa3665428d.mount' with exit code '5':  in /usr/share/php/openmediavault/system/process.inc:217
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/mergerfs.inc(197): OMV\System\Process->execute(Array, 5)
#1 [internal function]: OMVRpcServiceMergerfs->restartPool(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('restartPool', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Mergerfs', 'restartPool', Array, Array, 1)
#5 {main}

    Also i did try some commands in the CLI.

    Initially i got.

    mount -a

    mount: /export/data: mount(2) system call failed: Transport endpoint is not connected.

    I then did a umount.
    umount -l /srv/ae0f5928-3495-4ef8-9e08-3cfa3665428d

    but then mount -a reported different error.
    mount: /export/data: mount point does not exist.

    i don't know how to get my mergerfs mount to come back now. i have to reboot.

    IF there is a cheat sheet to follow or some guide for me to dig into the logs for troubleshooting mergerfs let me know.
    Just really want to note down the fixes in my notes.

    I feel so defeated having to reboot and not know why!. :(

  • Upgrade failed from 5.6.28 to 6.0 with "omv-release-upgrade"

    Awesome. well the gui is working it all looks cleaned up now.


    the drives are mounted. I have not rebooted yet. so that might make me a little nervious when i do. (af

    but thank you so much. I will be donating for sure when i get back from work tonight. I do appreciate the forum support!


    As these type of upgrades tend to make one a little nervous when it comes to data. :P

  • Upgrade failed from 5.6.28 to 6.0 with "omv-release-upgrade"

    Here are my results from running the scripts.

    fix5to6upgrade


    purge-union script


  • omv-extras plugins - porting progress to OMV 6.x (done)

    openmediavault-unionfilesystems - moving to openmediavault-mergerfs - done


    Even though i got latest updates to version 5.6.28
    It still shows

    Code
    ii  omvextras-unionbackend            5.0.2                        all          union filesystems backend plugin for openmediavault
ii  openmediavault-unionfilesystems   5.1.4                        all          Union filesystems plugin for OpenMediaVault.

    Am i supposed to install the new mergerFS plugin and then uninstall unionfilesystems before i upgrade to 6.0?
    The process is not clear.


    I simply looked at the plugin list and saw all my plugins listed as done or moved.

    So assumed omv-release-upgrade would do a clean upgrade

  • Upgrade failed from 5.6.28 to 6.0 with "omv-release-upgrade"

    I wanted to edit this in my post but i hit the character limit.

    How can i update unionbackend and unionfilesystem. I guess i was supposed to update them to new name of mergerfs?

    omv-release-upgrade is missing now. So not sure how best to update those now.

    Code
     dpkg -l | grep openm
ii  omvextras-unionbackend            5.0.2                        all          union filesystems backend plugin for openmediavault
iU  openmediavault                    6.0.20-1                     all          openmediavault - The open network attached storage solution
ii  openmediavault-keyring            1.0                          all          GnuPG archive keys of the OpenMediaVault archive
iU  openmediavault-luksencryption     6.0                          all          OpenMediaVault LUKS encryption plugin
iU  openmediavault-omvextrasorg       6.0.8                        all          OMV-Extras.org Package Repositories for OpenMediaVault
iU  openmediavault-snapraid           6.0.4                        all          snapraid plugin for OpenMediaVault.
ii  openmediavault-unionfilesystems   5.1.4                        all          Union filesystems plugin for OpenMediaVault.

  • Upgrade failed from 5.6.28 to 6.0 with "omv-release-upgrade"

    I got the latest updates for my OMV and rebooted it and everything was working fine. All my plugins seems to be on the approved list. Just using, luks, unionbackend, and snapraid,

    I typed the omv-release-upgrade and it failed. Here is what i could capture from my terminal.

    It fails when the collectd service fails to restart due to filename being too long. and then all the other packages after start to fail.


    Failed to restart collectd.service: Unit srv-ae0f5928\x2d3495\x2d4ef8\x2d9e08\x2d3cfa3665428d.mount failed to load properly: File name too long.


    Any ideas how to recover?

    Full code at the bottom.

  • LUKS + UnionFS

    I am doing a similar setup with luks and unionfs.


    adding nofail to the options of unionfs either in gui or fstab does allow the system to boot instead of crashing to emergency state.


    However after unlocking the luks encrypted drives the shared folder will not mount with nofail in the options of unionfs. I have to remove it and do a mount -a for shared folders to work gain.


    Any ideas on how to fix this? or a workaround?


    I really wanted to commit to encryption and get myself used to it.