Permission denied during server boot when mounting /export/ folders

  • Hello everyone,


    First poster here, and I decided to join the community as, unfortunately, I have a problem.
    I am facing an issue with fstab mounting, so here I come, seeking guidance.


    Following a bad partitioning, I have broken my previous OMV 2 installation. So be it then, that was a good oppotunity to switch to OMV3.
    So I am remaking my system from scratch.
    That means I have a basic OMV installation. I have only created a couple users, mounted my different partitions and set them as shared folders for NFS.


    This is what my /etc/fstab looks like at the moment:






    At boot, the mounting of the /export/ folders fails because of permission denied.
    It works correctly when I manually do a "mount -a" (via SSH).


    Here are the current permission for the initial and /export/ folders:

    Code
    drwxr-sr-x 4 root nas     4096 juin  25 19:53 dev-disk-by-id-ata-Crucial_CT275MX300SSD1_16431465C41E-part3
    drwxrwsr-x 6 root nas     4096 juin  25 18:11 dev-disk-by-id-ata-WDC_WD40EFRX-68WT0N0_WD-WCC4EKDH4L8K-part1
    drwx------ 2 root root    4096 juin  25 19:52 dev-disk-by-id-ata-WDC_WD60EFRX-68MYMN1_WD-WXL1H840CSYU-part1
    drwx------ 2 root root    4096 juin  25 19:52 dev-disk-by-id-ata-WDC_WD60EFRX-68MYMN1_WD-WXL1H840CSYU-part2
    drwxr-xr-x 2 ftp  nogroup 4096 juin  25 19:39 ftp


    Code
    drwx------ 2 root root 4096 juin  25 20:06 Audio
    drwx------ 2 root root 4096 juin  25 20:06 Files
    drwx------ 2 root root 4096 juin  25 20:06 Movies
    drwx------ 2 root root 4096 juin  25 20:06 Series
    drwxr-xr-x 2 root root 4096 juin  25 21:46 temp


    So I am aware that I have a permission to change here, but I don't know which one.
    Normally the mounting during boot is executed as root, so normally all the folders have the necessary permissions.


    So thanks in advance for your clarifications.

    • Offizieller Beitrag

    How do you know you get permission denied?
    Maybe post in a link the boot log (install curl first)


    journalctl | curl -F 'sprunge=<-' http://sprunge.us


    Try this deactivate, all services, comment (#) all fstab lines from in between openmediavault tags and boot again. You might have non empty folders in /export or even in /media

  • Thanks for your answer.
    I forgot to add the boot log, sorry for that. Here is the error:

    Code
    2017-06-27T08:33:30+0200 library systemd[1]: Cannot add dependency job for unit export-Series.mount, ignoring: Unit export-Series.mount failed to load: Operation not permitted. See system logs and 'systemctl status export-Series.mount' for details.
    2017-06-27T08:33:30+0200 library systemd[1]: Cannot add dependency job for unit export-Movies.mount, ignoring: Unit export-Movies.mount failed to load: Operation not permitted. See system logs and 'systemctl status export-Movies.mount' for details.
    2017-06-27T08:33:30+0200 library systemd[1]: Cannot add dependency job for unit export-Files.mount, ignoring: Unit export-Files.mount failed to load: Operation not permitted. See system logs and 'systemctl status export-Files.mount' for details.
    2017-06-27T08:33:30+0200 library systemd[1]: Cannot add dependency job for unit export-Audio.mount, ignoring: Unit export-Audio.mount failed to load: Operation not permitted. See system logs and 'systemctl status export-Audio.mount' for details.


    With the systemctl:


    Code
    Loaded: error (Reason: Operation not permitted)
       Active: inactive (dead)
        Where: /export/Movies
         What: /srv/dev-disk-by-id-ata-WDC_WD40EFRX-68WT0N0_WD-WCC4EKDH4L8K-part1/.
         Docs: man:fstab(5)
               man:systemd-fstab-generator(8)


    journalctl gives me no journal found, I guess I have to activate something ?


    After unmounting, all folders are empty in /srv/, /export/ or /media/ (I only have a cdrom folder there).

  • No, sorry too, I still get "no journal files were found."


    boot.txt
    I have these messages before the failures, that may be the cause:

    Code
    2017-06-28T19:29:15+0200 library systemd-fstab-generator[202]: Checking was requested for "/srv/dev-disk-by-id-ata-WDC_WD60EFRX-68MYMN1_WD-WXL1H840CSYU-part2/.", but it is not a device.
    2017-06-28T19:29:15+0200 library systemd-fstab-generator[202]: Checking was requested for "/srv/dev-disk-by-id-ata-Crucial_CT275MX300SSD1_16431465C41E-part3/.", but it is not a device.
    2017-06-28T19:29:15+0200 library systemd-fstab-generator[202]: Checking was requested for "/srv/dev-disk-by-id-ata-WDC_WD40EFRX-68WT0N0_WD-WCC4EKDH4L8K-part1/.", but it is not a device.
    2017-06-28T19:29:15+0200 library systemd-fstab-generator[202]: Checking was requested for "/srv/dev-disk-by-id-ata-WDC_WD60EFRX-68MYMN1_WD-WXL1H840CSYU-part1/.", but it is not a device.
    2017-06-28T19:29:15+0200 library systemd[1]: Cannot add dependency job for unit export-Series.mount, ignoring: Unit export-Series.mount failed to load: Operation not permitted. See system logs and 'systemctl status export-Series.mount' for details.
    2017-06-28T19:29:15+0200 library systemd[1]: Cannot add dependency job for unit export-Movies.mount, ignoring: Unit export-Movies.mount failed to load: Operation not permitted. See system logs and 'systemctl status export-Movies.mount' for details.
    2017-06-28T19:29:15+0200 library systemd[1]: Cannot add dependency job for unit export-Files.mount, ignoring: Unit export-Files.mount failed to load: Operation not permitted. See system logs and 'systemctl status export-Files.mount' for details.
    2017-06-28T19:29:15+0200 library systemd[1]: Cannot add dependency job for unit export-Audio.mount, ignoring: Unit export-Audio.mount failed to load: Operation not permitted. See system logs and 'systemctl status export-Audio.mount' for details.
  • Alright, I think I managed to solve my issue here.


    I had 2 partitions formatted in NTFS, that seemed to throw the install off. So I reformatted them to ext4.


    I had to restart the installation, there was some conflict afterwards, but once everything was set, I didn't have this issue anymore.


    So solved, I guess.
    Conclusion: Avoid NTFS partitions. Doesn't seem to work that great.

Jetzt mitmachen!

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