Linux fails on boot in strange way
I have restarted my machine after trying to install Skype, i have reverted changes made to
etc/dbus-1/system.conf
but after starting my machine i receive almost instantly stream of 99 and sometimes 80 and that's all. Nothing is being logged to aby log as it fails even before loading kernel,literally in Second or two after pressing Power.
I don't know if my change to above file is relevant,maybe that's just coincidence, where I should start looking for some clue? I even don't know what to Google now, or is it software or hardware (ssd?) failure.
boot slackware
edited Dec 16 at 11:48
Rui F Ribeiro
38.9k1479129
asked Sep 4 '13 at 20:27
zrl3dx
13615
add a comment |
I have restarted my machine after trying to install Skype, i have reverted changes made to
etc/dbus-1/system.conf
but after starting my machine i receive almost instantly stream of 99 and sometimes 80 and that's all. Nothing is being logged to aby log as it fails even before loading kernel,literally in Second or two after pressing Power.
I don't know if my change to above file is relevant,maybe that's just coincidence, where I should start looking for some clue? I even don't know what to Google now, or is it software or hardware (ssd?) failure.
boot slackware
edited Dec 16 at 11:48
Rui F Ribeiro
38.9k1479129
asked Sep 4 '13 at 20:27
zrl3dx
13615
What do you mean by "I receive almost instantly stream of 99 and sometimes 80 and that's all. "? Are you talking about a progress indicator?
– Joel Taylor
Sep 4 '13 at 20:59
No,it's just corrupted output, I have probably broken somehow my bootsector, i'm trying to fix it now.
– zrl3dx
Sep 4 '13 at 21:25
add a comment |
I have restarted my machine after trying to install Skype, i have reverted changes made to
etc/dbus-1/system.conf
but after starting my machine i receive almost instantly stream of 99 and sometimes 80 and that's all. Nothing is being logged to aby log as it fails even before loading kernel,literally in Second or two after pressing Power.
I don't know if my change to above file is relevant,maybe that's just coincidence, where I should start looking for some clue? I even don't know what to Google now, or is it software or hardware (ssd?) failure.
boot slackware
edited Dec 16 at 11:48
Rui F Ribeiro
38.9k1479129
asked Sep 4 '13 at 20:27
zrl3dx
13615
I have restarted my machine after trying to install Skype, i have reverted changes made to
etc/dbus-1/system.conf
but after starting my machine i receive almost instantly stream of 99 and sometimes 80 and that's all. Nothing is being logged to aby log as it fails even before loading kernel,literally in Second or two after pressing Power.
I don't know if my change to above file is relevant,maybe that's just coincidence, where I should start looking for some clue? I even don't know what to Google now, or is it software or hardware (ssd?) failure.
boot slackware
boot slackware
edited Dec 16 at 11:48
Rui F Ribeiro
38.9k1479129
asked Sep 4 '13 at 20:27
zrl3dx
13615
edited Dec 16 at 11:48
Rui F Ribeiro
38.9k1479129
asked Sep 4 '13 at 20:27
zrl3dx
13615
edited Dec 16 at 11:48
Rui F Ribeiro
38.9k1479129
edited Dec 16 at 11:48
Rui F Ribeiro
38.9k1479129
edited Dec 16 at 11:48
Rui F Ribeiro
38.9k1479129
38.9k1479129
asked Sep 4 '13 at 20:27
zrl3dx
13615
asked Sep 4 '13 at 20:27
zrl3dx
13615
asked Sep 4 '13 at 20:27
zrl3dx
13615
13615
What do you mean by "I receive almost instantly stream of 99 and sometimes 80 and that's all. "? Are you talking about a progress indicator?
– Joel Taylor
Sep 4 '13 at 20:59
No,it's just corrupted output, I have probably broken somehow my bootsector, i'm trying to fix it now.
– zrl3dx
Sep 4 '13 at 21:25
add a comment |
What do you mean by "I receive almost instantly stream of 99 and sometimes 80 and that's all. "? Are you talking about a progress indicator?
– Joel Taylor
Sep 4 '13 at 20:59
No,it's just corrupted output, I have probably broken somehow my bootsector, i'm trying to fix it now.
– zrl3dx
Sep 4 '13 at 21:25
What do you mean by "I receive almost instantly stream of 99 and sometimes 80 and that's all. "? Are you talking about a progress indicator?
– Joel Taylor
Sep 4 '13 at 20:59
What do you mean by "I receive almost instantly stream of 99 and sometimes 80 and that's all. "? Are you talking about a progress indicator?
– Joel Taylor
Sep 4 '13 at 20:59
No,it's just corrupted output, I have probably broken somehow my bootsector, i'm trying to fix it now.
– zrl3dx
Sep 4 '13 at 21:25
No,it's just corrupted output, I have probably broken somehow my bootsector, i'm trying to fix it now.
– zrl3dx
Sep 4 '13 at 21:25
add a comment |
1 Answer
1
active
oldest
votes
Ok, I've resolved it. Fortunately, everything is fine, that was only issue with bootsector. Failure even before kernel load pointed me towards MBR, so I've started system with my pendrive kept for such occasions with portable win, linux and several tools, mounted my disks (first relief - filesystem was fine) simply chrooted (please see edit below) to my regular root and called
lilo -v
and my system is alive again. I'm very curious what could made such strange error, I've already modified file mentioned in my question and of course it doesn't change anything, system starts with my changes and without them. I haven't touched anything connected with bootsector, or even anything in system's internals, so that's very disturbing, I'd really prefer if it was my failure.
Was that some error on my SSD? Or some cosmic rays? Or maybe virus? I don't know, if anyone has any idea how to reproduce that error I'll happily try it.
Edit: As @peterph wrote, "it is a Good Idea (TM) to bind-mount /dev and /proc into the appropriate places in your root partition before chrooting into it" - thanks for noticing that.
answered Sep 4 '13 at 21:43
zrl3dx
13615
2
Might have been a spurious error (even a read error in BIOS) - I've seen such thing once or twice and I don't have any better explanation for it. For the posterity you might want to add to your answer that it is a Good Idea (TM) to bind-mount/devand/procinto the appropriate places in your root partition before chrooting into it.
– peterph
Sep 4 '13 at 22:15
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',
autoActivateHeartbeat: false,
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
});
}
});
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%2funix.stackexchange.com%2fquestions%2f89455%2flinux-fails-on-boot-in-strange-way%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
Ok, I've resolved it. Fortunately, everything is fine, that was only issue with bootsector. Failure even before kernel load pointed me towards MBR, so I've started system with my pendrive kept for such occasions with portable win, linux and several tools, mounted my disks (first relief - filesystem was fine) simply chrooted (please see edit below) to my regular root and called
lilo -v
and my system is alive again. I'm very curious what could made such strange error, I've already modified file mentioned in my question and of course it doesn't change anything, system starts with my changes and without them. I haven't touched anything connected with bootsector, or even anything in system's internals, so that's very disturbing, I'd really prefer if it was my failure.
Was that some error on my SSD? Or some cosmic rays? Or maybe virus? I don't know, if anyone has any idea how to reproduce that error I'll happily try it.
Edit: As @peterph wrote, "it is a Good Idea (TM) to bind-mount /dev and /proc into the appropriate places in your root partition before chrooting into it" - thanks for noticing that.
answered Sep 4 '13 at 21:43
zrl3dx
13615
2
Might have been a spurious error (even a read error in BIOS) - I've seen such thing once or twice and I don't have any better explanation for it. For the posterity you might want to add to your answer that it is a Good Idea (TM) to bind-mount/devand/procinto the appropriate places in your root partition before chrooting into it.
– peterph
Sep 4 '13 at 22:15
add a comment |
Ok, I've resolved it. Fortunately, everything is fine, that was only issue with bootsector. Failure even before kernel load pointed me towards MBR, so I've started system with my pendrive kept for such occasions with portable win, linux and several tools, mounted my disks (first relief - filesystem was fine) simply chrooted (please see edit below) to my regular root and called
lilo -v
and my system is alive again. I'm very curious what could made such strange error, I've already modified file mentioned in my question and of course it doesn't change anything, system starts with my changes and without them. I haven't touched anything connected with bootsector, or even anything in system's internals, so that's very disturbing, I'd really prefer if it was my failure.
Was that some error on my SSD? Or some cosmic rays? Or maybe virus? I don't know, if anyone has any idea how to reproduce that error I'll happily try it.
Edit: As @peterph wrote, "it is a Good Idea (TM) to bind-mount /dev and /proc into the appropriate places in your root partition before chrooting into it" - thanks for noticing that.
answered Sep 4 '13 at 21:43
zrl3dx
13615
2
Might have been a spurious error (even a read error in BIOS) - I've seen such thing once or twice and I don't have any better explanation for it. For the posterity you might want to add to your answer that it is a Good Idea (TM) to bind-mount/devand/procinto the appropriate places in your root partition before chrooting into it.
– peterph
Sep 4 '13 at 22:15
add a comment |
Ok, I've resolved it. Fortunately, everything is fine, that was only issue with bootsector. Failure even before kernel load pointed me towards MBR, so I've started system with my pendrive kept for such occasions with portable win, linux and several tools, mounted my disks (first relief - filesystem was fine) simply chrooted (please see edit below) to my regular root and called
lilo -v
and my system is alive again. I'm very curious what could made such strange error, I've already modified file mentioned in my question and of course it doesn't change anything, system starts with my changes and without them. I haven't touched anything connected with bootsector, or even anything in system's internals, so that's very disturbing, I'd really prefer if it was my failure.
Was that some error on my SSD? Or some cosmic rays? Or maybe virus? I don't know, if anyone has any idea how to reproduce that error I'll happily try it.
Edit: As @peterph wrote, "it is a Good Idea (TM) to bind-mount /dev and /proc into the appropriate places in your root partition before chrooting into it" - thanks for noticing that.
answered Sep 4 '13 at 21:43
zrl3dx
13615
Ok, I've resolved it. Fortunately, everything is fine, that was only issue with bootsector. Failure even before kernel load pointed me towards MBR, so I've started system with my pendrive kept for such occasions with portable win, linux and several tools, mounted my disks (first relief - filesystem was fine) simply chrooted (please see edit below) to my regular root and called
lilo -v
and my system is alive again. I'm very curious what could made such strange error, I've already modified file mentioned in my question and of course it doesn't change anything, system starts with my changes and without them. I haven't touched anything connected with bootsector, or even anything in system's internals, so that's very disturbing, I'd really prefer if it was my failure.
Was that some error on my SSD? Or some cosmic rays? Or maybe virus? I don't know, if anyone has any idea how to reproduce that error I'll happily try it.
Edit: As @peterph wrote, "it is a Good Idea (TM) to bind-mount /dev and /proc into the appropriate places in your root partition before chrooting into it" - thanks for noticing that.
answered Sep 4 '13 at 21:43
zrl3dx
13615
edited Sep 6 '13 at 8:12
answered Sep 4 '13 at 21:43
zrl3dx
13615
answered Sep 4 '13 at 21:43
zrl3dx
13615
answered Sep 4 '13 at 21:43
zrl3dx
13615
13615
2
Might have been a spurious error (even a read error in BIOS) - I've seen such thing once or twice and I don't have any better explanation for it. For the posterity you might want to add to your answer that it is a Good Idea (TM) to bind-mount/devand/procinto the appropriate places in your root partition before chrooting into it.
– peterph
Sep 4 '13 at 22:15
add a comment |
2
Might have been a spurious error (even a read error in BIOS) - I've seen such thing once or twice and I don't have any better explanation for it. For the posterity you might want to add to your answer that it is a Good Idea (TM) to bind-mount/devand/procinto the appropriate places in your root partition before chrooting into it.
– peterph
Sep 4 '13 at 22:15
2
2
Might have been a spurious error (even a read error in BIOS) - I've seen such thing once or twice and I don't have any better explanation for it. For the posterity you might want to add to your answer that it is a Good Idea (TM) to bind-mount
/dev and /proc into the appropriate places in your root partition before chrooting into it.– peterph
Sep 4 '13 at 22:15
Might have been a spurious error (even a read error in BIOS) - I've seen such thing once or twice and I don't have any better explanation for it. For the posterity you might want to add to your answer that it is a Good Idea (TM) to bind-mount
/dev and /proc into the appropriate places in your root partition before chrooting into it.– peterph
Sep 4 '13 at 22:15
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f89455%2flinux-fails-on-boot-in-strange-way%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
What do you mean by "I receive almost instantly stream of 99 and sometimes 80 and that's all. "? Are you talking about a progress indicator?
– Joel Taylor
Sep 4 '13 at 20:59
No,it's just corrupted output, I have probably broken somehow my bootsector, i'm trying to fix it now.
– zrl3dx
Sep 4 '13 at 21:25