Kernel panic after upgrade to 18.04, boot-repair via usbflash failed











up vote
0
down vote

favorite
1












My boot directory seems to be full. I can't find a manual how to delete old kernels via usbflash. I don't know how to get to the hard drive boot folder when operating in usbflash. And I am afraid to delete sensible data of my old installation. But this shouldn't be the case if I only manipulate the boot folder, right. Btw it is also not possible to start from any of the other old installations listed in the grub. I did run boot-repair, but it failed and left me this report: http://paste.ubuntu.com/p/VgT8XjnyKR/
The hints here -->
kernel panic after upgrade to 18.10
sound good. But I am overasked to understand the boot-repair report and would be verz thankful for tips eighter on how to save my old data via usbflash or how to make the old installation running.



Kernel panic screenshots:



enter image description here



enter image description here










share|improve this question









New contributor




freddz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Your boot directory is not full. It is stored in the Ubuntu root partition on /dev/sda4, which is 616 Gb and nearly half-empty (see line 1286). What is the exact kernel panic?
    – Jos
    Nov 21 at 13:28












  • Thanks Jos! As i currently have no possibility to upload a screenshot of the panic elsewhere but in posting an answer here, forgive me to do that..., 1 sec
    – freddz
    Nov 21 at 13:47










  • The usual procedure is to upload a screenshot (or an actual photo if a screenshot is not possible) to imgur.com. A friendly editor with some reputation will then paste it into your question.
    – Jos
    Nov 21 at 13:49










  • ok, cool, here are two screenshots imgur.com/a/VaZxTJS
    – freddz
    Nov 21 at 13:55










  • Browsing through various solutions for this phenomenon I came across this one: forums.linuxmint.com/viewtopic.php?t=145252#p765027 . Please try it out (replacing sda7 by sda4 for your case). If it doesn't work, it is very probably harmless.
    – Jos
    Nov 21 at 14:22















up vote
0
down vote

favorite
1












My boot directory seems to be full. I can't find a manual how to delete old kernels via usbflash. I don't know how to get to the hard drive boot folder when operating in usbflash. And I am afraid to delete sensible data of my old installation. But this shouldn't be the case if I only manipulate the boot folder, right. Btw it is also not possible to start from any of the other old installations listed in the grub. I did run boot-repair, but it failed and left me this report: http://paste.ubuntu.com/p/VgT8XjnyKR/
The hints here -->
kernel panic after upgrade to 18.10
sound good. But I am overasked to understand the boot-repair report and would be verz thankful for tips eighter on how to save my old data via usbflash or how to make the old installation running.



Kernel panic screenshots:



enter image description here



enter image description here










share|improve this question









New contributor




freddz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • Your boot directory is not full. It is stored in the Ubuntu root partition on /dev/sda4, which is 616 Gb and nearly half-empty (see line 1286). What is the exact kernel panic?
    – Jos
    Nov 21 at 13:28












  • Thanks Jos! As i currently have no possibility to upload a screenshot of the panic elsewhere but in posting an answer here, forgive me to do that..., 1 sec
    – freddz
    Nov 21 at 13:47










  • The usual procedure is to upload a screenshot (or an actual photo if a screenshot is not possible) to imgur.com. A friendly editor with some reputation will then paste it into your question.
    – Jos
    Nov 21 at 13:49










  • ok, cool, here are two screenshots imgur.com/a/VaZxTJS
    – freddz
    Nov 21 at 13:55










  • Browsing through various solutions for this phenomenon I came across this one: forums.linuxmint.com/viewtopic.php?t=145252#p765027 . Please try it out (replacing sda7 by sda4 for your case). If it doesn't work, it is very probably harmless.
    – Jos
    Nov 21 at 14:22













up vote
0
down vote

favorite
1









up vote
0
down vote

favorite
1






1





My boot directory seems to be full. I can't find a manual how to delete old kernels via usbflash. I don't know how to get to the hard drive boot folder when operating in usbflash. And I am afraid to delete sensible data of my old installation. But this shouldn't be the case if I only manipulate the boot folder, right. Btw it is also not possible to start from any of the other old installations listed in the grub. I did run boot-repair, but it failed and left me this report: http://paste.ubuntu.com/p/VgT8XjnyKR/
The hints here -->
kernel panic after upgrade to 18.10
sound good. But I am overasked to understand the boot-repair report and would be verz thankful for tips eighter on how to save my old data via usbflash or how to make the old installation running.



Kernel panic screenshots:



enter image description here



enter image description here










share|improve this question









New contributor




freddz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











My boot directory seems to be full. I can't find a manual how to delete old kernels via usbflash. I don't know how to get to the hard drive boot folder when operating in usbflash. And I am afraid to delete sensible data of my old installation. But this shouldn't be the case if I only manipulate the boot folder, right. Btw it is also not possible to start from any of the other old installations listed in the grub. I did run boot-repair, but it failed and left me this report: http://paste.ubuntu.com/p/VgT8XjnyKR/
The hints here -->
kernel panic after upgrade to 18.10
sound good. But I am overasked to understand the boot-repair report and would be verz thankful for tips eighter on how to save my old data via usbflash or how to make the old installation running.



Kernel panic screenshots:



enter image description here



enter image description here







boot kernel boot-repair






share|improve this question









New contributor




freddz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




freddz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited Nov 21 at 13:54









Jos

14k53748




14k53748






New contributor




freddz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Nov 21 at 11:52









freddz

1




1




New contributor




freddz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





freddz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






freddz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • Your boot directory is not full. It is stored in the Ubuntu root partition on /dev/sda4, which is 616 Gb and nearly half-empty (see line 1286). What is the exact kernel panic?
    – Jos
    Nov 21 at 13:28












  • Thanks Jos! As i currently have no possibility to upload a screenshot of the panic elsewhere but in posting an answer here, forgive me to do that..., 1 sec
    – freddz
    Nov 21 at 13:47










  • The usual procedure is to upload a screenshot (or an actual photo if a screenshot is not possible) to imgur.com. A friendly editor with some reputation will then paste it into your question.
    – Jos
    Nov 21 at 13:49










  • ok, cool, here are two screenshots imgur.com/a/VaZxTJS
    – freddz
    Nov 21 at 13:55










  • Browsing through various solutions for this phenomenon I came across this one: forums.linuxmint.com/viewtopic.php?t=145252#p765027 . Please try it out (replacing sda7 by sda4 for your case). If it doesn't work, it is very probably harmless.
    – Jos
    Nov 21 at 14:22


















  • Your boot directory is not full. It is stored in the Ubuntu root partition on /dev/sda4, which is 616 Gb and nearly half-empty (see line 1286). What is the exact kernel panic?
    – Jos
    Nov 21 at 13:28












  • Thanks Jos! As i currently have no possibility to upload a screenshot of the panic elsewhere but in posting an answer here, forgive me to do that..., 1 sec
    – freddz
    Nov 21 at 13:47










  • The usual procedure is to upload a screenshot (or an actual photo if a screenshot is not possible) to imgur.com. A friendly editor with some reputation will then paste it into your question.
    – Jos
    Nov 21 at 13:49










  • ok, cool, here are two screenshots imgur.com/a/VaZxTJS
    – freddz
    Nov 21 at 13:55










  • Browsing through various solutions for this phenomenon I came across this one: forums.linuxmint.com/viewtopic.php?t=145252#p765027 . Please try it out (replacing sda7 by sda4 for your case). If it doesn't work, it is very probably harmless.
    – Jos
    Nov 21 at 14:22
















Your boot directory is not full. It is stored in the Ubuntu root partition on /dev/sda4, which is 616 Gb and nearly half-empty (see line 1286). What is the exact kernel panic?
– Jos
Nov 21 at 13:28






Your boot directory is not full. It is stored in the Ubuntu root partition on /dev/sda4, which is 616 Gb and nearly half-empty (see line 1286). What is the exact kernel panic?
– Jos
Nov 21 at 13:28














Thanks Jos! As i currently have no possibility to upload a screenshot of the panic elsewhere but in posting an answer here, forgive me to do that..., 1 sec
– freddz
Nov 21 at 13:47




Thanks Jos! As i currently have no possibility to upload a screenshot of the panic elsewhere but in posting an answer here, forgive me to do that..., 1 sec
– freddz
Nov 21 at 13:47












The usual procedure is to upload a screenshot (or an actual photo if a screenshot is not possible) to imgur.com. A friendly editor with some reputation will then paste it into your question.
– Jos
Nov 21 at 13:49




The usual procedure is to upload a screenshot (or an actual photo if a screenshot is not possible) to imgur.com. A friendly editor with some reputation will then paste it into your question.
– Jos
Nov 21 at 13:49












ok, cool, here are two screenshots imgur.com/a/VaZxTJS
– freddz
Nov 21 at 13:55




ok, cool, here are two screenshots imgur.com/a/VaZxTJS
– freddz
Nov 21 at 13:55












Browsing through various solutions for this phenomenon I came across this one: forums.linuxmint.com/viewtopic.php?t=145252#p765027 . Please try it out (replacing sda7 by sda4 for your case). If it doesn't work, it is very probably harmless.
– Jos
Nov 21 at 14:22




Browsing through various solutions for this phenomenon I came across this one: forums.linuxmint.com/viewtopic.php?t=145252#p765027 . Please try it out (replacing sda7 by sda4 for your case). If it doesn't work, it is very probably harmless.
– Jos
Nov 21 at 14:22















active

oldest

votes











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: 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
});


}
});






freddz is a new contributor. Be nice, and check out our Code of Conduct.










 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094780%2fkernel-panic-after-upgrade-to-18-04-boot-repair-via-usbflash-failed%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes








freddz is a new contributor. Be nice, and check out our Code of Conduct.










 

draft saved


draft discarded


















freddz is a new contributor. Be nice, and check out our Code of Conduct.













freddz is a new contributor. Be nice, and check out our Code of Conduct.












freddz is a new contributor. Be nice, and check out our Code of Conduct.















 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094780%2fkernel-panic-after-upgrade-to-18-04-boot-repair-via-usbflash-failed%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

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕