BRRABill's Field Report With Linux
-
df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/xvda1 236M 225M 0 100% /boot
-
This is what my Ubuntu 16.04.1 install gave me..
scott@scott-rog:~$ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 120G 20G 101G 16% /
-
@scottalanmiller said in BRRABill's Field Report With Linux:
This is what my Ubuntu 16.04.1 install gave me..
scott@scott-rog:~$ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 120G 20G 101G 16% /
WTH.
Let me run through a fresh install again and see what it does...
-
Here is a fresh Mint 18 install on the Scale and what it chose to do. It's Ubuntu 16.04 under the hood.
-
I was curious about my CentOS VM running production owncloud. -
CentOS 7 here
[root@omega ~]# df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/md126 488M 133M 321M 30% /boot [root@omega ~]#
-
@tiagom how do you get the pretty colors?
-
@alex.olynyk said in BRRABill's Field Report With Linux:
@tiagom how do you get the pretty colors?
He posted text, not a screen shot. MangoLassi added the colours.
-
This post is deleted! -
Yup, you add 4 spaces in front of what whatever you want.
like so
-
So it seems like it likes to undercut the boot partition?
@scottalanmiller did you manually set yours?
-
@BRRABill said in BRRABill's Field Report With Linux:
So it seems like it likes to undercut the boot partition?
@scottalanmiller did you manually set yours?
Yes, but not like it is now, so it didn't accept my manual changed and modified itself to that.
-
@BRRABill said in BRRABill's Field Report With Linux:
So it seems like it likes to undercut the boot partition?
Just on yours, we are all seeing larger sizes of around 500MB.
-
@scottalanmiller said in BRRABill's Field Report With Linux:
@BRRABill said in BRRABill's Field Report With Linux:
So it seems like it likes to undercut the boot partition?
@scottalanmiller did you manually set yours?
Yes, but not like it is now, so it didn't accept my manual changed and modified itself to that.
Seems like (from the Google) I can delete old packages and whatnot.
-
Yours is about 50% smaller then the others posted.
Maybe consider extending it?
-
I've run into this on two of the last 3 systems I've tried to upgrade... I just remove all but the most recent kernel files, and then run the upgrade again.
Ubuntu 15.10 at initial Install
Filesystem Size Used Avail Use% Mounted on /dev/vda1 236M 111M 113M 50% /boot
Ubuntu 14.04 at initial install
Filesystem Size Used Avail Use% Mounted on /dev/sda1 134M 72M 53M 58% /boot
KVM Server on Ubuntu 15.10: No separate /boot partition (root FS is ext4)
OpenSuSE Tumbleweed: No separate /boot partition (root FS is btrfs)
-
@dafyre said in BRRABill's Field Report With Linux:
I've run into this on two of the last 3 systems I've tried to upgrade... I just remove all but the most recent kernel files, and then run the upgrade again.
That's what I am doing, though only the absolute oldest, as the Google said not remove too many recent ones in case anything depends on them.
But, you are saying it's safe to delete everything except the one running? (Obviously.)
-
I've run into this multiple times in the past with Ubuntu. For some reason old kernel images aren't removed when space is running low. To check your current image use
uname -r
. Then you can uninstall the older images. -
@stacksofplates said in BRRABill's Field Report With Linux:
I've run into this multiple times in the past with Ubuntu. For some reason old kernel images aren't removed when space is running low. To check your current image use
uname -r
. Then you can uninstall the older images.And I can delete every kernel image I am not using?
-
@BRRABill said in BRRABill's Field Report With Linux:
@stacksofplates said in BRRABill's Field Report With Linux:
I've run into this multiple times in the past with Ubuntu. For some reason old kernel images aren't removed when space is running low. To check your current image use
uname -r
. Then you can uninstall the older images.And I can delete every kernel image I am not using?
I ask because I did an "autopurge" and it left two of them.