Re: [CentOS] Kernel crash

2017-10-12 Thread Diego Farias 
I'm sorry for all this trouble; I followed ElRepo's instructions and now I
have wifi! (someday I will fix bluetooth).

2017-10-12 18:52 GMT-03:00 Diego Farias :

> By the way, attached is the kernel panic screenshot, apparently it is
> related to cfg80211.
>
> On Oct 12, 2017 5:46 PM, "Diego Farias"  wrote:
>
>> Hi everyone,
>>
>> I updated the kernel from 3.10.0-514.16.1.el7.x86_64
>> to  3.10.0-693.2.2.el7.x86_64 . While I was following these steps
>> https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom (I knew that I
>> needed to compile again everything) in order to activate WIFI, the laptop
>> crashed doing
>>
>> # depmod -a
>> # modprobe wl
>>
>> Noting that I replaced (naively) # depmod $(uname -r) from the guide
>> (stupid mistake, I use tcsh and the command above didn't work; that's why
>> the replacement).
>>
>> After the crash, I had to manually shutdown the laptop. Then, I booted
>> the same kernel and it went to 'emergency mode'; as I don't have the root
>> password (second stupid mistake; I'm superuser but I don't remember the
>> root password/nor I can change it -I don't know-) I couldn't do a thing.
>>
>> Then, I booted the previous kernel, 3.10.0-514.16.1.el7.x86_64 (which
>> works fine), removed 3.10.0-693.2.2.el7.x86_64 (yum remove), and
>> reinstalling it from zero. Oddly,
>> when I boot with the new kernel, the laptop crashes before login; the
>> caps lock light tilts and nothing happens. I've done this several times and
>> the same.
>>
>> I know I can use the older kernels to work, but I really want to fix this
>> if possible.
>>
>> Thanks in advance.
>>
>>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Kernel crash

2017-10-12 Thread S. Tindall 

On 10/12/2017 05:32 PM, Yves Bellefeuille wrote:

  I updated the kernel from 3.10.0-514.16.1.el7.x86_64
  to  3.10.0-693.2.2.el7.x86_64 . While I was following these steps
  https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom

The instructions at https://elrepo.org/tiki/wl-kmod always worked for
me (BCM4312, if I remember correctly).

The centos wiki for broadcom is valid for EL 7.3, but needs another 
patch and another sed for EL 7.4.


The elrepo wl-kmod.srpm includes both and can build kmod-wl on your 
system for you by following the instructions at:


 http://elrepo.org/tiki/wl-kmod

Steve

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

Re: [CentOS] Kernel crash

2017-10-12 Thread Yves Bellefeuille 
>  I updated the kernel from 3.10.0-514.16.1.el7.x86_64
>  to  3.10.0-693.2.2.el7.x86_64 . While I was following these steps
>  https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom

The instructions at https://elrepo.org/tiki/wl-kmod always worked for
me (BCM4312, if I remember correctly).

-- 
Yves Bellefeuille


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

Re: [CentOS] Kernel crash

2017-10-12 Thread m . roth 
Diego Farias wrote:
> Hi everyone,
>
> I updated the kernel from 3.10.0-514.16.1.el7.x86_64
> to  3.10.0-693.2.2.el7.x86_64 . While I was following these steps
> https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom (I knew that I
> needed to compile again everything) in order to activate WIFI, the laptop
> crashed doing
>
> # depmod -a
> # modprobe wl
>
> Noting that I replaced (naively) # depmod $(uname -r) from the guide
> (stupid mistake, I use tcsh and the command above didn't work; that's why
> the replacement).
>
> After the crash, I had to manually shutdown the laptop. Then, I booted the
> same kernel and it went to 'emergency mode'; as I don't have the root
> password (second stupid mistake; I'm superuser but I don't remember the
> root password/nor I can change it -I don't know-) I couldn't do a thing.
>
> Then, I booted the previous kernel, 3.10.0-514.16.1.el7.x86_64 (which
> works
> fine), removed 3.10.0-693.2.2.el7.x86_64 (yum remove), and reinstalling it
> from zero. Oddly,
> when I boot with the new kernel, the laptop crashes before login; the caps
> lock light tilts and nothing happens. I've done this several times and the
> same.
>
> I know I can use the older kernels to work, but I really want to fix this
> if possible.
>
> Thanks in advance.

Congrats. It's nice to know other folks have the same problem I do, except
mine was on a honkin' Dell R730 server with lots of cores and memory.

Btw, folks, the normal update installs teh "with debugging" as an option;
I *assuem* that it has crash kernel enabled. However, /etc/kdump.conf is
default configured to dump to /var/crash, which has nothing at all in it.
Also - I believe I mentioned it, it kernel panics *just* as it tries to
switch root.

Diego, can you tell if you're getting a kernel panic?

   mark

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

[CentOS] Kernel crash

2017-10-12 Thread Diego Farias 
Hi everyone,

I updated the kernel from 3.10.0-514.16.1.el7.x86_64
to  3.10.0-693.2.2.el7.x86_64 . While I was following these steps
https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom (I knew that I
needed to compile again everything) in order to activate WIFI, the laptop
crashed doing

# depmod -a
# modprobe wl

Noting that I replaced (naively) # depmod $(uname -r) from the guide
(stupid mistake, I use tcsh and the command above didn't work; that's why
the replacement).

After the crash, I had to manually shutdown the laptop. Then, I booted the
same kernel and it went to 'emergency mode'; as I don't have the root
password (second stupid mistake; I'm superuser but I don't remember the
root password/nor I can change it -I don't know-) I couldn't do a thing.

Then, I booted the previous kernel, 3.10.0-514.16.1.el7.x86_64 (which works
fine), removed 3.10.0-693.2.2.el7.x86_64 (yum remove), and reinstalling it
from zero. Oddly,
when I boot with the new kernel, the laptop crashes before login; the caps
lock light tilts and nothing happens. I've done this several times and the
same.

I know I can use the older kernels to work, but I really want to fix this
if possible.

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

[CentOS-announce] Release for CentOS AltArch 7 (1708) on i386 Architecture

2017-10-12 Thread Johnny Hughes 
This is the release announcement for the i386 (Intel 32-bit)
Architecture based on the source code released for CentOS-7 (1708).  It
includes all packages that build on x86 32-bit processors.

The release notes for the normal CentOS-7 apply:

https://wiki.centos.org/Manuals/ReleaseNotes/CentOS7

with the following notes that are specific to i386:

https://wiki.centos.org/SpecialInterestGroup/AltArch/i386

If you already have a previous version of CentOS-7 i386 installed, just
running 'yum update' will get you the latest packages installed.

ISOs can be downloaded from:

http://mirror.centos.org/altarch/7/isos/i386/

Here are the SHA256SUMS for the ISOs:

CentOS-7-i386-DVD-1708.iso:
36df0a7d687e058ec11708ccace7981fe2faf1040d4efd796a4ffab67863eace

CentOS-7-i386-Everything-1708.iso
e118987646ca5e916a1cdc89e916ea64bd06e1c09564721a13ad90b0caffd4b2

CentOS-7-i386-LiveGNOME-1708.iso:
e97c5475e5a45539a213970d13231c3da85927c8d5f34f7fc187fd37cdfe72aa

CentOS-7-i386-LiveKDE-1708.iso:
7c2130993783c089453d6f55aea2431c9c7617be922e2b206bcef03580c521f7

CentOS-7-i386-Minimal-1708.iso:
8e73904c870f93ca3b553048a0092b1fc0ddebd2d8990e0f7b13a22d70eb725e

CentOS-7-i386-NetInstall-1708.iso:
5fd4075b841e8500826408ef95352ed1d2868b2ebe2cdcf66cd505a51a6c8484

===

Bug reports and feedback about specific packages should be filed at
https://bugs.centos.org/ against the relevant package name, for project
CentOS Linux 7, in the same manner as you would for x86_64. However, do
mention the architecture as applicable.

===

Johnny Hughes
Twitter:  @JohnnyCentOS
Freenode IRC:  hughesjr



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

[CentOS-es] OT certificado zimbra

2017-10-12 Thread César Martinez 
Saludos amigos tengo un problema que paso a describir haber si alguien 
me puede echar una mano, tengo instalado un servidor de correo centos 7 
+ zimbra 8.7, los clientes usan outlook 2010, 2013 y 2016, tengo el 
problema que cada vez que abro me da una alerta del certificado y debo 
poner usar este certificado a pesar de que la primera vez que configuré 
outlook ya lo instale y me apareció el mensaje de ha sido instalado.


Cabe recalcar que tengo solo el certificado auto firmado que genera 
zimbra al realizar la instalación.


De antemano agradezco a todos los que puedan ayudarme

--
|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

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

Re: [CentOS] nfsvers and nfs-utils-1.3.0-0.48.el7

2017-10-12 Thread Johnny Hughes 
On 10/12/2017 12:33 PM, Paul Heinlein wrote:
> We encountered a weird problem today, and I thought some of you might
> like to hear the solution.
> 
> The underlying change was listed in the 7.4 changelog, so it's not a
> bug, but it may drive you buggy.
> 
> The majority of our HPC cluster nodes run CentOS 7, though the exact
> patch levels vary from node to node. None is older than 7.3, but a few
> newer nodes were kickstarted right to 7.4.
> 
> The problem was that our mounts of Isilon NFS exports were failing
> randomly among the nodes. Routing was fine. Network connectivity was fine.
> 
> The short answer is that the default in 7.4, and I think in the
> nfs-utils-1.3.0-0.48.el7 package in particular, has changed. While NFS
> v4.0 was the default up to 7.3, the 7.4 protocols are subtly different:
> 
> 1. Try NFS v4.1 first
> 2. Fail down to NFS v3
> 3. Fail down to NFS v2
> 
> The problem is that our Isilon works with NFS v4.0, not 4.1, but 4.0 is
> not in the fail-down path.
> 
> The short-term answer is to specify nfsvers=4.0 in our autofs
> configuration files, which works like a charm.
> 
> Like I said, this was an announced change, but the implications escaped
> us until now. So this little writeup is just for the record.
> 

You are not the first person to have this issue .. thanks for the post.



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

[CentOS] nfsvers and nfs-utils-1.3.0-0.48.el7

2017-10-12 Thread Paul Heinlein 
We encountered a weird problem today, and I thought some of you might 
like to hear the solution.


The underlying change was listed in the 7.4 changelog, so it's not a 
bug, but it may drive you buggy.


The majority of our HPC cluster nodes run CentOS 7, though the exact 
patch levels vary from node to node. None is older than 7.3, but a few 
newer nodes were kickstarted right to 7.4.


The problem was that our mounts of Isilon NFS exports were failing 
randomly among the nodes. Routing was fine. Network connectivity was 
fine.


The short answer is that the default in 7.4, and I think in the 
nfs-utils-1.3.0-0.48.el7 package in particular, has changed. While NFS 
v4.0 was the default up to 7.3, the 7.4 protocols are subtly 
different:


1. Try NFS v4.1 first
2. Fail down to NFS v3
3. Fail down to NFS v2

The problem is that our Isilon works with NFS v4.0, not 4.1, but 4.0 
is not in the fail-down path.


The short-term answer is to specify nfsvers=4.0 in our autofs 
configuration files, which works like a charm.


Like I said, this was an announced change, but the implications 
escaped us until now. So this little writeup is just for the record.


--
Paul Heinlein
heinl...@madboa.com
45°38' N, 122°6' W
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-docs] [Gitblit] rbowen pushed 1 commits => websites/centos.org.git

2017-10-12 Thread Gitblit 
https://git.centos.org/summary/websites!centos.org.git

>---
 master branch updated (1 commits)
>---

 Rich Bowen 
 Thursday, October 12, 2017 13:32 +

 FOSDEM Dojo CFP

 
https://git.centos.org/commit/websites!centos.org.git/00b928fe2f21402da2bad04ed843b2948716a288
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

[CentOS-announce] CESA-2017:2885 Important CentOS 7 thunderbird Security Update

2017-10-12 Thread Johnny Hughes 

CentOS Errata and Security Advisory 2017:2885 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2017:2885

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
8689cc4ee4be5aeed443100d44d5a94bc1b58ad1aa061392c1971d5ed26f41c4  
thunderbird-52.4.0-2.el7.centos.x86_64.rpm

Source:
e402822a322f5e009ea129511cd0b9e449ba2a39e62de2ae77dce97af4ea  
thunderbird-52.4.0-2.el7.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

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

[CentOS-announce] CESA-2017:2885 Important CentOS 6 thunderbird Security Update

2017-10-12 Thread Johnny Hughes 

CentOS Errata and Security Advisory 2017:2885 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2017:2885

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
23ba7f540fdf0317df088f6434ca63634e7200ced7d735fe5c1921e2a1da1757  
thunderbird-52.4.0-2.el6.centos.i686.rpm

x86_64:
1b568daabf9aec0562d4781e18188a3cc8a257ce8fa6cfaa5772fbd003e9320b  
thunderbird-52.4.0-2.el6.centos.x86_64.rpm

Source:
6c5b1c8a602f538d77c40222646611d2c409de7f6e44d364ad7f3dbc2d0bb580  
thunderbird-52.4.0-2.el6.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

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

Re: [CentOS] [External] /boot partition too small

2017-10-12 Thread Mauricio Tavares 
On Thu, Oct 12, 2017 at 8:38 AM, John Hodrien  wrote:
> On Thu, 12 Oct 2017, Mauricio Tavares wrote:
>
>> Stupid question: can't you do
>>
>> rpm -qa | grep ^kernel
>>
>> and then
>>
>> rpm -e 
>
>
> With 100Mbyte /boot on a non-EFI system, I wouldn't have enough room for two
> kernels, so updates would be tricky.
>
  You have a point there. I was thinking the OP's situation was
/boot is a reasonable size but just got filled up because it was not
being monitored. And, as a result, he made yum sad. So now all he
wants is to clean it up just enough to use other stuff, and then as
mentioned before reconfigure grub2.cfg to keep only a couple of 3
kernels around.

Not going to say that happened to me in ubuntu before. O:)

> jh
>
> ___
> 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] [External] /boot partition too small

2017-10-12 Thread John Hodrien 

On Thu, 12 Oct 2017, Mauricio Tavares wrote:


Stupid question: can't you do

rpm -qa | grep ^kernel

and then

rpm -e 


With 100Mbyte /boot on a non-EFI system, I wouldn't have enough room for two
kernels, so updates would be tricky.

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

Re: [CentOS] [External] /boot partition too small

2017-10-12 Thread Mauricio Tavares 
Stupid question: can't you do

rpm -qa | grep ^kernel

and then

rpm -e 


On Thu, Oct 12, 2017 at 4:24 AM, Sorin Srbu  wrote:
>> -Original Message-
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Toralf Lund
>> Sent: den 12 oktober 2017 10:15
>> To: CentOS mailing list 
>> Subject: Re: [CentOS] [External] /boot partition too small
>>
>> >> Since a lot of people seem to say none of the above can be done, I'm
>> >> starting to feel slightly unsure, but I though gparted could extend,
>> >> shrink and move partitions while preserving data.
>> >
>> > You would be asking gparted to:
>> > 1. Reach inside an LVM PV and shrink one filesystem and its LV,
>> > 2. Rearrange the extents inside the PV to make free space at the
>> > beginning,
>> > 3. Move the start of the PV and adjust all of the starting offsets for
>> > the LVs,
>> > 4. Finally, enlarge partition 1 into the freed-up space.
>> >
>> > Even if gparted was willing to attempt that, there is no way I would
>> > trust it to do it correctly.
>> Quite. I'd never try this without a backup, of course. In fact, I've
>> only ever used gparted in situations where I had a system dump already.
>> Still, it could save you from a bit of work, as in, if it does succeed,
>> you won't have to do a full recovery.  Also, I'm not really sure about
>> the state of the LVM support, now that you mention it. (But there is
>> supposed to be *something* in that area.)
>
> Supposedly the below tool should be able to handle LVM volumes, and is
> bootable from CD. It costs though.
>
> https://www.partitionwizard.com/partition-wizard-bootable-cd.html
>
> Maybe helps a bit?
> --
> //Sorin
> ___
> 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

[CentOS] yum-cron hourly errors

2017-10-12 Thread John Ratliff 
I receive messages like this from cron often. Not every hour, and not 
consistently between the servers running CentOS, but at least two per 
day. Is this normal?


/etc/cron.hourly/0yum-hourly.cron:

Could not retrieve mirrorlist 
http://mirrorlist.centos.org/?release=7=x86_64=os=stock 
error was


14: HTTP Error 403 - Forbidden

Could not retrieve mirrorlist 
http://mirrorlist.centos.org/?release=7=x86_64=extras=stock 
error was


14: HTTP Error 403 - Forbidden

Could not retrieve mirrorlist 
http://mirrorlist.centos.org/?release=7=x86_64=updates=stock 
error was


14: HTTP Error 403 - Forbidden

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

[CentOS] CentOS-announce Digest, Vol 152, Issue 4

2017-10-12 Thread centos-announce-request 
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CESA-2017:2882 Moderate CentOS 7 httpd Security   Update
  (Johnny Hughes)


--

Message: 1
Date: Wed, 11 Oct 2017 20:46:20 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2017:2882 Moderate CentOS 7 httpd
SecurityUpdate
Message-ID: <20171011204620.ga63...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2017:2882 Moderate

Upstream details at : https://access.redhat.com/errata/RHSA-2017:2882

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
41421bbfa809cd1fea427ffd689e2caa4d92643aec1094ce7c2271702f19480a  
httpd-2.4.6-67.el7.centos.5.x86_64.rpm
2814b75b35bf8fed0fd12033d1fc0b6203a60926646fb3151cbda49260175522  
httpd-devel-2.4.6-67.el7.centos.5.x86_64.rpm
2156dda1f88729bbf47dcd000911942d122a0797d55fcfdcb65e1ead2e3601e8  
httpd-manual-2.4.6-67.el7.centos.5.noarch.rpm
d1152bdf63709d455dbba51fd7aafc4b69cb45dd48073edfe4b337157a3974b4  
httpd-tools-2.4.6-67.el7.centos.5.x86_64.rpm
0e4029a1ac0b75e2363c7803282e5230cdf4260122ffbf2daeaec955a94f71ac  
mod_ldap-2.4.6-67.el7.centos.5.x86_64.rpm
fe94afba530fb88bfbe1bd782afe61dd69212c30920d14574099468a2ce76844  
mod_proxy_html-2.4.6-67.el7.centos.5.x86_64.rpm
cae78de9a2bb32f12af2bf7895cc27c2f95119787b7139b5ab0ea018b6738113  
mod_session-2.4.6-67.el7.centos.5.x86_64.rpm
829d9f95fafbdc31c0e14180b688f27beb329c00961c5340e9609b9789070ea6  
mod_ssl-2.4.6-67.el7.centos.5.x86_64.rpm

Source:
5cc7d1292f22dc068f166c8e722456158f9856c29a71887581394a99a4615ab0  
httpd-2.4.6-67.el7.centos.5.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS



--

Subject: Digest Footer

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


--

End of CentOS-announce Digest, Vol 152, Issue 4
***
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-docs] wiki add

2017-10-12 Thread Karsten Dreifus 
Dear Team,

Wiki login Name KarstenDreifus

I want to add a wiki page:
CentOS 6.9 with SELinux enforcing denies mount action ZFS

Based on this blog post (I am not the author), I would like to add a
wikipage that states how to mount ZFS automatically on reboot.

Thanks,
Karsten
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

[CentOS] Seagate's firmware flash until in Centos 7.x - does it work?

2017-10-12 Thread lejeczek 

hi fellas

I wonder if any of you use(d) dl_sea_fw to flash SAS drive?
I try dl_sea_fw-0.2.3_64 to flash ST32000444SS but it fails:

$ ./linux\ cli\ tools/dl_sea_fw-0.2.3_64 -m ST32000444SS -f 
firmware/MU-SAS-0008.LOD -d /dev/sg59


 Seagate Firmware Download Utility v0.2.3 Build Date: Jan  
9 2013

 Copyright (c) 2012 Seagate Technology LLC, All Rights Reserved
 Thu Oct 12 11:33:05 2017

Downloading file firmware/MU-SAS-0008.LOD to /dev/sg59
send_io: Success
 !
FW Download FAILED

Would you have some advice?
many thanks, L.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [External] /boot partition too small

2017-10-12 Thread Sorin Srbu 
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Toralf Lund
> Sent: den 12 oktober 2017 10:15
> To: CentOS mailing list 
> Subject: Re: [CentOS] [External] /boot partition too small
>
> >> Since a lot of people seem to say none of the above can be done, I'm
> >> starting to feel slightly unsure, but I though gparted could extend,
> >> shrink and move partitions while preserving data.
> >
> > You would be asking gparted to:
> > 1. Reach inside an LVM PV and shrink one filesystem and its LV,
> > 2. Rearrange the extents inside the PV to make free space at the 
> > beginning,
> > 3. Move the start of the PV and adjust all of the starting offsets for 
> > the LVs,
> > 4. Finally, enlarge partition 1 into the freed-up space.
> >
> > Even if gparted was willing to attempt that, there is no way I would
> > trust it to do it correctly.
> Quite. I'd never try this without a backup, of course. In fact, I've
> only ever used gparted in situations where I had a system dump already.
> Still, it could save you from a bit of work, as in, if it does succeed,
> you won't have to do a full recovery.  Also, I'm not really sure about
> the state of the LVM support, now that you mention it. (But there is
> supposed to be *something* in that area.)

Supposedly the below tool should be able to handle LVM volumes, and is 
bootable from CD. It costs though.

https://www.partitionwizard.com/partition-wizard-bootable-cd.html

Maybe helps a bit?
--
//Sorin
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [External] /boot partition too small

2017-10-12 Thread Toralf Lund 

On 11/10/17 15:22, Robert Nichols wrote:

On 10/11/2017 02:04 AM, Toralf Lund wrote:

On 10/10/17 15: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.

Hi,

Since a lot of people seem to say none of the above can be done, I'm 
starting to feel slightly unsure, but I though gparted could extend, 
shrink and move partitions while preserving data.


You would be asking gparted to:
    1. Reach inside an LVM PV and shrink one filesystem and its LV,
    2. Rearrange the extents inside the PV to make free space at the 
beginning,
    3. Move the start of the PV and adjust all of the starting offsets 
for the LVs,

    4. Finally, enlarge partition 1 into the freed-up space.

Even if gparted was willing to attempt that, there is no way I would 
trust it to do it correctly.
Quite. I'd never try this without a backup, of course. In fact, I've 
only ever used gparted in situations where I had a system dump already. 
Still, it could save you from a bit of work, as in, if it does succeed, 
you won't have to do a full recovery.  Also, I'm not really sure about 
the state of the LVM support, now that you mention it. (But there is 
supposed to be *something* in that area.)


- Toralf


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

Re: [CentOS] I do not love thee, kernel-3.10.0-693.2.2.el7.x86_64

2017-10-12 Thread Johnny Hughes 
On 10/11/2017 04:30 PM, m.r...@5-cent.us wrote:
> J Martin Rushton wrote:
>> On 11/10/17 19:28, m.r...@5-cent.us wrote:
>>> I've been having a lot of issues with video, for example. However, this
>>> one... I have a user with a Dell R730. I install kernel and kernel
>>> devel, and the rest of the full update, and rebooted.
>>>
>>> Nope. 100% kernel panic, right around the time it switches root. I even
>>> rebuilt the initramfs, nope.
>>>
>>> And speaking of kernel panics, has *anyone* ever considered that all the
>>> data dumped to the console during one results in NOT BEING ABLE TO READ
>>> ANYTHING BUT THE LAST 24 or less, mostly less, lines?
>>>
>>>   mark, frustrated, removed that kernel
>>
>> Ah, the good old days of running a VAXcluster with hardcopy consoles.
>>
> Smartass. I never had that But, really, what's the point of dumping
> many, many lines of data... when it cannot be read? Why not assume that
> it's going to happen on a normal terminal, and dump no more than 25
> 80-char lines? So the admin might maybe possibly have a clue as to what
> caused it?

Surely you do realize there are SEVERAL other display options besides
just the video console, right?

You can use kdump, you can use a serial console .. you can use google
and the search term 'capture kernel oops' to get more than 10 full
search page results on how to capture the output of a kernel oops.



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