Re: [PLUG] Running out of disk space?

[Christopher Barry via plug <plug@lists.phillylinux.org>]

On Wed, 15 Dec 2021 15:00:20 -0800
Charles Hathaway via plug <plug@lists.phillylinux.org> wrote:

>Maybe try booting from an old kernel and rerunning the update?
>
>I think I've seen this issue in the past when my boot partition was
>full; I cleaned it up a bit, then updated/reinstalled the "Linux"
>package and it started working again.
>
>Charles
>
>On Wed, Dec 15, 2021, 14:59 Rich Mingin (PLUG) via plug <
>plug@lists.phillylinux.org> wrote:  
>
>> I would mount the file systems from another Linux install on that
>> machine. Since most people don’t keep a sidecar/life raft install
>> like I do, I’ll assume you don’t have one. A live CD/live USB is an
>> easy fix. I like Ubuntu for that. They reliably give you a working
>> gui and it’s not hard to mount, diagnose and fix.
>>
>>
>> On Wed, Dec 15, 2021 at 17:56 H Mottaleb via plug <  
>> plug@lists.phillylinux.org> wrote:  
>>  
>>> How do I get more information on what’s causing the problem? I have
>>> tried Alt, Ctl and F2 as stated on Google search but my system
>>> doesn’t do anything. It just stuck at that message.
>>>
>>> Sent from my iPad
>>>  
>>> > On Dec 15, 2021, at 5:46 PM, Rich Freeman via plug <
>>> plug@lists.phillylinux.org> wrote:
>>> >
>>> > On Wed, Dec 15, 2021 at 5:27 PM H Mottaleb via plug
>>> > <plug@lists.phillylinux.org> wrote:  
>>> >>
>>> >> I decided to restart my computer after running a few updates on
>>> >> the OS  
>>> and Geth but now it’s stuck at :  /dev/sda2: clean, 342386/31227904
>>> files, 118762585/124895488 blocks.  
>>> >>
>>> >> I’m not sure what this means.
>>> >>  
>>> >
>>> > I'm pretty sure that message means that nothing is wrong with
>>> > mounting that drive - it is a success message.
>>> >
>>> > It is stuck at whatever comes next most likely, and since whatever
>>> > comes next didn't print any output you'd need to dig through the
>>> > startup scripts/etc to figure out what it is, or otherwise get
>>> > access to a shell to see what is going on while the computer is
>>> > "stuck." With only that line it is hard to tell what point you're
>>> > at, and of course various distros do things differently.
>>> >
>>> > --
>>> > Rich  

Once you're booting again:

In your preferred search engine, search for:
 'Linux grub <your-distro> configure kernels to keep'

Depending on distribution, you'll edit that distro-specific
configuration file to tell it how many older kernels to keep around.
For example, for Fedora/RedHat-based distros, I think it is in
/etc/dnf/dnf.conf or similar.

Realistically, for most people, just keeping the last good one is
fine. It's just a fallback in case you hork the one that's set to
default. Saving only the last one as a backup will likely not fill your
/boot partition up again as you keep moving along upgrading. Plus, you
can always boot a live CD or USB image to fix things if something goes
south.


___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug