Mint won't update - out of memory? SOLVED!

Linux Support
1

Hi.

I hope someone can help me. For a while I’ve been getting error messages when updating. Today, as well as an error message, it said I would out of memory. I have no idea what to do.

This was the message today:

Preconfiguring packages …
(Reading database … 475539 files and directories currently installed.)
Preparing to unpack …/0-python3-samba_2%3a4.11.6+dfsg-0ubuntu1.10_amd64.deb …
Unpacking python3-samba (2:4.11.6+dfsg-0ubuntu1.10) over (2:4.11.6+dfsg-0ubuntu1.9) …
Preparing to unpack …/1-samba-common-bin_2%3a4.11.6+dfsg-0ubuntu1.10_amd64.deb …
Unpacking samba-common-bin (2:4.11.6+dfsg-0ubuntu1.10) over (2:4.11.6+dfsg-0ubuntu1.9) …
Preparing to unpack …/2-smbclient_2%3a4.11.6+dfsg-0ubuntu1.10_amd64.deb …
Unpacking smbclient (2:4.11.6+dfsg-0ubuntu1.10) over (2:4.11.6+dfsg-0ubuntu1.9) …
Preparing to unpack …/3-samba-common_2%3a4.11.6+dfsg-0ubuntu1.10_all.deb …
Unpacking samba-common (2:4.11.6+dfsg-0ubuntu1.10) over (2:4.11.6+dfsg-0ubuntu1.9) …
Preparing to unpack …/4-libsmbclient_2%3a4.11.6+dfsg-0ubuntu1.10_amd64.deb …
Unpacking libsmbclient:amd64 (2:4.11.6+dfsg-0ubuntu1.10) over (2:4.11.6+dfsg-0ubuntu1.9) …
Preparing to unpack …/5-libwbclient0_2%3a4.11.6+dfsg-0ubuntu1.10_amd64.deb …
Unpacking libwbclient0:amd64 (2:4.11.6+dfsg-0ubuntu1.10) over (2:4.11.6+dfsg-0ubuntu1.9) …
Preparing to unpack …/6-samba-libs_2%3a4.11.6+dfsg-0ubuntu1.10_amd64.deb …
Unpacking samba-libs:amd64 (2:4.11.6+dfsg-0ubuntu1.10) over (2:4.11.6+dfsg-0ubuntu1.9) …
Setting up linux-firmware (1.187.16) …
update-initramfs: Generating /boot/initrd.img-5.4.0-81-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgmint-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-81-generic with 1.
dpkg: error processing package linux-firmware (–configure):
installed linux-firmware package post-installation script subprocess returned error exit status 1
Setting up samba-common (2:4.11.6+dfsg-0ubuntu1.10) …
Setting up libwbclient0:amd64 (2:4.11.6+dfsg-0ubuntu1.10) …
Setting up samba-libs:amd64 (2:4.11.6+dfsg-0ubuntu1.10) …
Setting up libsmbclient:amd64 (2:4.11.6+dfsg-0ubuntu1.10) …
Setting up smbclient (2:4.11.6+dfsg-0ubuntu1.10) …
Setting up python3-samba (2:4.11.6+dfsg-0ubuntu1.10) …
Setting up samba-common-bin (2:4.11.6+dfsg-0ubuntu1.10) …
Checking smb.conf with testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE

Done
Processing triggers for man-db (2.9.1-1) …
Processing triggers for libc-bin (2.31-0ubuntu9.2) …
Errors were encountered while processing:
linux-firmware
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up linux-firmware (1.187.16) …
update-initramfs: Generating /boot/initrd.img-5.4.0-81-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgmint-swap_1)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block
cpio: write error: Broken pipe
E: mkinitramfs failure cpio 2 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-81-generic with 1.
dpkg: error processing package linux-firmware (–configure):
installed linux-firmware package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
linux-firmware

I don’t know what any of this means. I’d be very grateful for any help.

Thank you.

2

Hi - and welcome to the forum. This has also happened to me in the past and can be scary! It’s possible that Mint has run out of storage space to install the updated software, hence the error message. One solution may be the following -

When you get notifications of updates (via the Update Manager - the shield icon), have you ever noticed ‘new kernels’ in the list? They appear now and then in amongst the other, general stuff. It’s important that these kernels are installed as they are literally the heart of the system and ensure that security is kept up to date. Now Mint, for some reason known only to the developers, retains all of the old kernels and stores them on your system and eventually the partition they are on becomes full. It’s then up to you, the user to remove them. Other OS’s, I believe, don’t do this and remove older, redundant kernels automatically. It’s pretty straightforward to do but… YOU HAVE TO BE CAREFUL!

If you wish to try, follow the method below that I use periodically but please read it through fully before beginning!

Click on the shield icon to open Update Manager, then on 'View/Linux Kernels. Read the warning notice then hit Continue.

The top line tells you which kernel you are currently using. Make a note of this.

Click on the relevant kernel series in the left-hand column. (Mine is currently 4.15)

You should see that your current kernel is marked ‘Active’ with the others as ‘Installed’ and ‘Superseded’. (Click on the other series numbers and you will see that some will be marked ‘End of Life’)

Any kernel not ‘Active’ is safe to remove - HOWEVER - it is good practice to keep a couple of kernels in reserve just in case your current one plays up.

To do this, click on the button ‘Remove old kernels’. All of that range will be checked for removal and are listed in descending order, oldest to newest. (Your ‘Active’ one should NOT be on the list but if it is - UNCHECK IT) Also, uncheck the bottom 2 in the list - i.e the nearest ones to your current number.

When you are happy with your selection, click on ‘Remove old kernels’ and leave the system to do it’s thing (it may take a while if there are a lot of them to remove). When Update Manager box reappears, repeat the process for the other kernel series, especially those listed as ‘End of Life’. If no check box appears, they have been removed.

To test all is ok, restart the computer, click on Update Manager then ‘Refresh’ and ok any updates that appear. If they install alright, you have cured the issue.

Hope this helps,

Rich

3

Hi Rich

Thank you for your help. I have followed all your steps but I’m not yet sure if the problem is sorted. When I refreshed the Update Manager, I got this message:

"Could not download all repository indexes

The repository may no longer be available or could not be contacted because of network problems. If available, an older version of the failed index will be used. Otherwise, the repository will be ignored. Check your network connection and ensure the repository address is correct in ‘Repositories’ under ‘Settings’."

Then it goes on to say I’m up to date. Again, I don’t know what this means. Perhaps I’ll need to wait until an update is needed?

Thanks again.

Christine

4

You’re welcome!

It looks like it’s worked as it states you are now up to date. The error message refers to a repository that it has tried to contact but has failed for some reason. Either the software stored there has been ignored for the time being or it has found it somewhere else and installed from there.

Try this - Go to Menu/Administration/Synaptic Package Manager. (This is what Update Manager actually does for you when you fire it up ;))

Key in your password and authenticate. You now have Superuser privileges.

Click on Edit and look down the list for ‘Fix broken packages’. Click on that. Look at the very bottom of the box and the message “Successfully fixed dependency problems!” should appear.

Then click Edit again and click on “Reload Package Information”. When that finishes, close Synaptic.

Hopefully the error message should disappear.

Edit: Also - click on Update Manager and hit ‘Refresh’. If a tick appears, you are good to go.

5

Hi Rich

Thanks again for taking the time to help me.

I followed all your instructions and everything was good until the refresh. Unfortunately, the error message is still there.

Hopefully you will have something else I can try? If not, I’m very grateful for your help.

Thanks
Christine

PS It has this error message:

An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /deb stable InRelease: The following signatures were invalid: EXPKEYSIG 1F3045A5DF7587C3 Skype Linux Client Repository se-um@microsoft.comRepository ‘Index of /ubuntu focal-security InRelease’ changed its ‘Suite’ value from ‘focal-backports’ to 'focal-security’Repository ‘Index of /ubuntu focal-security InRelease’ changed its default priority for apt_preferences(5) from 100 to 500.

PPS

I’ve had my first update and it worked perfectly. Thank you so much!

6

You’re welcome - it’s great you’ve got it sorted. :wink:

Can you mark your post as ‘Solved’ as it may help others in the future with similar problems? Go to your original post, click on ‘Modify’ and then in the title box of your post. Add ‘Solved’ at the end of the line.

For info: As the error message is about a Skype module then I’d say don’t worry about it as it isn’t something critical to the OS. Do you use Skype - and does it still work ok? If you don’t, you can remove it via Synaptic PM. If you do, wait a while and see if the Skype (or Mint) developers update the software (or more likely, certificates) and the issue will likely resolve itself.