ubuntu does not boot after installing anaconda and pyinstaller
up vote
0
down vote
favorite
- What happened. After restarting, the system does not boot. It freezes at the Ubuntu logo and the dots.
- What I did just before that. I installed anaconda and then I installed Pyinstaller. When running pyinstaller it did not work because it could not find some libraries. But the libraries were there so I created a conf file with the path to the libraries in the anaconda/lib folder and I did sudo ldconfig to update the cache. the system said this path was not a symbolik link but apparently everything worked well because pyinstaller worked well after that. During the anaconda and pyinstaller installation I received a message that there were many packages not needed in the system and that I could get rid of them by an autoremove. Which I did. There were a lot of files but I did not worry much because the whole anaconda installation installed a lot of things (python and stuff) at its own paths so I thought all those files were redundant.
- What I did after not booting. First boot repair. After that getting into recovery mode and once that, nothing worked. dpkg gets frozen, doing nothing. same with failsafeX. Now with fsck something interesting happens. This is what I get:
fsck:/home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by /libx86_64-linux-gnu/libblkid.so.1)
fsck from util-linux 2.27.1
fsck.ext4: /home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by fsck.ext4)
fsck.ext4: /home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by /libx86_64-linux-gnu/libblkid.so.1)
/dev/sda2 is mounted
e2fsck: cannot continue, aborting.
And that's it. Any help would be very valuable.
Thanks in advance
Javier
boot libraries recovery-mode anaconda
asked Nov 19 at 23:53
Javier
164
add a comment |
up vote
0
down vote
favorite
- What happened. After restarting, the system does not boot. It freezes at the Ubuntu logo and the dots.
- What I did just before that. I installed anaconda and then I installed Pyinstaller. When running pyinstaller it did not work because it could not find some libraries. But the libraries were there so I created a conf file with the path to the libraries in the anaconda/lib folder and I did sudo ldconfig to update the cache. the system said this path was not a symbolik link but apparently everything worked well because pyinstaller worked well after that. During the anaconda and pyinstaller installation I received a message that there were many packages not needed in the system and that I could get rid of them by an autoremove. Which I did. There were a lot of files but I did not worry much because the whole anaconda installation installed a lot of things (python and stuff) at its own paths so I thought all those files were redundant.
- What I did after not booting. First boot repair. After that getting into recovery mode and once that, nothing worked. dpkg gets frozen, doing nothing. same with failsafeX. Now with fsck something interesting happens. This is what I get:
fsck:/home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by /libx86_64-linux-gnu/libblkid.so.1)
fsck from util-linux 2.27.1
fsck.ext4: /home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by fsck.ext4)
fsck.ext4: /home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by /libx86_64-linux-gnu/libblkid.so.1)
/dev/sda2 is mounted
e2fsck: cannot continue, aborting.
And that's it. Any help would be very valuable.
Thanks in advance
Javier
boot libraries recovery-mode anaconda
asked Nov 19 at 23:53
Javier
164
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
- What happened. After restarting, the system does not boot. It freezes at the Ubuntu logo and the dots.
- What I did just before that. I installed anaconda and then I installed Pyinstaller. When running pyinstaller it did not work because it could not find some libraries. But the libraries were there so I created a conf file with the path to the libraries in the anaconda/lib folder and I did sudo ldconfig to update the cache. the system said this path was not a symbolik link but apparently everything worked well because pyinstaller worked well after that. During the anaconda and pyinstaller installation I received a message that there were many packages not needed in the system and that I could get rid of them by an autoremove. Which I did. There were a lot of files but I did not worry much because the whole anaconda installation installed a lot of things (python and stuff) at its own paths so I thought all those files were redundant.
- What I did after not booting. First boot repair. After that getting into recovery mode and once that, nothing worked. dpkg gets frozen, doing nothing. same with failsafeX. Now with fsck something interesting happens. This is what I get:
fsck:/home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by /libx86_64-linux-gnu/libblkid.so.1)
fsck from util-linux 2.27.1
fsck.ext4: /home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by fsck.ext4)
fsck.ext4: /home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by /libx86_64-linux-gnu/libblkid.so.1)
/dev/sda2 is mounted
e2fsck: cannot continue, aborting.
And that's it. Any help would be very valuable.
Thanks in advance
Javier
boot libraries recovery-mode anaconda
asked Nov 19 at 23:53
Javier
164
- What happened. After restarting, the system does not boot. It freezes at the Ubuntu logo and the dots.
- What I did just before that. I installed anaconda and then I installed Pyinstaller. When running pyinstaller it did not work because it could not find some libraries. But the libraries were there so I created a conf file with the path to the libraries in the anaconda/lib folder and I did sudo ldconfig to update the cache. the system said this path was not a symbolik link but apparently everything worked well because pyinstaller worked well after that. During the anaconda and pyinstaller installation I received a message that there were many packages not needed in the system and that I could get rid of them by an autoremove. Which I did. There were a lot of files but I did not worry much because the whole anaconda installation installed a lot of things (python and stuff) at its own paths so I thought all those files were redundant.
- What I did after not booting. First boot repair. After that getting into recovery mode and once that, nothing worked. dpkg gets frozen, doing nothing. same with failsafeX. Now with fsck something interesting happens. This is what I get:
fsck:/home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by /libx86_64-linux-gnu/libblkid.so.1)
fsck from util-linux 2.27.1
fsck.ext4: /home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by fsck.ext4)
fsck.ext4: /home/javier/opt/anaconda/lib/libuuid.so.1: no version information available (required by /libx86_64-linux-gnu/libblkid.so.1)
/dev/sda2 is mounted
e2fsck: cannot continue, aborting.
And that's it. Any help would be very valuable.
Thanks in advance
Javier
boot libraries recovery-mode anaconda
boot libraries recovery-mode anaconda
asked Nov 19 at 23:53
Javier
164
asked Nov 19 at 23:53
Javier
164
asked Nov 19 at 23:53
Javier
164
asked Nov 19 at 23:53
Javier
164
asked Nov 19 at 23:53
Javier
164
164
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
SOLVED:
I went on the "drop to root shell" and I managed to delete the .conf file I created and updated the config cache. After that I could do a fsck. No errors. After that I could enter the dpkg option in the recovery menu. dpkg upgraded the system adn allowed me to log into the system again.
answered 2 days ago
Javier
164
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
SOLVED:
I went on the "drop to root shell" and I managed to delete the .conf file I created and updated the config cache. After that I could do a fsck. No errors. After that I could enter the dpkg option in the recovery menu. dpkg upgraded the system adn allowed me to log into the system again.
answered 2 days ago
Javier
164
add a comment |
up vote
0
down vote
SOLVED:
I went on the "drop to root shell" and I managed to delete the .conf file I created and updated the config cache. After that I could do a fsck. No errors. After that I could enter the dpkg option in the recovery menu. dpkg upgraded the system adn allowed me to log into the system again.
answered 2 days ago
Javier
164
add a comment |
up vote
0
down vote
up vote
0
down vote
SOLVED:
I went on the "drop to root shell" and I managed to delete the .conf file I created and updated the config cache. After that I could do a fsck. No errors. After that I could enter the dpkg option in the recovery menu. dpkg upgraded the system adn allowed me to log into the system again.
answered 2 days ago
Javier
164
SOLVED:
I went on the "drop to root shell" and I managed to delete the .conf file I created and updated the config cache. After that I could do a fsck. No errors. After that I could enter the dpkg option in the recovery menu. dpkg upgraded the system adn allowed me to log into the system again.
answered 2 days ago
Javier
164
answered 2 days ago
Javier
164
answered 2 days ago
Javier
164
answered 2 days ago
Javier
164
164
add a comment |
add a comment |
draft saved
draft discarded
draft saved
draft discarded
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%2f1094377%2fubuntu-does-not-boot-after-installing-anaconda-and-pyinstaller%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
