Otdfbt

Multi tool use

Is there a Spanish version of "dot your i's and cross your t's" that includes the letter 'ñ'?

Is the Standard Deduction better than Itemized when both are the same amount?

How do I keep my slimes from escaping their pens?

Why did the IBM 650 use bi-quinary?

Why are there no cargo aircraft with "flying wing" design?

How to say 'striped' in Latin

What is the longest distance a 13th-level monk can jump while attacking on the same turn?

How to bypass password on Windows XP account?

Is it true to say that an hosting provider's DNS server is what links the entire hosting environment to ICANN?

WAN encapsulation

When to stop saving and start investing?

Why is "Captain Marvel" translated as male in Portugal?

How to draw this diagram using TikZ package?

How to motivate offshore teams and trust them to deliver?

Is a manifold-with-boundary with given interior and non-empty boundary essentially unique?

What makes black pepper strong or mild?

Why does Python start at index 1 when iterating an array backwards?

When is phishing education going too far?

Is it possible to boil a liquid by just mixing many immiscible liquids together?

Is it true that "carbohydrates are of no use for the basal metabolic need"?

Are my PIs rude or am I just being too sensitive?

Does accepting a pardon have any bearing on trying that person for the same crime in a sovereign jurisdiction?

Did Xerox really develop the first LAN?

The logistics of corpse disposal

Continue boot with offline fstab disk (linux/systemd)

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

2

During boot, with pre-systemd versions of Ubuntu server (eg. 14.04), if a non-critical fstab disk was offline, the system would wait to mount the disk (30s iirc), timeout and continue booting.

Since upgrading through 16.04 to Ubuntu 18.04, thanks to systemd's dependencies I presume, a missing fstab disk stops the boot process resulting in the "Emergency mode... Press Enter for Maintenance" prompt at boot time.

1. Is there a way to change this behaviour by default? Ie. simply continue booting or an option to flag disks as non-critical?


2. Failing that, is there a straightforward systemctl command to 'continue booting ignoring missing disk' from maintenance?

linux ubuntu boot systemd fstab

share|improve this question

edited Apr 10 at 13:49

sebt

asked Apr 10 at 13:38

sebtsebt

1113

New contributor

sebt 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 | 

2

During boot, with pre-systemd versions of Ubuntu server (eg. 14.04), if a non-critical fstab disk was offline, the system would wait to mount the disk (30s iirc), timeout and continue booting.

Since upgrading through 16.04 to Ubuntu 18.04, thanks to systemd's dependencies I presume, a missing fstab disk stops the boot process resulting in the "Emergency mode... Press Enter for Maintenance" prompt at boot time.

1. Is there a way to change this behaviour by default? Ie. simply continue booting or an option to flag disks as non-critical?


2. Failing that, is there a straightforward systemctl command to 'continue booting ignoring missing disk' from maintenance?

linux ubuntu boot systemd fstab

share|improve this question

edited Apr 10 at 13:49

sebt

asked Apr 10 at 13:38

sebtsebt

1113

New contributor

sebt 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 | 

During boot, with pre-systemd versions of Ubuntu server (eg. 14.04), if a non-critical fstab disk was offline, the system would wait to mount the disk (30s iirc), timeout and continue booting.

Since upgrading through 16.04 to Ubuntu 18.04, thanks to systemd's dependencies I presume, a missing fstab disk stops the boot process resulting in the "Emergency mode... Press Enter for Maintenance" prompt at boot time.

1. Is there a way to change this behaviour by default? Ie. simply continue booting or an option to flag disks as non-critical?


2. Failing that, is there a straightforward systemctl command to 'continue booting ignoring missing disk' from maintenance?

linux ubuntu boot systemd fstab

share|improve this question

edited Apr 10 at 13:49

sebt

asked Apr 10 at 13:38

sebtsebt

1113

New contributor

sebt 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

edited Apr 10 at 13:49

sebt

asked Apr 10 at 13:38

sebtsebt

1113

New contributor

sebt 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

edited Apr 10 at 13:49

sebt

asked Apr 10 at 13:38

sebtsebt

1113

New contributor

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

asked Apr 10 at 13:38

sebtsebt

1113

New contributor

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

asked Apr 10 at 13:38

sebtsebt

1113

1 Answer
1

active

oldest

votes

4

In the /etc/fstab entries for your mounts you can add systemd specific options, including the nofail option will instruct systemd that the boot can continue without waiting for the mount unit and regardless whether the mount point can be mounted successfully.

You can add the options x-systemd.device-timeout and or x-systemd.mount-timeout to customize time-outs.

share|improve this answer

answered Apr 10 at 14:00

HBruijnHBruijn

56.5k1190150

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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
);



);

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

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962432%2fcontinue-boot-with-offline-fstab-disk-linux-systemd%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

4

In the /etc/fstab entries for your mounts you can add systemd specific options, including the nofail option will instruct systemd that the boot can continue without waiting for the mount unit and regardless whether the mount point can be mounted successfully.

You can add the options x-systemd.device-timeout and or x-systemd.mount-timeout to customize time-outs.

share|improve this answer

answered Apr 10 at 14:00

HBruijnHBruijn

56.5k1190150

add a comment | 

4

In the /etc/fstab entries for your mounts you can add systemd specific options, including the nofail option will instruct systemd that the boot can continue without waiting for the mount unit and regardless whether the mount point can be mounted successfully.

You can add the options x-systemd.device-timeout and or x-systemd.mount-timeout to customize time-outs.

share|improve this answer

answered Apr 10 at 14:00

HBruijnHBruijn

56.5k1190150

add a comment | 

In the /etc/fstab entries for your mounts you can add systemd specific options, including the nofail option will instruct systemd that the boot can continue without waiting for the mount unit and regardless whether the mount point can be mounted successfully.

You can add the options x-systemd.device-timeout and or x-systemd.mount-timeout to customize time-outs.

share|improve this answer

answered Apr 10 at 14:00

HBruijnHBruijn

56.5k1190150

share|improve this answer

answered Apr 10 at 14:00

HBruijnHBruijn

56.5k1190150

answered Apr 10 at 14:00

HBruijnHBruijn

56.5k1190150

answered Apr 10 at 14:00

HBruijnHBruijn

56.5k1190150