BTRFS disk pool mounted not showing in webui

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • BTRFS disk pool mounted not showing in webui

      Hi all,

      Recently I've updated to OMV4 and I've noticed that my BTRFS disk pool is not showing correctly in the WebUI.
      In the attached image MountStatus you can see that my 3 disk pool is showing NO in mount status. The problem is that the pool is really mounted. I have some folders shared with samba in this pool and I can read and write on them.
      If I click on MOUNT button in the WebUI it throws an error saying that is already mounted..

      btrfs fi show, blkid and lsblk -f show that "Almacen" is mounted... (see outputs attached)
      In the System Log you can see that there is an error message arising each 30secs...

      Anyone can imagine what is happening?

      At same time I noticed that I have lost two dockers container that was working correctly and their images. I cannot download new docker images... (I am not sure that these errors are interrelated , but I've notice them at same time and the docker configs files are stored in the btrfs pool).

      I would appreciate any help you can give me.
      Thanks in Advance.
      Manuel J. Ortega
      • MountStatus.png

        18.68 kB, 937×249, viewed 113 times
      • MountingError.png

        61.47 kB, 1,491×671, viewed 91 times
      • Putty.txt

        (2.16 kB, downloaded 48 times, last: )
      • syslog.txt

        (535.26 kB, downloaded 47 times, last: )
    • thewer wrote:

      Hi there,

      I think it could be the same problem I had with the encrypted drive -
      for OMV4 drives need to be mounted to /srv/dev-disk-by-label-XYZ (XYZ obviously the label of your drive)..
      Hi thewer,

      My btrfs pool is mounted and accesed via /media/XXXXXX/. This is the path used by all the system (shared folders, plugins, tc.), but it is also mounted at /srv/dev-disk-by-label-Almacen, as you can see in the df output... (line 11). I can access it via ssh and this path.

      Source Code

      1. root@NAS:~# df
      2. S.ficheros bloques de 1K Usados Disponibles Uso% Montado en
      3. udev 3898164 0 3898164 0% /dev
      4. tmpfs 783264 92436 690828 12% /run
      5. /dev/sda1 60675128 32317812 25252088 57% /
      6. tmpfs 3916308 0 3916308 0% /dev/shm
      7. tmpfs 5120 0 5120 0% /run/lock
      8. tmpfs 3916308 0 3916308 0% /sys/fs/cgroup
      9. tmpfs 3916308 12 3916296 1% /tmp
      10. /dev/sda3 234240888 77202620 145116452 35% /media/ef6c2291-292f-43d6-a853-dcded158f6b8
      11. /dev/sdc 7814047752 6463225308 303606596 96% /srv/dev-disk-by-label-Almacen
      12. overlay 60675128 32317812 25252088 57% /var/lib/docker/overlay2/d14e1347b2e40764d8de090849c651dc5cbaaa6cf3da70776897cf70f3974106/merged
      13. shm 65536 0 65536 0% /var/lib/docker/containers/d469ebbf6cea6f9e2c58a43f11c88ba93d4a59f7e0244a47412e73f031d79827/mounts/shm
      14. overlay 60675128 32317812 25252088 57% /var/lib/docker/overlay2/7b6fa438111440cf10fa0e94402bd38e9200db8ccda031a0d2659cdc3746d1dc/merged
      15. shm 65536 4 65532 1% /var/lib/docker/containers/be9f23e924d9eca8e44bc6ac33941ab6a36f114c30467f67c5ad55332329d937/mounts/shm
      16. root@NAS:~#
      Display All
      It seem like OMV is not being aware that the pool is already mounted. (The error thrown when trying to mount form webui points in that way) (see image in first post).

      On the other hand... lsblk -f output shows the pool mounting point at sdc (the pool has three hdds: sdb, sdc & sdd), but the error gived by the OMV webui mount command shows that cannot mount sdb...

      May be the problem related with this?
    • I really don't know much about Btrfs, but I would guess sdb, sdc and sdd all have the same UUID, only different UUID_SUBs…
      OMV sees them as a single pool with a single label and cannot mount them to the default address because sdc is already mounted there or because sdb can't...

      I think running blkid before creating the pool gives them unique UUIDs? Or unmounting sdb and mounting of them?