Error “failed to mount /etc/fstab” at startup after attempting to add an HDD to fstab












0














To start with, I am very new to Linux and Ubuntu in general (only had it a couple months) and so am operating off of what I have learned from actually using Ubuntu in that time.



I am currently running Ubuntu 18.04.1 LTS (Bionic Beaver) on a HP Compaq machine and until recently, everything was working nearly perfectly.



However, I decided to try expanding my storage and options by adding another hard drive, to store my /home folder on. Looking around, I found what looked to be the best way to do it: Partitioning/Home/Moving



Following those instructions, I immediately ran into errors, so I decided to try another way. To make a long story short, I eventually figured out how to get into my /etc/fstab file and tried adding a line on to mount my second hard drive. Unfortunately, I didn't know to make a backup originally, though I did (accidentally) after adding the line on the end. But when adding the line onto the end of the fstab file, as shown in the directions from that link, I encountered some weird warnings in the terminal when I saved the Gedit file. Looking those up, I found that Gedit had a bug that generates those warnings. I don't know how or why, as I am, after all, just a beginner.



Anyway, while messing around, trying to get the one line added on, I must have changed something somewhere, because when I restarted my computer, the /etc/fstab file failed to mount. Here's what it looked like the first time:"Failed to mount /etc/fstab" error
And this is what I got after typing in the command for more info: details on "Failed to mount /etc/fstab" error



Thinking I had just accidentally put in an extra number or something, I inserted my Ubuntu installation DVD, booted into "Try Ubuntu" mode, and tried to edit my fstab that way. Although I was able to get into, view, and edit my fstab, I couldn't figure out how to save it, and it kept saying that "/dev/sda1/etc/fstab not a directory". Here's what it looked like: Ubuntu installation disk terminal The /etc/fstab file as shown in this picture is exactly how it was before all this started, with the exception of the last line that I added on. The middle two lines in the picture got clipped by the edge of the terminal (didn't have the window expanded enough), but they are still the original, unedited entries. Everything above that last UUID entry is exactly as original.



Since then I have tried editing the fstab in a couple different ways, trying to get it to where it will at least boot my main drive (the first UUID entry in the last picture). So far, nothing seems to work. Every time I turn on the computer it goes into emergency mode and tells me that /etc/fstab has failed to mount. Is this a problem with the contents of the fstab file, or did something else get messed up? I really can't remember doing anything else at first other than adding the one line on the end. Also, does the number of spaces in an fstab entry really matter? I have tried to read up on fstab, but I've never really seen any mention of spaces being important or not.



Any help on what to do and how to do it, to get my Ubuntu up and running again would be VERY much appreciated. Right now, I'd be happy with just my main drive booting again. Also, clarification on adding a line to the fstab would be useful too. Once again, I am not very good with Linux or computers at all, so only basic computer language would be helpful.



Thanks,



Kaleb



Update:
If it is any help to those who commented on this post, these are my options when saving my fstab file in Gedit via the live DVD.






boot mount fstab







share|improve this question









New contributor




Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1




    Please use a LiveUSB and the run fsck -y on all your partitions except the one with the efi files that should be /dev/sda1! I wish you had done sudo mount -a before the reboot to ensure all went well.
    – George Udosen
    Dec 28 '18 at 6:37






  • 1




    It looks to me like the /etc/fstab file was saved with UTF16 character encoding (perhaps because of your default locale, or maybe because you configured gedit to save it that way) - the error message What: <U+FEFF> seems to be referring to a UTF16 byte order mark
    – steeldriver
    Dec 28 '18 at 14:36






  • 1




    ... so the simplest fix will probably be to boot with the live DVD, install dos2unix (you may need to enable the universe repository) then mount your old root partition in rw mode and run dos2unix on the /etc/fstab file. Make a backup of the file first in case anything goes wrong.
    – steeldriver
    Dec 28 '18 at 15:58










  • Unfortunately, I can't seem to make steeldriver's suggestion work, going off of what instructions I could find. I booted from the live DVD, opened a terminal and typed sudo add-apt-repository universe as directed by one website. Although it gave me a few errors, it did say that the "universe repository" had been enabled. However, when I tried to enter sudo apt-get update and sudo apt-get install -y dos2unix, it said "E: unable to locate package dos2unix". Am I doing something wrong here, or is there a better way to do this? Further instructions or optional methods would be helpful.
    – Kaleb
    Dec 28 '18 at 20:56








  • 1




    If you file /etc/fstab does it report the file as ASCII text? (the command file reports on what type of file it is from the contents of the file; this will provide nothing new except confirmation that steeldriver was correct, and you need to convert your file to ascii; be it using save-as from a gui-editor (that allows you to select format using live-media) or conversion utility like steeldriver was suggesting you try). Also when you tried a command, telling us it gave me a few errors doesn't allow us to help unless we know what those errors were (ie. significant?/irrelevant?)
    – guiverc
    Dec 29 '18 at 5:07
















0














To start with, I am very new to Linux and Ubuntu in general (only had it a couple months) and so am operating off of what I have learned from actually using Ubuntu in that time.



I am currently running Ubuntu 18.04.1 LTS (Bionic Beaver) on a HP Compaq machine and until recently, everything was working nearly perfectly.



However, I decided to try expanding my storage and options by adding another hard drive, to store my /home folder on. Looking around, I found what looked to be the best way to do it: Partitioning/Home/Moving



Following those instructions, I immediately ran into errors, so I decided to try another way. To make a long story short, I eventually figured out how to get into my /etc/fstab file and tried adding a line on to mount my second hard drive. Unfortunately, I didn't know to make a backup originally, though I did (accidentally) after adding the line on the end. But when adding the line onto the end of the fstab file, as shown in the directions from that link, I encountered some weird warnings in the terminal when I saved the Gedit file. Looking those up, I found that Gedit had a bug that generates those warnings. I don't know how or why, as I am, after all, just a beginner.



Anyway, while messing around, trying to get the one line added on, I must have changed something somewhere, because when I restarted my computer, the /etc/fstab file failed to mount. Here's what it looked like the first time:"Failed to mount /etc/fstab" error
And this is what I got after typing in the command for more info: details on "Failed to mount /etc/fstab" error



Thinking I had just accidentally put in an extra number or something, I inserted my Ubuntu installation DVD, booted into "Try Ubuntu" mode, and tried to edit my fstab that way. Although I was able to get into, view, and edit my fstab, I couldn't figure out how to save it, and it kept saying that "/dev/sda1/etc/fstab not a directory". Here's what it looked like: Ubuntu installation disk terminal The /etc/fstab file as shown in this picture is exactly how it was before all this started, with the exception of the last line that I added on. The middle two lines in the picture got clipped by the edge of the terminal (didn't have the window expanded enough), but they are still the original, unedited entries. Everything above that last UUID entry is exactly as original.



Since then I have tried editing the fstab in a couple different ways, trying to get it to where it will at least boot my main drive (the first UUID entry in the last picture). So far, nothing seems to work. Every time I turn on the computer it goes into emergency mode and tells me that /etc/fstab has failed to mount. Is this a problem with the contents of the fstab file, or did something else get messed up? I really can't remember doing anything else at first other than adding the one line on the end. Also, does the number of spaces in an fstab entry really matter? I have tried to read up on fstab, but I've never really seen any mention of spaces being important or not.



Any help on what to do and how to do it, to get my Ubuntu up and running again would be VERY much appreciated. Right now, I'd be happy with just my main drive booting again. Also, clarification on adding a line to the fstab would be useful too. Once again, I am not very good with Linux or computers at all, so only basic computer language would be helpful.



Thanks,



Kaleb



Update:
If it is any help to those who commented on this post, these are my options when saving my fstab file in Gedit via the live DVD.






boot mount fstab







share|improve this question









New contributor




Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1




    Please use a LiveUSB and the run fsck -y on all your partitions except the one with the efi files that should be /dev/sda1! I wish you had done sudo mount -a before the reboot to ensure all went well.
    – George Udosen
    Dec 28 '18 at 6:37






  • 1




    It looks to me like the /etc/fstab file was saved with UTF16 character encoding (perhaps because of your default locale, or maybe because you configured gedit to save it that way) - the error message What: <U+FEFF> seems to be referring to a UTF16 byte order mark
    – steeldriver
    Dec 28 '18 at 14:36






  • 1




    ... so the simplest fix will probably be to boot with the live DVD, install dos2unix (you may need to enable the universe repository) then mount your old root partition in rw mode and run dos2unix on the /etc/fstab file. Make a backup of the file first in case anything goes wrong.
    – steeldriver
    Dec 28 '18 at 15:58










  • Unfortunately, I can't seem to make steeldriver's suggestion work, going off of what instructions I could find. I booted from the live DVD, opened a terminal and typed sudo add-apt-repository universe as directed by one website. Although it gave me a few errors, it did say that the "universe repository" had been enabled. However, when I tried to enter sudo apt-get update and sudo apt-get install -y dos2unix, it said "E: unable to locate package dos2unix". Am I doing something wrong here, or is there a better way to do this? Further instructions or optional methods would be helpful.
    – Kaleb
    Dec 28 '18 at 20:56








  • 1




    If you file /etc/fstab does it report the file as ASCII text? (the command file reports on what type of file it is from the contents of the file; this will provide nothing new except confirmation that steeldriver was correct, and you need to convert your file to ascii; be it using save-as from a gui-editor (that allows you to select format using live-media) or conversion utility like steeldriver was suggesting you try). Also when you tried a command, telling us it gave me a few errors doesn't allow us to help unless we know what those errors were (ie. significant?/irrelevant?)
    – guiverc
    Dec 29 '18 at 5:07














0












0








0







To start with, I am very new to Linux and Ubuntu in general (only had it a couple months) and so am operating off of what I have learned from actually using Ubuntu in that time.



I am currently running Ubuntu 18.04.1 LTS (Bionic Beaver) on a HP Compaq machine and until recently, everything was working nearly perfectly.



However, I decided to try expanding my storage and options by adding another hard drive, to store my /home folder on. Looking around, I found what looked to be the best way to do it: Partitioning/Home/Moving



Following those instructions, I immediately ran into errors, so I decided to try another way. To make a long story short, I eventually figured out how to get into my /etc/fstab file and tried adding a line on to mount my second hard drive. Unfortunately, I didn't know to make a backup originally, though I did (accidentally) after adding the line on the end. But when adding the line onto the end of the fstab file, as shown in the directions from that link, I encountered some weird warnings in the terminal when I saved the Gedit file. Looking those up, I found that Gedit had a bug that generates those warnings. I don't know how or why, as I am, after all, just a beginner.



Anyway, while messing around, trying to get the one line added on, I must have changed something somewhere, because when I restarted my computer, the /etc/fstab file failed to mount. Here's what it looked like the first time:"Failed to mount /etc/fstab" error
And this is what I got after typing in the command for more info: details on "Failed to mount /etc/fstab" error



Thinking I had just accidentally put in an extra number or something, I inserted my Ubuntu installation DVD, booted into "Try Ubuntu" mode, and tried to edit my fstab that way. Although I was able to get into, view, and edit my fstab, I couldn't figure out how to save it, and it kept saying that "/dev/sda1/etc/fstab not a directory". Here's what it looked like: Ubuntu installation disk terminal The /etc/fstab file as shown in this picture is exactly how it was before all this started, with the exception of the last line that I added on. The middle two lines in the picture got clipped by the edge of the terminal (didn't have the window expanded enough), but they are still the original, unedited entries. Everything above that last UUID entry is exactly as original.



Since then I have tried editing the fstab in a couple different ways, trying to get it to where it will at least boot my main drive (the first UUID entry in the last picture). So far, nothing seems to work. Every time I turn on the computer it goes into emergency mode and tells me that /etc/fstab has failed to mount. Is this a problem with the contents of the fstab file, or did something else get messed up? I really can't remember doing anything else at first other than adding the one line on the end. Also, does the number of spaces in an fstab entry really matter? I have tried to read up on fstab, but I've never really seen any mention of spaces being important or not.



Any help on what to do and how to do it, to get my Ubuntu up and running again would be VERY much appreciated. Right now, I'd be happy with just my main drive booting again. Also, clarification on adding a line to the fstab would be useful too. Once again, I am not very good with Linux or computers at all, so only basic computer language would be helpful.



Thanks,



Kaleb



Update:
If it is any help to those who commented on this post, these are my options when saving my fstab file in Gedit via the live DVD.






boot mount fstab







share|improve this question









New contributor




Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











To start with, I am very new to Linux and Ubuntu in general (only had it a couple months) and so am operating off of what I have learned from actually using Ubuntu in that time.



I am currently running Ubuntu 18.04.1 LTS (Bionic Beaver) on a HP Compaq machine and until recently, everything was working nearly perfectly.



However, I decided to try expanding my storage and options by adding another hard drive, to store my /home folder on. Looking around, I found what looked to be the best way to do it: Partitioning/Home/Moving



Following those instructions, I immediately ran into errors, so I decided to try another way. To make a long story short, I eventually figured out how to get into my /etc/fstab file and tried adding a line on to mount my second hard drive. Unfortunately, I didn't know to make a backup originally, though I did (accidentally) after adding the line on the end. But when adding the line onto the end of the fstab file, as shown in the directions from that link, I encountered some weird warnings in the terminal when I saved the Gedit file. Looking those up, I found that Gedit had a bug that generates those warnings. I don't know how or why, as I am, after all, just a beginner.



Anyway, while messing around, trying to get the one line added on, I must have changed something somewhere, because when I restarted my computer, the /etc/fstab file failed to mount. Here's what it looked like the first time:"Failed to mount /etc/fstab" error
And this is what I got after typing in the command for more info: details on "Failed to mount /etc/fstab" error



Thinking I had just accidentally put in an extra number or something, I inserted my Ubuntu installation DVD, booted into "Try Ubuntu" mode, and tried to edit my fstab that way. Although I was able to get into, view, and edit my fstab, I couldn't figure out how to save it, and it kept saying that "/dev/sda1/etc/fstab not a directory". Here's what it looked like: Ubuntu installation disk terminal The /etc/fstab file as shown in this picture is exactly how it was before all this started, with the exception of the last line that I added on. The middle two lines in the picture got clipped by the edge of the terminal (didn't have the window expanded enough), but they are still the original, unedited entries. Everything above that last UUID entry is exactly as original.



Since then I have tried editing the fstab in a couple different ways, trying to get it to where it will at least boot my main drive (the first UUID entry in the last picture). So far, nothing seems to work. Every time I turn on the computer it goes into emergency mode and tells me that /etc/fstab has failed to mount. Is this a problem with the contents of the fstab file, or did something else get messed up? I really can't remember doing anything else at first other than adding the one line on the end. Also, does the number of spaces in an fstab entry really matter? I have tried to read up on fstab, but I've never really seen any mention of spaces being important or not.



Any help on what to do and how to do it, to get my Ubuntu up and running again would be VERY much appreciated. Right now, I'd be happy with just my main drive booting again. Also, clarification on adding a line to the fstab would be useful too. Once again, I am not very good with Linux or computers at all, so only basic computer language would be helpful.



Thanks,



Kaleb



Update:
If it is any help to those who commented on this post, these are my options when saving my fstab file in Gedit via the live DVD.






boot mount fstab




boot mount fstab






share|improve this question









New contributor




Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 2 days ago





















New contributor




Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Dec 28 '18 at 5:44









Kaleb

112




112




New contributor




Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1




    Please use a LiveUSB and the run fsck -y on all your partitions except the one with the efi files that should be /dev/sda1! I wish you had done sudo mount -a before the reboot to ensure all went well.
    – George Udosen
    Dec 28 '18 at 6:37






  • 1




    It looks to me like the /etc/fstab file was saved with UTF16 character encoding (perhaps because of your default locale, or maybe because you configured gedit to save it that way) - the error message What: <U+FEFF> seems to be referring to a UTF16 byte order mark
    – steeldriver
    Dec 28 '18 at 14:36






  • 1




    ... so the simplest fix will probably be to boot with the live DVD, install dos2unix (you may need to enable the universe repository) then mount your old root partition in rw mode and run dos2unix on the /etc/fstab file. Make a backup of the file first in case anything goes wrong.
    – steeldriver
    Dec 28 '18 at 15:58










  • Unfortunately, I can't seem to make steeldriver's suggestion work, going off of what instructions I could find. I booted from the live DVD, opened a terminal and typed sudo add-apt-repository universe as directed by one website. Although it gave me a few errors, it did say that the "universe repository" had been enabled. However, when I tried to enter sudo apt-get update and sudo apt-get install -y dos2unix, it said "E: unable to locate package dos2unix". Am I doing something wrong here, or is there a better way to do this? Further instructions or optional methods would be helpful.
    – Kaleb
    Dec 28 '18 at 20:56








  • 1




    If you file /etc/fstab does it report the file as ASCII text? (the command file reports on what type of file it is from the contents of the file; this will provide nothing new except confirmation that steeldriver was correct, and you need to convert your file to ascii; be it using save-as from a gui-editor (that allows you to select format using live-media) or conversion utility like steeldriver was suggesting you try). Also when you tried a command, telling us it gave me a few errors doesn't allow us to help unless we know what those errors were (ie. significant?/irrelevant?)
    – guiverc
    Dec 29 '18 at 5:07














  • 1




    Please use a LiveUSB and the run fsck -y on all your partitions except the one with the efi files that should be /dev/sda1! I wish you had done sudo mount -a before the reboot to ensure all went well.
    – George Udosen
    Dec 28 '18 at 6:37






  • 1




    It looks to me like the /etc/fstab file was saved with UTF16 character encoding (perhaps because of your default locale, or maybe because you configured gedit to save it that way) - the error message What: <U+FEFF> seems to be referring to a UTF16 byte order mark
    – steeldriver
    Dec 28 '18 at 14:36






  • 1




    ... so the simplest fix will probably be to boot with the live DVD, install dos2unix (you may need to enable the universe repository) then mount your old root partition in rw mode and run dos2unix on the /etc/fstab file. Make a backup of the file first in case anything goes wrong.
    – steeldriver
    Dec 28 '18 at 15:58










  • Unfortunately, I can't seem to make steeldriver's suggestion work, going off of what instructions I could find. I booted from the live DVD, opened a terminal and typed sudo add-apt-repository universe as directed by one website. Although it gave me a few errors, it did say that the "universe repository" had been enabled. However, when I tried to enter sudo apt-get update and sudo apt-get install -y dos2unix, it said "E: unable to locate package dos2unix". Am I doing something wrong here, or is there a better way to do this? Further instructions or optional methods would be helpful.
    – Kaleb
    Dec 28 '18 at 20:56








  • 1




    If you file /etc/fstab does it report the file as ASCII text? (the command file reports on what type of file it is from the contents of the file; this will provide nothing new except confirmation that steeldriver was correct, and you need to convert your file to ascii; be it using save-as from a gui-editor (that allows you to select format using live-media) or conversion utility like steeldriver was suggesting you try). Also when you tried a command, telling us it gave me a few errors doesn't allow us to help unless we know what those errors were (ie. significant?/irrelevant?)
    – guiverc
    Dec 29 '18 at 5:07








1




1




Please use a LiveUSB and the run fsck -y on all your partitions except the one with the efi files that should be /dev/sda1! I wish you had done sudo mount -a before the reboot to ensure all went well.
– George Udosen
Dec 28 '18 at 6:37




Please use a LiveUSB and the run fsck -y on all your partitions except the one with the efi files that should be /dev/sda1! I wish you had done sudo mount -a before the reboot to ensure all went well.
– George Udosen
Dec 28 '18 at 6:37




1




1




It looks to me like the /etc/fstab file was saved with UTF16 character encoding (perhaps because of your default locale, or maybe because you configured gedit to save it that way) - the error message What: <U+FEFF> seems to be referring to a UTF16 byte order mark
– steeldriver
Dec 28 '18 at 14:36




It looks to me like the /etc/fstab file was saved with UTF16 character encoding (perhaps because of your default locale, or maybe because you configured gedit to save it that way) - the error message What: <U+FEFF> seems to be referring to a UTF16 byte order mark
– steeldriver
Dec 28 '18 at 14:36




1




1




... so the simplest fix will probably be to boot with the live DVD, install dos2unix (you may need to enable the universe repository) then mount your old root partition in rw mode and run dos2unix on the /etc/fstab file. Make a backup of the file first in case anything goes wrong.
– steeldriver
Dec 28 '18 at 15:58




... so the simplest fix will probably be to boot with the live DVD, install dos2unix (you may need to enable the universe repository) then mount your old root partition in rw mode and run dos2unix on the /etc/fstab file. Make a backup of the file first in case anything goes wrong.
– steeldriver
Dec 28 '18 at 15:58












Unfortunately, I can't seem to make steeldriver's suggestion work, going off of what instructions I could find. I booted from the live DVD, opened a terminal and typed sudo add-apt-repository universe as directed by one website. Although it gave me a few errors, it did say that the "universe repository" had been enabled. However, when I tried to enter sudo apt-get update and sudo apt-get install -y dos2unix, it said "E: unable to locate package dos2unix". Am I doing something wrong here, or is there a better way to do this? Further instructions or optional methods would be helpful.
– Kaleb
Dec 28 '18 at 20:56






Unfortunately, I can't seem to make steeldriver's suggestion work, going off of what instructions I could find. I booted from the live DVD, opened a terminal and typed sudo add-apt-repository universe as directed by one website. Although it gave me a few errors, it did say that the "universe repository" had been enabled. However, when I tried to enter sudo apt-get update and sudo apt-get install -y dos2unix, it said "E: unable to locate package dos2unix". Am I doing something wrong here, or is there a better way to do this? Further instructions or optional methods would be helpful.
– Kaleb
Dec 28 '18 at 20:56






1




1




If you file /etc/fstab does it report the file as ASCII text? (the command file reports on what type of file it is from the contents of the file; this will provide nothing new except confirmation that steeldriver was correct, and you need to convert your file to ascii; be it using save-as from a gui-editor (that allows you to select format using live-media) or conversion utility like steeldriver was suggesting you try). Also when you tried a command, telling us it gave me a few errors doesn't allow us to help unless we know what those errors were (ie. significant?/irrelevant?)
– guiverc
Dec 29 '18 at 5:07




If you file /etc/fstab does it report the file as ASCII text? (the command file reports on what type of file it is from the contents of the file; this will provide nothing new except confirmation that steeldriver was correct, and you need to convert your file to ascii; be it using save-as from a gui-editor (that allows you to select format using live-media) or conversion utility like steeldriver was suggesting you try). Also when you tried a command, telling us it gave me a few errors doesn't allow us to help unless we know what those errors were (ie. significant?/irrelevant?)
– guiverc
Dec 29 '18 at 5:07










1 Answer
1






active

oldest

votes


















1














After much help from others and little bit or work, my problem has finally been resolved, no thanks to my limited computer skills.



However, the answer was quite a bit different than I thought it would be. The root of the error was that my /etc/fstab file was encoded in UTF-8, which is how gedit saved the file, and it needed to be in ASCII. Although I'm sure more experienced Linux users know a way to convert the one to the other, I couldn't seem to make it work right.

Instead, I took @steeldriver's advice and decided to re-make my fstab file completely.



Fortunately, I had a near-entire back-up of the original file, so the details of writing it were not a problem. The steps I took were: Booted from live Ubuntu DVD> mounted my original root drive> created a new folder and file in the /etc folder using terminal> pasted fstab entries into the new file using sudo nano to edit in the terminal> moved that file into /etc> deleted original fstab file> and renamed the new file as fstab to replace the original.
I then rebooted without the live DVD and everything started normally, with no errors.
I'm sure there are better ways out there to do this, but this just happened to be what worked in my situation.



Thanks again to everyone who helped me with this problem. It's so good to be able to use my computer normally again.



-Kaleb






share|improve this answer








New contributor




Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.


















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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
    });


    }
    });






    Kaleb is a new contributor. Be nice, and check out our Code of Conduct.










    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1105065%2ferror-failed-to-mount-etc-fstab-at-startup-after-attempting-to-add-an-hdd-to%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









    1














    After much help from others and little bit or work, my problem has finally been resolved, no thanks to my limited computer skills.



    However, the answer was quite a bit different than I thought it would be. The root of the error was that my /etc/fstab file was encoded in UTF-8, which is how gedit saved the file, and it needed to be in ASCII. Although I'm sure more experienced Linux users know a way to convert the one to the other, I couldn't seem to make it work right.

    Instead, I took @steeldriver's advice and decided to re-make my fstab file completely.



    Fortunately, I had a near-entire back-up of the original file, so the details of writing it were not a problem. The steps I took were: Booted from live Ubuntu DVD> mounted my original root drive> created a new folder and file in the /etc folder using terminal> pasted fstab entries into the new file using sudo nano to edit in the terminal> moved that file into /etc> deleted original fstab file> and renamed the new file as fstab to replace the original.
    I then rebooted without the live DVD and everything started normally, with no errors.
    I'm sure there are better ways out there to do this, but this just happened to be what worked in my situation.



    Thanks again to everyone who helped me with this problem. It's so good to be able to use my computer normally again.



    -Kaleb






    share|improve this answer








    New contributor




    Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      1














      After much help from others and little bit or work, my problem has finally been resolved, no thanks to my limited computer skills.



      However, the answer was quite a bit different than I thought it would be. The root of the error was that my /etc/fstab file was encoded in UTF-8, which is how gedit saved the file, and it needed to be in ASCII. Although I'm sure more experienced Linux users know a way to convert the one to the other, I couldn't seem to make it work right.

      Instead, I took @steeldriver's advice and decided to re-make my fstab file completely.



      Fortunately, I had a near-entire back-up of the original file, so the details of writing it were not a problem. The steps I took were: Booted from live Ubuntu DVD> mounted my original root drive> created a new folder and file in the /etc folder using terminal> pasted fstab entries into the new file using sudo nano to edit in the terminal> moved that file into /etc> deleted original fstab file> and renamed the new file as fstab to replace the original.
      I then rebooted without the live DVD and everything started normally, with no errors.
      I'm sure there are better ways out there to do this, but this just happened to be what worked in my situation.



      Thanks again to everyone who helped me with this problem. It's so good to be able to use my computer normally again.



      -Kaleb






      share|improve this answer








      New contributor




      Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





















        1












        1








        1






        After much help from others and little bit or work, my problem has finally been resolved, no thanks to my limited computer skills.



        However, the answer was quite a bit different than I thought it would be. The root of the error was that my /etc/fstab file was encoded in UTF-8, which is how gedit saved the file, and it needed to be in ASCII. Although I'm sure more experienced Linux users know a way to convert the one to the other, I couldn't seem to make it work right.

        Instead, I took @steeldriver's advice and decided to re-make my fstab file completely.



        Fortunately, I had a near-entire back-up of the original file, so the details of writing it were not a problem. The steps I took were: Booted from live Ubuntu DVD> mounted my original root drive> created a new folder and file in the /etc folder using terminal> pasted fstab entries into the new file using sudo nano to edit in the terminal> moved that file into /etc> deleted original fstab file> and renamed the new file as fstab to replace the original.
        I then rebooted without the live DVD and everything started normally, with no errors.
        I'm sure there are better ways out there to do this, but this just happened to be what worked in my situation.



        Thanks again to everyone who helped me with this problem. It's so good to be able to use my computer normally again.



        -Kaleb






        share|improve this answer








        New contributor




        Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        After much help from others and little bit or work, my problem has finally been resolved, no thanks to my limited computer skills.



        However, the answer was quite a bit different than I thought it would be. The root of the error was that my /etc/fstab file was encoded in UTF-8, which is how gedit saved the file, and it needed to be in ASCII. Although I'm sure more experienced Linux users know a way to convert the one to the other, I couldn't seem to make it work right.

        Instead, I took @steeldriver's advice and decided to re-make my fstab file completely.



        Fortunately, I had a near-entire back-up of the original file, so the details of writing it were not a problem. The steps I took were: Booted from live Ubuntu DVD> mounted my original root drive> created a new folder and file in the /etc folder using terminal> pasted fstab entries into the new file using sudo nano to edit in the terminal> moved that file into /etc> deleted original fstab file> and renamed the new file as fstab to replace the original.
        I then rebooted without the live DVD and everything started normally, with no errors.
        I'm sure there are better ways out there to do this, but this just happened to be what worked in my situation.



        Thanks again to everyone who helped me with this problem. It's so good to be able to use my computer normally again.



        -Kaleb







        share|improve this answer








        New contributor




        Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered yesterday









        Kaleb

        112




        112




        New contributor




        Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        Kaleb is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






















            Kaleb is a new contributor. Be nice, and check out our Code of Conduct.










            draft saved

            draft discarded


















            Kaleb is a new contributor. Be nice, and check out our Code of Conduct.













            Kaleb is a new contributor. Be nice, and check out our Code of Conduct.












            Kaleb is a new contributor. Be nice, and check out our Code of Conduct.
















            Thanks for contributing an answer to Ask Ubuntu!


            • 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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2faskubuntu.com%2fquestions%2f1105065%2ferror-failed-to-mount-etc-fstab-at-startup-after-attempting-to-add-an-hdd-to%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

            數位音樂下載

            Image
            數位音樂下載 為非以「實體」方式來販賣音樂的相關產品，而使用數位格式如mp3、AAC等文件格式來進行銷售販賣的一种音乐产业形式。著名的數位音樂下載服務商有iTunes Store、RecoChoku、Google Play音乐和微软Zune等。数字音乐下载在二十一世纪初一度风靡全球， [1] [2] 使得传统唱片产业走向衰落，但其自身也在2010年代流媒体音乐服务如Apple Music、Spotify等的挤压下迅速失去市场份额。 [3] [4] 数字音乐下载有便于携带、传播迅速、制作简单成本低等优点，与流媒体音乐相比也能更好保障音乐人权益； [5] 但它同时很可能带来侵犯版权和滥用的情形， [6] 也给音乐产业带来了诸多不利影响。数字音乐下载为音乐人和乐迷提供了更加便捷直接的交流渠道，也一定程度上推动了网络音乐人的出现和独立音乐的迅速发展。 [7] 目录 1 历史 1.1 技术积淀（1987-2000） 1.2 出现与兴起（2000-2004） 1.3 唱片市场的颠覆者（2004-2007） 1.4 巅峰和衰落（2005-2013） 1.5 摇摇欲坠的现状与不可预知的明天（2014至今） 2 主要文件格式 2.1 PCM编码格式 2.1.1 WAV 2.1.2 APE 2.1.3 FLAC 2.2 苹果推出的无损文件格式 2.2.1 AIFF 2.2.2 ALAC 2.3 有损压缩格式 2.3.1 MP3 2.3.2 AAC 3 主要市场 3.1 iTunes Store 3.2 Google Play音乐商店 3.3 亚马逊音乐商店 3.4 部分其他音乐商店 4 影响与评价 4.1 对音乐产业的影响 4.2 对科技行业的影响 4.3 正面评价 4.4 负面评价 4.4.1 侵权问题 4.4.2 经营模式不明晰 4.4.3 不适应移动时代 4.5 文化现象 5 延伸阅读 6 参考资料 历史 苹果iTunes+iPod的软硬件搭配让数字音...
            Read more

            When can things happen in Etherscan, such as the picture below?

            Image
            2 I don't know why balance of the address is 0. when can this situation? etherscan balances share | improve this question asked yesterday Ru Hi Ru Hi 11 1 New contributor Ru Hi is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment  |  ...
            Read more

            格利澤436b

            Image
            格利泽436b 太陽系外行星 太陽系外行星列表 艺术家笔下的格利泽436b 母恆星 母恆星 Gliese 436 星座 獅子座 赤經 ( α ) 11 h  42 m  11.0941 s [1] 赤緯 ( δ ) +26° 42′ 23.652″ [1] 距離 33.4 ly (10.2 pc) 光譜類型 M2.5 V [1] 軌道參數 半长轴 ( a ) 0.0291±0.0004 [2] AU 軌道離心率 ( e ) 0.150±0.012 [2] 公轉週期 ( P ) 2.643904±0.000005 [3] d (0.00723849 y) 軌道傾角 ( i ) 85.8 +0.21 −0.25 [3] ° 角距 ( θ ) 2.794 mas 近星點時間 ( T 0 ) 2,451,551.716 ±0.01 JD 半振幅 ( K ) 18.68±0.8 m/s 物理性质 质量 ( m ) 22.2±1.0 [2] M ⊕ 半徑 ( r ) 4.327±0.183 [2] [4] R ⊕ 密度 ( ρ ) 1.51 g cm -3 表面重力 ( g ) 1.18 g 溫度 ( T ) 712±36 [2] K 發現 發現時間 2004 發現者 巴特勒、沃格特、 馬西 et al. 發現方法 徑向速度、凌日法 發現地點 美國加利福尼亞州 發表論文 出版 其他名稱 Ross 905 b, GJ 436 b, [5] LTT 13213 b, GCTP 2704.10 b, LHS 310, AC+27:28217 b, Vyssotsky 616 b, HIP 57087 b, GEN# +9.80120068 b, LP 319-75 b, G 121-7 b, LSPM J1142+2642 b, 1RXS J114211.9+264328 b, ASCC 683818 b, G 147-68 b, UCAC2 41198281 b, BP...
            Read more