Discuss January 2014

discuss@lists.centos.org

194 participants
172 discussions

Re: [CentOS] Booting Software RAID
by Matt 24 Jan '14

24 Jan '14

>> I installed Centos 6.x 64 bit with the minimal ISO and used two disks >> in RAID 1 array. >> >> Filesystem Size Used Avail Use% Mounted on >> /dev/md2 97G 918M 91G 1% / >> tmpfs 16G 0 16G 0% /dev/shm >> /dev/md1 485M 54M 407M 12% /boot >> /dev/md3 3.4T 198M 3.2T 1% /vz >> >> Personalities : [raid1] >> md1 : active raid1 sda1[0] sdb1[1] >> 511936 blocks super 1.0 [2/2] [UU] >> md3 : active raid1 sda4[0] sdb4[1] >> 3672901440 blocks super 1.1 [2/2] [UU] >> bitmap: 0/28 pages [0KB], 65536KB chunk >> md2 : active raid1 sdb3[1] sda3[0] >> 102334336 blocks super 1.1 [2/2] [UU] >> bitmap: 0/1 pages [0KB], 65536KB chunk >> md0 : active raid1 sdb2[1] sda2[0] >> 131006336 blocks super 1.1 [2/2] [UU] >> >> My question is if sda one fails will it still boot on sdb? Did the >> install process write the boot sector on both disks or just sda? How >> do I check and if its not on sdb how do I copy it there? > no, you need to run grub-install /dev/sdb manually > keep in mind you need to do the same after replace a disk > the first part of grub is outside the RAID itself in the MBR # file -s /dev/sda /dev/sda: x86 boot sector; GRand Unified Bootloader, stage1 version 0x3, boot drive 0x80, 1st sector stage2 0x849fc, GRUB version 0.94; partition 1: ID=0xee, starthead 0, startsector 1, 4294967295 sectors, extended partition table (last)\011, code offset 0x48 # file -s /dev/sdb /dev/sdb: x86 boot sector; GRand Unified Bootloader, stage1 version 0x3, boot drive 0x80, 1st sector stage2 0x849fc, GRUB version 0.94; partition 1: ID=0xee, starthead 0, startsector 1, 4294967295 sectors, extended partition table (last)\011, code offset 0x48 I am guessing this is saying its present on both? I did nothing to copy it there so it must have done it during the centos 6.x install process.

5 8

ata marvel errors after kernel upgrade
by Steve Brooks 24 Jan '14

24 Jan '14

Hi, After upgrading to kernel 2.6.32-431.1.2.el6.x86_64 the messages below keep appearing in "/var/log/messages". -------------------------------------------------------------------------- ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 ata16.00: irq_stat 0x40000001 scsi 16:0:0:0: [sg18] CDB: Read Capacity(10): 25 00 00 00 00 00 00 00 00 00 ata16.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation) ata16: hard resetting link ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata16.00: configured for UDMA/66 ata16: EH complete -------------------------------------------------------------------------- Output from "sginfo -i /dev/sg18" shows Command Queueing 0 Vendor: Marvell Product: 91xx Config Revision level: 1.01 This is an unused SATA chipset on a the motherboard, no devices are plugged into it. Also oddly I am getting [root@mach~]# sginfo -r /dev/scanner-sg18 /dev/scanner /dev/sdb /dev/sda "/dev/sdb" and "/dev/sda" are HD's no idea what "/dev/scanner" is? [root@mach~]# sginfo /dev/scanner INQUIRY response (cmd: 0x12) ---------------------------- Device Type 3 Vendor: Marvell Product: 91xx Config Revision level: 1.01 ------------------------------------------------------------------------- There is no scanner attached to this machine so I am confused at the above output. Steve

2 2

Can't install Python i686 on x86_64 system (centos 6.5)
by Brian Bernard 23 Jan '14

23 Jan '14

Hello, This is my first time posting to the list adn I've run into a problem trying to install python-2.6.6-51.el6.i686 on my x86_64 bit system, which I updated to CentOS 6.5 this evening. I receive the following error: error: Failed dependencies: libpython2.6.so.1.0 is needed by python-2.6.6-51.el6.i686 python-libs(x86-32) = 2.6.6-51.el6 is needed by python-2.6.6-51.el6.i686 libpython2.6.so.1.0 is needed by python-devel-2.6.6-51.el6.i686 Now I've downloaded the python and python-devel i686 versions from a mirror and tried to install locally with 'sudo rpm -Uvh python-2.6.6-51.el6.i686 python-devel-2.6.6-51.el6.i686', but I always receive the same error. I tried 'sudo yum install python-2.6.6-51.el6.i686 python-devel-2.6.6-51.el6.i686 with again the same error. Brian Bernard

4 6

CentOS-announce Digest, Vol 107, Issue 12
by centos-announce-request＠centos.org 23 Jan '14

23 Jan '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:0085 CentOS 6 python Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 22 Jan 2014 11:54:29 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0085 CentOS 6 python Update To: centos-announce(a)centos.org Message-ID: <20140122115429.GA17044(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0085 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0085.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7ffc935bd1b74cc8f47aa56a89b18d076fb147c161d600ca4e8bb32f29e8d4d5 python-2.6.6-52.el6.i686.rpm 0d6ba30030d477e68b68a99c26aca8620439a56d8ed408827bc4e904f64bca04 python-devel-2.6.6-52.el6.i686.rpm 0ac4c0b448a9e9adf1fa69eaad6711aa59da693d3f81bff90078d481e55ead27 python-libs-2.6.6-52.el6.i686.rpm 395628883b0eaf52d0cde980f5aa8496aff2ad9fab402eee3c29d2729d9d449a python-test-2.6.6-52.el6.i686.rpm 9d064def2836ed06520a39b927ee2c88070c6fa762e2ecc6f6304964bd050349 python-tools-2.6.6-52.el6.i686.rpm 96af917955dd711ae2f91bec07615aba1f5518dbb8eccf9f75616d10a3e48b33 tkinter-2.6.6-52.el6.i686.rpm x86_64: 11b9dad91ba9df1f0f8f2749e1b57dce79f8125e8616a7a64274a21fdf35a6a2 python-2.6.6-52.el6.x86_64.rpm 44d27cb6b6cc1a0205c8f2ad2f6c054124f0d1de2ac872d126199ce7108b9fb0 python-devel-2.6.6-52.el6.x86_64.rpm 306f7507da559789672f2daab6162cecabde273b586bba1a559068ea08c0f4cc python-libs-2.6.6-52.el6.x86_64.rpm f454a64169260d6054fdc3fc8cb1facf00314efb7d3a5bd80f83875bbbecaa0b python-test-2.6.6-52.el6.x86_64.rpm 8e73ae937c9ce29a1aebd2b97b04f69d6cd2132df15d1974f768364cf743de9e python-tools-2.6.6-52.el6.x86_64.rpm 1a36833025bf5ca09caf35030b25122fd07e42fb50bfd3ab2f691c44d21b305f tkinter-2.6.6-52.el6.x86_64.rpm Source: f35557314a7f4b5ad15ad3cf1bef934f4a0eec26aaea57a8ca475efee237a5f8 python-2.6.6-52.el6.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 107, Issue 12 ************************************************

1 0

Re: [CentOS] Problem installing Centos 6.4/6.5 from USB stick seen as HDD by BIOS
by Emmanuel Noobadmin 23 Jan '14

23 Jan '14

On 1/23/14, Steve Clark <sclark(a)netwolves.com> wrote: > can you use -o remount in the mount command? For some odd reason, my current attempt to do this had no problem mounting the install USB drive. Which then led me to realize that the problem is something else. After figuring out where anaconda keeps log, I found that the error isn't that it couldn't find the drive. Rather, it couldn't find the file: media/repodata/0dafccfdbf892f02acca8267ade4bdcee7280a682e65dc7e29145f3341fd7a8c-primary.sqlite.bz2 (the target machine doesn't have network so there might be typo in the filename due to manual copy) listing the USB drive shows that the repodata directory has the file BUT missing the -primary.sqlite.bz2 extension. In fact, none of the human-unfriendly file names have any extension. In case it was an error transferrring the ISO to USB, I checked the ISO and found that the repodata directory appears the same. In comparison, browsing online mirrors such as http://ftp.linux.ncsu.edu/pub/CentOS/6.5/os/x86_64/repodata/ shows all the similar looking files have extensions. But the ISO's md5/sha1 checksums are correct. Based on the information in TRANS.TBL, I added the extensions to the files and anaconda was able to proceed to the package selection. I will start a new email to check if there is a problem with the ISO on mirrors.

1 0

Problem installing Centos 6.4/6.5 from USB stick seen as HDD by BIOS
by Emmanuel Noobadmin 23 Jan '14

23 Jan '14

I'm trying to install C6.5 on a USB stick (created using Fedora LiveUSB Creator). The problem is the machine using an Intel ITX board sets the USB stick as a HDD instead of a CDROM. During install, the DVD couldn't find the installer automatically and I must choose the HDD option for it to proceed to network/timezone/storage setup. After the storage partitioning, it will throw an error that it is unable to read package metadata. Although there is an option to edit the repo information, there isn't an option to specify a hard disk. Switching to console, attempts to mount /dev/sdb as /dev/cdrom or /mnt/sr0 met with failure because the USB drive is in use. Previously I used 6.4 and downloaded 6.5 thinking it might just be an issue with 6.4 but both failed at the same point. There doesn't appear to be anybody else who encounter the same problem on a quick google. Is this considered a bug with anaconda or is there some kind of workaround such as forcing the system to mount /dev/sdb as cdrom despite already being mounted/busy?

4 4

ipmi_si error on booting
by Timothy Murphy 22 Jan '14

22 Jan '14

I'm getting the (unintelligible to me) error message ipmi_si: Could not set up I/O space ERST: Failed to get Error Log Address Range when I try to boot any OS on the grub menu apart from the one I last installed. (Actually, Windows also boots properly.) I wonder if anyone has had this error message, and worked out where it comes from? I googled for it, and it has come up many times; but there seem to be several entirely different suggested causes. I am running CentOS-6.5 on an HP MicroServer. I mention that as some of the explanations suggest that it only occurs on certain machines. -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

3 2

migrate ext3 to ext4
by Jerry Geis 22 Jan '14

22 Jan '14

Hi all, I issued the commands on a single disk system: with two partitions / is linux sda1 and /home is sda3 yum -y update yum -y install e4fsprogs reboot umount /home tune2fs -O extents,uninit_bg,dir_index /dev/sda3 e2fsck -yfDC0 /dev/sda3 That worked just fine. I then had a different system that is software raid. where / is linux and md0 and /home is md1 yum -y update yum -y install e4fsprogs reboot umount /home tune2fs -O extents,uninit_bg,dir_index /dev/md1 at this point I get an error that invalid options for tune2fs Why is that and what to do next... The single disk sda3 worked fine. shouldnt the md1 work also. Thanks, Jerry

3 2

CentOS-announce Digest, Vol 107, Issue 11
by centos-announce-request＠centos.org 22 Jan '14

22 Jan '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:0048 CentOS 6 squid Update (Johnny Hughes) 2. CEBA-2014:0084 CentOS 6 firefox Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 21 Jan 2014 13:31:06 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0048 CentOS 6 squid Update To: centos-announce(a)centos.org Message-ID: <20140121133106.GA63218(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0048 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0048.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b8a0be85039b91b8dfe2cf96bdecbd84f08addc632353e872b711a878265597d squid-3.1.10-20.el6_5.i686.rpm x86_64: f3ffb6a5cfca53280e9b16f44953df3c7cc4342fadcfb0da0364e70c37b65540 squid-3.1.10-20.el6_5.x86_64.rpm Source: 146b6ddd11948c04afe936a37353820c0ee7da67d97c29b7e715ef135b686d9c squid-3.1.10-20.el6_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 22 Jan 2014 04:26:22 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0084 CentOS 6 firefox Update To: centos-announce(a)centos.org Message-ID: <20140122042622.GA10062(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0084 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0084.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d4be792a1455cbcbc0bf87520621be381b7058bb9b0d0cbab7de5ef31ca9ae20 firefox-24.2.0-6.el6.centos.i686.rpm x86_64: d4be792a1455cbcbc0bf87520621be381b7058bb9b0d0cbab7de5ef31ca9ae20 firefox-24.2.0-6.el6.centos.i686.rpm 91c18e09db27f0da1ab4ee78f1e55fb6ed7aa5146136c72a72d1f8d8e07888c2 firefox-24.2.0-6.el6.centos.x86_64.rpm Source: b146296bac575fafe20ed8435fbd9cbd9dbfbf91b03b98a340a95c01a2df252f firefox-24.2.0-6.el6.centos.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 107, Issue 11 ************************************************

1 0

XFS : Taking the plunge
by Steve Brooks 21 Jan '14

21 Jan '14

Hi All, I have been trying out XFS given it is going to be the file system of choice from upstream in el7. Starting with an Adaptec ASR71605 populated with sixteen 4TB WD enterprise hard drives. The version of OS is 6.4 x86_64 and has 64G of RAM. This next part was not well researched as I had a colleague bothering me late on Xmas Eve that he needed 14 TB immediately to move data to from an HPC cluster. I built an XFS file system straight onto the (raid 6) logical device made up of all sixteen drives with. > mkfs.xfs -d su=512k,sw=14 /dev/sda where "512k" is the Stripe-unit size of the single logical device built on the raid controller. "14" is from the total number of drives minus two (raid 6 redundancy). Any comments on the above from XFS users would be helpful! I mounted the filesystem with the default options assuming they would be sensible but I now believe I should have specified the "inode64" mount option to avoid all the inodes will being stuck in the first TB. The filesystem however is at 87% and does not seem to have had any issues/problems. > df -h | grep raid /dev/sda 51T 45T 6.7T 87% /raidstor Another question is could I now safely remount with the "inode64" option or will this cause problems in the future? I read this below in the XFS FAQ but wondered if it have been fixed (backported?) into el6.4? ""Starting from kernel 2.6.35, you can try and then switch back. Older kernels have a bug leading to strange problems if you mount without inode64 again. For example, you can't access files & dirs that have been created with an inode >32bit anymore."" I also noted that "xfs_check" ran out of memory and so after some reading noted that it is reccommended to use "xfs_repair -n -vv" instead as it uses far less memory. One remark is so why is "xfs_check" there at all? I do have the option of moving the data elsewhere and rebuilding but this would cause some problems. Any advice much appreciated. Steve

3 4

← Newer
1
...
4
5
6
7
8
9
10
...
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss January 2014