Can I repair Ubuntu after an interrupted upgrade?











up vote
0
down vote

favorite












I was in the middle of upgrading from 16.10 to 17.04. Eventually, during installing the upgrades, the OS sort of froze, but the mouse pointer and keyboard still worked (caps lock for example could still turn on/off) which I found weird. Since I couldn't do anything, I suspected something was wrong so I shut it off. When I turned it back on, it went through the usual boot phase. The cursor appeared for a second and then the "clearing orhpaned inode" screen looped over 10 times before the boot loader showed up and remained on the screen.



Can I repair Ubuntu somehow? I only have a 16.04 Live CD. I'm using Remix OS right now which is installed in the root directory. Or do I have to just reinstall?










share|improve this question






















  • What do you mean by the OS freezing? Did the windows just ignore your input? Did you try switching to tty1?
    – rplaughlin
    Oct 9 '17 at 23:51










  • @rplaughlin Nothing worked at all including keyboard shortcuts, I couldn't access the terminal or anything. My laptop speakers are muted by default, so I unplugged my headphones to see if the volume icon icon would change but it didn't. Thankfully I was able to fix it, so I'll update it.
    – Aric
    Oct 10 '17 at 0:42










  • Okay, thanks. Glad to hear you fixed it. How did you fix it, may I ask? Could you write an answer for anyone else who might have the same problem?
    – rplaughlin
    Oct 10 '17 at 0:44








  • 1




    @rplaughlin No problem. So am I, for a moment I thought I'd ultimately have to reinstall which I didn't look forward to doing. I wish I could go over how I fixed it but it took over a dozen steps through trial and error. I gave the starting point to what got me on the right track, though.
    – Aric
    Oct 10 '17 at 1:11















up vote
0
down vote

favorite












I was in the middle of upgrading from 16.10 to 17.04. Eventually, during installing the upgrades, the OS sort of froze, but the mouse pointer and keyboard still worked (caps lock for example could still turn on/off) which I found weird. Since I couldn't do anything, I suspected something was wrong so I shut it off. When I turned it back on, it went through the usual boot phase. The cursor appeared for a second and then the "clearing orhpaned inode" screen looped over 10 times before the boot loader showed up and remained on the screen.



Can I repair Ubuntu somehow? I only have a 16.04 Live CD. I'm using Remix OS right now which is installed in the root directory. Or do I have to just reinstall?










share|improve this question






















  • What do you mean by the OS freezing? Did the windows just ignore your input? Did you try switching to tty1?
    – rplaughlin
    Oct 9 '17 at 23:51










  • @rplaughlin Nothing worked at all including keyboard shortcuts, I couldn't access the terminal or anything. My laptop speakers are muted by default, so I unplugged my headphones to see if the volume icon icon would change but it didn't. Thankfully I was able to fix it, so I'll update it.
    – Aric
    Oct 10 '17 at 0:42










  • Okay, thanks. Glad to hear you fixed it. How did you fix it, may I ask? Could you write an answer for anyone else who might have the same problem?
    – rplaughlin
    Oct 10 '17 at 0:44








  • 1




    @rplaughlin No problem. So am I, for a moment I thought I'd ultimately have to reinstall which I didn't look forward to doing. I wish I could go over how I fixed it but it took over a dozen steps through trial and error. I gave the starting point to what got me on the right track, though.
    – Aric
    Oct 10 '17 at 1:11













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I was in the middle of upgrading from 16.10 to 17.04. Eventually, during installing the upgrades, the OS sort of froze, but the mouse pointer and keyboard still worked (caps lock for example could still turn on/off) which I found weird. Since I couldn't do anything, I suspected something was wrong so I shut it off. When I turned it back on, it went through the usual boot phase. The cursor appeared for a second and then the "clearing orhpaned inode" screen looped over 10 times before the boot loader showed up and remained on the screen.



Can I repair Ubuntu somehow? I only have a 16.04 Live CD. I'm using Remix OS right now which is installed in the root directory. Or do I have to just reinstall?










share|improve this question













I was in the middle of upgrading from 16.10 to 17.04. Eventually, during installing the upgrades, the OS sort of froze, but the mouse pointer and keyboard still worked (caps lock for example could still turn on/off) which I found weird. Since I couldn't do anything, I suspected something was wrong so I shut it off. When I turned it back on, it went through the usual boot phase. The cursor appeared for a second and then the "clearing orhpaned inode" screen looped over 10 times before the boot loader showed up and remained on the screen.



Can I repair Ubuntu somehow? I only have a 16.04 Live CD. I'm using Remix OS right now which is installed in the root directory. Or do I have to just reinstall?







boot upgrade






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 9 '17 at 21:49









Aric

2115




2115












  • What do you mean by the OS freezing? Did the windows just ignore your input? Did you try switching to tty1?
    – rplaughlin
    Oct 9 '17 at 23:51










  • @rplaughlin Nothing worked at all including keyboard shortcuts, I couldn't access the terminal or anything. My laptop speakers are muted by default, so I unplugged my headphones to see if the volume icon icon would change but it didn't. Thankfully I was able to fix it, so I'll update it.
    – Aric
    Oct 10 '17 at 0:42










  • Okay, thanks. Glad to hear you fixed it. How did you fix it, may I ask? Could you write an answer for anyone else who might have the same problem?
    – rplaughlin
    Oct 10 '17 at 0:44








  • 1




    @rplaughlin No problem. So am I, for a moment I thought I'd ultimately have to reinstall which I didn't look forward to doing. I wish I could go over how I fixed it but it took over a dozen steps through trial and error. I gave the starting point to what got me on the right track, though.
    – Aric
    Oct 10 '17 at 1:11


















  • What do you mean by the OS freezing? Did the windows just ignore your input? Did you try switching to tty1?
    – rplaughlin
    Oct 9 '17 at 23:51










  • @rplaughlin Nothing worked at all including keyboard shortcuts, I couldn't access the terminal or anything. My laptop speakers are muted by default, so I unplugged my headphones to see if the volume icon icon would change but it didn't. Thankfully I was able to fix it, so I'll update it.
    – Aric
    Oct 10 '17 at 0:42










  • Okay, thanks. Glad to hear you fixed it. How did you fix it, may I ask? Could you write an answer for anyone else who might have the same problem?
    – rplaughlin
    Oct 10 '17 at 0:44








  • 1




    @rplaughlin No problem. So am I, for a moment I thought I'd ultimately have to reinstall which I didn't look forward to doing. I wish I could go over how I fixed it but it took over a dozen steps through trial and error. I gave the starting point to what got me on the right track, though.
    – Aric
    Oct 10 '17 at 1:11
















What do you mean by the OS freezing? Did the windows just ignore your input? Did you try switching to tty1?
– rplaughlin
Oct 9 '17 at 23:51




What do you mean by the OS freezing? Did the windows just ignore your input? Did you try switching to tty1?
– rplaughlin
Oct 9 '17 at 23:51












@rplaughlin Nothing worked at all including keyboard shortcuts, I couldn't access the terminal or anything. My laptop speakers are muted by default, so I unplugged my headphones to see if the volume icon icon would change but it didn't. Thankfully I was able to fix it, so I'll update it.
– Aric
Oct 10 '17 at 0:42




@rplaughlin Nothing worked at all including keyboard shortcuts, I couldn't access the terminal or anything. My laptop speakers are muted by default, so I unplugged my headphones to see if the volume icon icon would change but it didn't. Thankfully I was able to fix it, so I'll update it.
– Aric
Oct 10 '17 at 0:42












Okay, thanks. Glad to hear you fixed it. How did you fix it, may I ask? Could you write an answer for anyone else who might have the same problem?
– rplaughlin
Oct 10 '17 at 0:44






Okay, thanks. Glad to hear you fixed it. How did you fix it, may I ask? Could you write an answer for anyone else who might have the same problem?
– rplaughlin
Oct 10 '17 at 0:44






1




1




@rplaughlin No problem. So am I, for a moment I thought I'd ultimately have to reinstall which I didn't look forward to doing. I wish I could go over how I fixed it but it took over a dozen steps through trial and error. I gave the starting point to what got me on the right track, though.
– Aric
Oct 10 '17 at 1:11




@rplaughlin No problem. So am I, for a moment I thought I'd ultimately have to reinstall which I didn't look forward to doing. I wish I could go over how I fixed it but it took over a dozen steps through trial and error. I gave the starting point to what got me on the right track, though.
– Aric
Oct 10 '17 at 1:11










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










I was able to fix it. Going into recovery mode and repairing the broken packages (to some extent) started me off on the right track. That didn't solve everything initially, though. A lot of things were all screwed up in different areas, I had missing packages and altered settings, so it took awhile for me to get everything back to normal, but I have a fully upgraded 17.04 now.



While I don't have a step-by-step on how to fix it (I should have recorded the process), for anyone suffering similar problems, just go into recovery mode -- in the GRUB menu -- and press "repair broken packages". That may not solve everything or it might, but if it doesn't just let me know and I'll try to guide you through it if I can.






share|improve this answer























  • You should accept your answer so people can more easily see that it can be fixed.
    – rplaughlin
    Oct 10 '17 at 1:23










  • @rplaughlin I haven't been able to and still can't do it yet. I have to wait 2 hours to accept my own answer according to the system in place.
    – Aric
    Oct 11 '17 at 19:41












  • I had a similar problem (interrupted update, then wlan not working, drm interface not set, etc.), and going through the "repair broken packages" GRUB option seems to have worked.
    – Franco
    May 4 at 20:26













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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f963438%2fcan-i-repair-ubuntu-after-an-interrupted-upgrade%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








up vote
1
down vote



accepted










I was able to fix it. Going into recovery mode and repairing the broken packages (to some extent) started me off on the right track. That didn't solve everything initially, though. A lot of things were all screwed up in different areas, I had missing packages and altered settings, so it took awhile for me to get everything back to normal, but I have a fully upgraded 17.04 now.



While I don't have a step-by-step on how to fix it (I should have recorded the process), for anyone suffering similar problems, just go into recovery mode -- in the GRUB menu -- and press "repair broken packages". That may not solve everything or it might, but if it doesn't just let me know and I'll try to guide you through it if I can.






share|improve this answer























  • You should accept your answer so people can more easily see that it can be fixed.
    – rplaughlin
    Oct 10 '17 at 1:23










  • @rplaughlin I haven't been able to and still can't do it yet. I have to wait 2 hours to accept my own answer according to the system in place.
    – Aric
    Oct 11 '17 at 19:41












  • I had a similar problem (interrupted update, then wlan not working, drm interface not set, etc.), and going through the "repair broken packages" GRUB option seems to have worked.
    – Franco
    May 4 at 20:26

















up vote
1
down vote



accepted










I was able to fix it. Going into recovery mode and repairing the broken packages (to some extent) started me off on the right track. That didn't solve everything initially, though. A lot of things were all screwed up in different areas, I had missing packages and altered settings, so it took awhile for me to get everything back to normal, but I have a fully upgraded 17.04 now.



While I don't have a step-by-step on how to fix it (I should have recorded the process), for anyone suffering similar problems, just go into recovery mode -- in the GRUB menu -- and press "repair broken packages". That may not solve everything or it might, but if it doesn't just let me know and I'll try to guide you through it if I can.






share|improve this answer























  • You should accept your answer so people can more easily see that it can be fixed.
    – rplaughlin
    Oct 10 '17 at 1:23










  • @rplaughlin I haven't been able to and still can't do it yet. I have to wait 2 hours to accept my own answer according to the system in place.
    – Aric
    Oct 11 '17 at 19:41












  • I had a similar problem (interrupted update, then wlan not working, drm interface not set, etc.), and going through the "repair broken packages" GRUB option seems to have worked.
    – Franco
    May 4 at 20:26















up vote
1
down vote



accepted







up vote
1
down vote



accepted






I was able to fix it. Going into recovery mode and repairing the broken packages (to some extent) started me off on the right track. That didn't solve everything initially, though. A lot of things were all screwed up in different areas, I had missing packages and altered settings, so it took awhile for me to get everything back to normal, but I have a fully upgraded 17.04 now.



While I don't have a step-by-step on how to fix it (I should have recorded the process), for anyone suffering similar problems, just go into recovery mode -- in the GRUB menu -- and press "repair broken packages". That may not solve everything or it might, but if it doesn't just let me know and I'll try to guide you through it if I can.






share|improve this answer














I was able to fix it. Going into recovery mode and repairing the broken packages (to some extent) started me off on the right track. That didn't solve everything initially, though. A lot of things were all screwed up in different areas, I had missing packages and altered settings, so it took awhile for me to get everything back to normal, but I have a fully upgraded 17.04 now.



While I don't have a step-by-step on how to fix it (I should have recorded the process), for anyone suffering similar problems, just go into recovery mode -- in the GRUB menu -- and press "repair broken packages". That may not solve everything or it might, but if it doesn't just let me know and I'll try to guide you through it if I can.







share|improve this answer














share|improve this answer



share|improve this answer








edited Oct 10 '17 at 1:04

























answered Oct 10 '17 at 0:53









Aric

2115




2115












  • You should accept your answer so people can more easily see that it can be fixed.
    – rplaughlin
    Oct 10 '17 at 1:23










  • @rplaughlin I haven't been able to and still can't do it yet. I have to wait 2 hours to accept my own answer according to the system in place.
    – Aric
    Oct 11 '17 at 19:41












  • I had a similar problem (interrupted update, then wlan not working, drm interface not set, etc.), and going through the "repair broken packages" GRUB option seems to have worked.
    – Franco
    May 4 at 20:26




















  • You should accept your answer so people can more easily see that it can be fixed.
    – rplaughlin
    Oct 10 '17 at 1:23










  • @rplaughlin I haven't been able to and still can't do it yet. I have to wait 2 hours to accept my own answer according to the system in place.
    – Aric
    Oct 11 '17 at 19:41












  • I had a similar problem (interrupted update, then wlan not working, drm interface not set, etc.), and going through the "repair broken packages" GRUB option seems to have worked.
    – Franco
    May 4 at 20:26


















You should accept your answer so people can more easily see that it can be fixed.
– rplaughlin
Oct 10 '17 at 1:23




You should accept your answer so people can more easily see that it can be fixed.
– rplaughlin
Oct 10 '17 at 1:23












@rplaughlin I haven't been able to and still can't do it yet. I have to wait 2 hours to accept my own answer according to the system in place.
– Aric
Oct 11 '17 at 19:41






@rplaughlin I haven't been able to and still can't do it yet. I have to wait 2 hours to accept my own answer according to the system in place.
– Aric
Oct 11 '17 at 19:41














I had a similar problem (interrupted update, then wlan not working, drm interface not set, etc.), and going through the "repair broken packages" GRUB option seems to have worked.
– Franco
May 4 at 20:26






I had a similar problem (interrupted update, then wlan not working, drm interface not set, etc.), and going through the "repair broken packages" GRUB option seems to have worked.
– Franco
May 4 at 20:26




















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f963438%2fcan-i-repair-ubuntu-after-an-interrupted-upgrade%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Quarter-circle Tiles

build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

Mont Emei