Ubuntu system won’t boot with error “Failed to start Create Volatile Files and Directories + Network Time...
I'm using Ubuntu 18.04.1 LTS and when I start my latpop, the screen stops at
[Failed] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-temfiles-setup.service' for details
[ .... ]
[Failed] Failed to start Network Time Synchronisation.
See 'systemctl status systemd-timesyncd.service' for details
[...]
I'm running the command shell from Ubuntu Recovery Mode.
linux ubuntu temporary-files
edited Feb 8 at 16:52
JakeGould
32.1k1098141
asked Feb 8 at 16:37
Vincere SempreVincere Sempre
12
add a comment |
I'm using Ubuntu 18.04.1 LTS and when I start my latpop, the screen stops at
[Failed] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-temfiles-setup.service' for details
[ .... ]
[Failed] Failed to start Network Time Synchronisation.
See 'systemctl status systemd-timesyncd.service' for details
[...]
I'm running the command shell from Ubuntu Recovery Mode.
linux ubuntu temporary-files
edited Feb 8 at 16:52
JakeGould
32.1k1098141
asked Feb 8 at 16:37
Vincere SempreVincere Sempre
12
add a comment |
I'm using Ubuntu 18.04.1 LTS and when I start my latpop, the screen stops at
[Failed] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-temfiles-setup.service' for details
[ .... ]
[Failed] Failed to start Network Time Synchronisation.
See 'systemctl status systemd-timesyncd.service' for details
[...]
I'm running the command shell from Ubuntu Recovery Mode.
linux ubuntu temporary-files
edited Feb 8 at 16:52
JakeGould
32.1k1098141
asked Feb 8 at 16:37
Vincere SempreVincere Sempre
12
I'm using Ubuntu 18.04.1 LTS and when I start my latpop, the screen stops at
[Failed] Failed to start Create Volatile Files and Directories.
See 'systemctl status systemd-temfiles-setup.service' for details
[ .... ]
[Failed] Failed to start Network Time Synchronisation.
See 'systemctl status systemd-timesyncd.service' for details
[...]
I'm running the command shell from Ubuntu Recovery Mode.
linux ubuntu temporary-files
linux ubuntu temporary-files
edited Feb 8 at 16:52
JakeGould
32.1k1098141
asked Feb 8 at 16:37
Vincere SempreVincere Sempre
12
edited Feb 8 at 16:52
JakeGould
32.1k1098141
asked Feb 8 at 16:37
Vincere SempreVincere Sempre
12
edited Feb 8 at 16:52
JakeGould
32.1k1098141
edited Feb 8 at 16:52
JakeGould
32.1k1098141
edited Feb 8 at 16:52
JakeGould
32.1k1098141
32.1k1098141
asked Feb 8 at 16:37
Vincere SempreVincere Sempre
12
asked Feb 8 at 16:37
Vincere SempreVincere Sempre
12
asked Feb 8 at 16:37
Vincere SempreVincere Sempre
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You won't be able to use your usual command shell hence
1. Restart your Ubuntu in Recovery Mode. You can do so by choosing Open Ubuntu with Advanced Option from your Grub menu
- For me, this issue occured because, I had wrongfully given access of some system files to
usernameinstead of myroot
There are other ways you you could get this issue so, definitely check out other resources as well.
Solution
0. You can check your ownership of / and /var folder
$ stat -c "%U %G" /
or,
$ stat -c "%U %G" /var/
You might be getting,username username
Start with giving ownership back to root
$ chown -R root:root /
it'll take a few minutesRemount.
$ mount -o remount,rw /
Restart these services.
- Tmpfiles-setup Services
$ systemctl start systemd-tmpfiles-setup.service - Timesyncd Service
$ systemctl start systemd-timesyncd.service
- Tmpfiles-setup Services
Reboot
$ reboot
If this didn't solve the issue for you, you might want to look here and then here
I hope this helped. Be well!
answered Feb 8 at 16:55
Vincere SempreVincere Sempre
12
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1403591%2fubuntu-system-won-t-boot-with-error-failed-to-start-create-volatile-files-and-d%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
You won't be able to use your usual command shell hence
1. Restart your Ubuntu in Recovery Mode. You can do so by choosing Open Ubuntu with Advanced Option from your Grub menu
- For me, this issue occured because, I had wrongfully given access of some system files to
usernameinstead of myroot
There are other ways you you could get this issue so, definitely check out other resources as well.
Solution
0. You can check your ownership of / and /var folder
$ stat -c "%U %G" /
or,
$ stat -c "%U %G" /var/
You might be getting,username username
Start with giving ownership back to root
$ chown -R root:root /
it'll take a few minutesRemount.
$ mount -o remount,rw /
Restart these services.
- Tmpfiles-setup Services
$ systemctl start systemd-tmpfiles-setup.service - Timesyncd Service
$ systemctl start systemd-timesyncd.service
- Tmpfiles-setup Services
Reboot
$ reboot
If this didn't solve the issue for you, you might want to look here and then here
I hope this helped. Be well!
answered Feb 8 at 16:55
Vincere SempreVincere Sempre
12
add a comment |
You won't be able to use your usual command shell hence
1. Restart your Ubuntu in Recovery Mode. You can do so by choosing Open Ubuntu with Advanced Option from your Grub menu
- For me, this issue occured because, I had wrongfully given access of some system files to
usernameinstead of myroot
There are other ways you you could get this issue so, definitely check out other resources as well.
Solution
0. You can check your ownership of / and /var folder
$ stat -c "%U %G" /
or,
$ stat -c "%U %G" /var/
You might be getting,username username
Start with giving ownership back to root
$ chown -R root:root /
it'll take a few minutesRemount.
$ mount -o remount,rw /
Restart these services.
- Tmpfiles-setup Services
$ systemctl start systemd-tmpfiles-setup.service - Timesyncd Service
$ systemctl start systemd-timesyncd.service
- Tmpfiles-setup Services
Reboot
$ reboot
If this didn't solve the issue for you, you might want to look here and then here
I hope this helped. Be well!
answered Feb 8 at 16:55
Vincere SempreVincere Sempre
12
add a comment |
You won't be able to use your usual command shell hence
1. Restart your Ubuntu in Recovery Mode. You can do so by choosing Open Ubuntu with Advanced Option from your Grub menu
- For me, this issue occured because, I had wrongfully given access of some system files to
usernameinstead of myroot
There are other ways you you could get this issue so, definitely check out other resources as well.
Solution
0. You can check your ownership of / and /var folder
$ stat -c "%U %G" /
or,
$ stat -c "%U %G" /var/
You might be getting,username username
Start with giving ownership back to root
$ chown -R root:root /
it'll take a few minutesRemount.
$ mount -o remount,rw /
Restart these services.
- Tmpfiles-setup Services
$ systemctl start systemd-tmpfiles-setup.service - Timesyncd Service
$ systemctl start systemd-timesyncd.service
- Tmpfiles-setup Services
Reboot
$ reboot
If this didn't solve the issue for you, you might want to look here and then here
I hope this helped. Be well!
answered Feb 8 at 16:55
Vincere SempreVincere Sempre
12
You won't be able to use your usual command shell hence
1. Restart your Ubuntu in Recovery Mode. You can do so by choosing Open Ubuntu with Advanced Option from your Grub menu
- For me, this issue occured because, I had wrongfully given access of some system files to
usernameinstead of myroot
There are other ways you you could get this issue so, definitely check out other resources as well.
Solution
0. You can check your ownership of / and /var folder
$ stat -c "%U %G" /
or,
$ stat -c "%U %G" /var/
You might be getting,username username
Start with giving ownership back to root
$ chown -R root:root /
it'll take a few minutesRemount.
$ mount -o remount,rw /
Restart these services.
- Tmpfiles-setup Services
$ systemctl start systemd-tmpfiles-setup.service - Timesyncd Service
$ systemctl start systemd-timesyncd.service
- Tmpfiles-setup Services
Reboot
$ reboot
If this didn't solve the issue for you, you might want to look here and then here
I hope this helped. Be well!
answered Feb 8 at 16:55
Vincere SempreVincere Sempre
12
answered Feb 8 at 16:55
Vincere SempreVincere Sempre
12
answered Feb 8 at 16:55
Vincere SempreVincere Sempre
12
answered Feb 8 at 16:55
Vincere SempreVincere Sempre
12
12
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1403591%2fubuntu-system-won-t-boot-with-error-failed-to-start-create-volatile-files-and-d%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
