Discuss

discuss@lists.centos.org

5 participants
34752 discussions

Building software RAID mdmad adding a second disk
by israel.garcia＠cimex.com.cu 12 Apr '06

12 Apr '06

I'am running CentOS 4.3 on an (Intel) with one SATA disk (/dev/sda). The output of fdisk -l: Disk /dev/sda: 81.9 GB, 81964302336 bytes 255 heads, 63 sectors/track, 9964 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 19 152586 83 Linux /dev/sda2 20 2569 20482875 83 Linux /dev/sda3 2570 2700 1052257+ 82 Linux swap /dev/sda4 2701 9964 58348080 5 Extended /dev/sda5 2701 9964 58348048+ 83 Linux So, I have an identical second disk (sdb) connected... My question is: How can I build a RAID 1 of all my particions of sda using mdadm? Something like this: /dev/md0 --> /dev/sda1 and /dev/sdb1 /dev/md1 --> /dev/sda2 and /dev/sdb2 /dev/md2 --> /dev/sda5 and /dev/sdb5 Regards Israel

2 1

Ctrl Alt +/-
by Chris Peikert 12 Apr '06

12 Apr '06

I guess my CentOS is screwed up because that function doesn't work. Only way to resize it was to go into the menu areas and set it there.

2 2

CentOS-announce Digest, Vol 14, Issue 5
by centos-announce-request＠centos.org 12 Apr '06

12 Apr '06

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. CESA-2006:0412-001 CentOS 4 i386 Horde - security update (EXTRAS only) (Johnny Hughes) 2. CESA-2006:0412-001 CentOS 4 x86_64 Horde - security update (EXTRAS only) (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 12 Apr 2006 05:05:03 -0500 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2006:0412-001 CentOS 4 i386 Horde - security update (EXTRAS only) To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <1144836303.9603.216.camel(a)myth.home.local> Content-Type: text/plain; charset="us-ascii" CESA-2006:0412-001 CentOS 4 i386 Horde - security update (EXTRAS only) This is an update to the Horde e-mail system currently in the CentOS Extras repository. This update rolls in the 3.1.1 Horde Application Framework and updates for all the below listed components. The following security issues are addressed in this upgrade: http://janschneider.de/cweb/home/index,channel,25,story,263.html ------------------------- When performing this upgrade, it is _CRITICAL_ that you also follow any upgrade requirements on the Horde website for the component in question as part of the upgrade. I will list each page and a link in this announcement that the horde website says to be addressed: 1. Horde (see the "Upgrading Horde from 3.0.x to 3.1.x" section and the "Upgrading Horde from 3.1 to 3.1.1" section): http://www.horde.org/horde/docs/?f=UPGRADING.html 2. IMP (see the "Upgrading IMP From 4.0.x To 4.1.x" section) http://www.horde.org/imp/docs/?f=UPGRADING.html 3. Ingo (see the "Upgrading Ingo From 1.0.x To 1.1.x" section) http://www.horde.org/ingo/docs/?f=UPGRADING.html 4. Turba (see the "Upgrading to Turba 2.1" section) http://www.horde.org/turba/docs/?f=UPGRADING.html ------------------- As with any upgrade, you will need to look at any .rpmnew or .rpmsave files that are created and set your configuration parameters after upgrade. ------------------- The following files are available and syncing to the mirrors: i386: gollem-h3-1.0.2-1.c4.noarch.rpm horde-3.1.1-1.c4.noarch.rpm imp-h3-4.1-1.c4.noarch.rpm ingo-h3-1.1-1.c4.noarch.rpm kronolith-h3-2.1-1.c4.noarch.rpm mnemo-h3-2.1-1..c4.noarch.rpm nag-h3-2.1-1.c4.noarch.rpm turba-h3-2.1-1.c4.noarch.rpm src: gollem-h3-1.0.2-1.c4.src.rpm horde-3.1.1-1.c4.src.rpm imp-h3-4.1-1.c4.src.rpm ingo-h3-1.1-1.c4.src.rpm kronolith-h3-2.1-1.c4.src.rpm mnemo-h3-2.1-1..c4.src.rpm nag-h3-2.1-1.c4.src.rpm turba-h3-2.1-1.c4.src.rpm

1 0

How to know it's i586?
by Kai Schaetzl 12 Apr '06

12 Apr '06

I plan to install CentOS 4.3 on some older IBM Netfinity which have Pentium III chips. I see that there is now a i586 pxeboot image for 4.3, I think that's new. Can I use that for Pentium III? Kai

4 7

Multiple ISPs
by Neil Jolly 12 Apr '06

12 Apr '06

I have a situation where I need, what I'll call, a high availability router to provide fail over between a cable service, and adsl service, from 2 separate ISPs. There is no requirement for outside access just high uptime requirements for internet access from the lan to the internet. At present I'm looking at just running a perl, or shell, script to ping the gateway and then fail over to the opposite interface, and vice-versa. Anybody know of a better way to do this, or have any experience with a similar situation? Thanks, Neil Jolly

1 0

Was ( ADP94XX Driver ) | Running Centos 4.3
by Mahayudin Mohd Hashim 12 Apr '06

12 Apr '06

--> Requote: Trying to install Centos 4.3 on IBM eseries with Adaptec 9405 SAS. Fail to install / recognized SAS. Download from IBM RHE4 driver unfortunately did not help. Then I install RHEL 4 / SLES 9 - Running fine. SAS was installed and recognized. Anybody have any idea? -- ----------- ( ) §( (.) (.) )§ ---o000o-(_)-o000o--- Mahayudin Mohd Hashim ------------------------------------------- |SEEK TO UNDERSTAND, THEN TO BE UNDERSTOOD| -------------------------------------------

2 5

Postgrey and Centos 4.2
by Francois Meehan 12 Apr '06

12 Apr '06

Hi, We have implemented postgrey (postgrey-1.24, compiled from source package) on a centos 4.3 server. It works except for the whitelistings, in file postgrey_whitelist_clients, no matter what domain we enter, their incoming mails gets greylisted. I have posted this question to postgrey list but have not received anything yet. I works OK on a centos 4.1 server. Has anyone experienced similar problems? Regards, Francois

2 3

Would like to install mplayer on CentOS 4.3 via yum
by Richard E Miles 11 Apr '06

11 Apr '06

I would like to install mplayer on CentOS 4.3 using yum. Ist ther a repo file that would allow me to do this? thanks -- Richard Miles Federal Way WA. USA registered linux user 46097

2 2

Thanks
by Chris Peikert 11 Apr '06

11 Apr '06

Thanks for the help guys. To resize my screen I had to go through the GUI part and change it but unlike Microsoft it makes me reboot in order for it to take affect which sucks. The Ctrl Alt +/- does not work. As for adding a printer someone finally gave me the link to the correct document which showed how to do it. I received a link where you can download the CentOS manual in PDF format: http://www.centos.org/docs/4/pdf/ but the guy didn't tell me which manual I'm suppose to download. I cant tell what's what by the name so unless someone here can point me in the right directions I'm still waiting on their response.

10 16

RE: [CentOS] yum update conflict
by Bowie Bailey 11 Apr '06

11 Apr '06

Jim Perrin wrote: > On 4/11/06, Bowie Bailey <Bowie_Bailey(a)buc.com> wrote: > > I updated my i386 systems without any problems, but when I tried to > > update one of my x86_64 systems, I got an error from yum. > > > > Transaction Check Error: file /usr/include/libdevmapper.h from > > install of device-mapper-1.02.02-3.0.RHEL4 conflicts with file from > > package device-mapper-1.01.04-1.0.RHEL4 > > > > So it can't install the newer package because it conflicts with the > > older package??? What's going on here? > > > > Should I force the upgrade in this case, or is there a better > > solution? > > That doesn't look right. Create a ~/.rpmmacros file for your user and > root with the following line > > %_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch} > > then rerun yum and see if the arch values listed are the same. With > the line above, instead of device-mapper-1.01.04-1.0.RHEL4 it should > show up as device-mapper-1.01.04-1.0.RHEL4.x86_64 Did that, but it didn't seem to affect anything. But you did manage to jump-start a few brain cells. Yum was installing the x86_64 version because of a dependency. The i386 package was also installed, but wasn't being upgraded. Once I specified device-mapper on the yum update line, it grabbed both packages and continued on. Thanks for the help! -- Bowie

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss