no access to File Systems

  • Hello,


    I urgently need your help, so any suggestion is appreciated!


    I decided to reinstall my OMV setup from scratch and after it was done, I can't access the File Systems. All Physical Disks (BTRFS, no RAID) are loaded but when I go to File Systems after a long loading phase I get an Error: "communication failure".


    Already reinstalled it on different devices - USB 3.0 HDD and USB 2.0 flash drive but always the same issue. I really need your help!

  • No, that did not helped.


    I downloaded the latest stable version (3.0.94-amd64) today and installed from USB drive - created with Etcher.


    Hardware that I'm using:
    ASRock J3160DC, Crucial 8GB RAM, 3x WD Red HDD's

  • can you access the file systems from a terminal?

    How can I do that?
    *edit: Do you mean if they are visible at /srv/...? No I can't. But I think therefore I have to mount them first, right?


    Kernel should be 4.9.


    Before that reinstall I used my OMV installation from December 2017 and there I created my BTRFS disks. So that should not be a problem for OMV or am I wrong?

  • If you are running 4.9 kernel that should be good i would think...
    I'm probably wrong but I was thinking the default kernel for omv3 was 3.16, but maybe that was the default debian jessie kernel since I installed jessie, then omv on top of it. Anyway.....


    what does lsblk or blkid command show?

  • Here are the outputs:

    Code
    /dev/sda1: LABEL="DISK1" UUID="2c323d25-ccbe-43a0-895f-ad0c43c28fd3" UUID_SUB="6d5b7e3f-574c-492e-8efc-1ce9c20cd8c0" TYPE="btrfs" PARTUUID="d336f7af-b822-4364-9c96-9cc8545e81ba"
    /dev/sdb1: LABEL="DISK3" UUID="b17a47ab-9851-47bd-a832-3f5f55960547" UUID_SUB="3c6ea61a-992e-4d1a-9a06-f0e8fbcb3d91" TYPE="btrfs" PARTUUID="b017634d-d9f3-42c4-aade-6ace46f03ff3"
    /dev/sdc1: LABEL="DISK2" UUID="95f87669-bcdd-4a93-8865-c91ecceb0dba" UUID_SUB="fb75640d-e996-4cd7-89c4-1dc6cadc1c80" TYPE="btrfs" PARTUUID="3095794c-5240-4a89-b41e-7d4e91dc4a58"
    /dev/sdd1: UUID="b34cfa23-09ae-43c2-b692-4af987fd66ff" TYPE="ext4" PARTUUID="cf6a0309-01"
    /dev/sdd5: UUID="e151c16e-a294-4cad-a084-1915f157a0f8" TYPE="swap" PARTUUID="cf6a0309-05"
  • @jollyrogr
    You brought me to the idea to edit fstab adding my disks manually. Now it's working! The disks were successfully mounted and now I curiously can access the File Systems menu, too.


    Somebody knows what could be the reason for that behavior?

  • No, I already tried to unmount them from the WebUI but it did not work (I think because of permissions?). Then I unmounted them via the cli and had again no access to the File Systems menu.


    Now I've added my disks manually into my OMV config, using the uuid's from blkid and it seems that it works (Shared Folders as well). I'll test a little bit around and give then a feedback.


    But it's still strange to me why this problem exists with the non accessible File Systems menu.

  • Yes, see my answer above. I edited the OMV config and it works for now. I'll check if that workaround just works without any consequences.


    But it would be great if somebody knows a "real" solution for that problem.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!