Upgrading to new kernel without space

New to Debian (Or Linux in general)? Ask your questions here!

Re: Upgrading to new kernel without space

Postby dbip » 2020-06-24 13:12

arid wrote:Followed a tutorial when I did it 9 years ago and it worked so far in fact, which size would you recommend me then?

So you think, in the magical world of computers, 9 years is an irrelevant time frame?


No, I think nothing on that because that has nothing to do with my question in the forum. I simply have no opinion on that.

This 9 years also suggests it's time to upgrade your computer.


Where did I say I haven't upgraded my computer? What does it have to do with the problem I have?

Wipe it and divide it up into sensible sizes.

Of course if you truly want the latest and greatest on your new computer, sid is your dream installation with a squeaky new 5.8 kernel. :mrgreen:


Thank you.


BR,

d.
dbip
 
Posts: 13
Joined: 2017-02-05 12:42

Re: Upgrading to new kernel without space

Postby dbip » 2020-06-24 13:24

CwF wrote:Let's not get ahead of ourselves here, as p.H. pointed to, ONLY the result images for the system need to be there, NOT the whole downloaded deb file. Otherwise I to would be out of space, instead of 2/3 free with my buster kernel in 255MiB. It takes 54MB and is a 270MB DL, yet lives...the one I posted earlier is a 23MB image, tidier yet still from a much larger download..

Maybe the OP should post the contents of / and /boot so we can see the 2-3 other kernels still in there.


I have no other kernels:

Code: Select all
dpkg --list | grep linux-image
ii  linux-image-3.16.0-4-586                  3.16.7-ckt11-1                              i386         Linux 3.16 for older PCs


Code: Select all
/boot# ls
total 20672
-rw-r--r-- 1 root root   162366 May 26  2015 config-3.16.0-4-586
drwxr-xr-x 5 root root     8192 Jun 14 15:44 grub
-rw-r--r-- 1 root root 16102112 Jun 14 23:08 initrd.img-3.16.0-4-586
-rw-r--r-- 1 root root  1986048 May 26  2015 System.map-3.16.0-4-586
-rw-r--r-- 1 root root  2820336 May 26  2015 vmlinuz-3.16.0-4-586


The size of that I have in /dev/sda1 315M 239M 60M 80% / is, sorted by size:

Code: Select all
177000  lib
29424   boot
10165   bin
7075    etc
6586    root
dbip
 
Posts: 13
Joined: 2017-02-05 12:42

Re: Upgrading to new kernel without space

Postby CwF » 2020-06-24 13:31

I didn't think /lib could be in there, but it is...that's why. My /lib 's are usually bigger, this is a problem.
CwF
 
Posts: 691
Joined: 2018-06-20 15:16

Re: Upgrading to new kernel without space

Postby dbip » 2020-06-24 13:40

p.H wrote:
dbip wrote:With "315MiB for the entire root partition" you mean such small space?

Yes. One 4.9 kernel requires 140 MiB for itself and 20 to 60 MB for its initramfs.
A kernel update requires as much available free space. It means that you need at least 140*2+20 = 300 MiB for the kernel alone. This leaves only 15 MiB for the rest of / (including /etc and /lib). I'm afrait it won't work.

Head_on_a_Stick wrote:I suppose you could clear some space for a new partition and mount it under /lib

Don't do that. /lib is not supposed to be separated, it is supposed to be available before mounting any filesystem other than / and /usr.
However /lib* may be a symlink pointing into /usr which is mounted at early boot by the initramfs.


This is the size of the top directories in that partition:

Code: Select all
177000  lib
29424   boot
10165   bin
7075    etc
6586    root


What would you suggest? From what I understand lib can't be moved (only mapped), would you suggest doing that?

Thanks for your help :-)


BR,

d.
dbip
 
Posts: 13
Joined: 2017-02-05 12:42

Re: Upgrading to new kernel without space

Postby dbip » 2020-06-24 13:46

CwF wrote:I didn't think /lib could be in there, but it is...that's why. My /lib 's are usually bigger, this is a problem.


How would you suggest to proceed in my case?

Thanks :-)


BR,

d.
dbip
 
Posts: 13
Joined: 2017-02-05 12:42

Re: Upgrading to new kernel without space

Postby p.H » 2020-06-24 14:09

dbip wrote:From what I understand lib can't be moved (only mapped)

What do you mean by "mapped" ?
Since Buster, /lib can be symlinked to /usr/lib as part of /usr merge. Merging /lib into /usr/lib may cause file conflicts in previous versions.
However I guess you could symlink /lib/modules to /usr/lib/modules as a temporary workaround.
p.H
 
Posts: 1365
Joined: 2017-09-17 07:12

Re: Upgrading to new kernel without space

Postby CwF » 2020-06-24 14:18

I have no experienced advice for this. A simple answer is to expand / or relocate /lib. That path is not something I've ever needed to do. With my resources I'd image it and try some solutions virtually. I think I'd first try and steal some /usr space for root. I'd use another machine to manipulate the disk. Doing in within the OS, well I'd wait for some other answers. I stopped using partitions within a device space long ago, in the rare case a device/partition needs more space, I do what I said on a second machine, image it to a bigger disk and expand it to fill, done.

If your sda1 and sda5 are contiguous then that's the first try - reduce sda5 and give it to sda1. That would be straight forward for Gparted, maybe live but I would do it on another machine.
CwF
 
Posts: 691
Joined: 2018-06-20 15:16

Re: Upgrading to new kernel without space

Postby CwF » 2020-06-24 14:36

Ya know, it is remotely possible to remove the working kernel, upgrade/install a new one in a single session. I want to say I tried that many years back and can't really remember the outcome. But I do remember for sure that removing the working kernel will prompt a few times if you're sure and it will continue to run the current session. If anything at all happens before the new one is installed you're hosed...
CwF
 
Posts: 691
Joined: 2018-06-20 15:16

Previous

Return to Beginners Questions

Who is online

Users browsing this forum: No registered users and 13 guests

fashionable