Not mounting after restart?












1















I am mounting a drive via SSH, and then editing the fstab to reflect the changes, however after I reboot, the drive doesnt mount?



I dont understand what I'm doing wrong?



This is my fstab and its /md0 that isnt mounting after reboot, am I missing something?



# <file system> <mount point>   <type>  <options>   <dump>  <pass>
/dev/md4 / ext3 errors=remount-ro,usrjquota=quota.user,jqfmt=vfsv0 0 1
/dev/md0 /BACKUP ext3 defaults 0 1
/dev/md1 /boot ext3 errors=remount-ro 0 1
/dev/md2 /var/tmp ext3 usrjquota=quota.user,jqfmt=vfsv0 1 2
/dev/sda3 swap swap defaults 0 0
/dev/sdb3 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0









share|improve this question


















  • 1





    Is the network started and ssh running by the time the system goes through fstab?

    – schaiba
    Mar 3 '13 at 18:26











  • hi, im not sure if ssh running by that time, i wouldnt have thought so?

    – Mike Meade
    Mar 3 '13 at 21:35











  • /dev/mdX is supposed to be a RAID device - is it properly created during boot? It usually requires you to have at least mdadm --auto-detect run before you can use it (and supposing you have created the RAD with a superblock that can be detected).

    – peterph
    Mar 3 '13 at 21:53






  • 1





    The output of grep --after-context=3 -- md0 /proc/mdstat, please.

    – Hauke Laging
    Mar 4 '13 at 0:27











  • You have not even specified an OS - different OS' have different fstab formats. Please help us avoid guessing, and timestamp your questions by specifying your OS distribution and version.

    – sourcejedi
    Apr 24 '18 at 21:17


















1















I am mounting a drive via SSH, and then editing the fstab to reflect the changes, however after I reboot, the drive doesnt mount?



I dont understand what I'm doing wrong?



This is my fstab and its /md0 that isnt mounting after reboot, am I missing something?



# <file system> <mount point>   <type>  <options>   <dump>  <pass>
/dev/md4 / ext3 errors=remount-ro,usrjquota=quota.user,jqfmt=vfsv0 0 1
/dev/md0 /BACKUP ext3 defaults 0 1
/dev/md1 /boot ext3 errors=remount-ro 0 1
/dev/md2 /var/tmp ext3 usrjquota=quota.user,jqfmt=vfsv0 1 2
/dev/sda3 swap swap defaults 0 0
/dev/sdb3 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0









share|improve this question


















  • 1





    Is the network started and ssh running by the time the system goes through fstab?

    – schaiba
    Mar 3 '13 at 18:26











  • hi, im not sure if ssh running by that time, i wouldnt have thought so?

    – Mike Meade
    Mar 3 '13 at 21:35











  • /dev/mdX is supposed to be a RAID device - is it properly created during boot? It usually requires you to have at least mdadm --auto-detect run before you can use it (and supposing you have created the RAD with a superblock that can be detected).

    – peterph
    Mar 3 '13 at 21:53






  • 1





    The output of grep --after-context=3 -- md0 /proc/mdstat, please.

    – Hauke Laging
    Mar 4 '13 at 0:27











  • You have not even specified an OS - different OS' have different fstab formats. Please help us avoid guessing, and timestamp your questions by specifying your OS distribution and version.

    – sourcejedi
    Apr 24 '18 at 21:17
















1












1








1


0






I am mounting a drive via SSH, and then editing the fstab to reflect the changes, however after I reboot, the drive doesnt mount?



I dont understand what I'm doing wrong?



This is my fstab and its /md0 that isnt mounting after reboot, am I missing something?



# <file system> <mount point>   <type>  <options>   <dump>  <pass>
/dev/md4 / ext3 errors=remount-ro,usrjquota=quota.user,jqfmt=vfsv0 0 1
/dev/md0 /BACKUP ext3 defaults 0 1
/dev/md1 /boot ext3 errors=remount-ro 0 1
/dev/md2 /var/tmp ext3 usrjquota=quota.user,jqfmt=vfsv0 1 2
/dev/sda3 swap swap defaults 0 0
/dev/sdb3 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0









share|improve this question














I am mounting a drive via SSH, and then editing the fstab to reflect the changes, however after I reboot, the drive doesnt mount?



I dont understand what I'm doing wrong?



This is my fstab and its /md0 that isnt mounting after reboot, am I missing something?



# <file system> <mount point>   <type>  <options>   <dump>  <pass>
/dev/md4 / ext3 errors=remount-ro,usrjquota=quota.user,jqfmt=vfsv0 0 1
/dev/md0 /BACKUP ext3 defaults 0 1
/dev/md1 /boot ext3 errors=remount-ro 0 1
/dev/md2 /var/tmp ext3 usrjquota=quota.user,jqfmt=vfsv0 1 2
/dev/sda3 swap swap defaults 0 0
/dev/sdb3 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0






mount fstab






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 3 '13 at 18:19









Mike MeadeMike Meade

134




134








  • 1





    Is the network started and ssh running by the time the system goes through fstab?

    – schaiba
    Mar 3 '13 at 18:26











  • hi, im not sure if ssh running by that time, i wouldnt have thought so?

    – Mike Meade
    Mar 3 '13 at 21:35











  • /dev/mdX is supposed to be a RAID device - is it properly created during boot? It usually requires you to have at least mdadm --auto-detect run before you can use it (and supposing you have created the RAD with a superblock that can be detected).

    – peterph
    Mar 3 '13 at 21:53






  • 1





    The output of grep --after-context=3 -- md0 /proc/mdstat, please.

    – Hauke Laging
    Mar 4 '13 at 0:27











  • You have not even specified an OS - different OS' have different fstab formats. Please help us avoid guessing, and timestamp your questions by specifying your OS distribution and version.

    – sourcejedi
    Apr 24 '18 at 21:17
















  • 1





    Is the network started and ssh running by the time the system goes through fstab?

    – schaiba
    Mar 3 '13 at 18:26











  • hi, im not sure if ssh running by that time, i wouldnt have thought so?

    – Mike Meade
    Mar 3 '13 at 21:35











  • /dev/mdX is supposed to be a RAID device - is it properly created during boot? It usually requires you to have at least mdadm --auto-detect run before you can use it (and supposing you have created the RAD with a superblock that can be detected).

    – peterph
    Mar 3 '13 at 21:53






  • 1





    The output of grep --after-context=3 -- md0 /proc/mdstat, please.

    – Hauke Laging
    Mar 4 '13 at 0:27











  • You have not even specified an OS - different OS' have different fstab formats. Please help us avoid guessing, and timestamp your questions by specifying your OS distribution and version.

    – sourcejedi
    Apr 24 '18 at 21:17










1




1





Is the network started and ssh running by the time the system goes through fstab?

– schaiba
Mar 3 '13 at 18:26





Is the network started and ssh running by the time the system goes through fstab?

– schaiba
Mar 3 '13 at 18:26













hi, im not sure if ssh running by that time, i wouldnt have thought so?

– Mike Meade
Mar 3 '13 at 21:35





hi, im not sure if ssh running by that time, i wouldnt have thought so?

– Mike Meade
Mar 3 '13 at 21:35













/dev/mdX is supposed to be a RAID device - is it properly created during boot? It usually requires you to have at least mdadm --auto-detect run before you can use it (and supposing you have created the RAD with a superblock that can be detected).

– peterph
Mar 3 '13 at 21:53





/dev/mdX is supposed to be a RAID device - is it properly created during boot? It usually requires you to have at least mdadm --auto-detect run before you can use it (and supposing you have created the RAD with a superblock that can be detected).

– peterph
Mar 3 '13 at 21:53




1




1





The output of grep --after-context=3 -- md0 /proc/mdstat, please.

– Hauke Laging
Mar 4 '13 at 0:27





The output of grep --after-context=3 -- md0 /proc/mdstat, please.

– Hauke Laging
Mar 4 '13 at 0:27













You have not even specified an OS - different OS' have different fstab formats. Please help us avoid guessing, and timestamp your questions by specifying your OS distribution and version.

– sourcejedi
Apr 24 '18 at 21:17







You have not even specified an OS - different OS' have different fstab formats. Please help us avoid guessing, and timestamp your questions by specifying your OS distribution and version.

– sourcejedi
Apr 24 '18 at 21:17












1 Answer
1






active

oldest

votes


















0














Sometimes the cause is not the fstab configuration itself, the problem could lay somewhere else.



By simply adding a swap entry into your /etc/fstab file it does not magically activate the swap partition. Usually this is done by a swapon call, which can be made either manually or programatically:




  • Manually: simply run swapon -a in your terminal which will try to turn on all swap partition declared within your fstab file.

  • Programatically: hopefully your distro comes with a /etc/init.d/swap daemon/service which does just that.


I had a situation when for some reasons I wanted to deactivate the swap (by swapoff and also prevent re-mounting automatically after each reboot by removing the init script service). However, after some time I changed my mind and I set back the swap except that I forgot to re-add the swap init script service (eg. /etc/init.d/swap).



So I fixed it by (1) configuring the fstab and (2) by adding the swap init script service.






share|improve this answer

























    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%2f66734%2fnot-mounting-after-restart%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Sometimes the cause is not the fstab configuration itself, the problem could lay somewhere else.



    By simply adding a swap entry into your /etc/fstab file it does not magically activate the swap partition. Usually this is done by a swapon call, which can be made either manually or programatically:




    • Manually: simply run swapon -a in your terminal which will try to turn on all swap partition declared within your fstab file.

    • Programatically: hopefully your distro comes with a /etc/init.d/swap daemon/service which does just that.


    I had a situation when for some reasons I wanted to deactivate the swap (by swapoff and also prevent re-mounting automatically after each reboot by removing the init script service). However, after some time I changed my mind and I set back the swap except that I forgot to re-add the swap init script service (eg. /etc/init.d/swap).



    So I fixed it by (1) configuring the fstab and (2) by adding the swap init script service.






    share|improve this answer






























      0














      Sometimes the cause is not the fstab configuration itself, the problem could lay somewhere else.



      By simply adding a swap entry into your /etc/fstab file it does not magically activate the swap partition. Usually this is done by a swapon call, which can be made either manually or programatically:




      • Manually: simply run swapon -a in your terminal which will try to turn on all swap partition declared within your fstab file.

      • Programatically: hopefully your distro comes with a /etc/init.d/swap daemon/service which does just that.


      I had a situation when for some reasons I wanted to deactivate the swap (by swapoff and also prevent re-mounting automatically after each reboot by removing the init script service). However, after some time I changed my mind and I set back the swap except that I forgot to re-add the swap init script service (eg. /etc/init.d/swap).



      So I fixed it by (1) configuring the fstab and (2) by adding the swap init script service.






      share|improve this answer




























        0












        0








        0







        Sometimes the cause is not the fstab configuration itself, the problem could lay somewhere else.



        By simply adding a swap entry into your /etc/fstab file it does not magically activate the swap partition. Usually this is done by a swapon call, which can be made either manually or programatically:




        • Manually: simply run swapon -a in your terminal which will try to turn on all swap partition declared within your fstab file.

        • Programatically: hopefully your distro comes with a /etc/init.d/swap daemon/service which does just that.


        I had a situation when for some reasons I wanted to deactivate the swap (by swapoff and also prevent re-mounting automatically after each reboot by removing the init script service). However, after some time I changed my mind and I set back the swap except that I forgot to re-add the swap init script service (eg. /etc/init.d/swap).



        So I fixed it by (1) configuring the fstab and (2) by adding the swap init script service.






        share|improve this answer















        Sometimes the cause is not the fstab configuration itself, the problem could lay somewhere else.



        By simply adding a swap entry into your /etc/fstab file it does not magically activate the swap partition. Usually this is done by a swapon call, which can be made either manually or programatically:




        • Manually: simply run swapon -a in your terminal which will try to turn on all swap partition declared within your fstab file.

        • Programatically: hopefully your distro comes with a /etc/init.d/swap daemon/service which does just that.


        I had a situation when for some reasons I wanted to deactivate the swap (by swapoff and also prevent re-mounting automatically after each reboot by removing the init script service). However, after some time I changed my mind and I set back the swap except that I forgot to re-add the swap init script service (eg. /etc/init.d/swap).



        So I fixed it by (1) configuring the fstab and (2) by adding the swap init script service.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Apr 24 '18 at 18:25

























        answered Apr 24 '18 at 17:57









        Eugen MihailescuEugen Mihailescu

        1115




        1115






























            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%2f66734%2fnot-mounting-after-restart%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

            How to make a Squid Proxy server?

            Is this a new Fibonacci Identity?

            19世紀