Ubuntu Boot Issues

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.

Dashrender

@scottalanmiller said in Ubuntu Boot Issues:

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.

Yep, this is why I use it.. Ubiquiti and XO.

gjacobse

:/boot$ sudo apt-get autoremove

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  linux-image-3.13.0-96-generic linux-image-extra-3.13.0-96-generic
0 upgraded, 0 newly installed, 2 to remove and 18 not upgraded.
After this operation, 195 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 649709 files and directories currently installed.)
Removing linux-image-extra-3.13.0-96-generic (3.13.0-96.143) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-96-generic /boot/vmlinuz-3.13.0-96-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-96-generic /boot/vmlinuz-3.13.0-96-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-96-generic
grep: /boot/config-3.13.0-96-generic: No such file or directory
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-96-generic /boot/vmlinuz-3.13.0-96-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-96-generic /boot/vmlinuz-3.13.0-96-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-105-generic
Found initrd image: /boot/initrd.img-3.13.0-105-generic
Found linux image: /boot/vmlinuz-3.13.0-103-generic
Found initrd image: /boot/initrd.img-3.13.0-103-generic
Found linux image: /boot/vmlinuz-3.13.0-101-generic
Found initrd image: /boot/initrd.img-3.13.0-101-generic
Found linux image: /boot/vmlinuz-3.13.0-100-generic
Found initrd image: /boot/initrd.img-3.13.0-100-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
Removing linux-image-3.13.0-96-generic (3.13.0-96.143) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-96-generic /boot/vmlinuz-3.13.0-96-generic
update-initramfs: Deleting /boot/initrd.img-3.13.0-96-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-96-generic /boot/vmlinuz-3.13.0-96-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-105-generic
Found initrd image: /boot/initrd.img-3.13.0-105-generic
Found linux image: /boot/vmlinuz-3.13.0-103-generic
Found initrd image: /boot/initrd.img-3.13.0-103-generic
Found linux image: /boot/vmlinuz-3.13.0-101-generic
Found initrd image: /boot/initrd.img-3.13.0-101-generic
Found linux image: /boot/vmlinuz-3.13.0-100-generic
Found initrd image: /boot/initrd.img-3.13.0-100-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done

gjacobse

i:/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  151M   66M  70% /boot

Dashrender

boy that didn't help much.

gjacobse

@Dashrender said in Ubuntu Boot Issues:

boy that didn't help much.

oh it did. went from 100% used to just 70% used.

momurda

Is this a problem started with the automatic security update feature of ubuntu? Is that option enabled on on this server?

Dashrender

@gjacobse said in Ubuntu Boot Issues:

@Dashrender said in Ubuntu Boot Issues:

boy that didn't help much.

oh it did. went from 100% used to just 70% used.

That was after you started your manual cleanup, which took you to 75%, now the automated tools took you down to 70%, that's what I was talking about.