Ubuntu Boot Issues
-
@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-upgradeswas set toPrompt=ltsI changed it to
Prompt=normaland 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 foundugh - 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 -dIt 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 -dIt 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. -
New VM Created and running. Updating normally:
Last login: Mon Feb 13 09:56:04 2017 ntg@UBNT-17:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 219M 0 219M 0% /dev tmpfs 48M 2.2M 46M 5% /run /dev/mapper/SSI--UniFi--17--vg-root 29G 1.4G 26G 6% / tmpfs 240M 0 240M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 240M 0 240M 0% /sys/fs/cgroup /dev/sda1 472M 61M 387M 14% /boot tmpfs 48M 0 48M 0% /run/user/1000 -
Ah the things we learn... the hard way.
/boot maxed out again as I had not been monitoring it. But - at least it was documented here so that I could come back and learn from my previous mistakes and move forward.
