need generic /home entry for Ubuntu 18.04 /etc/fstab
Short version:
in /etc/fstab on an Ubuntu 18.04 system, what are the typical options used when mounting a partition as /home? Just "defaults 0 2", or something else?
Longer version:
I screwed up my /etc/fstab today, but managed to get it back. Something I was messing with basically deleted the /home entry in fstab, but I wasn't aware that it had done that, and the system kept working normally. When I went to reboot the system (for other reasons), the system was hosed and would not even let me log in (not even on the Ctrl-Alt-F3 console). I eventually zero'd in on the fstab problem, recreated the missing line, and I'm now posting from that system.
But I just put in a generic line, with options="defaults", dump=0 and pass=2. I suspect that dump and pass are fine as is, but I bet the options should be some besides the defaults. Can someone look at a vanilla 18.04 system and tell me what the options are for the /home mount? auto_da_alloc?
I did search this forum before posting. There's a thread from 2011 that says just defaults is fine, but that's 8 years old ...
Even longer version with background on the screwup:
I upgraded to 18.04 week ago. I kept my /home partition, copied to a new drive, and installed the OS around that. It had worked great for a week now.
Today I was working on setting up a backup process, and was fiddling around with mounting other drives, including an external drive. The external drive was an existing HDD that I was putting into a brand new SATA3/USB enclosure, so my first step was to just make sure that the new enclosure worked.
The new enclosure/drive showed up in Ubuntu's Disks utility, and I could see the old partitions. I mounted one of the partitions to confirm that worked, and ran a df (or something like that) to confirm it.
That's when I noticed that it had mounted the new partition at /home, apparently replacing the regular /home. Uh oh, the mount operation had followed the label of the partition (and yes I now understand why). A quick look at /home confirm that it was seeing the data on the old drive there. Yikes! I immediately unmounted it, and IT WENT BACK TO THE CORRECT HOME PARTITION. The correct files showed up at /home again. Whew, OK, don't do that again!
The system was working normally again, but what I didn't know was that in doing this, the Disks util had messed up the fstab file. The original /home entry was gone, and now the UUID of the correct partition was associated with another partition (more detail that I'll skip here). The next time I rebooted, blammo, no /home.
After an hour of googling and thinking about what I had just been doing before it broke, I figured it out and restored it with a generic line in fstab.
Thanks for reading :)
mount fstab
add a comment |
Short version:
in /etc/fstab on an Ubuntu 18.04 system, what are the typical options used when mounting a partition as /home? Just "defaults 0 2", or something else?
Longer version:
I screwed up my /etc/fstab today, but managed to get it back. Something I was messing with basically deleted the /home entry in fstab, but I wasn't aware that it had done that, and the system kept working normally. When I went to reboot the system (for other reasons), the system was hosed and would not even let me log in (not even on the Ctrl-Alt-F3 console). I eventually zero'd in on the fstab problem, recreated the missing line, and I'm now posting from that system.
But I just put in a generic line, with options="defaults", dump=0 and pass=2. I suspect that dump and pass are fine as is, but I bet the options should be some besides the defaults. Can someone look at a vanilla 18.04 system and tell me what the options are for the /home mount? auto_da_alloc?
I did search this forum before posting. There's a thread from 2011 that says just defaults is fine, but that's 8 years old ...
Even longer version with background on the screwup:
I upgraded to 18.04 week ago. I kept my /home partition, copied to a new drive, and installed the OS around that. It had worked great for a week now.
Today I was working on setting up a backup process, and was fiddling around with mounting other drives, including an external drive. The external drive was an existing HDD that I was putting into a brand new SATA3/USB enclosure, so my first step was to just make sure that the new enclosure worked.
The new enclosure/drive showed up in Ubuntu's Disks utility, and I could see the old partitions. I mounted one of the partitions to confirm that worked, and ran a df (or something like that) to confirm it.
That's when I noticed that it had mounted the new partition at /home, apparently replacing the regular /home. Uh oh, the mount operation had followed the label of the partition (and yes I now understand why). A quick look at /home confirm that it was seeing the data on the old drive there. Yikes! I immediately unmounted it, and IT WENT BACK TO THE CORRECT HOME PARTITION. The correct files showed up at /home again. Whew, OK, don't do that again!
The system was working normally again, but what I didn't know was that in doing this, the Disks util had messed up the fstab file. The original /home entry was gone, and now the UUID of the correct partition was associated with another partition (more detail that I'll skip here). The next time I rebooted, blammo, no /home.
After an hour of googling and thinking about what I had just been doing before it broke, I figured it out and restored it with a generic line in fstab.
Thanks for reading :)
mount fstab
add a comment |
Short version:
in /etc/fstab on an Ubuntu 18.04 system, what are the typical options used when mounting a partition as /home? Just "defaults 0 2", or something else?
Longer version:
I screwed up my /etc/fstab today, but managed to get it back. Something I was messing with basically deleted the /home entry in fstab, but I wasn't aware that it had done that, and the system kept working normally. When I went to reboot the system (for other reasons), the system was hosed and would not even let me log in (not even on the Ctrl-Alt-F3 console). I eventually zero'd in on the fstab problem, recreated the missing line, and I'm now posting from that system.
But I just put in a generic line, with options="defaults", dump=0 and pass=2. I suspect that dump and pass are fine as is, but I bet the options should be some besides the defaults. Can someone look at a vanilla 18.04 system and tell me what the options are for the /home mount? auto_da_alloc?
I did search this forum before posting. There's a thread from 2011 that says just defaults is fine, but that's 8 years old ...
Even longer version with background on the screwup:
I upgraded to 18.04 week ago. I kept my /home partition, copied to a new drive, and installed the OS around that. It had worked great for a week now.
Today I was working on setting up a backup process, and was fiddling around with mounting other drives, including an external drive. The external drive was an existing HDD that I was putting into a brand new SATA3/USB enclosure, so my first step was to just make sure that the new enclosure worked.
The new enclosure/drive showed up in Ubuntu's Disks utility, and I could see the old partitions. I mounted one of the partitions to confirm that worked, and ran a df (or something like that) to confirm it.
That's when I noticed that it had mounted the new partition at /home, apparently replacing the regular /home. Uh oh, the mount operation had followed the label of the partition (and yes I now understand why). A quick look at /home confirm that it was seeing the data on the old drive there. Yikes! I immediately unmounted it, and IT WENT BACK TO THE CORRECT HOME PARTITION. The correct files showed up at /home again. Whew, OK, don't do that again!
The system was working normally again, but what I didn't know was that in doing this, the Disks util had messed up the fstab file. The original /home entry was gone, and now the UUID of the correct partition was associated with another partition (more detail that I'll skip here). The next time I rebooted, blammo, no /home.
After an hour of googling and thinking about what I had just been doing before it broke, I figured it out and restored it with a generic line in fstab.
Thanks for reading :)
mount fstab
Short version:
in /etc/fstab on an Ubuntu 18.04 system, what are the typical options used when mounting a partition as /home? Just "defaults 0 2", or something else?
Longer version:
I screwed up my /etc/fstab today, but managed to get it back. Something I was messing with basically deleted the /home entry in fstab, but I wasn't aware that it had done that, and the system kept working normally. When I went to reboot the system (for other reasons), the system was hosed and would not even let me log in (not even on the Ctrl-Alt-F3 console). I eventually zero'd in on the fstab problem, recreated the missing line, and I'm now posting from that system.
But I just put in a generic line, with options="defaults", dump=0 and pass=2. I suspect that dump and pass are fine as is, but I bet the options should be some besides the defaults. Can someone look at a vanilla 18.04 system and tell me what the options are for the /home mount? auto_da_alloc?
I did search this forum before posting. There's a thread from 2011 that says just defaults is fine, but that's 8 years old ...
Even longer version with background on the screwup:
I upgraded to 18.04 week ago. I kept my /home partition, copied to a new drive, and installed the OS around that. It had worked great for a week now.
Today I was working on setting up a backup process, and was fiddling around with mounting other drives, including an external drive. The external drive was an existing HDD that I was putting into a brand new SATA3/USB enclosure, so my first step was to just make sure that the new enclosure worked.
The new enclosure/drive showed up in Ubuntu's Disks utility, and I could see the old partitions. I mounted one of the partitions to confirm that worked, and ran a df (or something like that) to confirm it.
That's when I noticed that it had mounted the new partition at /home, apparently replacing the regular /home. Uh oh, the mount operation had followed the label of the partition (and yes I now understand why). A quick look at /home confirm that it was seeing the data on the old drive there. Yikes! I immediately unmounted it, and IT WENT BACK TO THE CORRECT HOME PARTITION. The correct files showed up at /home again. Whew, OK, don't do that again!
The system was working normally again, but what I didn't know was that in doing this, the Disks util had messed up the fstab file. The original /home entry was gone, and now the UUID of the correct partition was associated with another partition (more detail that I'll skip here). The next time I rebooted, blammo, no /home.
After an hour of googling and thinking about what I had just been doing before it broke, I figured it out and restored it with a generic line in fstab.
Thanks for reading :)
mount fstab
mount fstab
asked 3 mins ago
Chris C.Chris C.
12
12
add a comment |
add a comment |
0
active
oldest
votes
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117270%2fneed-generic-home-entry-for-ubuntu-18-04-etc-fstab%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117270%2fneed-generic-home-entry-for-ubuntu-18-04-etc-fstab%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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