Posts by GrgMdmn

  • Installing Nextcloud with OMV-compose

    Finally, I found how to solve my problem : I did not enable the mmap for my mergerfs pool so sqlite was unable to work correctly.


    I added this inside of the "options" field of my mergerfs pool : cache.files=partial,dropcacheonclose=true,category.create=mfs


    After reboot, everything is working fine. I found the instruction inside of the mergerfs doc :


    GitHub - trapexit/mergerfs: a featureful union filesystem
    a featureful union filesystem. Contribute to trapexit/mergerfs development by creating an account on GitHub.
    github.com

  • Installing Nextcloud with OMV-compose

    I have 5 4TB HDDS : 3 are merged on a mergerfs volume, and the 2 others are for parity, using SnapRAID. Is that a bad use/case ?


    What I want is to have my 12 TB pool available on Nextcloud so users can access this pool as a cloud... Should I proceed another way ?

  • Installing Nextcloud with OMV-compose

    Quote from Soma

    After installing OMV, the first user created will be id 1000.

    If you haven't created one, you are running OMV/Debian with the default system users.


    Go to users managment GUI and create one

    Thank you very much. I have created a user called appuser as proposed in the docker tutorial. I could restrict its accesses but I don't want for the moment since I do not want to complexify things on something that is already not working.


    Now, the folders seem to have the right user :

    Code
    root@madman-homelab-nas:~# ls -al /compose_settings/data/nextcloud/config
total 32
drwxr-sr-x 7 appuser 1000 4096 Jul 13 18:08 .
drwxr-sr-x 3 root    root 4096 Jul 13 18:08 ..
drwxr-sr-x 2 appuser 1000 4096 Jul 13 18:08 keys
drwxr-sr-x 4 appuser 1000 4096 Jul 13 18:08 log
-rw-r--r-- 1 root    root   48 Jul 13 18:08 .migrations
drwxrwsr-x 3 appuser 1000 4096 Jul 13 18:08 nginx
drwxr-sr-x 2 appuser 1000 4096 Jul 13 18:08 php
drwxr-sr-x 3 appuser 1000 4096 Jul 13 18:08 www

    However, I still have the same error when launching NextCloud :

    Quote from GrgMdmn

    I am now able to launch docker but I cannot set the admin logs : an error occurs : "Error while trying to initialise the database: An exception occurred while executing a query: SQLSTATE[HY000]: General error: 10 disk I/O error"

    I want to mention that there has never been any problem when keeping the default volumes configuration :

    Code
          - CHANGE_TO_COMPOSE_DATA_PATH/nextcloud/config:/config
      - CHANGE_TO_COMPOSE_DATA_PATH/nextcloud/data:/data

    But the main drive is not the right one. As soon as I replace CHANGE_TO_COMPOSE_DATA_PATH/nextcloud/data:/data with /srv/mergerfs/Main_NAS_Volume/Nextcloud:/data, then the container is broken...

  • Installing Nextcloud with OMV-compose

    I have created no USER with this "1000" id... Is omv-compose doing this when creating the Nextcloud container ? What should I do ?


    Here are my compose settings :


    I suppose the "1000" user is here in the Nextcloud configuration ?

  • Installing Nextcloud with OMV-compose

    Thanks for answering ! :)


    I have removed the shared folder, and all the folders linked to the nextcloud container.

    Code
    root@madman-homelab-nas:~# rm -r /srv/mergerfs/Main_NAS_Volume/Nextcloud/
root@madman-homelab-nas:~# rm -r /compose_settings/data/nextcloud/
root@madman-homelab-nas:~# rm -r /compose_settings/appdata/Nextcloud/

    I have removed the container itself, then added a new one.


    I am now able to launch docker but I cannot set the admin logs : an error occurs : "Error while trying to initialise the database: An exception occurred while executing a query: SQLSTATE[HY000]: General error: 10 disk I/O error"



    Here is the output of the ls -al commands you asked for :

  • Installing Nextcloud with OMV-compose

    Hello ! It seems that I am encountering a problem when installing Nextcloud with OMV-compose.


    When installing Nextcloud using "Add from Example" section, everything is working but the main drive is my ssd whereas I'd like my mergerFS volume (composed of 3 hdds) to be the main drive instead. In the compose settings, I have chosen CHANGE_TO_COMPOSE_DATA_PATH to be a path on my SSD.



    So I decided to modify the config file, changing CHANGE_TO_COMPOSE_DATA_PATH/nextcloud/data:/data with /srv/mergerfs/Main_NAS_Volume/Nextcloud:/data.

    I want to keep the config folder on the SSD as it is since the configuration can be changed many times, and using SSD for it is quicker and more power efficient.



    I've created the /srv/mergerfs/Main_NAS_Volume/Nextcloud folder inside of the "shared folders" section, and added "Read/Write" rights for "www-data" user.


    But now, after having cleaned the nextcloud files and reinstalling it with the config changes, nothing is working:


    My new folder does not seem to be accepted and I am almost sure the problem is linked to rights and sharing management but I don't really know how to solve this problem...

  • [SnapRAID] Missing 'parity' specification in '/etc/snapraid/omv-snapraid-f68c0a29-8e22-410d-8974-f50d43f4a511.conf'

    Thank you ! I already had asked google but maybe was I too impatient to have the information. Now I think that I have understood : split parity is useful when you have many disks that are not able to handle individually a parity. Splitting the parity helps distributing the parity and assembling disks to make a big enough volume that is now able to compute parity.


    I launched another sync, and I think everything is alright, now. I let you tell me if I am right :

  • [SnapRAID] Missing 'parity' specification in '/etc/snapraid/omv-snapraid-f68c0a29-8e22-410d-8974-f50d43f4a511.conf'

    Quote from gderf

    Why are you enabling Split Parity?


    You need a content file on at least one of the data disks; no reason not to have one on all of them.

    So what is the use for "split parity" ? :/


    Only setting "Parity nb : 1" and "Parity nb: 2" is enough to be able to recover from 2 dead HDDs ?


    So now, I checked "Content" for each drive (I don't really know why but I was asked to check "Content" for at least 3 drives), and I also added another drive only to make another content file save:


    Now I have used "sync" and here is what I have :

    I suppose there is no real problem since the disks are empty for now..?

  • [SnapRAID] Missing 'parity' specification in '/etc/snapraid/omv-snapraid-f68c0a29-8e22-410d-8974-f50d43f4a511.conf'

    Hi ! :)

    I am currently configuring MergerFS + SnapRAID with my 5 HDDs (4TB for each). 3 are intended as main volume and the remaining 2 are merged as a parity volume.


    Here is my mergerFS configuration for the two volumes :

    And now you can see my SnapRAID configuration (my aim is to have something equivalent as a RAID6 system, with recovery possibilities in cases of up to 2 disks failures):


    So my problem is that when using "Sync" feature, then I'm having an error message about missing parity information...

    Quote


    Missing 'parity' specification in '/etc/snapraid/omv-snapraid-f68c0a29-8e22-410d-8974-f50d43f4a511.conf'

    Do you have any idea of what did I wrong in my settings ?

  • BKHD-1264-NAS (Intel N100 mini-ITX)

    Quote from fravadd

    The link to download the bios files from the manufacturer's website does not work.

    Can someone tell me where I can download?

    I just wrote to the client service and they confirmed me that the url is not working. However, they gave me another that seems to be working. Please, if your fans are running at max speed before the BIOS update, tell me if the update solves this problem, because I have not made it yet :)


    The link :

    BKHD 1264 NAS – Google Drive


    Edit : the folder leads to the same BIOS I already have... I talked to the engineer that explained me that the PWM feature is not working on this motherboard yet and that is will eventually be handled in the future. But he did not give me any date.

  • [WireGuard] Client tab - DNS Server list is empty

    Hello ! I am encountering the exactly same problem... It happens wheter I am trying to use Wireguard or SnapRAID as scheduled task.


    Inside of the /etc/systemd/resolved.conf file, I changed FallbackDNS value to 127.0.0.1 ::1 just as Olivier did but it did not solve my probem. By the way, the DNS field is empty and commented.


    Here are the outputs I have :



    Could you please help me ? :)