Re: [gentoo-user] Re: Boot has no space left.
Wols Lists wrote: > On 01/07/2022 00:21, Dale wrote: >> When I upgrade to a new kernel, I run for a month or so and then >> manually clean out /boot, that would include kernel, init thingy, >> System.map and config files. >> >> Seeing this reminds me it might be a good time to look into updating, >> even tho I might not reboot for a while yet. > > When I update, I wait until I'm happy the new one seems okay, and then > I just leave the most recent one and the one before. > > That said, I need to upgrade, and I need to see if my random hangs are > fixed (there's apparently a bug in the Ryzen 3000, and I'm guessing > that's what I'm hitting). > > Cheers, > Wol > > After my previous reply, I updated to a newer kernel. It's in /boot but it may be months before I reboot. Anyway, I currently have four kernels in /boot. My current running kernel and two backup kernels plus the new untested one. Whenever I get around to rebooting and the new kernel works fine, I'll remove the oldest one including sources etc. I try to keep at least two backup kernels. One reason I do that, the init thingy. I admit dracut is working well for me but given the history I have with those thingys, I want extra protection. The odds of three boot options going bad are pretty slim and if it did happen, I likely have a serious hard drive problem anyway, file system at the very least. Either way, I have a lot to worry about. Maybe one of the suggestions mentioned here will help the OP. It seems he is letting the updater do the install or something and the kernel is a fast moving target. One has to have some way, automated or manual, to clean up the unneeded bits. I doubt most anyone makes their /boot to large anyway. Usually 300 or 400MBs is enough. Dale :-) :-)
Re: [gentoo-user] Re: Boot has no space left.
On 01/07/2022 00:21, Dale wrote: When I upgrade to a new kernel, I run for a month or so and then manually clean out /boot, that would include kernel, init thingy, System.map and config files. Seeing this reminds me it might be a good time to look into updating, even tho I might not reboot for a while yet. When I update, I wait until I'm happy the new one seems okay, and then I just leave the most recent one and the one before. That said, I need to upgrade, and I need to see if my random hangs are fixed (there's apparently a bug in the Ryzen 3000, and I'm guessing that's what I'm hitting). Cheers, Wol
Re: [gentoo-user] Re: Boot has no space left.
William Kenworthy wrote: > > and don't forget to run "uname -a" to get your currently running > kernel version and make sure you don't delete that! > > "IF" "uname -a" isn't the latest version you have in /boot, some more > investigation as to why will be needed. > > BillK > > Just to add another method. I have uprecords installed here. It lists the kernels and their uptime. I keep the last two with reasonably high uptimes with fairly recent version and the most recent kernel. I don't upgrade automatically so I control what and when I update. Of course, I also have long uptimes as well. My thinking on this. I want kernels that are known to be stable that I can use as a backup boot option but I also want newer kernels that have fixes etc in them. By keeping a couple with long uptimes, I get stable kernels. By also picking a recent kernel version, I get a kernel that I can boot into to see if it is stable. Over time, the versions get higher on both parts. When I do my checks, I look for kernels with at least 30 days or more of uptime. Generally, if a kernel can run that length of time, it is pretty stable. That said, I have some with many months of uptime. When I upgrade to a new kernel, I run for a month or so and then manually clean out /boot, that would include kernel, init thingy, System.map and config files. Seeing this reminds me it might be a good time to look into updating, even tho I might not reboot for a while yet. Just a thought. Dale :-) :-)
Re: [gentoo-user] Re: Boot has no space left.
and don't forget to run "uname -a" to get your currently running kernel version and make sure you don't delete that! "IF" "uname -a" isn't the latest version you have in /boot, some more investigation as to why will be needed. BillK On 1/7/22 04:29, Lee wrote: > The OP should read the section of the Gentoo manual on kernel install > to learn what files are installed where. Yea, but just rm the kernels > and initramfs's from /boot and you're golden. FWIW, I usually only > upgrade my kernel when it's a major revision. > > On Thu, Jun 30, 2022 at 12:39 PM Wols Lists > wrote: > > On 30/06/2022 19:23, Michael wrote: > > On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote: > >> Hello, > >> > >> I still have the same problem, but the command worked fine. > > The command "emerge -a --depclean" will only remove uninstall > the kernel > > packages, but will not remove files from/usr/src/, or old kernel > images and > > files from/boot/. > > As far as I'm aware, depclean only installs files it installed, so it > leaves quite a lot of garbage lying around from kernels, including > the > /usr/src/kernel-xx-xx-xx directory and various files involved in > making > your kernel, that you've modified. > > Cheers, > Wol > > > > -- > Lee >
Re: [gentoo-user] Re: Boot has no space left.
The OP should read the section of the Gentoo manual on kernel install to learn what files are installed where. Yea, but just rm the kernels and initramfs's from /boot and you're golden. FWIW, I usually only upgrade my kernel when it's a major revision. On Thu, Jun 30, 2022 at 12:39 PM Wols Lists wrote: > On 30/06/2022 19:23, Michael wrote: > > On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote: > >> Hello, > >> > >> I still have the same problem, but the command worked fine. > > The command "emerge -a --depclean" will only remove uninstall the kernel > > packages, but will not remove files from/usr/src/, or old kernel images > and > > files from/boot/. > > As far as I'm aware, depclean only installs files it installed, so it > leaves quite a lot of garbage lying around from kernels, including the > /usr/src/kernel-xx-xx-xx directory and various files involved in making > your kernel, that you've modified. > > Cheers, > Wol > > -- Lee
Re: [gentoo-user] Re: Boot has no space left.
On 30/06/2022 19:23, Michael wrote: On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote: Hello, I still have the same problem, but the command worked fine. The command "emerge -a --depclean" will only remove uninstall the kernel packages, but will not remove files from/usr/src/, or old kernel images and files from/boot/. As far as I'm aware, depclean only installs files it installed, so it leaves quite a lot of garbage lying around from kernels, including the /usr/src/kernel-xx-xx-xx directory and various files involved in making your kernel, that you've modified. Cheers, Wol
Re: [gentoo-user] Re: Boot has no space left.
On Thursday, 30 June 2022 19:15:33 BST Guillermo wrote: > Hello, > > I still have the same problem, but the command worked fine. The command "emerge -a --depclean" will only remove uninstall the kernel packages, but will not remove files from /usr/src/, or old kernel images and files from /boot/. Your /boot partition is full with old kernels you probably no longer use or need. You have to remove them manually as part of your regular maintenance of your installation, or you can install and use 'app-admin/eclean-kernel' as mentioned in the previous thread, to partly automate the cleanup process of stale kernels. Then update your GRUB to refresh the boot menu. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Re: Boot has no space left.
Hello, I still have the same problem, but the command worked fine. On 30/06/2022 19:24, Nikos Chantziaras wrote: On 30/06/2022 20:11, Guillermo wrote: [screenshot] Doesn't "emerge -a --depclean" remove all these old kernels?
