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 9.1k 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.
  • jdaviescoatesJ Offline
    jdaviescoatesJ Offline
    jdaviescoates
    wrote on last edited by
    #14

    Possible related to this?

    SMB1 disabled by default: can still be enabled via a /etc/samba/smb.conf config change;

    https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Samba_4.11

    More info here:
    https://www.samba.org/samba/history/samba-4.11.0.html

    Found via https://askubuntu.com/questions/1229929/cant-acces-nas-anymore-after-upgrading-to-20-04

    I use Cloudron with Gandi & Hetzner

    JOduMonTJ 1 Reply Last reply
    1
    • jdaviescoatesJ jdaviescoates

      Possible related to this?

      SMB1 disabled by default: can still be enabled via a /etc/samba/smb.conf config change;

      https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Samba_4.11

      More info here:
      https://www.samba.org/samba/history/samba-4.11.0.html

      Found via https://askubuntu.com/questions/1229929/cant-acces-nas-anymore-after-upgrading-to-20-04

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

      @jdaviescoates said in My CIFS automount fail on reboot with Ubuntu 20.04:

      Possible related to this?

      thank for your reach, I'll definitely give a try to this and come back soon.

      1 Reply Last reply
      2
      • JOduMonTJ Offline
        JOduMonTJ Offline
        JOduMonT
        wrote on last edited by
        #16

        @jdaviescoates I just look at it
        and on Cloudron Samba server is not installed
        so nothing to configure in /etc/samba/* which actually don't even exist.

        WEBDAV

        I have the same behavior with webdav
        on reboot I have to login and do mount -a

        here the option for my davfs in /etc/fstab: rw,_netdev,uid=yellowtent,gid=yellowtent,file_mode=0660,dir_mode=0770 0 0
        I also tried with auto and defaults

        few people suggest to use rc.local

        1 Reply Last reply
        0
        • JOduMonTJ Offline
          JOduMonTJ Offline
          JOduMonT
          wrote on last edited by JOduMonT
          #17

          I just got an idea
          @nebulon
          it is possible than cloudron mount the volumes before my automount so then the target directory of my automount is not empty ?

          Also how could I destroy thoses volumes the GUI don't make it happen ?
          3d381110-ff30-443a-87bf-7dd22fc3d4c9-image.png

          JOduMonTJ 1 Reply Last reply
          0
          • JOduMonTJ JOduMonT

            I just got an idea
            @nebulon
            it is possible than cloudron mount the volumes before my automount so then the target directory of my automount is not empty ?

            Also how could I destroy thoses volumes the GUI don't make it happen ?
            3d381110-ff30-443a-87bf-7dd22fc3d4c9-image.png

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

            @jodumont said in My CIFS automount fail on reboot with Ubuntu 20.04:

            it is possible than cloudron mount the volumes before my automount so then the target directory of my automount is not empty ?

            nope, even without any volumes configured in Cloudron
            CIFS and WEBDAV won't mount automatically 😞

            1 Reply Last reply
            0
            • JOduMonTJ Offline
              JOduMonTJ Offline
              JOduMonT
              wrote on last edited by JOduMonT
              #19

              @nebulon and @girish

              I just copy the config (/etc/fstab and /etc/davfs2/secret) to my Ubuntu 20.04LTS Desktop
              and my webdav mount automatically on the reboot.

              So it seams to be a bug on the cloudron side.

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

                Cloudron itself does not handle any mount points as such. So this looks like this is some issue with 20.04 server then. Note that the desktop flavor has a lot more things installed usually, which may or may not trigger automounting correctly.

                JOduMonTJ 1 Reply Last reply
                0
                • nebulonN nebulon

                  Cloudron itself does not handle any mount points as such. So this looks like this is some issue with 20.04 server then. Note that the desktop flavor has a lot more things installed usually, which may or may not trigger automounting correctly.

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

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

                  Cloudron itself does not handle any mount points as such. So this looks like this is some issue with 20.04 server then. Note that the desktop flavor has a lot more things installed usually, which may or may not trigger automounting correctly.

                  I have no doubt of the quality of coding from the Cloudron Team
                  but I just boot an ubuntu 20.04 LTS at Hetzner
                  did

                  apt update
                  apt install -y davfs2
                  mkdir /mnt/storagebox
                  

                  than cut and past my 2 lines
                  1 from /etc/fstab
                  1 for /etc/davfs2/secret

                  reboot and it work

                  so yes Ubuntu Desktop have probably more fuse than server but now the only difference is Cloudron.

                  nebulonN 1 Reply Last reply
                  0
                  • JOduMonTJ JOduMonT

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

                    Cloudron itself does not handle any mount points as such. So this looks like this is some issue with 20.04 server then. Note that the desktop flavor has a lot more things installed usually, which may or may not trigger automounting correctly.

                    I have no doubt of the quality of coding from the Cloudron Team
                    but I just boot an ubuntu 20.04 LTS at Hetzner
                    did

                    apt update
                    apt install -y davfs2
                    mkdir /mnt/storagebox
                    

                    than cut and past my 2 lines
                    1 from /etc/fstab
                    1 for /etc/davfs2/secret

                    reboot and it work

                    so yes Ubuntu Desktop have probably more fuse than server but now the only difference is Cloudron.

                    nebulonN Offline
                    nebulonN Offline
                    nebulon
                    Staff
                    wrote on last edited by
                    #22

                    thanks for testing, so then probably one of the dependencies we install, somehow changes either the init order or even disables some bits there. Looks like we have to debug this further then on fresh installations to get some more information what systemd does differently in both scenarios.

                    JOduMonTJ 1 Reply Last reply
                    0
                    • nebulonN nebulon

                      thanks for testing, so then probably one of the dependencies we install, somehow changes either the init order or even disables some bits there. Looks like we have to debug this further then on fresh installations to get some more information what systemd does differently in both scenarios.

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

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

                      Looks like we have to debug this further then on fresh installations to get some more information what systemd does differently in both scenarios.

                      I'll run an fresh install of Cloudron than install davfs2 just to be sure

                      JOduMonTJ 1 Reply Last reply
                      0
                      • JOduMonTJ JOduMonT

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

                        Looks like we have to debug this further then on fresh installations to get some more information what systemd does differently in both scenarios.

                        I'll run an fresh install of Cloudron than install davfs2 just to be sure

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

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

                        I'll run an fresh install of Cloudron than install davfs2 just to be sure

                        so boot up a new instance Ubuntu 20.04 LTS @Hetzner
                        ran

                        wget https://cloudron.io/cloudron-setup
                        chmod +x ./cloudron-setup
                        ./cloudron-setup
                        

                        reboot than install davfs2 apt install -y davfs2
                        and configure /etc/fstab and /etc/davfs2/secrets
                        reboot

                        it don't mount automatically
                        but mount without issue with mount -a

                        nebulonN 1 Reply Last reply
                        0
                        • JOduMonTJ JOduMonT

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

                          I'll run an fresh install of Cloudron than install davfs2 just to be sure

                          so boot up a new instance Ubuntu 20.04 LTS @Hetzner
                          ran

                          wget https://cloudron.io/cloudron-setup
                          chmod +x ./cloudron-setup
                          ./cloudron-setup
                          

                          reboot than install davfs2 apt install -y davfs2
                          and configure /etc/fstab and /etc/davfs2/secrets
                          reboot

                          it don't mount automatically
                          but mount without issue with mount -a

                          nebulonN Offline
                          nebulonN Offline
                          nebulon
                          Staff
                          wrote on last edited by
                          #25

                          @jodumont I was able to reproduce this now also outside of hetzner on 20.04...not yet sure why and what causes the difference

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

                            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

                            robiR JOduMonTJ 4 Replies Last reply
                            2
                            • 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

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

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

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

                              Conscious tech

                              JOduMonTJ 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
                                #28

                                @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 1 Reply Last reply
                                0
                                • 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
                                          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