Ubuntu 16.04 halts during shutdown UNLESS I restart systemd prior to shutdown
After years without issues on my Ubuntu 16.04, I have had this issue, where shutting my computer down would lead to my computer halting on a screen like the one in the picture below (revealed by pressing ESC).
HOWEVER, after some experimenting, I found out that by typing in a terminal and executing the commandsystemctl daemon-reexec
prior to invoking the shut down, the system would fast and surely shut down properly.
Could someone help me out to pinpont the cause of such behaviour?
Thank you in advance, and wishes of a merry Christmas
16.04 shutdown systemd
asked Dec 25 '18 at 9:12
ed0ed0
721217
|
show 2 more comments
After years without issues on my Ubuntu 16.04, I have had this issue, where shutting my computer down would lead to my computer halting on a screen like the one in the picture below (revealed by pressing ESC).
HOWEVER, after some experimenting, I found out that by typing in a terminal and executing the commandsystemctl daemon-reexec
prior to invoking the shut down, the system would fast and surely shut down properly.
Could someone help me out to pinpont the cause of such behaviour?
Thank you in advance, and wishes of a merry Christmas
16.04 shutdown systemd
asked Dec 25 '18 at 9:12
ed0ed0
721217
1
How about that File System Check entry? Is it possible that you need to run fsck as root manually on that disk?
– starkus
Dec 28 '18 at 18:17
1
you could also try to disable the automatic fsck for that device like: askubuntu.com/a/981295/196781
– starkus
Dec 28 '18 at 18:47
I admit to not fully understand your suggestion, as I don't know exactly how that would interfere with systemd or the boot process
– ed0
Dec 29 '18 at 22:34
however, fsck seems not to be requiring super user permissions on my system, this is the output of the command pastebin.com/W6GWdXfD
– ed0
Dec 29 '18 at 22:36
I thought about the need of a manual file check because of that entry, while shutting down your machine. And that maybe the automatic filecheck fails due to some error.
– starkus
Dec 30 '18 at 11:27
|
show 2 more comments
After years without issues on my Ubuntu 16.04, I have had this issue, where shutting my computer down would lead to my computer halting on a screen like the one in the picture below (revealed by pressing ESC).
HOWEVER, after some experimenting, I found out that by typing in a terminal and executing the commandsystemctl daemon-reexec
prior to invoking the shut down, the system would fast and surely shut down properly.
Could someone help me out to pinpont the cause of such behaviour?
Thank you in advance, and wishes of a merry Christmas
16.04 shutdown systemd
asked Dec 25 '18 at 9:12
ed0ed0
721217
After years without issues on my Ubuntu 16.04, I have had this issue, where shutting my computer down would lead to my computer halting on a screen like the one in the picture below (revealed by pressing ESC).
HOWEVER, after some experimenting, I found out that by typing in a terminal and executing the commandsystemctl daemon-reexec
prior to invoking the shut down, the system would fast and surely shut down properly.
Could someone help me out to pinpont the cause of such behaviour?
Thank you in advance, and wishes of a merry Christmas
16.04 shutdown systemd
16.04 shutdown systemd
asked Dec 25 '18 at 9:12
ed0ed0
721217
asked Dec 25 '18 at 9:12
ed0ed0
721217
asked Dec 25 '18 at 9:12
ed0ed0
721217
asked Dec 25 '18 at 9:12
ed0ed0
721217
asked Dec 25 '18 at 9:12
ed0ed0
721217
721217
1
How about that File System Check entry? Is it possible that you need to run fsck as root manually on that disk?
– starkus
Dec 28 '18 at 18:17
1
you could also try to disable the automatic fsck for that device like: askubuntu.com/a/981295/196781
– starkus
Dec 28 '18 at 18:47
I admit to not fully understand your suggestion, as I don't know exactly how that would interfere with systemd or the boot process
– ed0
Dec 29 '18 at 22:34
however, fsck seems not to be requiring super user permissions on my system, this is the output of the command pastebin.com/W6GWdXfD
– ed0
Dec 29 '18 at 22:36
I thought about the need of a manual file check because of that entry, while shutting down your machine. And that maybe the automatic filecheck fails due to some error.
– starkus
Dec 30 '18 at 11:27
|
show 2 more comments
1
How about that File System Check entry? Is it possible that you need to run fsck as root manually on that disk?
– starkus
Dec 28 '18 at 18:17
1
you could also try to disable the automatic fsck for that device like: askubuntu.com/a/981295/196781
– starkus
Dec 28 '18 at 18:47
I admit to not fully understand your suggestion, as I don't know exactly how that would interfere with systemd or the boot process
– ed0
Dec 29 '18 at 22:34
however, fsck seems not to be requiring super user permissions on my system, this is the output of the command pastebin.com/W6GWdXfD
– ed0
Dec 29 '18 at 22:36
I thought about the need of a manual file check because of that entry, while shutting down your machine. And that maybe the automatic filecheck fails due to some error.
– starkus
Dec 30 '18 at 11:27
1
1
How about that File System Check entry? Is it possible that you need to run fsck as root manually on that disk?
– starkus
Dec 28 '18 at 18:17
How about that File System Check entry? Is it possible that you need to run fsck as root manually on that disk?
– starkus
Dec 28 '18 at 18:17
1
1
you could also try to disable the automatic fsck for that device like: askubuntu.com/a/981295/196781
– starkus
Dec 28 '18 at 18:47
you could also try to disable the automatic fsck for that device like: askubuntu.com/a/981295/196781
– starkus
Dec 28 '18 at 18:47
I admit to not fully understand your suggestion, as I don't know exactly how that would interfere with systemd or the boot process
– ed0
Dec 29 '18 at 22:34
I admit to not fully understand your suggestion, as I don't know exactly how that would interfere with systemd or the boot process
– ed0
Dec 29 '18 at 22:34
however, fsck seems not to be requiring super user permissions on my system, this is the output of the command pastebin.com/W6GWdXfD
– ed0
Dec 29 '18 at 22:36
however, fsck seems not to be requiring super user permissions on my system, this is the output of the command pastebin.com/W6GWdXfD
– ed0
Dec 29 '18 at 22:36
I thought about the need of a manual file check because of that entry, while shutting down your machine. And that maybe the automatic filecheck fails due to some error.
– starkus
Dec 30 '18 at 11:27
I thought about the need of a manual file check because of that entry, while shutting down your machine. And that maybe the automatic filecheck fails due to some error.
– starkus
Dec 30 '18 at 11:27
|
show 2 more comments
1 Answer
1
active
oldest
votes
systemd - Failed unmounting /boot/efi
The closest error I can find to this is from Arch Linux: [SOLVED] Failed unmount temporary directory on shutdown
The solution there is to tell systemd to unmount the temporary directory and see what error messages occur.
To see the current status first use:
$ systemctl status /boot/efi
● boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: active (mounted) since Sun 2018-12-30 15:01:14 MST; 1 day 3h ago
Where: /boot/efi
What: /dev/nvme0n1p2
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 910 ExecMount=/bin/mount /dev/disk/by-uuid/D656-F2A8 /boot/efi -t vfat -o umask=
Dec 30 15:01:14 alien systemd[1]: Mounting /boot/efi...
Dec 30 15:01:14 alien systemd[1]: Mounted /boot/efi.
Save all your work first and use:
$ systemctl stop /boot/efi
A dialog box will appear requesting your password.
For myself I received no errors and then used:
$ systemctl status /boot/efi
● boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: inactive (dead) since Mon 2018-12-31 18:27:53 MST; 3s ago
Where: /boot/efi
What: /dev/disk/by-uuid/D656-F2A8
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 21384 ExecUnmount=/bin/umount /boot/efi (code=exited, status=0/SUCCESS)
Process: 20627 ExecMount=/bin/mount /dev/disk/by-uuid/D656-F2A8 /boot/efi -t vfat -o umas
Dec 30 15:01:14 alien systemd[1]: Mounting /boot/efi...
Dec 30 15:01:14 alien systemd[1]: Mounted /boot/efi.
Dec 31 18:27:53 alien systemd[1]: Unmounting /boot/efi...
Dec 31 18:27:53 alien systemd[1]: Unmounted /boot/efi.
Finally to return system to normal state use:
$ systemctl start /boot/efi
In your case hopefully some error messages will occur when unmounting /boot/efi.
answered Jan 1 at 1:31
WinEunuuchs2UnixWinEunuuchs2Unix
44.8k1080172
add a comment |
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%2f1104407%2fubuntu-16-04-halts-during-shutdown-unless-i-restart-systemd-prior-to-shutdown%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
systemd - Failed unmounting /boot/efi
The closest error I can find to this is from Arch Linux: [SOLVED] Failed unmount temporary directory on shutdown
The solution there is to tell systemd to unmount the temporary directory and see what error messages occur.
To see the current status first use:
$ systemctl status /boot/efi
● boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: active (mounted) since Sun 2018-12-30 15:01:14 MST; 1 day 3h ago
Where: /boot/efi
What: /dev/nvme0n1p2
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 910 ExecMount=/bin/mount /dev/disk/by-uuid/D656-F2A8 /boot/efi -t vfat -o umask=
Dec 30 15:01:14 alien systemd[1]: Mounting /boot/efi...
Dec 30 15:01:14 alien systemd[1]: Mounted /boot/efi.
Save all your work first and use:
$ systemctl stop /boot/efi
A dialog box will appear requesting your password.
For myself I received no errors and then used:
$ systemctl status /boot/efi
● boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: inactive (dead) since Mon 2018-12-31 18:27:53 MST; 3s ago
Where: /boot/efi
What: /dev/disk/by-uuid/D656-F2A8
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 21384 ExecUnmount=/bin/umount /boot/efi (code=exited, status=0/SUCCESS)
Process: 20627 ExecMount=/bin/mount /dev/disk/by-uuid/D656-F2A8 /boot/efi -t vfat -o umas
Dec 30 15:01:14 alien systemd[1]: Mounting /boot/efi...
Dec 30 15:01:14 alien systemd[1]: Mounted /boot/efi.
Dec 31 18:27:53 alien systemd[1]: Unmounting /boot/efi...
Dec 31 18:27:53 alien systemd[1]: Unmounted /boot/efi.
Finally to return system to normal state use:
$ systemctl start /boot/efi
In your case hopefully some error messages will occur when unmounting /boot/efi.
answered Jan 1 at 1:31
WinEunuuchs2UnixWinEunuuchs2Unix
44.8k1080172
add a comment |
systemd - Failed unmounting /boot/efi
The closest error I can find to this is from Arch Linux: [SOLVED] Failed unmount temporary directory on shutdown
The solution there is to tell systemd to unmount the temporary directory and see what error messages occur.
To see the current status first use:
$ systemctl status /boot/efi
● boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: active (mounted) since Sun 2018-12-30 15:01:14 MST; 1 day 3h ago
Where: /boot/efi
What: /dev/nvme0n1p2
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 910 ExecMount=/bin/mount /dev/disk/by-uuid/D656-F2A8 /boot/efi -t vfat -o umask=
Dec 30 15:01:14 alien systemd[1]: Mounting /boot/efi...
Dec 30 15:01:14 alien systemd[1]: Mounted /boot/efi.
Save all your work first and use:
$ systemctl stop /boot/efi
A dialog box will appear requesting your password.
For myself I received no errors and then used:
$ systemctl status /boot/efi
● boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: inactive (dead) since Mon 2018-12-31 18:27:53 MST; 3s ago
Where: /boot/efi
What: /dev/disk/by-uuid/D656-F2A8
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 21384 ExecUnmount=/bin/umount /boot/efi (code=exited, status=0/SUCCESS)
Process: 20627 ExecMount=/bin/mount /dev/disk/by-uuid/D656-F2A8 /boot/efi -t vfat -o umas
Dec 30 15:01:14 alien systemd[1]: Mounting /boot/efi...
Dec 30 15:01:14 alien systemd[1]: Mounted /boot/efi.
Dec 31 18:27:53 alien systemd[1]: Unmounting /boot/efi...
Dec 31 18:27:53 alien systemd[1]: Unmounted /boot/efi.
Finally to return system to normal state use:
$ systemctl start /boot/efi
In your case hopefully some error messages will occur when unmounting /boot/efi.
answered Jan 1 at 1:31
WinEunuuchs2UnixWinEunuuchs2Unix
44.8k1080172
add a comment |
systemd - Failed unmounting /boot/efi
The closest error I can find to this is from Arch Linux: [SOLVED] Failed unmount temporary directory on shutdown
The solution there is to tell systemd to unmount the temporary directory and see what error messages occur.
To see the current status first use:
$ systemctl status /boot/efi
● boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: active (mounted) since Sun 2018-12-30 15:01:14 MST; 1 day 3h ago
Where: /boot/efi
What: /dev/nvme0n1p2
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 910 ExecMount=/bin/mount /dev/disk/by-uuid/D656-F2A8 /boot/efi -t vfat -o umask=
Dec 30 15:01:14 alien systemd[1]: Mounting /boot/efi...
Dec 30 15:01:14 alien systemd[1]: Mounted /boot/efi.
Save all your work first and use:
$ systemctl stop /boot/efi
A dialog box will appear requesting your password.
For myself I received no errors and then used:
$ systemctl status /boot/efi
● boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: inactive (dead) since Mon 2018-12-31 18:27:53 MST; 3s ago
Where: /boot/efi
What: /dev/disk/by-uuid/D656-F2A8
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 21384 ExecUnmount=/bin/umount /boot/efi (code=exited, status=0/SUCCESS)
Process: 20627 ExecMount=/bin/mount /dev/disk/by-uuid/D656-F2A8 /boot/efi -t vfat -o umas
Dec 30 15:01:14 alien systemd[1]: Mounting /boot/efi...
Dec 30 15:01:14 alien systemd[1]: Mounted /boot/efi.
Dec 31 18:27:53 alien systemd[1]: Unmounting /boot/efi...
Dec 31 18:27:53 alien systemd[1]: Unmounted /boot/efi.
Finally to return system to normal state use:
$ systemctl start /boot/efi
In your case hopefully some error messages will occur when unmounting /boot/efi.
answered Jan 1 at 1:31
WinEunuuchs2UnixWinEunuuchs2Unix
44.8k1080172
systemd - Failed unmounting /boot/efi
The closest error I can find to this is from Arch Linux: [SOLVED] Failed unmount temporary directory on shutdown
The solution there is to tell systemd to unmount the temporary directory and see what error messages occur.
To see the current status first use:
$ systemctl status /boot/efi
● boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: active (mounted) since Sun 2018-12-30 15:01:14 MST; 1 day 3h ago
Where: /boot/efi
What: /dev/nvme0n1p2
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 910 ExecMount=/bin/mount /dev/disk/by-uuid/D656-F2A8 /boot/efi -t vfat -o umask=
Dec 30 15:01:14 alien systemd[1]: Mounting /boot/efi...
Dec 30 15:01:14 alien systemd[1]: Mounted /boot/efi.
Save all your work first and use:
$ systemctl stop /boot/efi
A dialog box will appear requesting your password.
For myself I received no errors and then used:
$ systemctl status /boot/efi
● boot-efi.mount - /boot/efi
Loaded: loaded (/etc/fstab; bad; vendor preset: enabled)
Active: inactive (dead) since Mon 2018-12-31 18:27:53 MST; 3s ago
Where: /boot/efi
What: /dev/disk/by-uuid/D656-F2A8
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 21384 ExecUnmount=/bin/umount /boot/efi (code=exited, status=0/SUCCESS)
Process: 20627 ExecMount=/bin/mount /dev/disk/by-uuid/D656-F2A8 /boot/efi -t vfat -o umas
Dec 30 15:01:14 alien systemd[1]: Mounting /boot/efi...
Dec 30 15:01:14 alien systemd[1]: Mounted /boot/efi.
Dec 31 18:27:53 alien systemd[1]: Unmounting /boot/efi...
Dec 31 18:27:53 alien systemd[1]: Unmounted /boot/efi.
Finally to return system to normal state use:
$ systemctl start /boot/efi
In your case hopefully some error messages will occur when unmounting /boot/efi.
answered Jan 1 at 1:31
WinEunuuchs2UnixWinEunuuchs2Unix
44.8k1080172
edited Jan 1 at 1:47
answered Jan 1 at 1:31
WinEunuuchs2UnixWinEunuuchs2Unix
44.8k1080172
answered Jan 1 at 1:31
WinEunuuchs2UnixWinEunuuchs2Unix
44.8k1080172
answered Jan 1 at 1:31
WinEunuuchs2UnixWinEunuuchs2Unix
44.8k1080172
44.8k1080172
add a comment |
add a comment |
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%2f1104407%2fubuntu-16-04-halts-during-shutdown-unless-i-restart-systemd-prior-to-shutdown%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
1
How about that File System Check entry? Is it possible that you need to run fsck as root manually on that disk?
– starkus
Dec 28 '18 at 18:17
1
you could also try to disable the automatic fsck for that device like: askubuntu.com/a/981295/196781
– starkus
Dec 28 '18 at 18:47
I admit to not fully understand your suggestion, as I don't know exactly how that would interfere with systemd or the boot process
– ed0
Dec 29 '18 at 22:34
however, fsck seems not to be requiring super user permissions on my system, this is the output of the command pastebin.com/W6GWdXfD
– ed0
Dec 29 '18 at 22:36
I thought about the need of a manual file check because of that entry, while shutting down your machine. And that maybe the automatic filecheck fails due to some error.
– starkus
Dec 30 '18 at 11:27