[sf-lug] /boot partition was too small
Bobbie Sellers
bliss-sf4ever at dslextreme.com
Fri Jun 21 08:48:32 PDT 2019
On 6/21/19 8:25 AM, Michael Paoli wrote:
>> From: "Bobbie Sellers" <bliss-sf4ever at dslextreme.com>
>> Subject: [sf-lug] SF-LUG meeting notes for Monday June 17, 2019
>> Date: Thu, 20 Jun 2019 21:18:30 -0700
>
>> Then John S. came in and was having a problem that
>> was simple but not so simple of solution for someone
>> as unskilled as me. He was having problems installing
>> updates. At one point in a test we learned that the
>> /boot partition was too small and we spent a lot of time
>> working on that and did not achieve a reliable result.
>> I was very unhappy about that last.
>
> Hmmm, I'm curious, how small was it, and what distro, and was it
> appropriately cleaned of unneeded cruft?
>
> $ echo $(lsb_release -d; uname -m); df -h /boot
> Description: Debian GNU/Linux 9.9 (stretch) x86_64
> Filesystem Size Used Avail Use% Mounted on
> /dev/md1 228M 51M 165M 24% /boot
> $ ssh -anx -4 balug-sf-lug-v2.balug.org. 'echo $(lsb_release -d; uname
> -m); df -h /boot'
> Description: Debian GNU/Linux 9.9 (stretch) x86_64
> Filesystem Size Used Avail Use% Mounted on
> /dev/vda1 244M 37M 197M 16% /boot
> $
>
it was reported by df as being a total of 30 MB. No attempt was made
to clean it. Why it was setup so small I have no idea at the present.
The distribution was of course PCLinuxOS64 KDE5 2019.05.
As I mentioned I was already very tired and that led me to attempt
to do unspeakable things to the disk and its space distribution. The only
reason to remember the things done is so that I do not do that
again.
bliss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/sf-lug/attachments/20190621/3b792727/attachment.html>
More information about the sf-lug
mailing list