No login screen, unable to login on tty2 to tty6 with “Login Incorrect” error
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm getting this problem after my computer froze while updating. I use Fedora 28 KDE. I was shown in task bar that there 171 updates, so I clicked it, as it was updating the computer froze, so I pressed the reset button, since then I'm getting this problem.
I don't see any login screen, but I see a cursor over black screen, I can move this cursor. Hoping to login through command line, when I pressed CTRL+ALT+F2-F6
, the text login, shows "Login Incorrect"
when I type in my username and press "ENTER"
to proceed to typing password. This problem exists across all Fedora entries on GRUB2 menu.
When I removed "rhgb"
from one of the GRUB2 Fedora entries and started it, I was shown a real time log of the boot up process, in it I saw these, which I think might be the cause of this problem:
"ostree-system-generator failed with exit status 127"
and this error below it:
"Failed to start Security Auditing Service"
nologin
|
show 1 more comment
I'm getting this problem after my computer froze while updating. I use Fedora 28 KDE. I was shown in task bar that there 171 updates, so I clicked it, as it was updating the computer froze, so I pressed the reset button, since then I'm getting this problem.
I don't see any login screen, but I see a cursor over black screen, I can move this cursor. Hoping to login through command line, when I pressed CTRL+ALT+F2-F6
, the text login, shows "Login Incorrect"
when I type in my username and press "ENTER"
to proceed to typing password. This problem exists across all Fedora entries on GRUB2 menu.
When I removed "rhgb"
from one of the GRUB2 Fedora entries and started it, I was shown a real time log of the boot up process, in it I saw these, which I think might be the cause of this problem:
"ostree-system-generator failed with exit status 127"
and this error below it:
"Failed to start Security Auditing Service"
nologin
2
Seems like you got corrupted credential files, most probably /etc/passwd. Hopefully you may have a system backup that may help you to recover. This will require some investigation on what files got corrupted. I suggest you to boot in single user mode (addsingle
to the end of your default fedora entry kernel command line). Once booted you will get a root prompt where you can remount your system as readonly (mount -o remount,ro /
); then you can run fsck as the first step. This is not an answer, just some thoughts on how to start your system recovery.
– Marcelo
Jul 21 '18 at 17:47
1
Alternatively, if this is easy for you to remove your harddisk, you can use a USB/SATA adapter to use another system to run the fsck tool. Good luck
– Marcelo
Jul 21 '18 at 17:48
1
Thanks a lot Marcelo. You have no idea how appreciative I am for your helpful comments because I've been asking this question at two places officially related to Fedora, but till now I didn't get a reply there. Unfortunately I don't have any backup but I'll try that single user mode and see. BTW sorry I forgot to mention this, mine is an encrypted LVM, I tried mounting and running fsck through Kali which I have on the same hard disk, but because of encryption I had a lot of trouble accessing it, when I managed to get it running(which I'm not even sure I did correctly), the results were clean.
– noviceFedora
Jul 21 '18 at 17:58
Instead of Kali (which is used for penetration testing), I recommend SystemRescuceCD on a USB stick to repair stuff.
– dirkt
Jul 22 '18 at 8:19
I haven't yet tried the SystemRescueCD but in case it fsck shows clean, what can I do to repair the problem? Is there way I can remove the corrupted credential files and create ones?
– noviceFedora
Jul 22 '18 at 21:29
|
show 1 more comment
I'm getting this problem after my computer froze while updating. I use Fedora 28 KDE. I was shown in task bar that there 171 updates, so I clicked it, as it was updating the computer froze, so I pressed the reset button, since then I'm getting this problem.
I don't see any login screen, but I see a cursor over black screen, I can move this cursor. Hoping to login through command line, when I pressed CTRL+ALT+F2-F6
, the text login, shows "Login Incorrect"
when I type in my username and press "ENTER"
to proceed to typing password. This problem exists across all Fedora entries on GRUB2 menu.
When I removed "rhgb"
from one of the GRUB2 Fedora entries and started it, I was shown a real time log of the boot up process, in it I saw these, which I think might be the cause of this problem:
"ostree-system-generator failed with exit status 127"
and this error below it:
"Failed to start Security Auditing Service"
nologin
I'm getting this problem after my computer froze while updating. I use Fedora 28 KDE. I was shown in task bar that there 171 updates, so I clicked it, as it was updating the computer froze, so I pressed the reset button, since then I'm getting this problem.
I don't see any login screen, but I see a cursor over black screen, I can move this cursor. Hoping to login through command line, when I pressed CTRL+ALT+F2-F6
, the text login, shows "Login Incorrect"
when I type in my username and press "ENTER"
to proceed to typing password. This problem exists across all Fedora entries on GRUB2 menu.
When I removed "rhgb"
from one of the GRUB2 Fedora entries and started it, I was shown a real time log of the boot up process, in it I saw these, which I think might be the cause of this problem:
"ostree-system-generator failed with exit status 127"
and this error below it:
"Failed to start Security Auditing Service"
nologin
nologin
edited 6 hours ago
Rui F Ribeiro
41.9k1483142
41.9k1483142
asked Jul 21 '18 at 17:35
noviceFedoranoviceFedora
12
12
2
Seems like you got corrupted credential files, most probably /etc/passwd. Hopefully you may have a system backup that may help you to recover. This will require some investigation on what files got corrupted. I suggest you to boot in single user mode (addsingle
to the end of your default fedora entry kernel command line). Once booted you will get a root prompt where you can remount your system as readonly (mount -o remount,ro /
); then you can run fsck as the first step. This is not an answer, just some thoughts on how to start your system recovery.
– Marcelo
Jul 21 '18 at 17:47
1
Alternatively, if this is easy for you to remove your harddisk, you can use a USB/SATA adapter to use another system to run the fsck tool. Good luck
– Marcelo
Jul 21 '18 at 17:48
1
Thanks a lot Marcelo. You have no idea how appreciative I am for your helpful comments because I've been asking this question at two places officially related to Fedora, but till now I didn't get a reply there. Unfortunately I don't have any backup but I'll try that single user mode and see. BTW sorry I forgot to mention this, mine is an encrypted LVM, I tried mounting and running fsck through Kali which I have on the same hard disk, but because of encryption I had a lot of trouble accessing it, when I managed to get it running(which I'm not even sure I did correctly), the results were clean.
– noviceFedora
Jul 21 '18 at 17:58
Instead of Kali (which is used for penetration testing), I recommend SystemRescuceCD on a USB stick to repair stuff.
– dirkt
Jul 22 '18 at 8:19
I haven't yet tried the SystemRescueCD but in case it fsck shows clean, what can I do to repair the problem? Is there way I can remove the corrupted credential files and create ones?
– noviceFedora
Jul 22 '18 at 21:29
|
show 1 more comment
2
Seems like you got corrupted credential files, most probably /etc/passwd. Hopefully you may have a system backup that may help you to recover. This will require some investigation on what files got corrupted. I suggest you to boot in single user mode (addsingle
to the end of your default fedora entry kernel command line). Once booted you will get a root prompt where you can remount your system as readonly (mount -o remount,ro /
); then you can run fsck as the first step. This is not an answer, just some thoughts on how to start your system recovery.
– Marcelo
Jul 21 '18 at 17:47
1
Alternatively, if this is easy for you to remove your harddisk, you can use a USB/SATA adapter to use another system to run the fsck tool. Good luck
– Marcelo
Jul 21 '18 at 17:48
1
Thanks a lot Marcelo. You have no idea how appreciative I am for your helpful comments because I've been asking this question at two places officially related to Fedora, but till now I didn't get a reply there. Unfortunately I don't have any backup but I'll try that single user mode and see. BTW sorry I forgot to mention this, mine is an encrypted LVM, I tried mounting and running fsck through Kali which I have on the same hard disk, but because of encryption I had a lot of trouble accessing it, when I managed to get it running(which I'm not even sure I did correctly), the results were clean.
– noviceFedora
Jul 21 '18 at 17:58
Instead of Kali (which is used for penetration testing), I recommend SystemRescuceCD on a USB stick to repair stuff.
– dirkt
Jul 22 '18 at 8:19
I haven't yet tried the SystemRescueCD but in case it fsck shows clean, what can I do to repair the problem? Is there way I can remove the corrupted credential files and create ones?
– noviceFedora
Jul 22 '18 at 21:29
2
2
Seems like you got corrupted credential files, most probably /etc/passwd. Hopefully you may have a system backup that may help you to recover. This will require some investigation on what files got corrupted. I suggest you to boot in single user mode (add
single
to the end of your default fedora entry kernel command line). Once booted you will get a root prompt where you can remount your system as readonly ( mount -o remount,ro /
); then you can run fsck as the first step. This is not an answer, just some thoughts on how to start your system recovery.– Marcelo
Jul 21 '18 at 17:47
Seems like you got corrupted credential files, most probably /etc/passwd. Hopefully you may have a system backup that may help you to recover. This will require some investigation on what files got corrupted. I suggest you to boot in single user mode (add
single
to the end of your default fedora entry kernel command line). Once booted you will get a root prompt where you can remount your system as readonly ( mount -o remount,ro /
); then you can run fsck as the first step. This is not an answer, just some thoughts on how to start your system recovery.– Marcelo
Jul 21 '18 at 17:47
1
1
Alternatively, if this is easy for you to remove your harddisk, you can use a USB/SATA adapter to use another system to run the fsck tool. Good luck
– Marcelo
Jul 21 '18 at 17:48
Alternatively, if this is easy for you to remove your harddisk, you can use a USB/SATA adapter to use another system to run the fsck tool. Good luck
– Marcelo
Jul 21 '18 at 17:48
1
1
Thanks a lot Marcelo. You have no idea how appreciative I am for your helpful comments because I've been asking this question at two places officially related to Fedora, but till now I didn't get a reply there. Unfortunately I don't have any backup but I'll try that single user mode and see. BTW sorry I forgot to mention this, mine is an encrypted LVM, I tried mounting and running fsck through Kali which I have on the same hard disk, but because of encryption I had a lot of trouble accessing it, when I managed to get it running(which I'm not even sure I did correctly), the results were clean.
– noviceFedora
Jul 21 '18 at 17:58
Thanks a lot Marcelo. You have no idea how appreciative I am for your helpful comments because I've been asking this question at two places officially related to Fedora, but till now I didn't get a reply there. Unfortunately I don't have any backup but I'll try that single user mode and see. BTW sorry I forgot to mention this, mine is an encrypted LVM, I tried mounting and running fsck through Kali which I have on the same hard disk, but because of encryption I had a lot of trouble accessing it, when I managed to get it running(which I'm not even sure I did correctly), the results were clean.
– noviceFedora
Jul 21 '18 at 17:58
Instead of Kali (which is used for penetration testing), I recommend SystemRescuceCD on a USB stick to repair stuff.
– dirkt
Jul 22 '18 at 8:19
Instead of Kali (which is used for penetration testing), I recommend SystemRescuceCD on a USB stick to repair stuff.
– dirkt
Jul 22 '18 at 8:19
I haven't yet tried the SystemRescueCD but in case it fsck shows clean, what can I do to repair the problem? Is there way I can remove the corrupted credential files and create ones?
– noviceFedora
Jul 22 '18 at 21:29
I haven't yet tried the SystemRescueCD but in case it fsck shows clean, what can I do to repair the problem? Is there way I can remove the corrupted credential files and create ones?
– noviceFedora
Jul 22 '18 at 21:29
|
show 1 more comment
0
active
oldest
votes
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%2f457678%2fno-login-screen-unable-to-login-on-tty2-to-tty6-with-login-incorrect-error%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
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.
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%2f457678%2fno-login-screen-unable-to-login-on-tty2-to-tty6-with-login-incorrect-error%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
2
Seems like you got corrupted credential files, most probably /etc/passwd. Hopefully you may have a system backup that may help you to recover. This will require some investigation on what files got corrupted. I suggest you to boot in single user mode (add
single
to the end of your default fedora entry kernel command line). Once booted you will get a root prompt where you can remount your system as readonly (mount -o remount,ro /
); then you can run fsck as the first step. This is not an answer, just some thoughts on how to start your system recovery.– Marcelo
Jul 21 '18 at 17:47
1
Alternatively, if this is easy for you to remove your harddisk, you can use a USB/SATA adapter to use another system to run the fsck tool. Good luck
– Marcelo
Jul 21 '18 at 17:48
1
Thanks a lot Marcelo. You have no idea how appreciative I am for your helpful comments because I've been asking this question at two places officially related to Fedora, but till now I didn't get a reply there. Unfortunately I don't have any backup but I'll try that single user mode and see. BTW sorry I forgot to mention this, mine is an encrypted LVM, I tried mounting and running fsck through Kali which I have on the same hard disk, but because of encryption I had a lot of trouble accessing it, when I managed to get it running(which I'm not even sure I did correctly), the results were clean.
– noviceFedora
Jul 21 '18 at 17:58
Instead of Kali (which is used for penetration testing), I recommend SystemRescuceCD on a USB stick to repair stuff.
– dirkt
Jul 22 '18 at 8:19
I haven't yet tried the SystemRescueCD but in case it fsck shows clean, what can I do to repair the problem? Is there way I can remove the corrupted credential files and create ones?
– noviceFedora
Jul 22 '18 at 21:29