Ubuntu Boot Issues
-
Run the auto-cleanup script now,too.
-
@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 autoremoveand 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!
-
@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 autoremoveand 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.
-
topic updated as requested.
-
@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.
-
:/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 -
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 -
boy that didn't help much.
-
@Dashrender said in Ubuntu Boot Issues:
boy that didn't help much.
oh it did. went from 100% used to just 70% used.
-
Is this a problem started with the automatic security update feature of ubuntu? Is that option enabled on on this server?
-
@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.
-
@Dashrender said in Ubuntu Boot Issues:
@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.
Same here.
-
During the course of this yesterday - the sources.list file got wiped.
Attempts to correct this resulted in more frustration so the VM was restored from back up and and running through this again.
I have updated a process or two to include the needed commands.
Currently space has been freed, the system updated, and autoremove is now running.
Post
sudo apt-get autoremovei:/boot$ df -h Filesystem Size Used Avail Use% Mounted on udev 231M 12K 231M 1% /dev tmpfs 49M 400K 48M 1% /run /dev/dm-0 49G 14G 33G 29% / 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 97M 120M 45% /bootWhich is better than yesterday.
-
Running out of disk space again -
i:/boot$ df -h Filesystem Size Used Avail Use% Mounted on udev 231M 12K 231M 1% /dev tmpfs 49M 400K 48M 1% /run /dev/dm-0 49G 14G 33G 29% / 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 38M 179M 18% /boot:/boot$ sudo apt-get updgrade E: Invalid operation updgrade ntgadmin@SSI-Unifi:/boot$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up initramfs-tools (0.103ubuntu4.6) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.127.23) ... update-initramfs: Generating /boot/initrd.img-3.13.0-105-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 update-initramfs: Generating /boot/initrd.img-3.13.0-44-generic grep: /boot/config-3.13.0-44-generic: No such file or directory update-initramfs: Generating /boot/initrd.img-3.5.0-54-generic grep: /boot/config-3.5.0-54-generic: No such file or directory update-initramfs: Generating /boot/initrd.img-3.5.0-39-generic grep: /boot/config-3.5.0-39-generic: No such file or directory update-initramfs: Generating /boot/initrd.img-3.5.0-37-generic grep: /boot/config-3.5.0-37-generic: No such file or directory update-initramfs: Generating /boot/initrd.img-3.5.0-34-generic grep: /boot/config-3.5.0-34-generic: No such file or directory update-initramfs: Generating /boot/initrd.img-3.5.0-32-generic grep: /boot/config-3.5.0-32-generic: No such file or directory update-initramfs: Generating /boot/initrd.img-3.5.0-31-generic grep: /boot/config-3.5.0-31-generic: No such file or directory update-initramfs: Generating /boot/initrd.img-3.5.0-30-generic grep: /boot/config-3.5.0-30-generic: No such file or directory update-initramfs: Generating /boot/initrd.img-3.5.0-28-generic grep: /boot/config-3.5.0-28-generic: No such file or directory update-initramfs: Generating /boot/initrd.img-3.5.0-27-generic grep: /boot/config-3.5.0-27-generic: No such file or directory update-initramfs: Generating /boot/initrd.img-3.5.0-23-generic grep: /boot/config-3.5.0-23-generic: No such file or directory gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.5.0-23-generic with 1. dpkg: error processing package linux-firmware (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for initramfs-tools (0.103ubuntu4.6) ... update-initramfs: Generating /boot/initrd.img-3.13.0-105-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-105-generic with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 E: Sub-process /usr/bin/dpkg returned an error code (1): /boot$ df -h Filesystem Size Used Avail Use% Mounted on udev 231M 12K 231M 1% /dev tmpfs 49M 400K 48M 1% /run /dev/dm-0 49G 14G 33G 30% / 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 226M 0 100% /boot -
I never looked. Why is it only 228M?
-
@stacksofplates said in Ubuntu Boot Issues:
I never looked. Why is it only 228M?
Maybe it was imported as an appliance or something.
I have had some appliances (Graylog, I'm staring at you) that set up odd partition sizes that crippled the system quickly.
-
Ubuntu's default partitioning makes the boot partition really small. I usually go in and make it bigger when I install Ubuntu.
-
@brianlittlejohn said in Ubuntu Boot Issues:
Ubuntu's default partitioning makes the boot partition really small. I usually go in and make it bigger when I install Ubuntu.
Here is what Ubuntu did on my UniFi controller. It has a 127GB vhdx because I was lazy and just clicked next through the VM creation wizard.
Welcome to Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-34-generic x86_64)user@bnauc02:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 473M 0 473M 0% /dev tmpfs 99M 4.3M 94M 5% /run /dev/mapper/bnauc02--vg-root 124G 12G 106G 11% / tmpfs 491M 0 491M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 491M 0 491M 0% /sys/fs/cgroup /dev/sda2 237M 111M 114M 50% /boot /dev/sda1 511M 3.6M 508M 1% /boot/efi tmpfs 99M 0 99M 0% /run/user/1000 user@bnauc02:~$user@bnauc02:~$ dpkg --list 'linux-image*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==========================-==================-==================-========================================================= un linux-image <none> <none> (no description available) un linux-image-3.0 <none> <none> (no description available) rc linux-image-3.19.0-15-gene 3.19.0-15.15 amd64 Linux kernel image for version 3.19.0 on 64 bit x86 SMP rc linux-image-3.19.0-25-gene 3.19.0-25.26 amd64 Linux kernel image for version 3.19.0 on 64 bit x86 SMP rc linux-image-3.19.0-33-gene 3.19.0-33.38 amd64 Linux kernel image for version 3.19.0 on 64 bit x86 SMP rc linux-image-4.2.0-18-gener 4.2.0-18.22 amd64 Linux kernel image for version 4.2.0 on 64 bit x86 SMP ii linux-image-4.2.0-22-gener 4.2.0-22.27 amd64 Linux kernel image for version 4.2.0 on 64 bit x86 SMP ii linux-image-4.4.0-34-gener 4.4.0-34.53 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP rc linux-image-extra-3.19.0-1 3.19.0-15.15 amd64 Linux kernel extra modules for version 3.19.0 on 64 bit x rc linux-image-extra-3.19.0-2 3.19.0-25.26 amd64 Linux kernel extra modules for version 3.19.0 on 64 bit x rc linux-image-extra-3.19.0-3 3.19.0-33.38 amd64 Linux kernel extra modules for version 3.19.0 on 64 bit x rc linux-image-extra-4.2.0-18 4.2.0-18.22 amd64 Linux kernel extra modules for version 4.2.0 on 64 bit x8 ii linux-image-extra-4.2.0-22 4.2.0-22.27 amd64 Linux kernel extra modules for version 4.2.0 on 64 bit x8 ii linux-image-extra-4.4.0-34 4.4.0-34.53 amd64 Linux kernel extra modules for version 4.4.0 on 64 bit x8 ii linux-image-generic 4.4.0.34.36 amd64 Generic Linux kernel image@bnauc02:~$ ls -l /boot total 103700 -rw-r--r-- 1 root root 1312266 Dec 17 2015 abi-4.2.0-22-generic -rw-r--r-- 1 root root 1241623 Jul 27 2016 abi-4.4.0-34-generic -rw-r--r-- 1 root root 184850 Dec 17 2015 config-4.2.0-22-generic -rw-r--r-- 1 root root 189676 Jul 27 2016 config-4.4.0-34-generic drwx------ 3 root root 4096 Dec 31 1969 efi drwxr-xr-x 5 root root 1024 Jan 30 13:46 grub -rw-r--r-- 1 root root 32325185 Dec 23 09:07 initrd.img-4.2.0-22-generic -rw-r--r-- 1 root root 34624651 Feb 8 00:28 initrd.img-4.4.0-34-generic drwx------ 2 root root 12288 Jul 31 2015 lost+found -rw-r--r-- 1 root root 182704 Jan 28 2016 memtest86+.bin -rw-r--r-- 1 root root 184380 Jan 28 2016 memtest86+.elf -rw-r--r-- 1 root root 184840 Jan 28 2016 memtest86+_multiboot.bin -rw------- 1 root root 3740849 Dec 17 2015 System.map-4.2.0-22-generic -rw------- 1 root root 3866644 Jul 27 2016 System.map-4.4.0-34-generic -rw------- 1 root root 6799856 Dec 17 2015 vmlinuz-4.2.0-22-generic -rw------- 1 root root 6801784 Dec 28 2015 vmlinuz-4.2.0-22-generic.efi.signed -rw------- 1 root root 7046160 Jul 27 2016 vmlinuz-4.4.0-34-generic -rw------- 1 root root 7048088 Aug 26 02:17 vmlinuz-4.4.0-34-generic.efi.signed -
@brianlittlejohn said in Ubuntu Boot Issues:
Ubuntu's default partitioning makes the boot partition really small. I usually go in and make it bigger when I install Ubuntu.
In the week or so since we discussed "Why CentOS and not Ubuntu" there are like 3 of these annoying types of things every day.
-
