mergerfs after upgrade to OMV 3 not accessable

Firefly · 25. Juni 2017

Hi,

with OMV 2 I was using 4HDDs with mergerfs to store my data and access it via samba share. After upgrading to OMV 3 something went totally wrong and i can not access my share (sorry if the Menus are not named correctly, but I am using german language)). Under "Union-Filesystem" everything is as expected, 4 HDDs combined unter the name "Data".

In "Filesystem" the drive "data has the same size like the system drive.

Output of: omv-showkey unionfilesystems
<unionfilesystems>
<pools>

</pools>
<filesystem>
<uuid>72b1b9aa-2f4f-47c8-a2b4-d4dc535f72e1</uuid>
<name>data</name>
<options>defaults,allow_other,direct_io,use_ino</options>
<self-mntentref>a2a045b0-bb11-4a6b-b272-6908c557318f</self-mntentref>
<mntentref>6248b30e-7450-4df4-94c0-34312731a28f</mntentref>
<mntentref>cab4fc4c-29e9-4b7a-9c82-4311447e5f63</mntentref>
<mntentref>fc61f663-780d-48b3-8a2e-224a5e05862f</mntentref>
<mntentref>86be82d7-57b3-4eab-a95f-b50db16694f7</mntentref>
<create-policy>epmfs</create-policy>
<min-free-space>4G</min-free-space>
</filesystem>
</unionfilesystems>

Hopefully someone has an idea

gderf · 25. Juni 2017

Can you post the contents of your /etc/fstab file?

Firefly · 25. Juni 2017

Sure

Code

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=1c0a80e5-566a-4876-9a2d-d097230b489b /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=01e88b6c-dd93-4765-8293-72295418341f none            swap    sw              0       0
/dev/sdb1       /media/usb0     auto    rw,user,noauto  0       0
# >>> [openmediavault]
UUID=cd1913e5-5bba-4529-a562-6e042cf29b10 /media/cd1913e5-5bba-4529-a562-6e042cf29b10 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
UUID=f9db61cb-8e28-41ac-a421-a1c910d2c951 /media/f9db61cb-8e28-41ac-a421-a1c910d2c951 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
UUID=4009a0bd-cd8d-41b9-97b8-77f0ee536666 /media/4009a0bd-cd8d-41b9-97b8-77f0ee536666 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
UUID=2e0dd4b2-dc30-4fce-8ffc-19be3d66b398 /media/2e0dd4b2-dc30-4fce-8ffc-19be3d66b398 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
UUID=32b085dc-67ca-4063-9b6e-a753de60b099 /media/32b085dc-67ca-4063-9b6e-a753de60b099 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
UUID=d2b05b8e-60cd-47e9-8c70-ea1c12c22f82 /media/d2b05b8e-60cd-47e9-8c70-ea1c12c22f82 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
none /media/72b1b9aa-2f4f-47c8-a2b4-d4dc535f72e1 aufs br:/media/cd1913e5-5bba-4529-a562-6e042cf29b10=rw:/media/f9db61cb-8e28-41ac-a421-a1c910d2c951=rw:/media/4009a0bd-cd8d-41b9-97b8-77f0ee536666=rw:/media/2e0dd4be0dd4b2-dc30-4fce-8ffc-19be3d66b398=rw,sum,create=mfs 0 0


# <<< [openmediavault]

Alles anzeigen

gderf · 25. Juni 2017

It looks like your OMV 2 had an aufs pool of drives. I am saying this from what I see on line 20 of your fstab file.

aufs is not supported in OMV 3, so that line can not work. I have no idea if the upgrade from OMV2 to OMV 3 was supposed to translate that line into one for a mergerfs pool, but I would not be surprised if that conversion is not supported, I just don't know one way or the other.

I suggest that you comment that line out for now. You can delete it later once you get your pool reestablished. You will have to recreate the pool in the Storage | Union Filesystems panel.

Should be a very straight forward procedure.

Firefly · 26. Juni 2017

Will my files be safe while recreating?

gderf · 26. Juni 2017

Zitat von Firefly

Will my files be safe while recreating?

Yes. It doesn't touch the drives.

Firefly · 26. Juni 2017

Hi,
first of all, thanks for your support. I was able to delete the entry in the fstabs and recreate the Union-Filesystem with the drives. But the old "Shared Folder" of "data" is still in the list and I can not delete it to recreate the new one.
I cant delete it and trying to edit it..

Code

Failed to execute XPath query '//system/fstab/mntent[uuid='a2a045b0-bb11-4a6b-b272-6908c557318f']'.


Fehler #0:
exception 'OMV\Config\DatabaseException' with message 'Failed to execute XPath query '//system/fstab/mntent[uuid='a2a045b0-bb11-4a6b-b272-6908c557318f']'.' in /usr/share/php/openmediavault/config/database.inc:78
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/sharemgmt.inc(231): OMV\Config\Database->get('conf.system.fil...', 'a2a045b0-bb11-4...')
#1 [internal function]: OMVRpcServiceShareMgmt->get(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('get', Array, Array)
#4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('ShareMgmt', 'get', Array, Array, 1)
#5 {main}

Alles anzeigen

Jetzt mitmachen!