Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. [BUG] Automount fail on reboot with Ubuntu 20.04

[BUG] Automount fail on reboot with Ubuntu 20.04

Scheduled Pinned Locked Moved Unsolved Support
20.04cifswebdav
52 Posts 8 Posters 8.3k Views 7 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • robiR robi

    @nebulon what about a retry after the initial failure after unbound loads?

    maybe add a mount -a at the end of the unbound script?

    JOduMonTJ Offline
    JOduMonTJ Offline
    JOduMonT
    wrote on last edited by
    #29

    @robi said in [BUG] Automount fail on reboot with Ubuntu 20.04:

    @nebulon what about a retry after the initial failure after unbound loads?
    maybe add a mount -a at the end of the unbound script?

    How disabling the IPv6 in Cloudron

    1 Reply Last reply
    0
    • JOduMonTJ JOduMonT

      @nebulon said in [BUG] Automount fail on reboot with Ubuntu 20.04:

      Instead of using the DNS name in the fstab entry, just use the IP

      I'm old school, I prefer IP 🙂
      So it is probably related to unbound-resolvconf no ?:

      Also on my side, by default my Hetzner NAS return me an IPv6, I didn't even know my Cloudron box as an IPv6 😛

      it is the same on your side ?

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #30

      @jodumont said in [BUG] Automount fail on reboot with Ubuntu 20.04:

      So it is probably related to unbound-resolvconf no ?:

      Issue is related to Cloudron. We have an internal DNS server (unbound) and it's configured in such a way that it has to start after docker (very tricky to make it start before docker). Unfortunately, because the DNS starts only after docker, it's a bit too late for services like network mounts which start before them. Which is why changing the mount from name based to IP makes it all work.

      I guess the fix is to change the way DNS server starts up but this is quite a complex task.

      1 Reply Last reply
      0
      • nebulonN nebulon

        To give some update, this is DNS related and how the init sequence works on 20.04 now.
        Problem is at the point when systemd decides to attempt to mount the remote filesystems, unbound, the dns resolver is not yet started. This means the remote fs cannot be mounted.

        There are currently two workarounds:

        1. Instead of using the DNS name in the fstab entry, just use the IP
        2. add x-systemd.automount as an additional argument for the mountpoint in the fstab entry

        Ideally we find a better flow by tweaking some of the init order in the future.

        For now I've added that option requirement at https://docs.cloudron.io/backups/#cifs

        JOduMonTJ Offline
        JOduMonTJ Offline
        JOduMonT
        wrote on last edited by
        #31

        @nebulon said in [BUG] Automount fail on reboot with Ubuntu 20.04:

        Instead of using the DNS name in the fstab entry, just use the IP

        • with IPv6 I have this error: /sbin/mount.davfs: invalid URL
        • with IPv4 I have this error: /sbin/mount.davfs: Mounting failed. 301 Moved Permanently
        girishG 1 Reply Last reply
        0
        • JOduMonTJ JOduMonT

          @nebulon said in [BUG] Automount fail on reboot with Ubuntu 20.04:

          Instead of using the DNS name in the fstab entry, just use the IP

          • with IPv6 I have this error: /sbin/mount.davfs: invalid URL
          • with IPv4 I have this error: /sbin/mount.davfs: Mounting failed. 301 Moved Permanently
          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #32

          @jodumont Oh.. maybe davfs requires the hostname because of vhost based configs! Can you try adding x-systemd.automount into the fstab entry instead?

          JOduMonTJ 1 Reply Last reply
          1
          • nebulonN nebulon

            To give some update, this is DNS related and how the init sequence works on 20.04 now.
            Problem is at the point when systemd decides to attempt to mount the remote filesystems, unbound, the dns resolver is not yet started. This means the remote fs cannot be mounted.

            There are currently two workarounds:

            1. Instead of using the DNS name in the fstab entry, just use the IP
            2. add x-systemd.automount as an additional argument for the mountpoint in the fstab entry

            Ideally we find a better flow by tweaking some of the init order in the future.

            For now I've added that option requirement at https://docs.cloudron.io/backups/#cifs

            JOduMonTJ Offline
            JOduMonTJ Offline
            JOduMonT
            wrote on last edited by JOduMonT
            #33

            @nebulon said in [BUG] Automount fail on reboot with Ubuntu 20.04:

            add x-systemd.automount as an additional argument for the mountpoint in the fstab entry

            🎺 adding x-systemd.automount, in /etc/fstab after _netdev, work well

            Thanks for all of you (but specially @nebulon); without your help, I would probably be crying in a corner

            1 Reply Last reply
            1
            • girishG girish

              @jodumont Oh.. maybe davfs requires the hostname because of vhost based configs! Can you try adding x-systemd.automount into the fstab entry instead?

              JOduMonTJ Offline
              JOduMonTJ Offline
              JOduMonT
              wrote on last edited by JOduMonT
              #34

              @girish said in [BUG] Automount fail on reboot with Ubuntu 20.04:

              @jodumont Oh.. maybe davfs requires the hostname because of vhost based configs! Can you try adding x-systemd.automount into the fstab entry instead?

              it worked for one or two reboot, than I started adding Volumes in my Cloudron (not really sure if it related) and I noticed it stop.

              • not on Cloudron, on my machine (but also Ubuntu 20.04LTS) it work well if I add user,noauto than mount it as a user.
              • on proxmox (Debian 10) it work well with x-system-d.automount

              Now CIFS or DAVFS2 with the option x-systemd.automount and even after I deleted all my Volumes in Cloudron WebUI have to same behavior (I need to login and do a mount -a)

              1 Reply Last reply
              0
              • robiR Offline
                robiR Offline
                robi
                wrote on last edited by
                #35

                The simpler solution would be to add the domains for mounts into the /etc/hosts file so no resolution is required.

                Conscious tech

                JOduMonTJ 1 Reply Last reply
                1
                • robiR robi

                  The simpler solution would be to add the domains for mounts into the /etc/hosts file so no resolution is required.

                  JOduMonTJ Offline
                  JOduMonTJ Offline
                  JOduMonT
                  wrote on last edited by JOduMonT
                  #36

                  @robi said in [BUG] Automount fail on reboot with Ubuntu 20.04:

                  The simpler solution would be to add the domains for mounts into the /etc/hosts file so no resolution is required.

                  where were you ?
                  it is interesting more the technology become complex
                  more we forget about simple solution which was the norm 30 years ago 🍕

                  FYI: I add both IPv6 and IPv4

                  robiR 1 Reply Last reply
                  0
                  • JOduMonTJ JOduMonT

                    @robi said in [BUG] Automount fail on reboot with Ubuntu 20.04:

                    The simpler solution would be to add the domains for mounts into the /etc/hosts file so no resolution is required.

                    where were you ?
                    it is interesting more the technology become complex
                    more we forget about simple solution which was the norm 30 years ago 🍕

                    FYI: I add both IPv6 and IPv4

                    robiR Offline
                    robiR Offline
                    robi
                    wrote on last edited by robi
                    #37

                    @jodumont said in [BUG] Automount fail on reboot with Ubuntu 20.04:

                    where were you ?

                    I am here. Funny you should mention it.
                    Lol, I went to get some pizza today and got inspired. 🍕
                    Sometimes all we need is a break and some perspective.
                    Maybe that's a superpower. 💪 😄 👍

                    FYI: I add both IPv6 and IPv4

                    Well done. Curious which it actually uses to connect.

                    Conscious tech

                    JOduMonTJ 1 Reply Last reply
                    0
                    • M Offline
                      M Offline
                      msbt
                      App Dev
                      wrote on last edited by
                      #38

                      the problem with the storagebox might be an ip change, hetzner specifically states

                      It is very important to use the DNS name (.your-storagebox.de) instead of the IP address for your Storage Box; this is because the IP address can change. With the DNS address, you can access your Storage Box via IPv4 and IPv6.

                      robiR JOduMonTJ 2 Replies Last reply
                      0
                      • M msbt

                        the problem with the storagebox might be an ip change, hetzner specifically states

                        It is very important to use the DNS name (.your-storagebox.de) instead of the IP address for your Storage Box; this is because the IP address can change. With the DNS address, you can access your Storage Box via IPv4 and IPv6.

                        robiR Offline
                        robiR Offline
                        robi
                        wrote on last edited by
                        #39

                        @msbt v4 addresses changing I can understand, but v6 generally don't change much at all.

                        Also odd that a storage box would have dynamic addressing. Is there any additional info on why it's not static?

                        Conscious tech

                        1 Reply Last reply
                        0
                        • nebulonN Offline
                          nebulonN Offline
                          nebulon
                          Staff
                          wrote on last edited by
                          #40

                          Using remote mounts also with volumes does add some possible race and inconsistency it looks like. So on Cloudron docker has to be started before unbound, now the remote mounting requires unbound for DNS resolving, however depending on how fast docker containers come up, they require volume mounts, which in turn, if depending on the remote mount points, we end up with some circular dependency.

                          The systemd automount would attempt to mount a remote once anything accesses the mountpoint. So if docker is quick enough and you have assigned some volumes from a mountpoint for a container, then again it would attempt to mount this before unbound is working.

                          For a start the automount will solve the issue of using a remote storage as a backup storage. When used with volumes, I think only using IPs will work for now.

                          JOduMonTJ 1 Reply Last reply
                          0
                          • M msbt

                            the problem with the storagebox might be an ip change, hetzner specifically states

                            It is very important to use the DNS name (.your-storagebox.de) instead of the IP address for your Storage Box; this is because the IP address can change. With the DNS address, you can access your Storage Box via IPv4 and IPv6.

                            JOduMonTJ Offline
                            JOduMonTJ Offline
                            JOduMonT
                            wrote on last edited by
                            #41

                            @msbt said in [BUG] Automount fail on reboot with Ubuntu 20.04:

                            the problem with the storagebox might be an ip change, hetzner specifically states

                            they obviously say that simply to cover their ass in case of an power interruption, I don't really see when that would happen in other case.

                            @msbt I'm curious to read the whole chapter, where did you found this info ?

                            M 1 Reply Last reply
                            0
                            • robiR robi

                              @jodumont said in [BUG] Automount fail on reboot with Ubuntu 20.04:

                              where were you ?

                              I am here. Funny you should mention it.
                              Lol, I went to get some pizza today and got inspired. 🍕
                              Sometimes all we need is a break and some perspective.
                              Maybe that's a superpower. 💪 😄 👍

                              FYI: I add both IPv6 and IPv4

                              Well done. Curious which it actually uses to connect.

                              JOduMonTJ Offline
                              JOduMonTJ Offline
                              JOduMonT
                              wrote on last edited by
                              #42

                              @robi said in [BUG] Automount fail on reboot with Ubuntu 20.04:

                              I am here. Funny you should mention it.
                              Lol, I went to get some pizza today and got inspired.

                              I eat pizza last tonight, still not really inspired, but I installed Windows 👽

                              1 Reply Last reply
                              1
                              • JOduMonTJ JOduMonT

                                @msbt said in [BUG] Automount fail on reboot with Ubuntu 20.04:

                                the problem with the storagebox might be an ip change, hetzner specifically states

                                they obviously say that simply to cover their ass in case of an power interruption, I don't really see when that would happen in other case.

                                @msbt I'm curious to read the whole chapter, where did you found this info ?

                                M Offline
                                M Offline
                                msbt
                                App Dev
                                wrote on last edited by
                                #43

                                @jodumont the word "hetzner" was a link to the docs where this is mentioned: https://docs.hetzner.com/robot/storage-box/general

                                1 Reply Last reply
                                1
                                • nebulonN nebulon

                                  Using remote mounts also with volumes does add some possible race and inconsistency it looks like. So on Cloudron docker has to be started before unbound, now the remote mounting requires unbound for DNS resolving, however depending on how fast docker containers come up, they require volume mounts, which in turn, if depending on the remote mount points, we end up with some circular dependency.

                                  The systemd automount would attempt to mount a remote once anything accesses the mountpoint. So if docker is quick enough and you have assigned some volumes from a mountpoint for a container, then again it would attempt to mount this before unbound is working.

                                  For a start the automount will solve the issue of using a remote storage as a backup storage. When used with volumes, I think only using IPs will work for now.

                                  JOduMonTJ Offline
                                  JOduMonTJ Offline
                                  JOduMonT
                                  wrote on last edited by
                                  #44

                                  @nebulon said in [BUG] Automount fail on reboot with Ubuntu 20.04:

                                  Using remote mounts also with volumes does add some possible race and inconsistency it looks like

                                  Not on the Cloudron side, but remotely NAS is in Germany, I'm in Bangkok I feel it and even for backup sometime the NAS is not available.

                                  1 Reply Last reply
                                  0
                                  • jdaviescoatesJ jdaviescoates

                                    @p44 I'm not having any problems. Streaming music off of my Hetzner Storage Box mounted as a Cloudron Volume and connected to my Navidrome app as I type.

                                    JOduMonTJ Offline
                                    JOduMonTJ Offline
                                    JOduMonT
                                    wrote on last edited by
                                    #45

                                    @jdaviescoates said in [BUG] Automount fail on reboot with Ubuntu 20.04:

                                    Streaming music off of my Hetzner Storage Box mounted as a Cloudron Volume and connected to my Navidrome app as I type.

                                    How it goes actually,
                                    I'm trying to mount some directory from the NAS as volumes in CLOUDRON but most of the time apps (mainly tried with Nextcloud) start before so then it mess everything up
                                    For now I mount it directly from Nextcloud interface but I can't share it with others apps.
                                    My goal would be

                                    1. saving money since 1TB is 10€ instead of 40€ if you build a volume of 1TB
                                    2. but also make apps interactive/sharing space such as: sync/uploading files with Nextcloud and make it available in Navidrome or Jellyfin
                                    3. I, aesthetically don't like to see the sharing arrow
                                      58467039-5c54-44a6-9ab6-173948711675-image.png

                                    @nebulon I wonder if it would be possible to transfer the mount volume principle inside the docker, at the container level ?
                                    such as every docker will be the samba/davfs2 client and retain the info in their /etc/fstab ??

                                    girishG 1 Reply Last reply
                                    0
                                    • JOduMonTJ JOduMonT

                                      @jdaviescoates said in [BUG] Automount fail on reboot with Ubuntu 20.04:

                                      Streaming music off of my Hetzner Storage Box mounted as a Cloudron Volume and connected to my Navidrome app as I type.

                                      How it goes actually,
                                      I'm trying to mount some directory from the NAS as volumes in CLOUDRON but most of the time apps (mainly tried with Nextcloud) start before so then it mess everything up
                                      For now I mount it directly from Nextcloud interface but I can't share it with others apps.
                                      My goal would be

                                      1. saving money since 1TB is 10€ instead of 40€ if you build a volume of 1TB
                                      2. but also make apps interactive/sharing space such as: sync/uploading files with Nextcloud and make it available in Navidrome or Jellyfin
                                      3. I, aesthetically don't like to see the sharing arrow
                                        58467039-5c54-44a6-9ab6-173948711675-image.png

                                      @nebulon I wonder if it would be possible to transfer the mount volume principle inside the docker, at the container level ?
                                      such as every docker will be the samba/davfs2 client and retain the info in their /etc/fstab ??

                                      girishG Offline
                                      girishG Offline
                                      girish
                                      Staff
                                      wrote on last edited by
                                      #46

                                      @jodumont I think you can raise this issue in Nextcloud forum to change the icon. TBH, I am not entirely sure why they are different icons. What does a normal user have to gain by knowing the distinction between a volume and a normal folder? Also, the arrow seems to suggest that it's going to pop up a new window or something, which I assume it doesn't.

                                      JOduMonTJ 1 Reply Last reply
                                      1
                                      • girishG girish

                                        @jodumont I think you can raise this issue in Nextcloud forum to change the icon. TBH, I am not entirely sure why they are different icons. What does a normal user have to gain by knowing the distinction between a volume and a normal folder? Also, the arrow seems to suggest that it's going to pop up a new window or something, which I assume it doesn't.

                                        JOduMonTJ Offline
                                        JOduMonTJ Offline
                                        JOduMonT
                                        wrote on last edited by
                                        #47

                                        @girish fair for the icons, and good point about open in a new tab
                                        but what about the sharing volume in Cloudron ?
                                        do you think would make sense to do the apps level or it will become too confusing and heavy on the system ?

                                        JOduMonTJ 1 Reply Last reply
                                        0
                                        • marcusquinnM Offline
                                          marcusquinnM Offline
                                          marcusquinn
                                          wrote on last edited by
                                          #48

                                          Those folder icons look like they are because they are shared folders.

                                          Web Design https://www.evergreen.je
                                          Development https://brandlight.org
                                          Life https://marcusquinn.com

                                          girishG 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Bookmarks
                                          • Search