Re: [CentOS] /boot partition too small

[Sorin Srbu]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of KM
> Sent: den 10 oktober 2017 21:06
> To: centos@centos.org; Phil Perry 
> Subject: Re: [CentOS] /boot partition too small
>
>  Do i need to do something special or is it as easy as:
> - save the contents of the current /boot - umount /boot and change the
> /etc/fstab so it doesn't mount again-  create a boot directory that is in
> the root  filesystem- copy the contents back
> I realize the physical/current /boot will be a waste of space but it's not 
> that
> big so it's fine.
> I thought i probably have to make configuration changes of some sort.
> Again I apologize in advance since I am not really good at this 
> (partition/file
> system).  I have tried searching but am never sure exactly what I should
> try.   I need to find the "for dummies" version(s) of this. Thanks again.
> KM

Assuming you have backups, if something should go south, you might want to try 
out the Gparted boot-iso.

Using Gparted you should be able to shrink some of the other partitions, and 
then grow the boot partition.

More info on:
https://gparted.org/index.php

If you have another non-critical computer to test using Gparted on, do that 
first before doing it "for real".

Hope this helps.
--
//Sorin
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[Sorin Srbu]

> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of KM
> Sent: den 10 oktober 2017 15:55
> To: CentOS Mailing List 
> Subject: [CentOS] /boot partition too small
>
> 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 just mount it as /boot from
> now on so it uses the space or is that not a good idea?  I am sure I could 
> easily
> copy the rpms/kernel stuff over to it and then unmounts the real /boot and
> mount this new area as /boot.
> Can you administrators let me know what you think of all this?   Thanks in
> advance.

Been there done that.

A simple solution is to edit /etc/yum.conf and change the line

installonly_limit=5

to e.g.

installonly_limit=3

and see if that's enough with the existing boot partition size.

A "yum update" should delete the two oldest kernel images.


--
//Sorin
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[John R Pierce]

On 10/10/2017 6:50 PM, John R Pierce wrote:
Your root filesystem is in an LVM volume. CentOS 6 is still using 
GRUB legacy, which does not support /boot in LVM. 



says up there, /boot is /dev/sda1, this is almost exactly the config 
of my C6 servers. 



never mind, I realized after I sent this, you were talking about him 
MOVING his /boot to /



--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[John R Pierce]

On 10/10/2017 6:20 PM, Robert Nichols wrote:

Filesystem Size  Used Avail Use% Mounted on
/dev/mapper/vg_bldsrv-lv_root
    50G   26G   22G  55% /
tmpfs 9.0G  156K  9.0G   1% /dev/shm
/dev/sda1  96M   33M   59M  36% /boot
/dev/mapper/vg_bldsrv-lv_home
   861G  371G  447G  46% /home


Your root filesystem is in an LVM volume. CentOS 6 is still using GRUB 
legacy, which does not support /boot in LVM. 



says up there, /boot is /dev/sda1, this is almost exactly the config of 
my C6 servers.



--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[Robert Nichols]

On 10/10/2017 09:53 AM, KM wrote:

  Thanks for all of the input, not really sure what if anything I will do.  i 
was hoping it would be easy and i could just create a /boot in root, and copy 
the actual boot contents to it and use it.   wishful thinking i guess.  just to 
give a complete picture here is the current partitioning on the serverin 
case anyone wants to say anymore.  Thanks in advance.
Filesystem    Size  Used Avail Use% Mounted on
/dev/mapper/vg_bldsrv-lv_root
    50G   26G   22G  55% /
tmpfs 9.0G  156K  9.0G   1% /dev/shm
/dev/sda1  96M   33M   59M  36% /boot
/dev/mapper/vg_bldsrv-lv_home
   861G  371G  447G  46% /home


Your root filesystem is in an LVM volume. CentOS 6 is still using GRUB legacy, 
which does not support /boot in LVM.

For you, there really is no way around the messy and delicate process of 
shrinking and relocating a filesystem and the LVM volumes to make space for a 
larger /boot partition. Frankly, I would hesitate to do that in place on my own 
system, and I have quite a bit of experience with doing unspeakable things with 
LVM volumes. You really need to do that resizing in the context of moving 
everything to another disk.

If it's a server that you don't want to take down for the time it takes for 
that procedure, you can do amazing things with pvmove while your system 
continues to run, but you still need another disk to hold those volumes 
temporarily.

--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[m . roth]

KM wrote:
>  Thanks for all of the input, not really sure what if anything I will do. 
> i was hoping it would be easy and i could just create a /boot in root,
> and copy the actual boot contents to it and use it.   wishful thinking i
> guess.  just to give a complete picture here is the current partitioning
> on the serverin case anyone wants to say anymore.  Thanks in advance.
> Filesystem    Size  Used Avail Use% Mounted on
> /dev/mapper/vg_bldsrv-lv_root
>    50G   26G   22G  55% /
> tmpfs 9.0G  156K  9.0G   1% /dev/shm
> /dev/sda1  96M   33M   59M  36% /boot
> /dev/mapper/vg_bldsrv-lv_home
>   861G  371G  447G  46% /home
>
> Most of this is like speaking another language to me anyway.  I'll
> consider it all.

What I would recommend: go out and buy a "small" new h/d, say, 150GB or
250GB. Also get an adapter for it (let me note that I actually bought, a
year or two ago, a hot-swap drive bay that fits in a std. tower case...).
Then partition that (we've been using 1G for /boot for years), mount it on
/mnt, mount newdrive/boot /mnt/newdrive/boot, and rsync -HPavx /.
/mnt/newdrive, and rsync -HPavx /boot /mnt/newdrive/boot

Then grub-install /dev/newdrive, and swap drives.

mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] kernel-plus PXE virt-install with Xen?

[Johnny Hughes]

On 10/10/2017 01:46 PM, PJ Welsh wrote:
> I'm trying to figure out how to replace the vmlinuz and initrd.img from
> CentOS 7.4 with "fixed" kernel-plus versions in order create CentOS 7.4
> VM's. So far I'm stuck booting via 7.3 install, adding new kernel-plus
> and upgrading to 7.4. I've not found any complete Google answers and was
> looking for help making sure I choose the correct approach.
> 
> I've tried to build an initrd.img from a kernel-plus booting system via
> "mkinitrd -f -v /boot/initrd.img $(uname -r)", but the file size is less
> than half the one from CentOS 7.4 (17MB -vs- 47MB). I'm not even sure I
> can just replace those files yet either.
> 
> Any help going the correct path?

I have not had time to do this yet .. BUT .. you can edit the lorax
template to to use kernel-plus instead of kernel (and new repodata)..
then rerun lorax to get a bootable tree and boot.iso

You would then need a tree with the new kernel-plus* packages instead of
the kernel-* packages

This bug kind of explains the process:

https://bugs.centos.org/view.php?id=13763

(look for lorax in the bug)

I do want to create a process and tree somewhere for this (likely on
buildlogs.centos.org).  Sometime soon after I finish the i386 distro
release (hopefully that is this week .. next week for some kind of
bootable x86_64 Xen PV solution).

The good news is, the 7.5 RHEL kernel Source RPMs should have Kevin's
patch in it and it should work as released on Xen PV.





signature.asc
Description: OpenPGP digital signature
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] /boot partition too small

[Yves Bellefeuille]

KM  wrote:

> Do i need to do something special or is it as easy as:
> - save the contents of the current /boot - umount /boot and change
> the /etc/fstab so it doesn't mount again-  create a boot directory
> that is in the root filesystem- copy the contents back

You'll also have to reinstall Grub. The wiki has information on this.

-- 
Yves Bellefeuille



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum security update issue

[Johnny Hughes]

I have no idea how that script works (not maintained by CentOS Project)

.. BUT ..

If it does not also look at the CR announce list, it will miss those.
We do not double annonuce:

https://lists.centos.org/pipermail/centos-cr-announce/

(August 2017 and September 2017 were for the updates released into CR
for the 7.4.1708 cycle)

On 10/10/2017 08:19 AM, Thomas Roth wrote:
> Hi all,
> 
> I have used http://cefs.steve-meier.de/  plus
> https://github.com/vmfarms/generate_updateinfo to insert some
> security-information into my os-updates - mirror.
> 
> This seems to work, but only partially.
> 
> On my 7.4 test server,
>> yum --security -v check-update
> gives me dnsmasq, nss, nss-sysinit and nss-tools as the packages to
> install.
> 
> The nss-packages are all of "severity = Important"
> 
> But there are more of this type of packages, e.g. emacs. The
> centos-announce mails as well as the errata of Steve Meier as well as
> the generated updateinfo.xml all contain "CESA-2017:2771 Important
> CentOS 7 emacs Security Update"
> Just like the mentioned nss-packages, emacs is also labeled "severity =
> Important". But yum doesn't like it ;-(
> 
> 
> The output of
>> yum --security -v check-update
> tells me more, of course:
> 
> --> 1:emacs-24.3-20.el7_4.x86_64 from os-updates excluded (updateinfo)
> 
> Neither dnsmasq nor the nss-packages are listed, in particular not as
> excluded -?
> 
> 
> And at the end it says
> 
>> Nothing matches emacs.x86_64 1:24.3-20.el7_4 from update
> 
> 
> Btw, "yum info emacs" lists the installed and wanted emacs versions
> correctly.
> 
> 
> What did I miss?
> 
> Regards,
> Thomas
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> 




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[KM]

 Do i need to do something special or is it as easy as:
- save the contents of the current /boot - umount /boot and change the 
/etc/fstab so it doesn't mount again-  create a boot directory that is in the 
root  filesystem- copy the contents back
I realize the physical/current /boot will be a waste of space but it's not that 
big so it's fine.   
I thought i probably have to make configuration changes of some sort.
Again I apologize in advance since I am not really good at this (partition/file 
system).  I have tried searching but am never sure exactly what I should try.   
I need to find the "for dummies" version(s) of this. Thanks again.
KM

On ‎Tuesday‎, ‎October‎ ‎10‎, ‎2017‎ ‎02‎:‎44‎:‎12‎ ‎PM, Phil Perry 
 wrote:  
 
 On 10/10/17 15:27, John Hodrien wrote:
> On Tue, 10 Oct 2017, Pete Biggs wrote:
> 
>> No, you can't do that. /boot is special and needs to be a separate
>> partition.
> 
> Needs is a bit strong, as grub2 does support LVM.  It's not a supported
> configuration for Redhat.
> 
> I'm not a sure there's a lot to it beyond having the lvm module loaded in
> grub, but I've honestly not tried.
> 

Indeed, /boot does not need to be a separate partition. I have /boot 
within the root filesystem on my test boxes where I know I will need to 
install many / all kernels for testing / development purposes for the 
specific reason that I do not need to set a size for /boot and it can 
just consume whatever it needs from the rest of the filesystem.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
  
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[Alice Wonder]

On 10/10/2017 07:04 AM, Vanhorn, Mike wrote:

If there are many old kernels in there, you can probably remove the oldest 
one(s) to make room for newer ones.


This is what I do. When /boot hits about 80% I go through and remove old 
kernels I will never boot into anyway.


Usually that's at four kernels.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-virt] kernel-plus PXE virt-install with Xen?

[PJ Welsh]

I'm trying to figure out how to replace the vmlinuz and initrd.img from
CentOS 7.4 with "fixed" kernel-plus versions in order create CentOS 7.4
VM's. So far I'm stuck booting via 7.3 install, adding new kernel-plus and
upgrading to 7.4. I've not found any complete Google answers and was
looking for help making sure I choose the correct approach.

I've tried to build an initrd.img from a kernel-plus booting system via
"mkinitrd -f -v /boot/initrd.img $(uname -r)", but the file size is less
than half the one from CentOS 7.4 (17MB -vs- 47MB). I'm not even sure I can
just replace those files yet either.

Any help going the correct path?

Thanks
PJ
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] /boot partition too small

[Phil Perry]

On 10/10/17 15:27, John Hodrien wrote:

On Tue, 10 Oct 2017, Pete Biggs wrote:


No, you can't do that. /boot is special and needs to be a separate
partition.


Needs is a bit strong, as grub2 does support LVM.  It's not a supported
configuration for Redhat.

I'm not a sure there's a lot to it beyond having the lvm module loaded in
grub, but I've honestly not tried.



Indeed, /boot does not need to be a separate partition. I have /boot 
within the root filesystem on my test boxes where I know I will need to 
install many / all kernels for testing / development purposes for the 
specific reason that I do not need to set a size for /boot and it can 
just consume whatever it needs from the rest of the filesystem.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[Yves Bellefeuille]

KM  wrote:

>  if it's not easy to actually increase it,

It's possible to resize partitions. I use System Rescue CD,
http://www.system-rescue-cd.org/

-- 
Yves Bellefeuille



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Flame war police

[Valeri Galtsev]

On Tue, October 10, 2017 10:22 am, Mark Haney wrote:
> On 10/10/2017 11:03 AM, Andrew Holway wrote:
>> Hiya everyone,
>>
>> Is there a way to disable a thread that has degenerated into flaming?
>> The
>> recent "discussion" on /var/run descended into some quite nasty places
>> and
>> perhaps a lid should have been put on it. This seems to happen every few
>> weeks and is somewhat embarrassing when I'm trying to persuade people of
>> the "active and friendly Centos community"
>>
>> It was a shame that no one actually read past the belligerence his
>> original
>> post enough to come up with a solution. It was quite clearly a problem
>> with
>> third party packages not coming with SELinux policies.
> Also just as clearly, everyone on the list said this wasn't standard
> CentOS practice, the third party repo/packages OP used was not built
> properly and to either find a package that did, or compile from source. 
> At no point will anyone on this list try to fix a 'problem' by ignoring
> the 40+ years of UNIX design.  Liability aside, if someone doesn't like
> what the majority say on the list, that's their problem.  Trying to
> stick persistent data in /var/run isn't standard (or best) practice and,
> indeed, /var/run is literally designed to not be persistent.  Any sane
> admin wouldn't countenance that, and most of us are sane, and experienced.
>
> Let me ask, would you allow your kids to do something that was obviously
> dangerous?  This is the same thing.  We're here to guide those willing
> to learn the /best/ method of resolving problems. Some aren't willing to
> learn and refuse to believe the majority here know what we're talking
> about.  The true answer to OPs question wasn't what he wanted to hear
> and continued ad nauseum to insist that's what he wants to do. 
> Sometimes people just have to fail to learn.
>
> Most of us make a living in IT, and get paid to do things within the
> parameters of the systems we manage.  How hard is it to understand such
> a simple concept? What you insist on calling a flame war, was some of
> us, me included, trying to get people to understand that 1) OP is wrong
> trying to do it this way 2) that OPs package wasn't standard CentOS
> packaging and was dangerous to use on CentOS systems and 3) that there's
> no way any of us would offer a work around for something that will
> almost certainly result in lost data.
>
> OP appeared, to me at least,  to be quite immature in insisting going
> against how CentOS (and RHEL) is designed and would very likely have
> come back to the list raising hell over losing data and how it's our
> fault for his inability to listen to us. Don't you think that would have
> been a bigger blow to the 'active and friendly community' if we'd
> actually offered advice contrary to design/best practice?  Would you
> take advice from someone you know has given dangerous advice in the past?
>
> We have this discussion on every list I've ever been, or currently are
> on about every 6 months or so.  I do my best to contribute to the list
> as often as I can, but I can't help people when they are deadset on
> doing dangerous things.  Posts like his, and posts like yours make it
> harder for me to bother trying to help those unwilling to listen.  I
> don't take it from my children, and I certainly won't from adults who
> won't listen.
>

Thanks, Mark! Not only I agree with all you said, but these were the same
points that I was seeing in this whole thread. The OP gave me the same
feeling as I have when sometimes someone comes to me to fix their system,
and when I start doing what I see necessary starts direct me what I should
do next. Which brings these feelings: you already failed to fix it
yourself, that is why you came to get me do that, now step back and
observe how it is done...

Valeri

> --
> Mark Haney
> Network Engineer at NeoNova
> 919-460-3330 option 1
> mark.ha...@neonova.net
> www.neonova.net
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Flame war police

[Leon Fauster]

Am 10.10.2017 um 17:03 schrieb Andrew Holway :
> Is there a way to disable a thread that has degenerated into flaming? The
> recent "discussion" on /var/run descended into some quite nasty places and
> perhaps a lid should have been put on it. This seems to happen every few
> weeks and is somewhat embarrassing when I'm trying to persuade people of
> the "active and friendly Centos community"


A community has always at least "17%" of unpleasant behaviour - thats natural! 
The 
other part is very "active and friendly". Everything else is not realistic. :-) 
 


> It was a shame that no one actually read past the belligerence his original
> post enough to come up with a solution. It was quite clearly a problem with
> third party packages not coming with SELinux policies.


--
LF


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Flame war police

[Mark Haney]

On 10/10/2017 11:03 AM, Andrew Holway wrote:

Hiya everyone,

Is there a way to disable a thread that has degenerated into flaming? The
recent "discussion" on /var/run descended into some quite nasty places and
perhaps a lid should have been put on it. This seems to happen every few
weeks and is somewhat embarrassing when I'm trying to persuade people of
the "active and friendly Centos community"

It was a shame that no one actually read past the belligerence his original
post enough to come up with a solution. It was quite clearly a problem with
third party packages not coming with SELinux policies.
Also just as clearly, everyone on the list said this wasn't standard 
CentOS practice, the third party repo/packages OP used was not built 
properly and to either find a package that did, or compile from source.  
At no point will anyone on this list try to fix a 'problem' by ignoring 
the 40+ years of UNIX design.  Liability aside, if someone doesn't like 
what the majority say on the list, that's their problem.  Trying to 
stick persistent data in /var/run isn't standard (or best) practice and, 
indeed, /var/run is literally designed to not be persistent.  Any sane 
admin wouldn't countenance that, and most of us are sane, and experienced.


Let me ask, would you allow your kids to do something that was obviously 
dangerous?  This is the same thing.  We're here to guide those willing 
to learn the /best/ method of resolving problems. Some aren't willing to 
learn and refuse to believe the majority here know what we're talking 
about.  The true answer to OPs question wasn't what he wanted to hear 
and continued ad nauseum to insist that's what he wants to do.  
Sometimes people just have to fail to learn.


Most of us make a living in IT, and get paid to do things within the 
parameters of the systems we manage.  How hard is it to understand such 
a simple concept? What you insist on calling a flame war, was some of 
us, me included, trying to get people to understand that 1) OP is wrong 
trying to do it this way 2) that OPs package wasn't standard CentOS 
packaging and was dangerous to use on CentOS systems and 3) that there's 
no way any of us would offer a work around for something that will 
almost certainly result in lost data.


OP appeared, to me at least,  to be quite immature in insisting going 
against how CentOS (and RHEL) is designed and would very likely have 
come back to the list raising hell over losing data and how it's our 
fault for his inability to listen to us. Don't you think that would have 
been a bigger blow to the 'active and friendly community' if we'd 
actually offered advice contrary to design/best practice?  Would you 
take advice from someone you know has given dangerous advice in the past?


We have this discussion on every list I've ever been, or currently are 
on about every 6 months or so.  I do my best to contribute to the list 
as often as I can, but I can't help people when they are deadset on 
doing dangerous things.  Posts like his, and posts like yours make it 
harder for me to bother trying to help those unwilling to listen.  I 
don't take it from my children, and I certainly won't from adults who 
won't listen.


--
Mark Haney
Network Engineer at NeoNova
919-460-3330 option 1
mark.ha...@neonova.net
www.neonova.net

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Flame war police

[Giles Coochey]

On 10/10/2017 16:03, Andrew Holway wrote:

Hiya everyone,

Is there a way to disable a thread that has degenerated into flaming? The
recent "discussion" on /var/run descended into some quite nasty places and
perhaps a lid should have been put on it. This seems to happen every few
weeks and is somewhat embarrassing when I'm trying to persuade people of
the "active and friendly Centos community"
In Thunderbird, right click on a message in the thread, and click 
"Ignore Thread", for other mail user agents you can find a similar feature.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Flame war police

[Andrew Holway]

Hiya everyone,

Is there a way to disable a thread that has degenerated into flaming? The
recent "discussion" on /var/run descended into some quite nasty places and
perhaps a lid should have been put on it. This seems to happen every few
weeks and is somewhat embarrassing when I'm trying to persuade people of
the "active and friendly Centos community"

It was a shame that no one actually read past the belligerence his original
post enough to come up with a solution. It was quite clearly a problem with
third party packages not coming with SELinux policies.

Cheers,

Andrew
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[KM]

 Thanks for all of the input, not really sure what if anything I will do.  i 
was hoping it would be easy and i could just create a /boot in root, and copy 
the actual boot contents to it and use it.   wishful thinking i guess.  just to 
give a complete picture here is the current partitioning on the serverin 
case anyone wants to say anymore.  Thanks in advance. 
Filesystem    Size  Used Avail Use% Mounted on
/dev/mapper/vg_bldsrv-lv_root
   50G   26G   22G  55% /
tmpfs 9.0G  156K  9.0G   1% /dev/shm
/dev/sda1  96M   33M   59M  36% /boot
/dev/mapper/vg_bldsrv-lv_home
  861G  371G  447G  46% /home

Most of this is like speaking another language to me anyway.  I'll consider it 
all. 
KM

On ‎Tuesday‎, ‎October‎ ‎10‎, ‎2017‎ ‎10‎:‎42‎:‎21‎ ‎AM, Fred Smith 
 wrote:  
 
 On Tue, Oct 10, 2017 at 10:36:16AM -0400, Stephen John Smoogen wrote:
> On 10 October 2017 at 09:55, 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.

> > 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 just mount it as /boot 
> > from now on so it uses the space or is that not a good idea?  I am sure I 
> > could easily copy the rpms/kernel stuff over to it and then unmounts the 
> > real /boot and mount this new area as /boot.
> > Can you administrators let me know what you think of all this?  Thanks in 
> > advance.
> > KM
> 
> There is no easy way to increase the /boot partition. One can try to
> build another /boot partition and use that but that isn't simple
> either and prone to problems if the /boot is outside of where that
> particular BIOS can intepret (aka embedded in an LVM) or jump to.
> 
> I have found the simpler method is usually: dump the disks to backup,
> reinstall the system with 500 to 1000 MB /boot and restore from
> backups.

You can do this (warning--back up everything first, just in case):
-download the grub live CD image (google for it)
-burn it to a CD
-boot it
-use the graphical partition editor to resize and/or move existing
partitions to make room for a larger boot then enlarge the /boot.
all this may take a while once you tell it to commit your changes,
but it isn't hard to do. I've done it several times, as well as smaller
changes, and have yet to have a failure (knock on wood).

Does it work with LVM? Hmmm... good question. I think so, but would
have to go check to be sure.

Good luck!


-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
                      I can do all things through Christ 
                              who strengthens me.
-- Philippians 4:13 ---
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
  
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[Fred Smith]

On Tue, Oct 10, 2017 at 10:36:16AM -0400, Stephen John Smoogen wrote:
> On 10 October 2017 at 09:55, 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.

> > 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 just mount it as /boot 
> > from now on so it uses the space or is that not a good idea?  I am sure I 
> > could easily copy the rpms/kernel stuff over to it and then unmounts the 
> > real /boot and mount this new area as /boot.
> > Can you administrators let me know what you think of all this?   Thanks in 
> > advance.
> > KM
> 
> There is no easy way to increase the /boot partition. One can try to
> build another /boot partition and use that but that isn't simple
> either and prone to problems if the /boot is outside of where that
> particular BIOS can intepret (aka embedded in an LVM) or jump to.
> 
> I have found the simpler method is usually: dump the disks to backup,
> reinstall the system with 500 to 1000 MB /boot and restore from
> backups.

You can do this (warning--back up everything first, just in case):
-download the grub live CD image (google for it)
-burn it to a CD
-boot it
-use the graphical partition editor to resize and/or move existing
partitions to make room for a larger boot then enlarge the /boot.
all this may take a while once you tell it to commit your changes,
but it isn't hard to do. I've done it several times, as well as smaller
changes, and have yet to have a failure (knock on wood).

Does it work with LVM? Hmmm... good question. I think so, but would
have to go check to be sure.

Good luck!


-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
   I can do all things through Christ 
  who strengthens me.
-- Philippians 4:13 ---
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[Stephen John Smoogen]

On 10 October 2017 at 09:55, 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.
> 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 just mount it as /boot from 
> now on so it uses the space or is that not a good idea?  I am sure I could 
> easily copy the rpms/kernel stuff over to it and then unmounts the real /boot 
> and mount this new area as /boot.
> Can you administrators let me know what you think of all this?   Thanks in 
> advance.
> KM

There is no easy way to increase the /boot partition. One can try to
build another /boot partition and use that but that isn't simple
either and prone to problems if the /boot is outside of where that
particular BIOS can intepret (aka embedded in an LVM) or jump to.

I have found the simpler method is usually: dump the disks to backup,
reinstall the system with 500 to 1000 MB /boot and restore from
backups.



> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos



-- 
Stephen J Smoogen.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[John Hodrien]

On Tue, 10 Oct 2017, Pete Biggs wrote:


No, you can't do that. /boot is special and needs to be a separate
partition.


Needs is a bit strong, as grub2 does support LVM.  It's not a supported
configuration for Redhat.

I'm not a sure there's a lot to it beyond having the lvm module loaded in
grub, but I've honestly not tried.

jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[KM]

 Here is my current info, should have increased it to like 500M or so at least.
Filesystem Size  Used   Avail Use% Mounted on/dev/sda1   96M   33M   
59M  36%   /boot

ls /boot
config-2.6.32-358.el6.x86_64
efi
grub
initramfs-2.6.32-358.el6.x86_64.img
initrd-2.6.32-358.el6.x86_64kdump.img
lost+found
symvers-2.6.32-358.el6.x86_64.gz
System.map-2.6.32-358.el6.x86_64
vmlinuz-2.6.32-358.el6.x86_64



On ‎Tuesday‎, ‎October‎ ‎10‎, ‎2017‎ ‎10‎:‎17‎:‎46‎ ‎AM, Pete Biggs 
 wrote:  
 
 On Tue, 2017-10-10 at 13:55 +, 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 it, is it safe to take a chunk
> in my root filesystem (like /new.boot or something) and just mount it
> as /boot from now on so it uses the space or is that not a good
> idea?  I am sure I could easily copy the rpms/kernel stuff over to it
> and then unmounts the real /boot and mount this new area as /boot.
> Can you administrators let me know what you think of all this?  

No, you can't do that. /boot is special and needs to be a separate
partition. 

The most likely cause of your problems is that you have multiple
kernels installed - when you boot the machine do you see multiple
versions on the grub boot screen? If you don't need the previous
versions then they can just be deleted using yum: do 'rpm -q kernel' to
see which kernels are installed and 'uname -r' to see which version you
are currently running (it should be the same as the highest version
installed).  You can then use 'yum erase ...' to remove the old
kernels. It's always handy to have a version or two old ones in case of
emergency so I always leave three on a system.

The multiple versions installed of some things - i.e. the kernel - is
controlled by a yum variable in /etc/yum.conf called
'installonly_limit'. It's probably set to 5 at the moment, you can set
it to 3 safely and that is usually sufficient to stop /boot filling up.

P.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
  
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[John Hodrien]

On Tue, 10 Oct 2017, KM wrote:


Thanks for the idea.  I've already restricted it to one kernel.   so this 
will not help me.


And did you also delete the rescue kernel/image from /boot?

jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[KM]

 Thanks for the idea.  I've already restricted it to one kernel.   so this 
will not help me.

On ‎Tuesday‎, ‎October‎ ‎10‎, ‎2017‎ ‎10‎:‎04‎:‎56‎ ‎AM, Vanhorn, Mike 
 wrote:  
 
 If there are many old kernels in there, you can probably remove the oldest 
one(s) to make room for newer ones.

I've run into problems where the yum update didn't work because there wasn't 
enough room in /boot; my notes for updating now include removing old kernels 
first before running updates.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu

On 10/10/17, 9:55 AM, "CentOS on behalf of 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.
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 just mount it as /boot from now on 
so it uses the space or is that not a good idea?  I am sure I could easily copy 
the rpms/kernel stuff over to it and then unmounts the real /boot and mount 
this new area as /boot.
Can you administrators let me know what you think of all this?  Thanks in 
advance.
KM
___
CentOS mailing list
CentOS@centos.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mailman_listinfo_centos=DwIGaQ=3buyMx9JlH1z22L_G5pM28wz_Ru6WjhVHwo-vpeS0Gk=_s0N94AIK4hLWzZ1WmAPvZjr8bPWpBPPuhyNjJkGAHs=oiG0zd3adnkmuJP8BRsykJqAVPEQ_hXcq80Jj-Bfl_c=hg7Ww_cslaLQa4jGDLcy3NhAmURSXvBOW3LXB3JXCuc=
 


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
  
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[Pete Biggs]

On Tue, 2017-10-10 at 13:55 +, 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 it, is it safe to take a chunk
> in my root filesystem (like /new.boot or something) and just mount it
> as /boot from now on so it uses the space or is that not a good
> idea?  I am sure I could easily copy the rpms/kernel stuff over to it
> and then unmounts the real /boot and mount this new area as /boot.
> Can you administrators let me know what you think of all this?   

No, you can't do that. /boot is special and needs to be a separate
partition. 

The most likely cause of your problems is that you have multiple
kernels installed - when you boot the machine do you see multiple
versions on the grub boot screen? If you don't need the previous
versions then they can just be deleted using yum: do 'rpm -q kernel' to
see which kernels are installed and 'uname -r' to see which version you
are currently running (it should be the same as the highest version
installed).  You can then use 'yum erase ...' to remove the old
kernels. It's always handy to have a version or two old ones in case of
emergency so I always leave three on a system.

The multiple versions installed of some things - i.e. the kernel - is
controlled by a yum variable in /etc/yum.conf called
'installonly_limit'. It's probably set to 5 at the moment, you can set
it to 3 safely and that is usually sufficient to stop /boot filling up.

P.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Lock-up during boot when Logitech unifying receiver is connected (UEFI problem?)

[Steven Tardy]

> On Oct 10, 2017, at 5:39 AM, Toralf Lund  wrote:
> 
> If this unit (a small USB thingummy) is connected when I try to boot the 
> system, it locks up completely.

I’ve seen USB power draw be an issue similar to this previously. Does the same 
problem occur if connected through a powered USB hub?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /boot partition too small

[Vanhorn, Mike]

If there are many old kernels in there, you can probably remove the oldest 
one(s) to make room for newer ones.

I've run into problems where the yum update didn't work because there wasn't 
enough room in /boot; my notes for updating now include removing old kernels 
first before running updates.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu

On 10/10/17, 9:55 AM, "CentOS on behalf of 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.
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 just mount it as /boot from now on 
so it uses the space or is that not a good idea?  I am sure I could easily copy 
the rpms/kernel stuff over to it and then unmounts the real /boot and mount 
this new area as /boot.
Can you administrators let me know what you think of all this?   Thanks in 
advance.
KM
___
CentOS mailing list
CentOS@centos.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mailman_listinfo_centos=DwIGaQ=3buyMx9JlH1z22L_G5pM28wz_Ru6WjhVHwo-vpeS0Gk=_s0N94AIK4hLWzZ1WmAPvZjr8bPWpBPPuhyNjJkGAHs=oiG0zd3adnkmuJP8BRsykJqAVPEQ_hXcq80Jj-Bfl_c=hg7Ww_cslaLQa4jGDLcy3NhAmURSXvBOW3LXB3JXCuc=
 


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] /boot partition too small

[KM]

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 just mount it as /boot from now on 
so it uses the space or is that not a good idea?  I am sure I could easily copy 
the rpms/kernel stuff over to it and then unmounts the real /boot and mount 
this new area as /boot.
Can you administrators let me know what you think of all this?   Thanks in 
advance.
KM
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] yum security update issue

[Thomas Roth]

Hi all,

I have used http://cefs.steve-meier.de/  plus https://github.com/vmfarms/generate_updateinfo to insert 
some security-information into my os-updates - mirror.


This seems to work, but only partially.

On my 7.4 test server,
> yum --security -v check-update
gives me dnsmasq, nss, nss-sysinit and nss-tools as the packages to install.

The nss-packages are all of "severity = Important"

But there are more of this type of packages, e.g. emacs. The centos-announce mails as well as the 
errata of Steve Meier as well as the generated updateinfo.xml all contain "CESA-2017:2771 Important 
CentOS 7 emacs Security Update"
Just like the mentioned nss-packages, emacs is also labeled "severity = Important". But yum doesn't 
like it ;-(



The output of
> yum --security -v check-update
tells me more, of course:

--> 1:emacs-24.3-20.el7_4.x86_64 from os-updates excluded (updateinfo)

Neither dnsmasq nor the nss-packages are listed, in particular not as excluded 
-?


And at the end it says

> Nothing matches emacs.x86_64 1:24.3-20.el7_4 from update


Btw, "yum info emacs" lists the installed and wanted emacs versions correctly.


What did I miss?

Regards,
Thomas
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Small GRUB screen (menu/splash image)

[Toralf Lund]

Hi,

After moving my CentOS 6 installation over to a new PC, the GRUB 
start-up screen looks a bit strange. On the old machine, the menu area 
and splash image would cover the entire screen, but now they occupy only 
a small rectangle in its centre. I think what happens is that the max 
resolution of the graphics card/monitor combo is enabled even at this 
early stage, but GRUB assumes a 640x480 display.


Is there any way I can change the resolution so that the GRUB screen 
covers the entire display? I couldn't find anything related to this in 
the documentation, or when searching the web, or actually, the topic is 
mentioned a few places, but they all refer to GRUB 2, and CentOS 6 of 
course has (a patched version of) 0.97.


Thanks,

- Toralf

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] OT Imagen de disco

[César Martinez]

Gracias Ricardo lo voy a revisar y les comento

--
|Saludos Cordiales
|César Martínez M. | Ingeniero de Sistemas
|Consultor & Proyectos Software Libre| SERVICOM
|Teléfono: (593-2)554-271 2221-386 | Ext 4501
|Celular:593 999374317 |Skype servicomecuador
|Web www.servicomecuador.com Síguenos en:
|Twitter: @servicomecuador |Facebook: servicomec
|Zona Clientes: www.servicomecuador.com/billing
|Blog: http://servicomecuador.com/blog
|Dir. Av. 10 de Agosto N29-140 Entre
|Acuña y  Cuero y Caicedo
|Quito - Ecuador - Sudamérica

El 09/10/17 a las 12:41, Ricardo J. Barberis escribió:

El Sábado 07/10/2017 a las 13:20, Cesar Martinez escribió:

Saludos amigos listeros espero todos se encuentren bien acudo a ustedes
para hacerles una pregunta haber si alguien tiene experiencia y me puede
orientar con esta consulta.

Tengo un cliente en el cuál inicialmente instalé un servidor proxy con
centos 7 y de acuerdo a sus necesidades a ido creciendo en tema de
servicios ya tiene un sistema con mysql un servidor de correo y una vpn,
por temas de seguridad he sacado un respaldo de todos los archivos de
configuración y tengo un script que se ejecuta cada noche y genera un
respaldo de las bases de datos de mysql y lo saca fuera de este
servidor, ahora por temas de velocidad en caso de un desastre, que el
disco falle se dañe la maquina o peor aún se lleven la máquina el tiempo
de volver a levantar todo puede ser alto para ello me preguntaba si
alguien sabe o a implementado algún sistema que se pueda ejecutar una
imagen completa de todo el disco tipo una ISO, de tal forma que si pasa
algo poder usar esta ISO en un nuevo disco y el tiempo de estar fuera
con estos servicios sea mínimo.

De antemano gracias a todos.

Hace poco RedHat (y por lo tanto CentOS) incorporo ReaR a sus repositorios,
creo que es exactamente lo que buscas (aunque no lo he usado personalmente):

[root@centos7 ~] # LANG=C yum info rear
Loaded plugins: changelog, fastestmirror, keys, priorities
Loading mirror speeds from cached hostfile
Available Packages
Name: rear
Arch: x86_64
Version : 2.00
Release : 2.el7
Size: 434 k
Repo: base/7/x86_64
Summary : Relax-and-Recover is a Linux disaster recovery and system 
migration tool
URL : http://relax-and-recover.org/
License : GPLv3
Description : Relax-and-Recover is the leading Open Source disaster recovery 
and system
 : migration solution. It comprises of a modular
 : frame-work and ready-to-go workflows for many common situations 
to produce
 : a bootable image and restore from backup using this image. As a 
benefit,
 : it allows to restore to different hardware and can therefore be 
used as
 : a migration tool as well.
 :
 : Currently Relax-and-Recover supports various boot media (incl. 
ISO, PXE,
 : OBDR tape, USB or eSATA storage), a variety of network protocols 
(incl.
 : sftp, ftp, http, nfs, cifs) as well as a multitude of backup 
strategies
 : (incl.  IBM TSM, HP DataProtector, Symantec NetBackup, EMC 
NetWorker,
 : Bacula, Bareos, rsync).
 :
 : Relax-and-Recover was designed to be easy to set up, requires no 
maintenance
 : and is there to assist when disaster strikes. Its 
setup-and-forget nature
 : removes any excuse for not having a disaster recovery solution 
implemented.
 :
 : Professional services and support are available.


Saludos,


___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

[CentOS] Lock-up during boot when Logitech unifying receiver is connected (UEFI problem?)

[Toralf Lund]

Hi,

I've got a bit of an issue after I switched to a new laptop for my 
CentOS 6.9 installation: I'm using a Logitech cordless keyboard and 
mouse that communicate with the system via a so-called "unifying 
receiver". If this unit (a small USB thingummy) is connected when I try 
to boot the system, it locks up completely. This happens before the GRUB 
screen is displayed. The set-up otherwise works just fine, i.e. I notice 
no ill effects of connecting the receiver once the system is up-and-running.


I did not not have this problem on my old laptop, which ran a more or 
less identical Linux configuration (I cloned the partition.) Something 
that's new, though, is that I now have GPT partitions and boot using 
UEFI, where the old PC used  traditional BIOS. I also had a hard time 
installing in the first place because I got similar issues when trying 
to boot the installer as well as "stand-alone" tools like "parted" and 
"clonezilla" from USB sticks, and these seemed to be restricted to GPT 
and UEFI, too. (I didn't realise at the time that the unifying receiver 
was the problem, so I ended up installing via "legacy" boot.)


Has anyone else seen this? Any suggestions? I can live with the problem, 
I guess, but having to unplug and reconnect the unit every time I boot 
is a bit annoying.


I've tried connecting the unit to several different USB ports, with the 
same result. I've also searched for firmware updates, but didn't find 
anything.


TIA,

- Toralf

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos