Ubuntu upgrade to 18.04 LTS from 17.10 failed

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite












I upgraded to 18.04 LTS from 17.10 and after the completion of the upgrade it said upgrade failed you system will be unstable, recovery will run now. The system could not launch when I restarted the system first time and second time it started. However I see some software are not working and I submitting bug reports. Can I downgrade to 17.10 now? What if my system becomes unstable? should I then run in recover mode (Kernel 4.13)?







share|improve this question




















  • Have you tried uninstalling Ubuntu and re-instaling it?
    – YoureSOStubborn
    Apr 27 at 19:47






  • 1




    Well I did not. Ubuntu is running in my laptop and uninstalling and installing means a lot (I need to reconfigure many a thing).
    – Sabyasachi Mitra
    Apr 27 at 19:59














up vote
1
down vote

favorite












I upgraded to 18.04 LTS from 17.10 and after the completion of the upgrade it said upgrade failed you system will be unstable, recovery will run now. The system could not launch when I restarted the system first time and second time it started. However I see some software are not working and I submitting bug reports. Can I downgrade to 17.10 now? What if my system becomes unstable? should I then run in recover mode (Kernel 4.13)?







share|improve this question




















  • Have you tried uninstalling Ubuntu and re-instaling it?
    – YoureSOStubborn
    Apr 27 at 19:47






  • 1




    Well I did not. Ubuntu is running in my laptop and uninstalling and installing means a lot (I need to reconfigure many a thing).
    – Sabyasachi Mitra
    Apr 27 at 19:59












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I upgraded to 18.04 LTS from 17.10 and after the completion of the upgrade it said upgrade failed you system will be unstable, recovery will run now. The system could not launch when I restarted the system first time and second time it started. However I see some software are not working and I submitting bug reports. Can I downgrade to 17.10 now? What if my system becomes unstable? should I then run in recover mode (Kernel 4.13)?







share|improve this question












I upgraded to 18.04 LTS from 17.10 and after the completion of the upgrade it said upgrade failed you system will be unstable, recovery will run now. The system could not launch when I restarted the system first time and second time it started. However I see some software are not working and I submitting bug reports. Can I downgrade to 17.10 now? What if my system becomes unstable? should I then run in recover mode (Kernel 4.13)?









share|improve this question











share|improve this question




share|improve this question










asked Apr 27 at 19:41









Sabyasachi Mitra

164




164











  • Have you tried uninstalling Ubuntu and re-instaling it?
    – YoureSOStubborn
    Apr 27 at 19:47






  • 1




    Well I did not. Ubuntu is running in my laptop and uninstalling and installing means a lot (I need to reconfigure many a thing).
    – Sabyasachi Mitra
    Apr 27 at 19:59
















  • Have you tried uninstalling Ubuntu and re-instaling it?
    – YoureSOStubborn
    Apr 27 at 19:47






  • 1




    Well I did not. Ubuntu is running in my laptop and uninstalling and installing means a lot (I need to reconfigure many a thing).
    – Sabyasachi Mitra
    Apr 27 at 19:59















Have you tried uninstalling Ubuntu and re-instaling it?
– YoureSOStubborn
Apr 27 at 19:47




Have you tried uninstalling Ubuntu and re-instaling it?
– YoureSOStubborn
Apr 27 at 19:47




1




1




Well I did not. Ubuntu is running in my laptop and uninstalling and installing means a lot (I need to reconfigure many a thing).
– Sabyasachi Mitra
Apr 27 at 19:59




Well I did not. Ubuntu is running in my laptop and uninstalling and installing means a lot (I need to reconfigure many a thing).
– Sabyasachi Mitra
Apr 27 at 19:59










1 Answer
1






active

oldest

votes

















up vote
1
down vote













I experienced the same problem when upgrading to 16.04 on one of my computers. I initially had booting problems, but it finally booted. I got the same unstable error messages you describe. I run a series of these commands:



$ sudo apt update
$ sudo apt upgrade
$ sudo apt dist-upgrade


I paid attention to the screen output of commands and ran the suggested command for that error.



Initially cat /etc/lsb-release showed the previous version.



It became stable by running the above commands 3 times. cat /etc/lsb-release showed the intended 16.04. That was two years ago. It's still running perfectly without any problems.



I believe trying to downgrade would be more problematic than fixing the upgrade issues.



All the commands was running from the console without GUI until the errors were addressed.



If the above commands (because of the /etc/apt/sources.list repository configuration) bring stability to 17.10, you should be able to complete your release upgrade to 18.04.






share|improve this answer






















  • +1 weird cat has to be run 3 times in a row!
    – WinEunuuchs2Unix
    Apr 27 at 19:58










  • There's some type of typo. I'll fix it.
    – L. D. James
    Apr 27 at 20:01










  • Ii was reading from cell phone in bright sunlight!
    – WinEunuuchs2Unix
    Apr 27 at 20:03






  • 1




    @WinEunuuchs2Unix The 3 times part, I often do. Sometimes an upgrade brings in new repository servers of which and update refreshes the caches, then the upgrade updates the apps and libraries from the new cache updates. /usr/lib/update-notifier/apt-check sometimes shows more applications after running the three commands the first time. This is especially the case when the system is broken.
    – L. D. James
    Apr 27 at 20:08











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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1028938%2fubuntu-upgrade-to-18-04-lts-from-17-10-failed%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote













I experienced the same problem when upgrading to 16.04 on one of my computers. I initially had booting problems, but it finally booted. I got the same unstable error messages you describe. I run a series of these commands:



$ sudo apt update
$ sudo apt upgrade
$ sudo apt dist-upgrade


I paid attention to the screen output of commands and ran the suggested command for that error.



Initially cat /etc/lsb-release showed the previous version.



It became stable by running the above commands 3 times. cat /etc/lsb-release showed the intended 16.04. That was two years ago. It's still running perfectly without any problems.



I believe trying to downgrade would be more problematic than fixing the upgrade issues.



All the commands was running from the console without GUI until the errors were addressed.



If the above commands (because of the /etc/apt/sources.list repository configuration) bring stability to 17.10, you should be able to complete your release upgrade to 18.04.






share|improve this answer






















  • +1 weird cat has to be run 3 times in a row!
    – WinEunuuchs2Unix
    Apr 27 at 19:58










  • There's some type of typo. I'll fix it.
    – L. D. James
    Apr 27 at 20:01










  • Ii was reading from cell phone in bright sunlight!
    – WinEunuuchs2Unix
    Apr 27 at 20:03






  • 1




    @WinEunuuchs2Unix The 3 times part, I often do. Sometimes an upgrade brings in new repository servers of which and update refreshes the caches, then the upgrade updates the apps and libraries from the new cache updates. /usr/lib/update-notifier/apt-check sometimes shows more applications after running the three commands the first time. This is especially the case when the system is broken.
    – L. D. James
    Apr 27 at 20:08















up vote
1
down vote













I experienced the same problem when upgrading to 16.04 on one of my computers. I initially had booting problems, but it finally booted. I got the same unstable error messages you describe. I run a series of these commands:



$ sudo apt update
$ sudo apt upgrade
$ sudo apt dist-upgrade


I paid attention to the screen output of commands and ran the suggested command for that error.



Initially cat /etc/lsb-release showed the previous version.



It became stable by running the above commands 3 times. cat /etc/lsb-release showed the intended 16.04. That was two years ago. It's still running perfectly without any problems.



I believe trying to downgrade would be more problematic than fixing the upgrade issues.



All the commands was running from the console without GUI until the errors were addressed.



If the above commands (because of the /etc/apt/sources.list repository configuration) bring stability to 17.10, you should be able to complete your release upgrade to 18.04.






share|improve this answer






















  • +1 weird cat has to be run 3 times in a row!
    – WinEunuuchs2Unix
    Apr 27 at 19:58










  • There's some type of typo. I'll fix it.
    – L. D. James
    Apr 27 at 20:01










  • Ii was reading from cell phone in bright sunlight!
    – WinEunuuchs2Unix
    Apr 27 at 20:03






  • 1




    @WinEunuuchs2Unix The 3 times part, I often do. Sometimes an upgrade brings in new repository servers of which and update refreshes the caches, then the upgrade updates the apps and libraries from the new cache updates. /usr/lib/update-notifier/apt-check sometimes shows more applications after running the three commands the first time. This is especially the case when the system is broken.
    – L. D. James
    Apr 27 at 20:08













up vote
1
down vote










up vote
1
down vote









I experienced the same problem when upgrading to 16.04 on one of my computers. I initially had booting problems, but it finally booted. I got the same unstable error messages you describe. I run a series of these commands:



$ sudo apt update
$ sudo apt upgrade
$ sudo apt dist-upgrade


I paid attention to the screen output of commands and ran the suggested command for that error.



Initially cat /etc/lsb-release showed the previous version.



It became stable by running the above commands 3 times. cat /etc/lsb-release showed the intended 16.04. That was two years ago. It's still running perfectly without any problems.



I believe trying to downgrade would be more problematic than fixing the upgrade issues.



All the commands was running from the console without GUI until the errors were addressed.



If the above commands (because of the /etc/apt/sources.list repository configuration) bring stability to 17.10, you should be able to complete your release upgrade to 18.04.






share|improve this answer














I experienced the same problem when upgrading to 16.04 on one of my computers. I initially had booting problems, but it finally booted. I got the same unstable error messages you describe. I run a series of these commands:



$ sudo apt update
$ sudo apt upgrade
$ sudo apt dist-upgrade


I paid attention to the screen output of commands and ran the suggested command for that error.



Initially cat /etc/lsb-release showed the previous version.



It became stable by running the above commands 3 times. cat /etc/lsb-release showed the intended 16.04. That was two years ago. It's still running perfectly without any problems.



I believe trying to downgrade would be more problematic than fixing the upgrade issues.



All the commands was running from the console without GUI until the errors were addressed.



If the above commands (because of the /etc/apt/sources.list repository configuration) bring stability to 17.10, you should be able to complete your release upgrade to 18.04.







share|improve this answer














share|improve this answer



share|improve this answer








edited Apr 27 at 20:11

























answered Apr 27 at 19:53









L. D. James

17.4k43178




17.4k43178











  • +1 weird cat has to be run 3 times in a row!
    – WinEunuuchs2Unix
    Apr 27 at 19:58










  • There's some type of typo. I'll fix it.
    – L. D. James
    Apr 27 at 20:01










  • Ii was reading from cell phone in bright sunlight!
    – WinEunuuchs2Unix
    Apr 27 at 20:03






  • 1




    @WinEunuuchs2Unix The 3 times part, I often do. Sometimes an upgrade brings in new repository servers of which and update refreshes the caches, then the upgrade updates the apps and libraries from the new cache updates. /usr/lib/update-notifier/apt-check sometimes shows more applications after running the three commands the first time. This is especially the case when the system is broken.
    – L. D. James
    Apr 27 at 20:08

















  • +1 weird cat has to be run 3 times in a row!
    – WinEunuuchs2Unix
    Apr 27 at 19:58










  • There's some type of typo. I'll fix it.
    – L. D. James
    Apr 27 at 20:01










  • Ii was reading from cell phone in bright sunlight!
    – WinEunuuchs2Unix
    Apr 27 at 20:03






  • 1




    @WinEunuuchs2Unix The 3 times part, I often do. Sometimes an upgrade brings in new repository servers of which and update refreshes the caches, then the upgrade updates the apps and libraries from the new cache updates. /usr/lib/update-notifier/apt-check sometimes shows more applications after running the three commands the first time. This is especially the case when the system is broken.
    – L. D. James
    Apr 27 at 20:08
















+1 weird cat has to be run 3 times in a row!
– WinEunuuchs2Unix
Apr 27 at 19:58




+1 weird cat has to be run 3 times in a row!
– WinEunuuchs2Unix
Apr 27 at 19:58












There's some type of typo. I'll fix it.
– L. D. James
Apr 27 at 20:01




There's some type of typo. I'll fix it.
– L. D. James
Apr 27 at 20:01












Ii was reading from cell phone in bright sunlight!
– WinEunuuchs2Unix
Apr 27 at 20:03




Ii was reading from cell phone in bright sunlight!
– WinEunuuchs2Unix
Apr 27 at 20:03




1




1




@WinEunuuchs2Unix The 3 times part, I often do. Sometimes an upgrade brings in new repository servers of which and update refreshes the caches, then the upgrade updates the apps and libraries from the new cache updates. /usr/lib/update-notifier/apt-check sometimes shows more applications after running the three commands the first time. This is especially the case when the system is broken.
– L. D. James
Apr 27 at 20:08





@WinEunuuchs2Unix The 3 times part, I often do. Sometimes an upgrade brings in new repository servers of which and update refreshes the caches, then the upgrade updates the apps and libraries from the new cache updates. /usr/lib/update-notifier/apt-check sometimes shows more applications after running the three commands the first time. This is especially the case when the system is broken.
– L. D. James
Apr 27 at 20:08


















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1028938%2fubuntu-upgrade-to-18-04-lts-from-17-10-failed%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491