nfs-kernel-server starts too early












3















I have an RPI-based NFS server with an external USB hard disk. After a recent upgrade to Raspbian 8.0 and systemd I noticed that now nfs-kernel-server seems to be starting before all file systems on the external disk are mounted:




Jun 29 12:01:33 nas nfs-kernel-server[369]: Exporting directories for NFS kernel daemon...exportfs: Failed to stat ▒▒▒▒▒▒▒▒▒▒(redacted): No such file or directory




The nfs-kernel-server has a sysV startup script in /etc/init.d. I tried adding $local_fs to the list of its requirements, but it did not help. I would really appreciate any suggestions on how to fix this.



(I also see smartd starting before the udev tree is fully populated, but I'll save that for another question.)










share|improve this question
















bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    3















    I have an RPI-based NFS server with an external USB hard disk. After a recent upgrade to Raspbian 8.0 and systemd I noticed that now nfs-kernel-server seems to be starting before all file systems on the external disk are mounted:




    Jun 29 12:01:33 nas nfs-kernel-server[369]: Exporting directories for NFS kernel daemon...exportfs: Failed to stat ▒▒▒▒▒▒▒▒▒▒(redacted): No such file or directory




    The nfs-kernel-server has a sysV startup script in /etc/init.d. I tried adding $local_fs to the list of its requirements, but it did not help. I would really appreciate any suggestions on how to fix this.



    (I also see smartd starting before the udev tree is fully populated, but I'll save that for another question.)










    share|improve this question
















    bumped to the homepage by Community 11 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      3












      3








      3


      1






      I have an RPI-based NFS server with an external USB hard disk. After a recent upgrade to Raspbian 8.0 and systemd I noticed that now nfs-kernel-server seems to be starting before all file systems on the external disk are mounted:




      Jun 29 12:01:33 nas nfs-kernel-server[369]: Exporting directories for NFS kernel daemon...exportfs: Failed to stat ▒▒▒▒▒▒▒▒▒▒(redacted): No such file or directory




      The nfs-kernel-server has a sysV startup script in /etc/init.d. I tried adding $local_fs to the list of its requirements, but it did not help. I would really appreciate any suggestions on how to fix this.



      (I also see smartd starting before the udev tree is fully populated, but I'll save that for another question.)










      share|improve this question
















      I have an RPI-based NFS server with an external USB hard disk. After a recent upgrade to Raspbian 8.0 and systemd I noticed that now nfs-kernel-server seems to be starting before all file systems on the external disk are mounted:




      Jun 29 12:01:33 nas nfs-kernel-server[369]: Exporting directories for NFS kernel daemon...exportfs: Failed to stat ▒▒▒▒▒▒▒▒▒▒(redacted): No such file or directory




      The nfs-kernel-server has a sysV startup script in /etc/init.d. I tried adding $local_fs to the list of its requirements, but it did not help. I would really appreciate any suggestions on how to fix this.



      (I also see smartd starting before the udev tree is fully populated, but I'll save that for another question.)







      systemd nfs startup raspbian






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 29 '15 at 6:51









      G-Man

      13.1k93465




      13.1k93465










      asked Jun 29 '15 at 6:20









      kolbusakolbusa

      163




      163





      bumped to the homepage by Community 11 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 11 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          2 Answers
          2






          active

          oldest

          votes


















          0














          In /etc/fstab you can try to add x-systemd.before=nfs-kernel-server.service as option to the mount maybe?






          share|improve this answer

































            -1














            You could try to add a sleep to the nfs-kernel-server script.



            Open up the script with:



            $ sudo vim /etc/init.d/nfs-kernel-server


            Scroll down and find the start() section (it's usally under the first case) and add a sleep for 30 seconds under start:



            sleep 30


            Save and exit.






            share|improve this answer


























            • Thanks. That's will be the hack of the last resort. I did not loose hope yet to find a solution...

              – kolbusa
              Jun 29 '15 at 8:24











            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f212785%2fnfs-kernel-server-starts-too-early%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            In /etc/fstab you can try to add x-systemd.before=nfs-kernel-server.service as option to the mount maybe?






            share|improve this answer






























              0














              In /etc/fstab you can try to add x-systemd.before=nfs-kernel-server.service as option to the mount maybe?






              share|improve this answer




























                0












                0








                0







                In /etc/fstab you can try to add x-systemd.before=nfs-kernel-server.service as option to the mount maybe?






                share|improve this answer















                In /etc/fstab you can try to add x-systemd.before=nfs-kernel-server.service as option to the mount maybe?







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Mar 24 '18 at 8:54

























                answered Mar 24 '18 at 8:40









                BigonBigon

                1,257713




                1,257713

























                    -1














                    You could try to add a sleep to the nfs-kernel-server script.



                    Open up the script with:



                    $ sudo vim /etc/init.d/nfs-kernel-server


                    Scroll down and find the start() section (it's usally under the first case) and add a sleep for 30 seconds under start:



                    sleep 30


                    Save and exit.






                    share|improve this answer


























                    • Thanks. That's will be the hack of the last resort. I did not loose hope yet to find a solution...

                      – kolbusa
                      Jun 29 '15 at 8:24
















                    -1














                    You could try to add a sleep to the nfs-kernel-server script.



                    Open up the script with:



                    $ sudo vim /etc/init.d/nfs-kernel-server


                    Scroll down and find the start() section (it's usally under the first case) and add a sleep for 30 seconds under start:



                    sleep 30


                    Save and exit.






                    share|improve this answer


























                    • Thanks. That's will be the hack of the last resort. I did not loose hope yet to find a solution...

                      – kolbusa
                      Jun 29 '15 at 8:24














                    -1












                    -1








                    -1







                    You could try to add a sleep to the nfs-kernel-server script.



                    Open up the script with:



                    $ sudo vim /etc/init.d/nfs-kernel-server


                    Scroll down and find the start() section (it's usally under the first case) and add a sleep for 30 seconds under start:



                    sleep 30


                    Save and exit.






                    share|improve this answer















                    You could try to add a sleep to the nfs-kernel-server script.



                    Open up the script with:



                    $ sudo vim /etc/init.d/nfs-kernel-server


                    Scroll down and find the start() section (it's usally under the first case) and add a sleep for 30 seconds under start:



                    sleep 30


                    Save and exit.







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Jun 29 '15 at 7:59

























                    answered Jun 29 '15 at 7:52









                    krtkrt

                    70548




                    70548













                    • Thanks. That's will be the hack of the last resort. I did not loose hope yet to find a solution...

                      – kolbusa
                      Jun 29 '15 at 8:24



















                    • Thanks. That's will be the hack of the last resort. I did not loose hope yet to find a solution...

                      – kolbusa
                      Jun 29 '15 at 8:24

















                    Thanks. That's will be the hack of the last resort. I did not loose hope yet to find a solution...

                    – kolbusa
                    Jun 29 '15 at 8:24





                    Thanks. That's will be the hack of the last resort. I did not loose hope yet to find a solution...

                    – kolbusa
                    Jun 29 '15 at 8:24


















                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f212785%2fnfs-kernel-server-starts-too-early%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    CARDNET

                    Boot-repair Failure: Unable to locate package grub-common:i386

                    濃尾地震