Insufficient /boot W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

Sometimes the update system will appear: W: mdadm: /etc/mdadm/mdadm.conf defines no arrays., W: mdadm: no arrays defined in configuration file. What should I do? Generally speaking, it is caused by insufficient space in the /boot partition. The biggest possibility is that multiple versions are occupied by the kernel upgrade. We only need to clean up the unused kernel files. Solution:

 

 

 

First check which kernels are available:

 

dpkg -l'linux-image-*' | grep'^ii' or dpkg --get-selections |grep linux-image

 

 

 

For example, on my VPS:

 

root@server-jp:~# dpkg --get-selections |grep linux-image

 

linux-image-4.10.1-041001-generic install

 

linux-image-4.4.0-21-generic install

 

linux-image-4.4.0-53-generic install

 

linux-image-4.4.0-64-generic install

 

linux-image-extra-4.4.0-21-generic install

 

linux-image-extra-4.4.0-53-generic install

 

linux-image-extra-4.4.0-64-generic install

 

linux-image-generic install

 

 

 

You can also use the "ls /boot" command to view which files are in /boot:

 

ls /boot

 

 

 

Uninstall the old kernel, the command is as follows:

 

sudo apt-get purge Linux-image-3.5.0-17-generic

 

Note: The green ones are to be uninstalled, everyone corresponds to your own, only keep what you need to leave!


at 12/06/2020, 18:25pm

Been read 543 times

Similar Articles

BBR acceleration


       This article introduces one-key fool-style upgrade of the kernel and installation of BBR acceleration. Affirm: The tutorial for one-click installation of BBR was created by Teddy! Google's TCP BBR congestion control...

How to mount a disk under Linux


Theoretically adapt to all Linux systems, just determine the mount point Copy all the following commands directly and paste them into the SS terminal: mkfs.ext4 /dev/vdb echo'/dev/vdb /home ext4 defaults 0 0'>> /etc/fstab mount...

What People wrote...

Powered by WHMCompleteSolution