Reason for orphaned inodes and boot failure fixable by manual fsck?
my first post here.
I am running 18.04.1 and I have recently gotten an error while booting - the screen remains black after POST and nothing happens. I went into recovery mode and found that my root partition doesn't get mounted due to orphaned inodes and the like - I cannot supply a log since I have rebooted twice since fixing that and I do not actually know how to access historical boot logs. I could fix it by running fsck.ext4 -p /dev/mapper/name-of-root-partition, and everything is fine and dandy again... However, I know this will probably happen again in the future, as I have had the exact same problem with Debian - it was in fact one of the reasons I switched to Ubuntu (the other being worse compatibility on Debian and some other small problems I didn't feel like fixing by hand, on Ubuntu it just werks).
Now fixing the problem is easy and rather pain-free, but I wonder what could be the reason, as it happens fairly frequently (I reckon twice a week) - I realized it might have something to do with me shutting the computer down with sudo shutdown now. Am I on the right track? I could not find any proper information about this approach being "dangerous" but at the same time everybody seems to be inputting various arguments before now, never running it "raw".
My hardware is pretty generic and I would assume rather unimportant, really. I have a single Kingston SSD and the weirdest thing in my setup is probably me forcing the kernel to load amdgpu instead of the default radeon drivers.
boot shutdown fsck inode
asked Jan 7 at 11:13
Michal TomaszukMichal Tomaszuk
111
New contributor
Michal Tomaszuk 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 |
my first post here.
I am running 18.04.1 and I have recently gotten an error while booting - the screen remains black after POST and nothing happens. I went into recovery mode and found that my root partition doesn't get mounted due to orphaned inodes and the like - I cannot supply a log since I have rebooted twice since fixing that and I do not actually know how to access historical boot logs. I could fix it by running fsck.ext4 -p /dev/mapper/name-of-root-partition, and everything is fine and dandy again... However, I know this will probably happen again in the future, as I have had the exact same problem with Debian - it was in fact one of the reasons I switched to Ubuntu (the other being worse compatibility on Debian and some other small problems I didn't feel like fixing by hand, on Ubuntu it just werks).
Now fixing the problem is easy and rather pain-free, but I wonder what could be the reason, as it happens fairly frequently (I reckon twice a week) - I realized it might have something to do with me shutting the computer down with sudo shutdown now. Am I on the right track? I could not find any proper information about this approach being "dangerous" but at the same time everybody seems to be inputting various arguments before now, never running it "raw".
My hardware is pretty generic and I would assume rather unimportant, really. I have a single Kingston SSD and the weirdest thing in my setup is probably me forcing the kernel to load amdgpu instead of the default radeon drivers.
boot shutdown fsck inode
asked Jan 7 at 11:13
Michal TomaszukMichal Tomaszuk
111
New contributor
Michal Tomaszuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
sudo shutdown nowwould not leave you with orphaned inodes, let alone an unbootable system.
– Jos
Jan 7 at 12:48
I knew one fellow who dutifully told the system to shutdown the right way, then (unwisely) immediately held the power button. You're not doing anything like that are you?
– user535733
Jan 7 at 13:08
Oh, no, nothing of the like. I just went withsudo shutdown nowand washed my hands of the all thing, letting it die, which usually happened immediately. Now, just in case, I use the dedicated "power button" in the tray, choosing "Shutdown" (without invoking it through shell). But apparently it is not necessary?
– Michal Tomaszuk
2 days ago
add a comment |
my first post here.
I am running 18.04.1 and I have recently gotten an error while booting - the screen remains black after POST and nothing happens. I went into recovery mode and found that my root partition doesn't get mounted due to orphaned inodes and the like - I cannot supply a log since I have rebooted twice since fixing that and I do not actually know how to access historical boot logs. I could fix it by running fsck.ext4 -p /dev/mapper/name-of-root-partition, and everything is fine and dandy again... However, I know this will probably happen again in the future, as I have had the exact same problem with Debian - it was in fact one of the reasons I switched to Ubuntu (the other being worse compatibility on Debian and some other small problems I didn't feel like fixing by hand, on Ubuntu it just werks).
Now fixing the problem is easy and rather pain-free, but I wonder what could be the reason, as it happens fairly frequently (I reckon twice a week) - I realized it might have something to do with me shutting the computer down with sudo shutdown now. Am I on the right track? I could not find any proper information about this approach being "dangerous" but at the same time everybody seems to be inputting various arguments before now, never running it "raw".
My hardware is pretty generic and I would assume rather unimportant, really. I have a single Kingston SSD and the weirdest thing in my setup is probably me forcing the kernel to load amdgpu instead of the default radeon drivers.
boot shutdown fsck inode
asked Jan 7 at 11:13
Michal TomaszukMichal Tomaszuk
111
New contributor
Michal Tomaszuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
my first post here.
I am running 18.04.1 and I have recently gotten an error while booting - the screen remains black after POST and nothing happens. I went into recovery mode and found that my root partition doesn't get mounted due to orphaned inodes and the like - I cannot supply a log since I have rebooted twice since fixing that and I do not actually know how to access historical boot logs. I could fix it by running fsck.ext4 -p /dev/mapper/name-of-root-partition, and everything is fine and dandy again... However, I know this will probably happen again in the future, as I have had the exact same problem with Debian - it was in fact one of the reasons I switched to Ubuntu (the other being worse compatibility on Debian and some other small problems I didn't feel like fixing by hand, on Ubuntu it just werks).
Now fixing the problem is easy and rather pain-free, but I wonder what could be the reason, as it happens fairly frequently (I reckon twice a week) - I realized it might have something to do with me shutting the computer down with sudo shutdown now. Am I on the right track? I could not find any proper information about this approach being "dangerous" but at the same time everybody seems to be inputting various arguments before now, never running it "raw".
My hardware is pretty generic and I would assume rather unimportant, really. I have a single Kingston SSD and the weirdest thing in my setup is probably me forcing the kernel to load amdgpu instead of the default radeon drivers.
boot shutdown fsck inode
boot shutdown fsck inode
asked Jan 7 at 11:13
Michal TomaszukMichal Tomaszuk
111
New contributor
Michal Tomaszuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 7 at 11:13
Michal TomaszukMichal Tomaszuk
111
New contributor
Michal Tomaszuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 7 at 11:13
Michal TomaszukMichal Tomaszuk
111
New contributor
Michal Tomaszuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Jan 7 at 11:13
Michal TomaszukMichal Tomaszuk
111
asked Jan 7 at 11:13
Michal TomaszukMichal Tomaszuk
111
111
New contributor
Michal Tomaszuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Michal Tomaszuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Michal Tomaszuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
sudo shutdown nowwould not leave you with orphaned inodes, let alone an unbootable system.
– Jos
Jan 7 at 12:48
I knew one fellow who dutifully told the system to shutdown the right way, then (unwisely) immediately held the power button. You're not doing anything like that are you?
– user535733
Jan 7 at 13:08
Oh, no, nothing of the like. I just went withsudo shutdown nowand washed my hands of the all thing, letting it die, which usually happened immediately. Now, just in case, I use the dedicated "power button" in the tray, choosing "Shutdown" (without invoking it through shell). But apparently it is not necessary?
– Michal Tomaszuk
2 days ago
add a comment |
sudo shutdown nowwould not leave you with orphaned inodes, let alone an unbootable system.
– Jos
Jan 7 at 12:48
I knew one fellow who dutifully told the system to shutdown the right way, then (unwisely) immediately held the power button. You're not doing anything like that are you?
– user535733
Jan 7 at 13:08
Oh, no, nothing of the like. I just went withsudo shutdown nowand washed my hands of the all thing, letting it die, which usually happened immediately. Now, just in case, I use the dedicated "power button" in the tray, choosing "Shutdown" (without invoking it through shell). But apparently it is not necessary?
– Michal Tomaszuk
2 days ago
sudo shutdown now would not leave you with orphaned inodes, let alone an unbootable system.– Jos
Jan 7 at 12:48
sudo shutdown now would not leave you with orphaned inodes, let alone an unbootable system.– Jos
Jan 7 at 12:48
I knew one fellow who dutifully told the system to shutdown the right way, then (unwisely) immediately held the power button. You're not doing anything like that are you?
– user535733
Jan 7 at 13:08
I knew one fellow who dutifully told the system to shutdown the right way, then (unwisely) immediately held the power button. You're not doing anything like that are you?
– user535733
Jan 7 at 13:08
Oh, no, nothing of the like. I just went with
sudo shutdown now and washed my hands of the all thing, letting it die, which usually happened immediately. Now, just in case, I use the dedicated "power button" in the tray, choosing "Shutdown" (without invoking it through shell). But apparently it is not necessary?– Michal Tomaszuk
2 days ago
Oh, no, nothing of the like. I just went with
sudo shutdown now and washed my hands of the all thing, letting it die, which usually happened immediately. Now, just in case, I use the dedicated "power button" in the tray, choosing "Shutdown" (without invoking it through shell). But apparently it is not necessary?– Michal Tomaszuk
2 days ago
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
});
}
});
Michal Tomaszuk is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1107695%2freason-for-orphaned-inodes-and-boot-failure-fixable-by-manual-fsck%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
Michal Tomaszuk is a new contributor. Be nice, and check out our Code of Conduct.
Michal Tomaszuk is a new contributor. Be nice, and check out our Code of Conduct.
Michal Tomaszuk is a new contributor. Be nice, and check out our Code of Conduct.
Michal Tomaszuk is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1107695%2freason-for-orphaned-inodes-and-boot-failure-fixable-by-manual-fsck%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
sudo shutdown nowwould not leave you with orphaned inodes, let alone an unbootable system.– Jos
Jan 7 at 12:48
I knew one fellow who dutifully told the system to shutdown the right way, then (unwisely) immediately held the power button. You're not doing anything like that are you?
– user535733
Jan 7 at 13:08
Oh, no, nothing of the like. I just went with
sudo shutdown nowand washed my hands of the all thing, letting it die, which usually happened immediately. Now, just in case, I use the dedicated "power button" in the tray, choosing "Shutdown" (without invoking it through shell). But apparently it is not necessary?– Michal Tomaszuk
2 days ago