Is it okay to modify Ubuntu Linux 16.04's /etc/fstab after I initialized it?












0















I modified /etc/fstab after I initialized it on an Ubuntu Linux 16.04 system running on an Lenovo Thinkstation desktop. After it messed up my Ubuntu Linux 16.04 system causing it to go into emergency reboot status endlessly.



I would like to know what caused this mishap and how to fix /etc/fstab correctly so as to change the symbolic name.



Any help is greatly appreciated.



[EDIT 5/24/2016 2:00PM by Frank]
The /etc/fstab changed from underneath me after the emergency reboot.



The original read like this:



Data1 /media/Data1 vfat defaults 0 1 

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb7 during installation
UUID=71f42e33-6984-4905-9932-17cd4adb7b41 / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb5 during installation
UUID=0a3b409b-f7bf-4a22-a05f-0dc35e1bb111 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0









share|improve this question
















bumped to the homepage by Community 7 hours ago


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
















  • Comments are not for extended discussion; this conversation has been moved to chat.

    – terdon
    May 25 '16 at 13:23
















0















I modified /etc/fstab after I initialized it on an Ubuntu Linux 16.04 system running on an Lenovo Thinkstation desktop. After it messed up my Ubuntu Linux 16.04 system causing it to go into emergency reboot status endlessly.



I would like to know what caused this mishap and how to fix /etc/fstab correctly so as to change the symbolic name.



Any help is greatly appreciated.



[EDIT 5/24/2016 2:00PM by Frank]
The /etc/fstab changed from underneath me after the emergency reboot.



The original read like this:



Data1 /media/Data1 vfat defaults 0 1 

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb7 during installation
UUID=71f42e33-6984-4905-9932-17cd4adb7b41 / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb5 during installation
UUID=0a3b409b-f7bf-4a22-a05f-0dc35e1bb111 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0









share|improve this question
















bumped to the homepage by Community 7 hours ago


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
















  • Comments are not for extended discussion; this conversation has been moved to chat.

    – terdon
    May 25 '16 at 13:23














0












0








0








I modified /etc/fstab after I initialized it on an Ubuntu Linux 16.04 system running on an Lenovo Thinkstation desktop. After it messed up my Ubuntu Linux 16.04 system causing it to go into emergency reboot status endlessly.



I would like to know what caused this mishap and how to fix /etc/fstab correctly so as to change the symbolic name.



Any help is greatly appreciated.



[EDIT 5/24/2016 2:00PM by Frank]
The /etc/fstab changed from underneath me after the emergency reboot.



The original read like this:



Data1 /media/Data1 vfat defaults 0 1 

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb7 during installation
UUID=71f42e33-6984-4905-9932-17cd4adb7b41 / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb5 during installation
UUID=0a3b409b-f7bf-4a22-a05f-0dc35e1bb111 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0









share|improve this question
















I modified /etc/fstab after I initialized it on an Ubuntu Linux 16.04 system running on an Lenovo Thinkstation desktop. After it messed up my Ubuntu Linux 16.04 system causing it to go into emergency reboot status endlessly.



I would like to know what caused this mishap and how to fix /etc/fstab correctly so as to change the symbolic name.



Any help is greatly appreciated.



[EDIT 5/24/2016 2:00PM by Frank]
The /etc/fstab changed from underneath me after the emergency reboot.



The original read like this:



Data1 /media/Data1 vfat defaults 0 1 

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb7 during installation
UUID=71f42e33-6984-4905-9932-17cd4adb7b41 / ext4 errors=remount-ro 0 1
# swap was on /dev/sdb5 during installation
UUID=0a3b409b-f7bf-4a22-a05f-0dc35e1bb111 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0






ubuntu fstab reboot






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 24 '16 at 19:02







Frank

















asked May 24 '16 at 17:32









FrankFrank

2881619




2881619





bumped to the homepage by Community 7 hours 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 7 hours ago


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















  • Comments are not for extended discussion; this conversation has been moved to chat.

    – terdon
    May 25 '16 at 13:23



















  • Comments are not for extended discussion; this conversation has been moved to chat.

    – terdon
    May 25 '16 at 13:23

















Comments are not for extended discussion; this conversation has been moved to chat.

– terdon
May 25 '16 at 13:23





Comments are not for extended discussion; this conversation has been moved to chat.

– terdon
May 25 '16 at 13:23










1 Answer
1






active

oldest

votes


















0














Yes , it is okay to modify Ubuntu Linux 16.04's /etc/fstab after one initializes it.



I narrowed the cause of the problem where we modify /etc/fstab to sudo nano /etc/rc.local :



e.g. Add these lines before the exit line:
sleep 30
sudo mount -a
exit
exit 0


which were intended for the usb drive taking a long time to initiate , this automount may fail.






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%2f285216%2fis-it-okay-to-modify-ubuntu-linux-16-04s-etc-fstab-after-i-initialized-it%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














    Yes , it is okay to modify Ubuntu Linux 16.04's /etc/fstab after one initializes it.



    I narrowed the cause of the problem where we modify /etc/fstab to sudo nano /etc/rc.local :



    e.g. Add these lines before the exit line:
    sleep 30
    sudo mount -a
    exit
    exit 0


    which were intended for the usb drive taking a long time to initiate , this automount may fail.






    share|improve this answer






























      0














      Yes , it is okay to modify Ubuntu Linux 16.04's /etc/fstab after one initializes it.



      I narrowed the cause of the problem where we modify /etc/fstab to sudo nano /etc/rc.local :



      e.g. Add these lines before the exit line:
      sleep 30
      sudo mount -a
      exit
      exit 0


      which were intended for the usb drive taking a long time to initiate , this automount may fail.






      share|improve this answer




























        0












        0








        0







        Yes , it is okay to modify Ubuntu Linux 16.04's /etc/fstab after one initializes it.



        I narrowed the cause of the problem where we modify /etc/fstab to sudo nano /etc/rc.local :



        e.g. Add these lines before the exit line:
        sleep 30
        sudo mount -a
        exit
        exit 0


        which were intended for the usb drive taking a long time to initiate , this automount may fail.






        share|improve this answer















        Yes , it is okay to modify Ubuntu Linux 16.04's /etc/fstab after one initializes it.



        I narrowed the cause of the problem where we modify /etc/fstab to sudo nano /etc/rc.local :



        e.g. Add these lines before the exit line:
        sleep 30
        sudo mount -a
        exit
        exit 0


        which were intended for the usb drive taking a long time to initiate , this automount may fail.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        answered May 24 '16 at 19:37


























        community wiki





        Frank































            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%2f285216%2fis-it-okay-to-modify-ubuntu-linux-16-04s-etc-fstab-after-i-initialized-it%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

            Loup dans la culture

            How to solve the problem of ntp “Unable to contact time server” from KDE?

            ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux