Ubuntu Boot Issues

BRRABill

@gjacobse said in Linux system maintenance; /boot nearly full:

Does this seem correct?

Open terminal and check your current kernel:

uname -r
DO NOT REMOVE THIS KERNEL!

Next, type the command below to view/list all installed kernels on your system.

dpkg --list | grep linux-image
Find all the kernels that lower than your current kernel. When you know which kernel to remove, continue below to remove it. Run the commands below to remove the kernel you selected.

sudo apt-get purge linux-image-x.x.x.x-generic
Finally, run the commands below to update grub2

sudo update-grub2
Reboot your system.

I'm not sure if that worked for me either.

I had to manually remove them.

I did not update grub

gjacobse

Any attempt to remove old packages results in:

~$ sudo apt-get purge linux-image-3.13.0-48-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 linux-image-extra-3.13.0-105-generic : Depends: linux-image-3.13.0-105-generic but it is not going to be installed
 linux-image-generic : Depends: linux-image-3.13.0-105-generic but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).

~~~

scottalanmiller

Have you tried the suggestion yet?

apt-get -f install

gjacobse

@scottalanmiller said in Linux system maintenance; /boot nearly full:

Have you tried the suggestion yet?
apt-get -f install

~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
  linux-image-3.13.0-105-generic
Suggested packages:
  fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools
The following NEW packages will be installed:
  linux-image-3.13.0-105-generic
0 upgraded, 1 newly installed, 0 to remove and 18 not upgraded.
11 not fully installed or removed.
Need to get 0 B/15.3 MB of archives.
After this operation, 43.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 648954 files and directories currently installed.)
Preparing to unpack .../linux-image-3.13.0-105-generic_3.13.0-105.152_amd64.deb ...
Done.
Unpacking linux-image-3.13.0-105-generic (3.13.0-105.152) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-105-generic_3.13.0-105.152_amd64.deb (--unpack):
 cannot copy extracted data for './boot/System.map-3.13.0-105-generic' to '/boot/System.map-3.13.0-105-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
                                                                              dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-105-generic /boot/vmlinuz-3.13.0-105-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-105-generic /boot/vmlinuz-3.13.0-105-generic
Errors were encountered while processing:
 /var/cache/apt/archives/linux-image-3.13.0-105-generic_3.13.0-105.152_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Yes, and the above is the result.

scottalanmiller

Ah, the issue appears to be that you allowed the disk to fill to a point that the automated tools can no longer manage it.

scottalanmiller

cd into /boot and give us an ls

gjacobse

i:/boot$ ls
abi-3.13.0-100-generic  abi-3.5.0-31-generic       config-3.13.0-96-generic       memtest86+.bin                 vmlinuz-3.13.0-100-generic
abi-3.13.0-101-generic  abi-3.5.0-32-generic       config-3.13.0-98-generic       memtest86+.elf                 vmlinuz-3.13.0-101-generic
abi-3.13.0-103-generic  abi-3.5.0-34-generic       grub                           memtest86+_multiboot.bin       vmlinuz-3.13.0-103-generic
abi-3.13.0-62-generic   abi-3.5.0-37-generic       initrd.img-3.13.0-100-generic  System.map-3.13.0-100-generic  vmlinuz-3.13.0-62-generic
abi-3.13.0-95-generic   abi-3.5.0-39-generic       initrd.img-3.13.0-101-generic  System.map-3.13.0-101-generic  vmlinuz-3.13.0-95-generic
abi-3.13.0-96-generic   abi-3.5.0-54-generic       initrd.img-3.13.0-103-generic  System.map-3.13.0-103-generic  vmlinuz-3.13.0-96-generic
abi-3.13.0-98-generic   config-3.13.0-100-generic  initrd.img-3.13.0-62-generic   System.map-3.13.0-44-generic   vmlinuz-3.13.0-98-generic
abi-3.5.0-23-generic    config-3.13.0-101-generic  initrd.img-3.13.0-95-generic   System.map-3.13.0-62-generic
abi-3.5.0-27-generic    config-3.13.0-103-generic  initrd.img-3.13.0-96-generic   System.map-3.13.0-95-generic
abi-3.5.0-28-generic    config-3.13.0-62-generic   initrd.img-3.13.0-98-generic   System.map-3.13.0-96-generic
abi-3.5.0-30-generic    config-3.13.0-95-generic   lost+found                     System.map-3.13.0-98-generic

scottalanmiller

Should be save to delete all of these. Copy them into /tmp if you are worried. Double check as you go, but these all seem to be unneeded.

abi-3.5.0-31-generic      
config-3.13.0-96-generic       
abi-3.5.0-32-generic       
config-3.13.0-98-generic        
abi-3.5.0-34-generic       
abi-3.13.0-62-generic   
abi-3.5.0-37-generic       
vmlinuz-3.13.0-62-generic
abi-3.13.0-95-generic   
abi-3.5.0-39-generic         
vmlinuz-3.13.0-95-generic
abi-3.13.0-96-generic   
abi-3.5.0-54-generic       
vmlinuz-3.13.0-96-generic
abi-3.13.0-98-generic     
initrd.img-3.13.0-62-generic   
System.map-3.13.0-44-generic   
vmlinuz-3.13.0-98-generic
abi-3.5.0-23-generic    
initrd.img-3.13.0-95-generic   
System.map-3.13.0-62-generic
abi-3.5.0-27-generic     
initrd.img-3.13.0-96-generic   
System.map-3.13.0-95-generic
abi-3.5.0-28-generic    
config-3.13.0-62-generic   
initrd.img-3.13.0-98-generic   
System.map-3.13.0-96-generic
abi-3.5.0-30-generic    
config-3.13.0-95-generic                    
System.map-3.13.0-98-generic

BRRABill

Yep, exact issue I had.

YOU LET BOOT GET FULL. Lol. That's another feature, right @scottalanmiller

gjacobse

@BRRABill said in Linux system maintenance; /boot nearly full:

Yep, exact issue I had.

YOU LET BOOT GET FULL. Lol. That's another feature, right @scottalanmiller

Not to make an excuse - but as someone who doesn't know much and is trying to learn Linux - I am not sure it can be said that I allowed it to happen.

Therefore - I blame it on the fain.

BRRABill

@gjacobse said in Linux system maintenance; /boot nearly full:

@BRRABill said in Linux system maintenance; /boot nearly full:

Yep, exact issue I had.

YOU LET BOOT GET FULL. Lol. That's another feature, right @scottalanmiller

Not to make an excuse - but as someone who doesn't know much and is trying to learn Linux - I am not sure it can be said that I allowed it to happen.

Therefore - I blame it on the fain.

Oh I am on your side.

That was more a jab at @scottalanmiller

Who will now blame us.

scottalanmiller

@gjacobse said in Linux system maintenance; /boot nearly full:

@BRRABill said in Linux system maintenance; /boot nearly full:

Yep, exact issue I had.

YOU LET BOOT GET FULL. Lol. That's another feature, right @scottalanmiller

Not to make an excuse - but as someone who doesn't know much and is trying to learn Linux - I am not sure it can be said that I allowed it to happen.

Therefore - I blame it on the fain.

Who deployed old Ubuntu in the first place? What server is this?

gjacobse

@scottalanmiller said in Linux system maintenance; /boot nearly full:

@gjacobse said in Linux system maintenance; /boot nearly full:

@BRRABill said in Linux system maintenance; /boot nearly full:

Yep, exact issue I had.

YOU LET BOOT GET FULL. Lol. That's another feature, right @scottalanmiller

Not to make an excuse - but as someone who doesn't know much and is trying to learn Linux - I am not sure it can be said that I allowed it to happen.

Therefore - I blame it on the fain.

Who deployed old Ubuntu in the first place? What server is this?

We took over this install
been running for ( x) years - it is for an UnFi controller.

scottalanmiller

@gjacobse said in Linux system maintenance; /boot nearly full:

We took over this install
been running for ( x) years - it is for an UnFi controller.

"It's been running for..." is another way of stating "it's been unmaintained for..."

gjacobse

pass

Freed up enough space to move forward.

sudo rm -f (File list from above)

Running:

sudo apt-get -f install

(2017 Feb 8: Updated with command used to remove files to free up space in /boot)

gjacobse

Post

:/boot$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            231M   12K  231M   1% /dev
tmpfs            49M  396K   48M   1% /run
/dev/dm-0        49G   13G   34G  28% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
none            5.0M     0  5.0M   0% /run/lock
none            242M     0  242M   0% /run/shm
none            100M     0  100M   0% /run/user
/dev/sda1       228M  155M   61M  72% /boot

scottalanmiller

Run the auto-cleanup script now,too.

Dashrender

@scottalanmiller said in Linux system maintenance; /boot nearly full:

@gjacobse said in Linux system maintenance; /boot nearly full:

I not sure what should be removed, but reading father down the article suggests just running sudo apt-get autoremove and this should be fine.

Welcome to one of the many unpolished bits of Ubuntu compared to the other enterprise Linux offerings. It needs manual maintenance of updates. It's ridiculous. Yes, the autoremove option is the proper way to handle it.

LOL - see it's things like this, or XS's lack of autodetection being on USB and not disabling/moving Log Files like VMWare that just make some of us pull our hair out.

Don't get me wrong - Windows 10's desire to constantly change the default viewer for PDFs is currently driving me mad!

scottalanmiller

@Dashrender said in Linux system maintenance; /boot nearly full:

@scottalanmiller said in Linux system maintenance; /boot nearly full:

@gjacobse said in Linux system maintenance; /boot nearly full:

I not sure what should be removed, but reading father down the article suggests just running sudo apt-get autoremove and this should be fine.

Welcome to one of the many unpolished bits of Ubuntu compared to the other enterprise Linux offerings. It needs manual maintenance of updates. It's ridiculous. Yes, the autoremove option is the proper way to handle it.

LOL - see it's things like this.... that just make some of us pull our hair out.

And that is why Ubuntu is not recommended for newbies to Linux or those not looking for a little more challenge. It's not polished and easy like CentOS is. It's fine, it's a very good system. It's easier than Windows. But it's not comparable to the OSes that would be recommended for someone coming to the Linux world.

The real question would be... why are you running Ubuntu if this is seen as a frustration? I realize in this case, Ubiquiti controllers more or less require it and that's a huge pain that they have introduced. But in general, just don't use it.

gjacobse

topic updated as requested.