similar to: Centos 7 Boot Partition

>> What size is recommended for the /boot partition? After doing a fresh >> install and lengthy backup restore I realized I only made it 200M. Is >> this going to be a problem? > > Mine was about 500 MB and I removed some kernels because I got a warning the > partition was getting full. > > With only two kernels installed, 182 MB are used. I would suggest 1 GB

I have a CentOS 6 machine that was initially installed as CentOS 6.4 in May of 2013. It's /boot filesystem is 200M which, IIRC, was the default /boot size at the time. The most recent kernel update (2.6.32-573.18.1.el6) fails because of lack of space in /boot. The workaround is edit /etc/yum.conf, reduce installonly_limit from 5 to something lower (I used 3), remove the oldest kernel via

First off - let me say I am not an administrator.?? I need to know?if there is an easy way to increase my /boot partition.? When I installed CentOS 6 after running 5, it was my oversight not to increase the /boot size.? it's too small and I can't do yum updates. if it's not easy to actually increase it, is it safe to take a chunk in my root filesystem (like /new.boot or something) and

On 11/15/2016 03:58 PM, Matt wrote: > What size is recommended for the /boot partition? After doing a fresh > install and lengthy backup restore I realized I only made it 200M. Is > this going to be a problem? > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > Mine was about

I've recently had this problem on two C7 systems, wherein when doing "yum update", I get a warning about /boot being low on space. both systems were installed using the partition size recommended by Anaconda, right now "df -h" shows /boot as 494M, with 79M free. I don't store unrelated crap on /boot, I assume that yum and/or grub will manage it for me. So, why, after

Default boot volume on Fedora is 500M, with a kernel installonly_limit of 3. So far this seems sufficient, even accounting for the "rescue kernel" (which is really a nohostonly initramfs, which is quite a bit larger than the standard hostonly initramfs used for numbered kernels).

I have 4 kernels in /boot, leaving on 20MB which is not enough for the next one. I had installonly_limit= set at 5, as there were some kernel problems.? After I got the error that there was not enough room for another kernel, I set installonly_limit= to 3 and did the update with --exclude=kernel* That worked to update everything else, but not remove the oldest kernel. How can I remove the

On Wed, 16 Nov 2016, Matt wrote: > Can I just change yum.conf with the setting installonly_limit=2 to > limit kernels installed too two? I really wouldn't. You can scrape by with that if you also make sure you don't have dracut-config-rescue installed, but you can find yourself struggling even with that, and so have to micromanage even further. Upgrade a kmod, watch /boot fill

Hi ext3-gurus, I was doing some testing of our 100 Mbit ethernet at work, and found a weird problem which appears to be ext3 releated as far as I can tell. The test is very simple. I use ncftp to connect to another machine running vsftpd and download a very large file over the network. The network is switched, and I get 8-10 MB/s transfers usually. Now, if I download to /dev/null ("get

On 1/8/19 5:30 PM, mark wrote: > Robert Moskowitz wrote: >> I have 4 kernels in /boot, leaving on 20MB which is not enough for the >> next one. >> >> I had installonly_limit= set at 5, as there were some kernel problems. >> After I got the error that there was not enough room for another kernel, >> I set installonly_limit= to 3 and did the update with

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

Hi, Can someone help explain why sometimes ext3 failed to recover from a sudden loss of power (ie. has to run lengthy fsck on paritions)? This happened to Redhat 7.2, 7.3 with latest stable kernel. Simon Gao

On Tue, 2017-10-10 at 13:55 +0000, KM wrote: > First off - let me say I am not an administrator. I need to know if > there is an easy way to increase my /boot partition. When I > installed CentOS 6 after running 5, it was my oversight not to > increase the /boot size. it's too small and I can't do yum updates. How big is it? > if it's not easy to actually increase

Hi, I just replaced Slackware64 14.1 running on my office's HP Proliant Microserver with a fresh installation of CentOS 7. The server has 4 x 250 GB disks. Every disk is configured like this : * 200 MB /dev/sdX1 for /boot * 4 GB /dev/sdX2 for swap * 248 GB /dev/sdX3 for / There are supposed to be no spare devices. /boot and swap are all supposed to be assembled in RAID level 1 across

Hi, I have a specific needs that requires yum do not to uninstall old version when install new one. For example, I found that yum install kernel will install new kernel, and old kernel will remained. But yum install <something-else> will uninstall old version after install new one, how to disable it? Thanks.

Howdy! Could somebody point me to some good introductory readings about data mining and descriptive data analysis? I'm a psychologist and a couple of times I realized that some things just don't appear in psychological literature, e.g. I've never seen a box plot anywhere in psych journals so I'm not familiar with them. The R help function is great when it comes to explaining

Devin Reade wrote: > I have a CentOS 6 machine that was initially installed as CentOS 6.4 > in May of 2013. It's /boot filesystem is 200M which, IIRC, was the > default /boot size at the time. > > The most recent kernel update (2.6.32-573.18.1.el6) fails because of > lack of space in /boot. The workaround is edit /etc/yum.conf, reduce > installonly_limit from 5 to

After a brief stint offlist (thanks Bradley), I'm closer to getting SMB/LDAP working but now am encountering something very odd, which he suggested I bring back to the list for "further evaluation". :-) > $ smbclient //TESTBOX/testshare -U dballing > added interface ip=10.15.49.142 bcast=10.15.49.255 nmask=255.255.255.0 > Password: > session setup failed:

Hi Last week I had a lengthy thread in which someone indicated the my SIL card is a FRAID (don't know if F stands for the F word or Fake, though it doesn't really matter). I want to replace the controller with a controller that Linux will see the RAID1 group as a single HD and not multiple HDs as it happens with the SIL controller. Recommendations anyone? -- TIA Paolo --------------

In order to keep only 3 kernel images on a CentOS 7 I edited /etc/yum.conf and I put installonly_limit=3 This parameter works for standard kernel images, but does not work for rescue images: $ ls -al /boot/vmlinuz* -rwxr-xr-x 1 root root 5027376 May 13 20:46 /boot/vmlinuz-0-rescue-2554e2ffad84452bb07401bed0a61089 -rwxr-xr-x 1 root root 3084288 Jun 27 06:42