So I decided, in my wisdom, to try and update the two Linux machines I have here to Ubuntu 18.04 to at least stay up to date.

One went super smooth. The other? Well...not so much. The first attempt is what Linux should be. Smooth. Seamless. Fast. Just some yes/no prompts in the terminal and after the 1.3 gb or so download, off it went and installed.

On the other Machine, I attempted a sudo apt-get update and upgrade.

Unfortunately, for some reason, Any time I attempt to install, fix, or remove packages, I got, and still get, this.

Errors were encountered while processing:
linux-image-extra-4.13.0-38-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
So, doing some research, I found that I need to navigate to /boot and remove all of the earlier colonels (why Ubuntu itself can't bother doing this I have no idea). Did that.

Now I try and fix things again.

Sudo apt-get -f install

It continuously tells me it will 'remove 167 mb'. That doesn't happen, and instead it adds all of the old colonels and gives me the exact same error all over again.

That was all last night. I noticed the fans of the laptop weren't spinning up as they should, so upon further investigation.
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 2
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 58
Model name: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
Stepping: 9
CPU MHz: 2294.865
CPU max MHz: 3300.0000
CPU min MHz: 1200.0000
BogoMIPS: 4589.73

Turbo boost is, and always was, enabled in the bios, and was, until last night, utilized to its full potential, even at 100%.

Does anyone have any ideas before I either completely reinstall Linux or just put Windows on here and be done? Leaning toward the latter option so I can at least get some CPD work and have my Turbo boost back. 8x800 MHZ can add up. Still, would be nice to at least figure this out for when it inevitably happens again...

Can you

sudo apt autoremove

to get rid of the old kernels, or will that throw an error as well?

Can you

sudo apt autoremove

to get rid of the old kernels, or will that throw an error as well?

Here's what resulted from that.

Reading package lists... 0%

Reading package lists... 100%

Reading package lists... Done


Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree


Reading state information... 0%

Reading state information... 0%

Reading state information... Done

The following packages will be REMOVED:
linux-image-extra-4.13.0-38-generic
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 167 MB disk space will be freed.
Do you want to continue? [Y/n] yes

78(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 345337 files and directories currently installed.)
Removing linux-image-extra-4.13.0-38-generic (4.13.0-38.43~16.04.1) ...
7Progress: [ 0%] [..........................................................] 8depmod: FATAL: could not load /boot/System.map-4.13.0-38-generic: No such file or directory
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-38-generic /boot/vmlinuz-4.13.0-38-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-38-generic /boot/vmlinuz-4.13.0-38-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0-38-generic /boot/vmlinuz-4.13.0-38-generic
update-initramfs: Generating /boot/initrd.img-4.13.0-38-generic
depmod: WARNING: could not open /var/tmp/mkinitramfs_LmakVi/lib/modules/4.13.0-38-generic/modules.order: No such file or directory
depmod: WARNING: could not open /var/tmp/mkinitramfs_LmakVi/lib/modules/4.13.0-38-generic/modules.builtin: No such file or directory

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.13.0-38-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-extra-4.13.0-38-generic (--remove):
subprocess installed post-removal script returned error exit status 1
Errors were encountered while processing:
linux-image-extra-4.13.0-38-generic

78E: Sub-process /usr/bin/dpkg returned an error code (1)
]0;wolfman1360@~wolfman1360@~$

Can you

sudo apt autoremove

to get rid of the old kernels, or will that throw an error as well?

Interestingly, I don't get an error but it doesn't remove the kernels as I see when I look in /boot/

0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
dave@Willow:~$

It may be because of having done a version upgrade from 18.10 to 19.04 but at some point I will look at other options for pruning.

Can you

sudo apt autoremove

to get rid of the old kernels, or will that throw an error as well?

Interestingly, I don't get an error but it doesn't remove the kernels as I see when I look in /boot/

0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
dave@Willow:~$

It may be because of having done a version upgrade from 18.10 to 19.04 but at some point I will look at other options for pruning.

Thanks. At least it isn't stopping me from crunching at this point.

Perhaps you've already found this thread in your troubleshooting, but if not, maybe something in it will help:

https://askubuntu.com/questions/585736/cant-clean-a-full-boot-because-of-unmet-dependencies

Perhaps you've already found this thread in your troubleshooting, but if not, maybe something in it will help:

https://askubuntu.com/questions/585736/cant-clean-a-full-boot-because-of-unmet-dependencies

I found that along the way. I'll be trying a few of the things suggested as the week goes on.
Thanks for the help.