{"id":421,"date":"2026-03-12T21:31:56","date_gmt":"2026-03-13T05:31:56","guid":{"rendered":"https:\/\/www.dumpsterfirecomputing.com\/?p=421"},"modified":"2026-03-13T05:22:27","modified_gmt":"2026-03-13T13:22:27","slug":"its-never-coming-back","status":"publish","type":"post","link":"https:\/\/www.dumpsterfirecomputing.com\/?p=421","title":{"rendered":"“It’s Never Coming Back”"},"content":{"rendered":"\n

Or is it?<\/p>\n\n\n\n

Two and a half months in and I finally broke my Mint install on the desktop. I created the purple-screen “Kernel Panic” (reminiscent of the many BSOD’s I’ve encountered in Windows over the last 2+ decades). <\/p>\n\n\n\n

The TL;DR is that I managed to figure out how to roll back to the Windows version of “Last Known Good” – a previous kernel.<\/p>\n\n\n\n

This post is mostly a raw-form account of what was broken, how I tried to fix it, where I think I went wrong, and ends with what I hope to learn from the experience. And no, this has not led to me wanting to reinstall Windows 11 — far from it, I want to understand exactly what I did wrong, and why some things didn’t work as expected.<\/p>\n\n\n\n

It Started With Updates<\/h2>\n\n\n\n

At some point in the last 3-4 weeks, I made a change on my system that caused the following error to pop up every time I ran updates:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
<\/code><\/pre>\n\n\n\n
The full content of the error can be exposed here<\/summary>\n
InstallArchives() failed: (Reading database ... \n(Reading database ... 5%%\n(Reading database ... 10%%\n(Reading database ... 15%%\n(Reading database ... 20%%\n(Reading database ... 25%%\n(Reading database ... 30%%\n(Reading database ... 35%%\n(Reading database ... 40%%\n(Reading database ... 45%%\n(Reading database ... 50%%\n(Reading database ... 55%%\n(Reading database ... 60%%\n(Reading database ... 65%%\n(Reading database ... 70%%\n(Reading database ... 75%%\n(Reading database ... 80%%\n(Reading database ... 85%%\n(Reading database ... 90%%\n(Reading database ... 95%%\n(Reading database ... 100%%\n(Reading database ... 545024 files and directories currently installed.)\nPreparing to unpack ...\/0-curl_8.5.0-2ubuntu10.8_amd64.deb ...\nUnpacking curl (8.5.0-2ubuntu10.8) over (8.5.0-2ubuntu10.7) ...\nPreparing to unpack ...\/1-libcurl4t64_8.5.0-2ubuntu10.8_amd64.deb ...\nDe-configuring libcurl4t64:i386 (8.5.0-2ubuntu10.7), to allow configuration of libcurl4t64:amd64 (8.5.0-2ubuntu10.8) ...\nUnpacking libcurl4t64:amd64 (8.5.0-2ubuntu10.8) over (8.5.0-2ubuntu10.7) ...\nPreparing to unpack ...\/2-libcurl4t64_8.5.0-2ubuntu10.8_i386.deb ...\nUnpacking libcurl4t64:i386 (8.5.0-2ubuntu10.8) over (8.5.0-2ubuntu10.7) ...\nPreparing to unpack ...\/3-libcurl3t64-gnutls_8.5.0-2ubuntu10.8_i386.deb ...\nDe-configuring libcurl3t64-gnutls:amd64 (8.5.0-2ubuntu10.7), to allow configuration of libcurl3t64-gnutls:i386 (8.5.0-2ubuntu10.8) ...\nUnpacking libcurl3t64-gnutls:i386 (8.5.0-2ubuntu10.8) over (8.5.0-2ubuntu10.7) ...\nPreparing to unpack ...\/4-libcurl3t64-gnutls_8.5.0-2ubuntu10.8_amd64.deb ...\nUnpacking libcurl3t64-gnutls:amd64 (8.5.0-2ubuntu10.8) over (8.5.0-2ubuntu10.7) ...\nPreparing to unpack ...\/5-libgtk-4-common_4.14.5+ds-0ubuntu0.9_all.deb ...\nUnpacking libgtk-4-common (4.14.5+ds-0ubuntu0.9) over (4.14.5+ds-0ubuntu0.7) ...\nPreparing to unpack ...\/6-libgtk-4-1_4.14.5+ds-0ubuntu0.9_amd64.deb ...\nUnpacking libgtk-4-1:amd64 (4.14.5+ds-0ubuntu0.9) over (4.14.5+ds-0ubuntu0.7) ...\nSetting up linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...\nSetting up libcurl4t64:amd64 (8.5.0-2ubuntu10.8) ...\nSetting up libcurl4t64:i386 (8.5.0-2ubuntu10.8) ...\nSetting up libcurl3t64-gnutls:amd64 (8.5.0-2ubuntu10.8) ...\nSetting up libcurl3t64-gnutls:i386 (8.5.0-2ubuntu10.8) ...\nSetting up linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...\n\/etc\/kernel\/header_postinst.d\/dkms:\n * dkms: running auto installation service for kernel 6.17.0-14-generic\nSign command: \/usr\/bin\/kmodsign\nSigning key: \/var\/lib\/shim-signed\/mok\/MOK.priv\nPublic certificate (MOK): \/var\/lib\/shim-signed\/mok\/MOK.der\n\nBuilding module:\nCleaning build area...\nmake -j12 KERNELRELEASE=6.17.0-14-generic -C \/lib\/modules\/6.17.0-14-generic\/build M=\/var\/lib\/dkms\/virtualbox\/7.0.16\/build...(bad exit status: 2)\nError! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)\nConsult \/var\/lib\/dkms\/virtualbox\/7.0.16\/build\/make.log for more information.\ndkms autoinstall on 6.17.0-14-generic\/x86_64 failed for virtualbox(10)\nError! One or more modules failed to install during autoinstall.\nRefer to previous errors for more information.\n * dkms: autoinstall for kernel 6.17.0-14-generic\n   ...fail!\nrun-parts: \/etc\/kernel\/header_postinst.d\/dkms exited with return code 11\ndpkg: error processing package linux-headers-6.17.0-14-generic (--configure):\n installed linux-headers-6.17.0-14-generic package post-installation script subprocess returned error exit status 11\ndpkg: dependency problems prevent configuration of linux-headers-generic-hwe-24.04:\n linux-headers-generic-hwe-24.04 depends on linux-headers-6.17.0-14-generic; however:\n  Package linux-headers-6.17.0-14-generic is not configured yet.\n\ndpkg: error processing package linux-headers-generic-hwe-24.04 (--configure):\n dependency problems - leaving unconfigured\nSetting up curl (8.5.0-2ubuntu10.8) ...\nSetting up libgtk-4-common (4.14.5+ds-0ubuntu0.9) ...\ndpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:\n linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (= 6.17.0-14.14~24.04.1); however:\n  Package linux-headers-generic-hwe-24.04 is not configured yet.\n\ndpkg: error processing package linux-generic-hwe-24.04 (--configure):\n dependency problems - leaving unconfigured\nProcessing triggers for libc-bin (2.39-0ubuntu8.7) ...\nProcessing triggers for man-db (2.12.0-4build2) ...\nProcessing triggers for libglib2.0-0t64:amd64 (2.80.0-6ubuntu3.8) ...\nProcessing triggers for libglib2.0-0t64:i386 (2.80.0-6ubuntu3.8) ...\nSetting up libgtk-4-1:amd64 (4.14.5+ds-0ubuntu0.9) ...\nProcessing triggers for linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...\n\/etc\/kernel\/postinst.d\/dkms:\n * dkms: running auto installation service for kernel 6.17.0-14-generic\nSign command: \/usr\/bin\/kmodsign\nSigning key: \/var\/lib\/shim-signed\/mok\/MOK.priv\nPublic certificate (MOK): \/var\/lib\/shim-signed\/mok\/MOK.der\n\nBuilding module:\nCleaning build area...\nmake -j12 KERNELRELEASE=6.17.0-14-generic -C \/lib\/modules\/6.17.0-14-generic\/build M=\/var\/lib\/dkms\/virtualbox\/7.0.16\/build...(bad exit status: 2)\nError! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)\nConsult \/var\/lib\/dkms\/virtualbox\/7.0.16\/build\/make.log for more information.\ndkms autoinstall on 6.17.0-14-generic\/x86_64 failed for virtualbox(10)\nError! One or more modules failed to install during autoinstall.\nRefer to previous errors for more information.\n * dkms: autoinstall for kernel 6.17.0-14-generic\n   ...fail!\nrun-parts: \/etc\/kernel\/postinst.d\/dkms exited with return code 11\ndpkg: error processing package linux-image-6.17.0-14-generic (--configure):\n installed linux-image-6.17.0-14-generic package post-installation script subprocess returned error exit status 11\nProcessing triggers for libc-bin (2.39-0ubuntu8.7) ...\nErrors were encountered while processing:\n linux-headers-6.17.0-14-generic\n linux-headers-generic-hwe-24.04\n linux-generic-hwe-24.04\n linux-image-6.17.0-14-generic\nSetting up linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...\nSetting up linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...\n\/etc\/kernel\/header_postinst.d\/dkms:\n * dkms: running auto installation service for kernel 6.17.0-14-generic\nSign command: \/usr\/bin\/kmodsign\nSigning key: \/var\/lib\/shim-signed\/mok\/MOK.priv\nPublic certificate (MOK): \/var\/lib\/shim-signed\/mok\/MOK.der\n\nBuilding module:\nCleaning build area...\nmake -j12 KERNELRELEASE=6.17.0-14-generic -C \/lib\/modules\/6.17.0-14-generic\/build M=\/var\/lib\/dkms\/virtualbox\/7.0.16\/build...(bad exit status: 2)\nError! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)\nConsult \/var\/lib\/dkms\/virtualbox\/7.0.16\/build\/make.log for more information.\ndkms autoinstall on 6.17.0-14-generic\/x86_64 failed for virtualbox(10)\nError! One or more modules failed to install during autoinstall.\nRefer to previous errors for more information.\n * dkms: autoinstall for kernel 6.17.0-14-generic\n   ...fail!\nrun-parts: \/etc\/kernel\/header_postinst.d\/dkms exited with return code 11\ndpkg: error processing package linux-headers-6.17.0-14-generic (--configure):\n installed linux-headers-6.17.0-14-generic package post-installation script subprocess returned error exit status 11\ndpkg: dependency problems prevent configuration of linux-headers-generic-hwe-24.04:\n linux-headers-generic-hwe-24.04 depends on linux-headers-6.17.0-14-generic; however:\n  Package linux-headers-6.17.0-14-generic is not configured yet.\n\ndpkg: error processing package linux-headers-generic-hwe-24.04 (--configure):\n dependency problems - leaving unconfigured\ndpkg: dependency problems prevent configuration of linux-generic-hwe-24.04:\n linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (= 6.17.0-14.14~24.04.1); however:\n  Package linux-headers-generic-hwe-24.04 is not configured yet.\n\ndpkg: error processing package linux-generic-hwe-24.04 (--configure):\n dependency problems - leaving unconfigured\nProcessing triggers for linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ...\n\/etc\/kernel\/postinst.d\/dkms:\n * dkms: running auto installation service for kernel 6.17.0-14-generic\nSign command: \/usr\/bin\/kmodsign\nSigning key: \/var\/lib\/shim-signed\/mok\/MOK.priv\nPublic certificate (MOK): \/var\/lib\/shim-signed\/mok\/MOK.der\n\nBuilding module:\nCleaning build area...\nmake -j12 KERNELRELEASE=6.17.0-14-generic -C \/lib\/modules\/6.17.0-14-generic\/build M=\/var\/lib\/dkms\/virtualbox\/7.0.16\/build...(bad exit status: 2)\nError! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64)\nConsult \/var\/lib\/dkms\/virtualbox\/7.0.16\/build\/make.log for more information.\ndkms autoinstall on 6.17.0-14-generic\/x86_64 failed for virtualbox(10)\nError! One or more modules failed to install during autoinstall.\nRefer to previous errors for more information.\n * dkms: autoinstall for kernel 6.17.0-14-generic\n   ...fail!\nrun-parts: \/etc\/kernel\/postinst.d\/dkms exited with return code 11\ndpkg: error processing package linux-image-6.17.0-14-generic (--configure):\n installed linux-image-6.17.0-14-generic package post-installation script subprocess returned error exit status 11\nErrors were encountered while processing:<\/code><\/pre>\n<\/details>\n\n\n\n
The error popped up after every update, but it seemed like updates went ahead and installed anyway.  So I did what most users do – ignored it.  This week, though, I decided to look into it.  Since this was unfamiliar territory for me, I wanted to take that wall-o-text and look at the first error in an attempt to narrow down where the problem could be.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
The error relates to Virtual Box, which I do have installed.  It’s pretty core to the function this desktop serves for me.  The error also says to check a specific make.log<\/code> file for more information.  In that log file, there are a number of errors about being unable to find specific .h<\/code> files for including in builds.  In my long-ago-C++ days, I recognize these as header files.  And that’s where my knowledge of these files ends.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
I did notice that the errors in the make.log<\/code> file referenced similar package found in the earlier message where Virtual Box was mentioned:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
I felt like I was on to something.<\/p>\n\n\n\n
From here I took parts of the error right to the Brave Search to look for potential solutions, and it gave me some fairly sensible direction:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
But here is where I think I made my first mistake (at least as I write this and look back at the “what went wrong”).  More on that near the end…<\/p>\n\n\n\n
The first tip was to attempt to reconfigure any pending packages.  A reasonable first step, so I ran it:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Seems stuck on these last four packages for some reason…<\/p>\n\n\n\n
The second step was to attempt to fix broken dependencies – any dependencies that may be missing or just full on broken:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Same issue it seems.<\/p>\n\n\n\n
Rather than explain my next step, I took a screenshot of the specific notes I wrote to myself as I worked through this:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
I feel like I was foreshadowing…<\/p>\n\n\n\n
Reinstall the problematic packages.  I followed along:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
We’re down to just the one package giving errors.  I thought this was progress, so I went ahead and run the install command to reinstall what I’d just removed.  That process took perhaps two minutes in total, but this time I’m back up to two errors:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
At this point I’m not sure if I’ve helped or hurt my cause.  I decide to run the reconfigure packages again just to see if there was any change, and there was not.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
I took a step back and decided to search for any information on this new dpkg: error....<\/code> message I was seeing:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
“Broadcom drivers, you say?” I haven’t added\/removed any hardware since installing Mint on this desktop in early January, so I don’t think this is a rabbit worth chasing down the hole.<\/p>\n\n\n\n
I took two steps back and remembered that from the very beginning this seemed related to Virtual Box somehow.  And then it smacked me right in the face:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
“VirtualBox 7.0.16 is incompatible with the Linux kernel 6.17.0-14-generic”<\/em><\/p>\n\n\n\n
Oh dear.  But, I think we’ve found root cause!<\/p>\n\n\n\n
I often hear that people don’t like Linux Mint because of the slow-roll for the latest and greatest.  It’s based on an Ubuntu LTS and it doesn’t change drastically as fast as others.  So….perhaps that’s what I’ve bumped in to.  While VirtualBox 7.2 is available for download on Oracle’s website, only version 7.0.16 is available through Mint’s Software Manager:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
By this point, I’d done a little more research to ensure that if I removed VirtualBox it would leave my VM’s intact (which I read that it would), and my plan was to come back the next day and remove the older VirtualBox and manually download\/install version 7.2<\/p>\n\n\n\n
VFS: Unable to mount root fs on unknown-block(0,)<\/h2>\n\n\n\n
Uh oh – the next day I was greeted with the kernel panic.  So now I had an entirely new adventure to embark on — how to safely fix this self-inflicted wound.<\/p>\n\n\n\n
Luckily, my grub advanced screen had options to boot into older kernel versions, which ultimately got me back to where I am now.  The broken kernel version was 6.17.0-14-generic<\/code> and the previous one I had which worked is 6.14.0-37-generic<\/code><\/p>\n\n\n\n
That said, while I was able to boot into the 6.14 kernel, I’d attempted a few things to “fix” my 6.17.  <\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Well none of that really did the trick, and this time I’m told that there are some critical modules missing out of the kernel.  I can only assume that I removed those modules.<\/p>\n\n\n\n
The other thing I tried was using my Timeshift restore point that I took before I started voiding my own warranty, and curiously…..that didn’t fix anything.  In the restore settings, I’d event checked the Update initramfs<\/code> just in case that could help it along.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
No dice.<\/p>\n\n\n\n
I ended up going with the final recommendation, which is to remove the broken kernel and clean things up:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
There were no problems or errors while doing that, I was able to restart safely and boot normally (albeit in the 6.14 kernel).<\/p>\n\n\n\n
Proving I’m Wrong<\/h2>\n\n\n\n
I know I did a bad.  I may have done a few bad’s.  What I hope to do now is try to understand where I went wrong, and what I could have done differently.<\/p>\n\n\n\n
Remember I hinted at my first mistake earlier?  Well, my first search was for a slightly different error than I probably should have searched for.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
I plugged in this dpkg line which led me down the path of what I believe was my downfall – removing this header package.<\/p>\n\n\n\n
I’m also curious why Timeshift didn’t fix my issues – I was under the (perhaps incorrect assumption) that Timeshfit was designed exactly for this kind of situation.  Take a backup, bork some files, revert to the previous backup.  Maybe I’m missing something there — but I want to understand that more as well.<\/p>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
I feel that situations like this must be taken as learning opportunities.  As I’ve said in other posts, I’m not afraid to get my hands dirty in the terminal, though it’s clear I need better understanding of just what I’m doing.  None of the actual commands I ran above seemed scary, and I obviously felt a certain level of comfort in running them, but the files and packages and modules I was working with were clearly more important than I realized.  <\/p>\n\n\n\n
In a way, it feels a little exciting to know that I stumbled my way into a mess and stumbled my way back out.  Perhaps I got incredibly lucky, but when I think back to my early days of how I first learned to use Windows it all boils down to the same thing – trial and error.  Fix what I break.  Learn from the experience.  That’s what I intend to do here as well…<\/p>\n","protected":false},"excerpt":{"rendered":"
Or is it? Two and a half months in and I finally broke my Mint install on the desktop. I created the purple-screen “Kernel Panic” (reminiscent of the many BSOD’s […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,65,24],"tags":[],"class_list":["post-421","post","type-post","status-publish","format-standard","hentry","category-general","category-linux","category-troubleshooting"],"_links":{"self":[{"href":"https:\/\/www.dumpsterfirecomputing.com\/index.php?rest_route=\/wp\/v2\/posts\/421","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dumpsterfirecomputing.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dumpsterfirecomputing.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dumpsterfirecomputing.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dumpsterfirecomputing.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=421"}],"version-history":[{"count":4,"href":"https:\/\/www.dumpsterfirecomputing.com\/index.php?rest_route=\/wp\/v2\/posts\/421\/revisions"}],"predecessor-version":[{"id":446,"href":"https:\/\/www.dumpsterfirecomputing.com\/index.php?rest_route=\/wp\/v2\/posts\/421\/revisions\/446"}],"wp:attachment":[{"href":"https:\/\/www.dumpsterfirecomputing.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=421"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dumpsterfirecomputing.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=421"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dumpsterfirecomputing.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=421"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}