Boot/systemd problem in Ubuntu

up vote
0
down vote

favorite

I have Ubuntu MATE 16.04.5 running on Raspberry Pi.
I did a apt update/upgrade to install 18 upgraded packages but the system failed on reboot.

It entered emergency mode and on entering Ctl-D I could boot as normal and everything works as normal!

The only problem I could see is is dependencies in systemd

[Sun Nov 18 17:34:57 2018] systemd[1]: sockets.target: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start

[Sun Nov 18 17:34:57 2018] systemd[1]: paths.target: Job paths.target/start deleted to break ordering cycle starting with basic.target/start

[Sun Nov 18 17:34:57 2018] systemd[1]: nfs-mountd.service: Job nfs-mountd.service/start deleted to break ordering cycle starting with nfs-server.service/start

I could restore from backup, but wonder if this is a known issue, or just a random failure?

edited Nov 18 at 9:32

Filipe Brandenburger

6,2021725

asked Nov 18 at 6:59

Milliways

532621

add a comment |

up vote
0
down vote

favorite

I have Ubuntu MATE 16.04.5 running on Raspberry Pi.
I did a apt update/upgrade to install 18 upgraded packages but the system failed on reboot.

It entered emergency mode and on entering Ctl-D I could boot as normal and everything works as normal!

The only problem I could see is is dependencies in systemd

[Sun Nov 18 17:34:57 2018] systemd[1]: sockets.target: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start

[Sun Nov 18 17:34:57 2018] systemd[1]: paths.target: Job paths.target/start deleted to break ordering cycle starting with basic.target/start

[Sun Nov 18 17:34:57 2018] systemd[1]: nfs-mountd.service: Job nfs-mountd.service/start deleted to break ordering cycle starting with nfs-server.service/start

I could restore from backup, but wonder if this is a known issue, or just a random failure?

edited Nov 18 at 9:32

Filipe Brandenburger

6,2021725

asked Nov 18 at 6:59

Milliways

532621

add a comment |

up vote
0
down vote

favorite

I have Ubuntu MATE 16.04.5 running on Raspberry Pi.
I did a apt update/upgrade to install 18 upgraded packages but the system failed on reboot.

It entered emergency mode and on entering Ctl-D I could boot as normal and everything works as normal!

The only problem I could see is is dependencies in systemd

[Sun Nov 18 17:34:57 2018] systemd[1]: sockets.target: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start

[Sun Nov 18 17:34:57 2018] systemd[1]: paths.target: Job paths.target/start deleted to break ordering cycle starting with basic.target/start

[Sun Nov 18 17:34:57 2018] systemd[1]: nfs-mountd.service: Job nfs-mountd.service/start deleted to break ordering cycle starting with nfs-server.service/start

I could restore from backup, but wonder if this is a known issue, or just a random failure?

edited Nov 18 at 9:32

Filipe Brandenburger

6,2021725

asked Nov 18 at 6:59

Milliways

532621

I have Ubuntu MATE 16.04.5 running on Raspberry Pi.
I did a apt update/upgrade to install 18 upgraded packages but the system failed on reboot.

It entered emergency mode and on entering Ctl-D I could boot as normal and everything works as normal!

The only problem I could see is is dependencies in systemd

[Sun Nov 18 17:34:57 2018] systemd[1]: sockets.target: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start

[Sun Nov 18 17:34:57 2018] systemd[1]: paths.target: Job paths.target/start deleted to break ordering cycle starting with basic.target/start

[Sun Nov 18 17:34:57 2018] systemd[1]: nfs-mountd.service: Job nfs-mountd.service/start deleted to break ordering cycle starting with nfs-server.service/start

I could restore from backup, but wonder if this is a known issue, or just a random failure?

ubuntu boot

edited Nov 18 at 9:32

Filipe Brandenburger

6,2021725

asked Nov 18 at 6:59

Milliways

532621

edited Nov 18 at 9:32

Filipe Brandenburger

6,2021725

asked Nov 18 at 6:59

Milliways

532621

edited Nov 18 at 9:32

Filipe Brandenburger

6,2021725

edited Nov 18 at 9:32

Filipe Brandenburger

6,2021725

edited Nov 18 at 9:32

Filipe Brandenburger

6,2021725

asked Nov 18 at 6:59

Milliways

532621

asked Nov 18 at 6:59

Milliways

532621

asked Nov 18 at 6:59

Milliways

532621

add a comment |

1 Answer
1

active

oldest

votes

up vote
0
down vote

I would try a hard reboot and see it the problem recurs. If it doesn't, this was possibly a transient problem with the upgrade ... that has resolved itself.

If it does, then read the advice in generic methodology to debug ordering cycles in systemd, and when you are ready reboot into emergency mode ans see if you can see what is causing the cycle.

(My guess would be that you are either trying to export NFS file systems or mount NFS file systems too early in the startup sequence.)

answered Nov 18 at 10:42

Stephen C

27614

add a comment |

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',
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

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f482480%2fboot-systemd-problem-in-ubuntu%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
0
down vote

I would try a hard reboot and see it the problem recurs. If it doesn't, this was possibly a transient problem with the upgrade ... that has resolved itself.

If it does, then read the advice in generic methodology to debug ordering cycles in systemd, and when you are ready reboot into emergency mode ans see if you can see what is causing the cycle.

(My guess would be that you are either trying to export NFS file systems or mount NFS file systems too early in the startup sequence.)

answered Nov 18 at 10:42

Stephen C

27614

add a comment |

up vote
0
down vote

I would try a hard reboot and see it the problem recurs. If it doesn't, this was possibly a transient problem with the upgrade ... that has resolved itself.

If it does, then read the advice in generic methodology to debug ordering cycles in systemd, and when you are ready reboot into emergency mode ans see if you can see what is causing the cycle.

(My guess would be that you are either trying to export NFS file systems or mount NFS file systems too early in the startup sequence.)

answered Nov 18 at 10:42

Stephen C

27614

add a comment |

up vote
0
down vote

I would try a hard reboot and see it the problem recurs. If it doesn't, this was possibly a transient problem with the upgrade ... that has resolved itself.

If it does, then read the advice in generic methodology to debug ordering cycles in systemd, and when you are ready reboot into emergency mode ans see if you can see what is causing the cycle.

(My guess would be that you are either trying to export NFS file systems or mount NFS file systems too early in the startup sequence.)

answered Nov 18 at 10:42

Stephen C

27614

I would try a hard reboot and see it the problem recurs. If it doesn't, this was possibly a transient problem with the upgrade ... that has resolved itself.

If it does, then read the advice in generic methodology to debug ordering cycles in systemd, and when you are ready reboot into emergency mode ans see if you can see what is causing the cycle.

(My guess would be that you are either trying to export NFS file systems or mount NFS file systems too early in the startup sequence.)

answered Nov 18 at 10:42

Stephen C

27614

answered Nov 18 at 10:42

Stephen C

27614

answered Nov 18 at 10:42

Stephen C

27614

answered Nov 18 at 10:42

Stephen C

27614

add a comment |

draft saved

draft discarded

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfrtjryk