Discuss

discuss@lists.centos.org

34753 discussions

OT hard disk geometry
by Timothy Murphy 10 Feb '14

10 Feb '14

My only excuse for asking this question here is that I am running CentOS-6.5 on my HP MicroServer. I recently purchased a 2TB WD hard drive (WD20ESRX), and was surprised to find that the power-connector on this drive did not seem to be in the correct place for the drive-bay. (The drive bay closes, but the disk does not spin.) The power connector on the drive is further from the SATA connectors than on the other 4 drives I have in my two MicroServers - it is about 2/3 of the way across the back of the drive, on the opposite side to the SATA connectors. I'm surprised because I always thought that the positions of the connectors on SATA hard drives was standard. How can I find whether or not a hard drive will connect properly in the drive-bay? Was I unlucky to choose a drive that did not fit? -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

5 7

conntrack-tools not in 6.4
by Steve Clark 10 Feb '14

10 Feb '14

HI List, Did I miss something? I have 6.2 system that has conntrack-tools conntrack-tools.i686 1.0.0-1.el6 @anaconda-CentOS-201112130233.i386/6.2 But I can't seem to find conntrack-tools for 6.4 yum install conntrack-tools Loaded plugins: fastestmirror, security Loading mirror speeds from cached hostfile * base: mirror.umd.edu * elrepo: repos.mia.lax-noc.com * epel: mirror.cogentco.com * extras: mirror.fdcservers.net * rpmforge: mirror.teklinks.com * updates: mirror.wiredtree.com Setting up Install Process No package conntrack-tools available. Error: Nothing to do # cat /etc/redhat-release CentOS release 6.4 (Final) -- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark(a)netwolves.com http://www.netwolves.com

1 0

bind (named) compromised?
by James Pifer 10 Feb '14

10 Feb '14

I'm having problems where my upstream bandwidth is being saturated. I've narrowed it down to a DNS issue of some type. If I stop the named service then my bandwidth drops to "normal" according to my untangle firewall. I'm running bind-9.3.6-20.P1.el5_8.6. I'm seeing the following in /var/log/messages: 2014-02-08T23:03:09.558315-05:00 mailserver named[3497]: network unreachable resolving 'hccforums.nl/ANY/IN': 2a00:1188:5::212#53 2014-02-08T23:03:09.558441-05:00 mailserver named[3497]: network unreachable resolving 'hccforums.nl/ANY/IN': 2001:7b8:606::85#53 2014-02-08T23:03:10.008926-05:00 mailserver named[3497]: client 174.128.253.163#5209: view external: no more recursive clients: quota reached 2014-02-08T23:03:11.001878-05:00 mailserver named[3497]: client 173.234.39.133#5209: view external: no more recursive clients: quota reached 2014-02-08T23:03:12.000487-05:00 mailserver named[3497]: client 173.234.39.133#5209: view external: no more recursive clients: quota reached 2014-02-08T23:03:13.000820-05:00 mailserver named[3497]: client 173.234.39.133#5209: view external: no more recursive clients: quota reached 2014-02-08T23:03:14.001501-05:00 mailserver named[3497]: client 192.126.118.105#5209: view external: no more recursive clients: quota reached 2014-02-08T23:03:15.005720-05:00 mailserver named[3497]: client 192.126.118.105#5209: view external: no more recursive clients: quota reached I've tried changing the following in /etc/named.conf but it doesn't seem to have any affect so I commented them back out. tcp-clients 1000; recursive-clients 10000; I also see a chroot directory, but if I grep for named it doesn't appear to be using the chroot(?): # ps aux | grep named named 3497 0.4 0.7 170088 15836 ? Ssl 23:02 0:02 /usr/sbin/named -u named root 3763 0.0 0.0 61192 764 pts/1 S+ 23:13 0:00 grep named I've also tried adding the following to iptables, but it also seems to have no affect: iptables --insert INPUT -p udp --dport 53 -m string --from 40 --to 56 --algo bm --hex-string '|09686363666f72756d73026e6c0000ff|' -j DROP -m comment --comment "DROP DNS Q hccforums.nl" Any suggestions or troubleshooting advice? Much appreciated. James

4 3

openswan and ipsec
by Markus Falb 10 Feb '14

10 Feb '14

# ipsec verify ... If you encounter network related SElinux errors, especially when using KLIPS, try disabling SElinux ... Well, it is not running KLIPS but netkey, anyways I feel not comfortable about disabling selinux on a ipsec router. I am not sure how to handle possible probems in this case, too. If I decide not to disable selinux, and I run into problems, should I a) report it to redhat as a bug, because it is b) disable selinux because ipsec is not meant to work with selinux Maybe just the verify script should be fixed? Maybe I should ask RedHat about this, hm. And finally, do you encounter network related SElinux errors with IPSec, both 5 and 6? -- Kind Regards, Markus

2 1

CentOS-announce Digest, Vol 108, Issue 5
by centos-announce-request＠centos.org 09 Feb '14

09 Feb '14

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)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. CEBA-2014:0141 CentOS 6 fence-agents Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Sat, 8 Feb 2014 14:54:37 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0141 CentOS 6 fence-agents Update To: centos-announce(a)centos.org Message-ID: <20140208145437.GA1163(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0141 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0141.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 614c2be12f6ca445d7360a443ff0c9a773fac116d7b2b72eb528b3028d0d69a6 fence-agents-3.1.5-35.el6_5.3.i686.rpm x86_64: ebff912c9701ccec8c7b247cb37a0128a7e04e81c919a81c8e7fed3f66caeb90 fence-agents-3.1.5-35.el6_5.3.x86_64.rpm Source: d3b3ae9ea2033c27e97cfe73f51ece788baed09206ef7c57ccb3676dfb04b617 fence-agents-3.1.5-35.el6_5.3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 108, Issue 5 ***********************************************

1 0

Upgrading Perl (modules) / RequestTracker
by Michael Mol 08 Feb '14

08 Feb '14

I'm attempting to install RequestTracker on CentOS 6.5. Running "make testdeps" as recommended by RT's installation guide, I'm presented with lists of missing Perl modules. One of these lines reads: Encode >= 2.39 ...MISSING Now, "yum whatprovides '*/Encode.pm' " informs me that that module is part of the core Perl distribution, and is installed on my system. Opening the file itself reveals: # $Id: Encode.pm,v 2.35 2009/07/13 00:49:38 dankogai Exp $ so I know that I have version 2.35 of that module installed, and obviously that's < 2.39. So I need to get 2.39 installed. What is the correct way to do this on CentOS? The last time I had to do anything like this, it was on a Debian box, I went through the process recommended by the guys in #perl, and was left with a broken system that was a real joy to piece back together...

7 8

iso burn
by Hal Wigoda 08 Feb '14

08 Feb '14

I downloaded the CentOS-6.5-x86_64-bin-DVD1.iso and CentOS-6.5-x86_64-bin-DVD12.iso and tried to burn them to a DVD but both Windows 7 and IOS ( MacBook Pro ) do not recognize these as valid isos. What am I doing wrong? -- ----------------- Hal Wigoda Chicago

9 16

Re: [CentOS] OT hard disk geometry
by Miguel Medalha 08 Feb '14

08 Feb '14

It seems to me that there's some confusion on your part about what a SATA power connector is... The SATA edge connector is divided in two parts, a larger one and a narrower one. The narrower one is the signal, or data, connector. The larger one is the power connector. Some older drives also had an additional common Molex connector for power, for compatibility reasons, since at first only a few power supplies had the SATA power connector. Note that the Molex connector does not enable the hot-plugging and unplugging of SATA drives. This needs the 3.3V supply that only the SATA connector provides. As far as I can see, the ST3250318AS does not have such a connector. The manual for the ST3250318AS is here: http://www.seagate.com/staticfiles/support/disc/manuals/desktop/Barracuda%2… On page 28 you can read about the SATA cables and connectors. The pins you refer to, which are not present on the WD at the same position, are NOT power connections, that is a jumper block as you can read on the first image of page 28. The manual states the following: « It is usually not necessary to set any jumpers on the drive for proper operation; however, if you connect the drive and receive a “drive not detected” error, your SATAequipped motherboard or host adapter may use a chipset that does not support SATA speed autonegotiation. If you have a motherboard or host adapter that does not support autonegotiation: -Install a jumper as shown in Figure 1 below to limit the data transfer rate to 1.5 Gbits per second (and leave the drive connected to the SATA-equipped motherboard or host adapter that doesn’t support autonegotiation) or -Install a SATA host adapter that supports autonegotiation, leave the drive jumper block set to “Normal operation” (see Figure 1 below), and connect the drive to that adapter. This option has the benefit of not limiting the drive to a 1.5 Gbits/sec transfer rate. » I think this is not a power connector issue. The WD is a SATA3 drive (6gb/s). Are you sure that your motherboard supports SATA3 drives? Maybe SOME ports support them while others do not? If not, can you force the WD to operate in a lower mode? Some drives can, either by hardware or software.

5 4

Software RAID1 Failure Help
by Matt 08 Feb '14

08 Feb '14

I am running software RAID1 on a somewhat critical server. Today I noticed one drive is giving errors. Good thing I had RAID. I planned on upgrading this server in next month or so. Just wandering if there was an easy way to fix this to avoid rushing the upgrade? Having a single drive is slowing down reads as well, I think. Thanks. Feb 7 15:28:28 server smartd[2980]: Device: /dev/sdb [SAT], 1 Currently unreadable (pending) sectors Feb 7 15:28:28 server smartd[2980]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors Feb 7 15:58:29 server smartd[2980]: Device: /dev/sdb [SAT], 1 Currently unreadable (pending) sectors Feb 7 15:58:29 server smartd[2980]: Device: /dev/sdb [SAT], 1 Offline uncorrectable sectors [root@server ~]# smartctl -H /dev/sda === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED [root@server ~]# smartctl -H /dev/sdb === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED [root@server ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/md2 1.4T 142G 1.2T 12% / /dev/md0 99M 37M 58M 39% /boot tmpfs 7.9G 20K 7.9G 1% /dev/shm [root@server ~]# cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb1[1] sda1[0] 104320 blocks [2/2] [UU] md1 : active raid1 sdb2[1] sda2[0] 8385856 blocks [2/2] [UU] md2 : active raid1 sdb3[2](F) sda3[0] 1456645568 blocks [2/1] [U_] unused devices: <none> [root@server ~]# mdadm --detail /dev/md2 /dev/md2: Version : 0.90 Creation Time : Tue Jan 4 05:39:36 2011 Raid Level : raid1 Array Size : 1456645568 (1389.17 GiB 1491.61 GB) Used Dev Size : 1456645568 (1389.17 GiB 1491.61 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 2 Persistence : Superblock is persistent Update Time : Fri Feb 7 15:21:45 2014 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 1 Spare Devices : 0 Events : 0.758203 Number Major Minor RaidDevice State 0 8 3 0 active sync /dev/sda3 1 0 0 1 removed 2 8 19 - faulty spare /dev/sdb3 [root@server ~]# mdadm --detail /dev/md1 /dev/md1: Version : 0.90 Creation Time : Tue Jan 4 05:39:36 2011 Raid Level : raid1 Array Size : 8385856 (8.00 GiB 8.59 GB) Used Dev Size : 8385856 (8.00 GiB 8.59 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Fri Feb 7 14:29:36 2014 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Events : 0.460 Number Major Minor RaidDevice State 0 8 2 0 active sync /dev/sda2 1 8 18 1 active sync /dev/sdb2 [root@server ~]# mdadm --detail /dev/md0 /dev/md0: Version : 0.90 Creation Time : Tue Jan 4 05:48:17 2011 Raid Level : raid1 Array Size : 104320 (101.89 MiB 106.82 MB) Used Dev Size : 104320 (101.89 MiB 106.82 MB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Wed Feb 5 11:02:25 2014 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Events : 0.460 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1

8 8

Re: [CentOS] OT hard disk geometry
by Miguel Medalha 08 Feb '14

08 Feb '14

The server's manual recommends filling the drive bays in the 1,2,3,4 order. At this point, you should check the HP support page for the server, Look for controller firmware updates, BIOS updates, troubleshooting advice and so on. Did you try to connect the drive alone? If it is detected alone, you will have a clue there. Some drives don't go along with some others when installed in the same pair of ports, for example. I would also suspect the cable. I have had more problems with SATA cables than I could expect. Also, the drive itself can be defective. I once received two new WD high end drives that couldn't be detected by any controller and I had to return them. The new ones worked fine.

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss