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.
-
@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.
-
-
@stacksofplates said in Ubuntu Boot Issues:
It has a 127GB vhd
Holy crap that's big
Hyper-V default VHDX size in the New VM screens.
-
So I just tried to upgrade my UniFi controller since I noticed it was stuck on 16.04. Apparently when it upgraded from whatever previous version it was on, the release flag got set to only upgrade to the LTS line /sigh...
/etc/update-manager/release-upgrades
was set toPrompt=lts
I changed it to
Prompt=normal
and then did the upgrade. Boom not enough space on /boot. -
@JaredBusch When I upgraded to 16.10, it also disabled the unifi repos and I had to go in and enable them again.
-
@brianlittlejohn said in Ubuntu Boot Issues:
@JaredBusch When I upgraded to 16.10, it also disabled the unifi repos and I had to go in and enable them again.
That is normal with ever distribution upgrade in unbuntu. i know and expect that. part of the upgrade process is to disable all 3rd party repos.
-
@JaredBusch Good to know... this was the first time I upgraded a distro and didn't realize that would happen.
-
This right here is hateful.
New release available run this.
Run that, and
no release found
ugh - but linux is so much the easy. -
@JaredBusch said in Ubuntu Boot Issues:
/etc/update-manager/release-upgrades was set to Prompt=lts
I changed it to Prompt=normal and then did the upgrade. Boom not enough space on /boot. -
@JaredBusch said in Ubuntu Boot Issues:
@JaredBusch said in Ubuntu Boot Issues:
/etc/update-manager/release-upgrades was set to Prompt=lts
I changed it to Prompt=normal and then did the upgrade. Boom not enough space on /boot.Read that,.//
Did that,
-
I never bothered to check syntax, google told me to do this.
bnaadmin@bnauc02:~$ sudo do-release-upgrade -d
It worked.
I'm not out to learn Ubuntu practices.
-
@JaredBusch said in Ubuntu Boot Issues:
I never bothered to check syntax, google told me to do this.
bnaadmin@bnauc02:~$ sudo do-release-upgrade -d
It worked.
I'm not out to learn Ubuntu practices.
yea,.. just did that too..
Still showing no release found.
-
Honestly, you spent too much time on this. I would have performed a backup and installed a new system then migrated.
You only have to install to the same version to make it all work.
-
I mean that screen shows it is Ubuntu 14.04 FFS
-
@JaredBusch said in Ubuntu Boot Issues:
Honestly, you spent too much time on this. I would have performed a backup and installed a new system then migrated.
You only have to install to the same version to make it all work.
Really thinking that also. Tired of being jerked around on something so ' simple and easy'. When it works it is...
sigh
-
@gjacobse said in Ubuntu Boot Issues:
@JaredBusch said in Ubuntu Boot Issues:
Honestly, you spent too much time on this. I would have performed a backup and installed a new system then migrated.
You only have to install to the same version to make it all work.
Really thinking that also. Tired of being jerked around on something so ' simple and easy'. When it works it is...
sigh
What version is the controller itself?
-
@JaredBusch said in Ubuntu Boot Issues:
@gjacobse said in Ubuntu Boot Issues:
@JaredBusch said in Ubuntu Boot Issues:
Honestly, you spent too much time on this. I would have performed a backup and installed a new system then migrated.
You only have to install to the same version to make it all work.
Really thinking that also. Tired of being jerked around on something so ' simple and easy'. When it works it is...
sigh
What version is the controller itself?
Currently 4.x - I don't recall right off, and don't directly feel like signing into it. New VM created, just need to get an ISO mounted to start the install. But as it's not critical - Monday task.....
-
@gjacobse said in Ubuntu Boot Issues:
@JaredBusch said in Ubuntu Boot Issues:
@gjacobse said in Ubuntu Boot Issues:
@JaredBusch said in Ubuntu Boot Issues:
Honestly, you spent too much time on this. I would have performed a backup and installed a new system then migrated.
You only have to install to the same version to make it all work.
Really thinking that also. Tired of being jerked around on something so ' simple and easy'. When it works it is...
sigh
What version is the controller itself?
Currently 4.x - I don't recall right off, and don't directly feel like signing into it. New VM created, just need to get an ISO mounted to start the install. But as it's not critical - Monday task.....
All this means is that you need to install the UniFi 4.x on the new system first, not the 5.x branch.
Then once you see everything reporting in, you can change to the UniFi 5 line.