Cannot loging because of ubuntu--vg-root: clean - Ubuntu 16.0.4 LTS
up vote
0
down vote
favorite
After a reboot I could not log back in via the GUI. I got the black screen with a flash of text saying:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/ubuntu--vg-root: clean, XXX/XXXfiles, XXX/XXX
and then reverts back to the login screen.
I did the 'uselvmetad = 0' fix and ran 'sudo update-initramfs -u -k all'
THis got rid of the lvmetad errors, but not the 'ubuntu--vg-root: clean' error. From what I can tell people have fixed it by running 'sudo apt-get install --reinstall ubuntu-desktop', but this did not work for me. I also tried 'sudo apt-get install --reinstall unity' with no luck.
Does anyone know of anything else that I could try?
16.04 login
edited Nov 22 at 16:33
George Udosen
18.5k94265
asked Nov 22 at 16:20
B.P.
1
New contributor
B.P. 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 |
up vote
0
down vote
favorite
After a reboot I could not log back in via the GUI. I got the black screen with a flash of text saying:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/ubuntu--vg-root: clean, XXX/XXXfiles, XXX/XXX
and then reverts back to the login screen.
I did the 'uselvmetad = 0' fix and ran 'sudo update-initramfs -u -k all'
THis got rid of the lvmetad errors, but not the 'ubuntu--vg-root: clean' error. From what I can tell people have fixed it by running 'sudo apt-get install --reinstall ubuntu-desktop', but this did not work for me. I also tried 'sudo apt-get install --reinstall unity' with no luck.
Does anyone know of anything else that I could try?
16.04 login
edited Nov 22 at 16:33
George Udosen
18.5k94265
asked Nov 22 at 16:20
B.P.
1
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
That's not an error and where did you see the suggestion to reinstall?
– George Udosen
Nov 22 at 16:34
These showed up when I had an issue where I couldn't login because my login screen kept restarting. I saw some posts where others had both problems as well and some fixed it by reinstalling the desktop. Anyways, I found that the actual problem was that the ownership had been changed to ~/.XAuthority
– B.P.
2 days ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
After a reboot I could not log back in via the GUI. I got the black screen with a flash of text saying:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/ubuntu--vg-root: clean, XXX/XXXfiles, XXX/XXX
and then reverts back to the login screen.
I did the 'uselvmetad = 0' fix and ran 'sudo update-initramfs -u -k all'
THis got rid of the lvmetad errors, but not the 'ubuntu--vg-root: clean' error. From what I can tell people have fixed it by running 'sudo apt-get install --reinstall ubuntu-desktop', but this did not work for me. I also tried 'sudo apt-get install --reinstall unity' with no luck.
Does anyone know of anything else that I could try?
16.04 login
edited Nov 22 at 16:33
George Udosen
18.5k94265
asked Nov 22 at 16:20
B.P.
1
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
After a reboot I could not log back in via the GUI. I got the black screen with a flash of text saying:
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/ubuntu--vg-root: clean, XXX/XXXfiles, XXX/XXX
and then reverts back to the login screen.
I did the 'uselvmetad = 0' fix and ran 'sudo update-initramfs -u -k all'
THis got rid of the lvmetad errors, but not the 'ubuntu--vg-root: clean' error. From what I can tell people have fixed it by running 'sudo apt-get install --reinstall ubuntu-desktop', but this did not work for me. I also tried 'sudo apt-get install --reinstall unity' with no luck.
Does anyone know of anything else that I could try?
16.04 login
16.04 login
edited Nov 22 at 16:33
George Udosen
18.5k94265
asked Nov 22 at 16:20
B.P.
1
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 22 at 16:33
George Udosen
18.5k94265
asked Nov 22 at 16:20
B.P.
1
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 22 at 16:33
George Udosen
18.5k94265
edited Nov 22 at 16:33
George Udosen
18.5k94265
edited Nov 22 at 16:33
George Udosen
18.5k94265
18.5k94265
asked Nov 22 at 16:20
B.P.
1
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 22 at 16:20
B.P.
1
asked Nov 22 at 16:20
B.P.
1
1
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
That's not an error and where did you see the suggestion to reinstall?
– George Udosen
Nov 22 at 16:34
These showed up when I had an issue where I couldn't login because my login screen kept restarting. I saw some posts where others had both problems as well and some fixed it by reinstalling the desktop. Anyways, I found that the actual problem was that the ownership had been changed to ~/.XAuthority
– B.P.
2 days ago
add a comment |
That's not an error and where did you see the suggestion to reinstall?
– George Udosen
Nov 22 at 16:34
These showed up when I had an issue where I couldn't login because my login screen kept restarting. I saw some posts where others had both problems as well and some fixed it by reinstalling the desktop. Anyways, I found that the actual problem was that the ownership had been changed to ~/.XAuthority
– B.P.
2 days ago
That's not an error and where did you see the suggestion to reinstall?
– George Udosen
Nov 22 at 16:34
That's not an error and where did you see the suggestion to reinstall?
– George Udosen
Nov 22 at 16:34
These showed up when I had an issue where I couldn't login because my login screen kept restarting. I saw some posts where others had both problems as well and some fixed it by reinstalling the desktop. Anyways, I found that the actual problem was that the ownership had been changed to ~/.XAuthority
– B.P.
2 days ago
These showed up when I had an issue where I couldn't login because my login screen kept restarting. I saw some posts where others had both problems as well and some fixed it by reinstalling the desktop. Anyways, I found that the actual problem was that the ownership had been changed to ~/.XAuthority
– B.P.
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I found that the actual problem was that the ownership had been changed to ~/.XAuthority and I had to chown it back to my user.
answered 2 days ago
B.P.
1
New contributor
B.P. 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 |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I found that the actual problem was that the ownership had been changed to ~/.XAuthority and I had to chown it back to my user.
answered 2 days ago
B.P.
1
New contributor
B.P. 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 |
up vote
0
down vote
I found that the actual problem was that the ownership had been changed to ~/.XAuthority and I had to chown it back to my user.
answered 2 days ago
B.P.
1
New contributor
B.P. 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 |
up vote
0
down vote
up vote
0
down vote
I found that the actual problem was that the ownership had been changed to ~/.XAuthority and I had to chown it back to my user.
answered 2 days ago
B.P.
1
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I found that the actual problem was that the ownership had been changed to ~/.XAuthority and I had to chown it back to my user.
answered 2 days ago
B.P.
1
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
B.P.
1
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
B.P.
1
answered 2 days ago
B.P.
1
1
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
B.P. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
B.P. 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 |
add a comment |
B.P. is a new contributor. Be nice, and check out our Code of Conduct.
B.P. is a new contributor. Be nice, and check out our Code of Conduct.
B.P. is a new contributor. Be nice, and check out our Code of Conduct.
B.P. 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%2f1095150%2fcannot-loging-because-of-ubuntu-vg-root-clean-ubuntu-16-0-4-lts%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
That's not an error and where did you see the suggestion to reinstall?
– George Udosen
Nov 22 at 16:34
These showed up when I had an issue where I couldn't login because my login screen kept restarting. I saw some posts where others had both problems as well and some fixed it by reinstalling the desktop. Anyways, I found that the actual problem was that the ownership had been changed to ~/.XAuthority
– B.P.
2 days ago