dpkg: error processing linux-image-amd64

linux debian dpkg upgrade

We see that df claims only 19MB is used in /boot and 151MB is available. But the directory listing shows far more than 19MB of files!

Therefore I would guess that the /boot filesystem has been corrupted.

Unmount it and check it:

umount /boot
fsck -f /boot

Rannie Ollit

Updated on September 18, 2022

Comments

Rannie Ollit over 1 year
Let's say that:
1. A user has many post
2. A user has many event
3. An event has many post
The question is, how can i connect the related events, post and user?
- Abhishek Anand Amralkar almost 11 years
  
  I think your server/system is getting out of disk space check for /boot partition . what is the output of df -h?
- h00j almost 11 years
  
  It says I have 24G free
- Flup almost 11 years
  
  No, you have 151M free on /boot.
- scai almost 11 years
  
  Also check the output of df -i.
- h00j almost 11 years
  
  Added output of df -i, so how can I free space on /boot or allocate more space?
- h00j almost 11 years
  
  Could I not just remove some of the stuff in /boot ?
- Abhishek Anand Amralkar almost 11 years
  
  No please dont do that. You need to resize your boot partition, shrink any other parttion free up some space and aloocate it to boot partion.
- Abhishek Anand Amralkar almost 11 years
  
  apt-get install gparted is the good tool to resize your partitions.
- h00j almost 11 years
  
  Its non GUI, shall I use parted?
- scai almost 11 years
  
  And don't shrink your partitions without having a backup.
- h00j almost 11 years
  
  It wont let me install parted because of the error.
- Sergey Vlasov almost 11 years
  
  Resizing /boot is problematic, because you may need to reinstall your bootloader after doing this, and may be left with an unbootable system. However, you may think about deleting some old kernel packages which were not used for a long time (if you did not need to revert to the old kernel for some months, you probably can remove it).
- user6949202 almost 11 years
  
  Check the output of dmesg. It should show the signs of corruption if there's something wrong with your filesystems.
- Ali Özen almost 6 years
  
  laravel.com/docs/5.6/eloquent-relationships#many-to-many
h00j almost 11 years

fsck from util-linux 2.20.1 e2fsck 1.42.5 (29-Jul-2012) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sda2: 304/48672 files (16.4% non-contiguous), 92609/97280 blocks
Sergey Vlasov almost 11 years

92609/97280 blocks means that your /boot filesystem is almost full; probably some summary information was corrupted, so df gave wrong data. Now you can mount /boot again and continue with solving the “full /boot” problem.