Discuss

discuss@lists.centos.org

1 participants
34753 discussions

Big trouble: can't start server after new kernel
by Mário Gamito 16 Jun '05

16 Jun '05

Hi, I have this file server with CentOS 4.0 Each time a new kernel comes out, i have to recompile it, becuse i need Appletalk support and the kernel doesn't have it. I've done this before many times and in other servers, and all went well. Now, in this particular server, with the new 2.6.9-11, after i've recompiled it, created the .img and edited grub, the machine doesn't start at all. It says it can't find the kernel image. I cannot even boot with older kernels. To worsten things, i have LVM, so "linux rescue" tells me there's no Linux installation in the server and leaves me with a prompt. Now, i can mount /boot because it is outside the LVM, but when i do it, i lost access to any command, even a mere ls. Tried to pre-copy vi before the /boot mount and could access /boot/grub/menu.lst Everything seems fine, the files are all in /boot ...!!! Do i need to run grub command after editing menu.lst ? Never did that. And why can't i boot from older kernels ? Now, the really nasty thing: somehow, i don't have the smallest hint, i had a 500 GB external USB disk to make the backups, and the "linux rescue" erased it :( :( :( Bogles me!!! Please help me. This one can cost me the job. Loosing 300 GB of files from ~ 100 users on the file server is unforgiven. Any help would be apreciated. Warm Regards, Mário Gamito

2 2

CentOS 4.1
by alex＠milivojevic.org 16 Jun '05

16 Jun '05

Question about differences in RHEL 4.1 and CentOS 4.1 organization. Does CentOS follows same organization as RHEL? I don't see separate directory for 4.1 on Red Hat's ftp server (well, the public part of it, with SRPM packages), seems like all the updates were simply dumped into the 4.0 updates area, so basically doing normal system upgrade will bump all RHEL 4.0 systems to 4.1. On the other hand, on CentOS site, there is a separate directory for 4.1, with distinct set of packages for 4.1 that are not present in 4.0 update area. So basically, one would need to manually point yum to 4.1 directory tree to fully update system with latest bug fixes. Is this difference in approach intentional? Or the acutal update process (for those with RHEL subscriptions) is actually like the one for CentOS? How do you determine what packages were "regular" updates, and which packages were part of U1? ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

10 13

Re: Burning CDs
by Bryan J. Smith <b.j.smith＠ieee.org> 15 Jun '05

15 Jun '05

From: centos(a)911networks.com > Hi, > I have just installed 4.1 on a new Dell Latitude d610. It does > not automount the CDs. When I mount the CD manually I get: > $mount /media/cdrecorder > mount: block device /dev/hdc is write-protected, mounting read-only First off, there is a multitude of understanding that is required. Most consumers are not aware of many differences between CD-R v. CD-RW access, CD-R v. CD-RW filesystems, etc... In Windows, some of this is hidden from you to a point, but not all. E.g., you use a program to "record" whereas you directly access the drive letter to to "read/write." Windows only lets you "record" to CD-R (or CD-RW emulating CD-R), and won't "read/write" to anything but CD-RW (with a non-ISO9660 fs). These two processes are actually _different_. What type of CD did you insert? A CD-RW? CD-R? Or CD-ROM? Also note that CDs are not "formatted read/write" with ISO9660. ISO9660 is a linear, byte-by-byte track, that is not modifyable (most specifically, data is a "Yellow Book" track of ISO9660). You have to use _another_ filesystem to have "read/write." UDF is its replacement, although almost any filesystem can be used. As I said, a multitude of understanding. > The CD writer is an Philips IDE: CDRW/DVD-ROM CDD5263 There is some "read/write" support for CD-RW in kernel 2.6. I haven't messed with it personally. Otherwise, you pre-master an .iso file with "mkisofs," and then you record with "cdrecord." There are GUI tools build around those 2 programs to help you. That's for CD-R (or CD-RW emulating CD-R). > Here is my mtab: > $ cat /etc/mtab > /dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0 > none /proc proc rw 0 0 > none /sys sysfs rw 0 0 > none /dev/pts devpts rw,gid=5,mode=620 0 0 > usbfs /proc/bus/usb usbfs rw 0 0 > /dev/sda1 /boot ext3 rw 0 0 > none /dev/shm tmpfs rw 0 0 > none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0 > /dev/hdc /media/cdrecorder iso9660 ro,nosuid,nodev,user=froggy 0 0 > How do I change /dev/hdc /media/cdrecorder iso9660 ro to rw? You can't. You can't really "read/write" anything that is ISO9660. It is clear that this CD media (CD-RW?) was written as ISO9660. All you can do is append additional sessions/tracks (if CD-R), or re-format it (if CD-RW). These are just things that some Windows tools "hide" from you. But you still probably need to know about them. > $ cat /etc/fstab > # This file is edited by fstab-sync - see 'man fstab-sync' for details > /dev/VolGroup00/LogVol00 / ext3 defaults 1 1 > LABEL=/boot /boot ext3 defaults 1 2 > none /dev/pts devpts gid=5,mode=620 0 0 > none /dev/shm tmpfs defaults 0 0 > none /proc proc defaults 0 0 > none /sys sysfs defaults 0 0 > /dev/VolGroup00/LogVol01 swap swap defaults 0 0 > /dev/hdc /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0 Stick in a new CD-RW media that has been formatted UDF and see what happens. -- Bryan J. Smith mailto:b.j.smith@ieee.org

1 0

Sound card under CentOS 4
by Harper, Patrick 15 Jun '05

15 Jun '05

I am swapping my laptop over to CentOS and for some reason alsa swapped my headphone jack and speakers designations during the install. I got it so that my sounds work but was wondering how to swap them back so they are defined/labeled right and why it might have done it in the first place Thanks for your help ----------------------------------------- Disclaimer: This electronic message, including any attachments, is confidential and intended solely for use of the intended recipient(s). This message may contain information that is privileged or otherwise protected from disclosure by applicable law. Any unauthorized disclosure, dissemination, use or reproduction is strictly prohibited. If you have received this message in error, please delete it and notify the sender immediately.

1 0

Re: New Server Recommendation -- Hot-Swap SATA enclosure ...
by Bryan J. Smith <b.j.smith＠ieee.org> 15 Jun '05

15 Jun '05

[ Yes, SP^M'n the list with follow-ups to myself ;-] From: Bryan J. Smith > If you are building a new system with such storage requirements, > I would really push you towards a 3Ware Escalade 8006-2 or 8506-4. When cost is supreme, then just a Escalade 7006-2 or 8006-2 with (2) [P]ATA or [S]ATA drives is what you want. It only adds ~$125 to system cost. When you want to minimize cost, but also minimize troubles, I recommend an Escalade 8506-4LP with an EN-8721A02 (Beige) or EN-8721B02 (Black) 5.25" x 3U (3xHH) internal enclosure. SATA was explicitly designed for hot-swap with fixed, SCA-like, staggered, fixed-position connectors with _no_ extra interconnect (i.e., like SCA SCSI drives, SATA drives _should_ connect _directly_ to the backplane, and the "can" is just a frame/handle), so _avoid_ doing such with [P]ATA which is only asking for issues. The EN-8721x02 will only set you back $150, so it's well worth it (especially when you're already spending $300 for the Escalade 8506-4LP, it's only 50% more). It's also nice to have an "extra can" for either holding a spare, or mounting a replacement without having to take one of the existing drives out before it is replaced. Enlight EN-8721: http://us.enlightcorp.com/products/server/detel.php?serial=42 Enlight EN-8721_SATA (x02) Guide: http://us.enlightcorp.com/products/server/pdf_files/EN-8721_SATA.pdf -- Bryan J. Smith mailto:b.j.smith@ieee.org

1 0

Re: New Server Recommendation -- disk label strategy, quotas, etc...
by "Bryan J. Smith <b.j.smith＠ieee.org>" 15 Jun '05

15 Jun '05

> LVM/LVM2 helps reduce this, but I still like to use the approach > (except I just don't make spares, I just reserve 15-30% of disk > space for LVM/LVM2). Let me clarify that -- I still put the _whole_ disk under LVM/LVM2 (maybe leaving a legacy BIOS/DOS primary 256MB in a pre-formatted FAT16 if I need it for firmware updates). But instead of pre-allocating "spares" of each size (essential/support/discretionary), I reserve 15-30% of the disk for future allocation by LVM/LVM2. -- Bryan J. Smith mailto:b.j.smith@ieee.org

1 0

Re: New Server Recommendation -- disk label strategy, quotas, etc...
by "Bryan J. Smith <b.j.smith＠ieee.org>" 15 Jun '05

15 Jun '05

From: Mike Kercher <mike(a)CamaroSS.net> > I'm about to deploy a new server for hosting sites and email for a > number of small individuals using a CentOS 4 box. I've been looking > for a recommended installation guide for RHEL4/CentOS4 giving > recommended disk partitioning I have personal recommendations I follow. One thing I really try to do is make 2-3 "classes" of filesystem sizes, with 1 "spare" for each. That way I can flop around filesystems, accomodate additions, etc... LVM/LVM2 helps reduce this, but I still like to use the approach (except I just don't make spares, I just reserve 15-30% of disk space for LVM/LVM2). E.g., the "essential" class is typically 2-8GB each. The "support" class is typically 8-64GB each. The "discretionary" class is typically 64+GB each. For all systems, I typically do these "essential" classes: / /tmp /var I also typically create the following "support" classes: /usr /usr/local (and a symlink from /opt -> /usr/local) And more "support" class filesystems for servers: /var (instead of an "essential" size) /srv (newer FHS 2.3+ compliant systems) /var/log /var/lib (application, database, etc... servers) /var/mail (mail servers) /var/spool (mail, print, etc... servers) /var/www (web servers) /var/ftp (FTP servers) In some cases -- FHS 2.3+ compliant -- these are under /srv instead of /var. If I want local data/temporary storage, I typically create of the "discretionary" size: /export|home/(systemname) I like to make at least _3_ "discretionary" size, 2 mounted with 1 spare, so 1/3rd each. Again, in the day of LVM/LVM2, I typically just reserve 15-30% of the disk allocation instead of making pre-made spares of each class -- but I would at least make _2_ "discretionary" size (instead of one big one). I also use "/export" when I know I'm going to be exporting them via NFS (and setting up my NIS/LDAP autmounter maps accordingly). Otherwise I use /home. Even if I'm not sure I'm going to export via NFS, if I'm sharing via SMB, then I put them under /export. In a nutshell, if they are network mountable (for whatever protocol), they are under /export. > as well as quotas. I've not used quotas with LVM yet. Don't quote me, but quotas are a filesystem issue and shouldn't matter with LVM/LVM2 disk labels. I'd personally like to see a performance evaluation of Ext3 v. XFS _with_ quota operations. Most comparisons these days seem to be "raw" block operations -- whether big or small -- instead of disk operations sysadmins would normally do day-to-day. > This box is going to have an 80 IDE system drive, an 80G SATA and a > 250G SATA for everything else. One thing I want to be sure of is that > I don't run out of space for the mail spools in /var/spool/mail. If you are building a new system with such storage requirements, I would really push you towards a 3Ware Escalade 8006-2 or 8506-4. Have you already purchased the hard drives? If so, then merely buy a 2nd 80GB SATA and 2nd 250GB SATA with a 8506-4 and use RAID-1 for each. If not, then just buy a cheaper 8006-2 and use RAID-1 with (2) 300GB disks (you might consider this even if you already have some drives). > Does anyone know of a guide for this online? I think sysadmins differ so widly that there is no uniform approach. Even my 2-3 class approach is rather dated in the age of LVM/LVM2, although I continue to use it out of habit. > I wish Johnny had a guide like this on his site :) Well, I'm sure most of my approaches come from SunOS/Solaris even before Linux really caught on, much less the Linux FHS, more recent updates, etc... -- Bryan J. Smith mailto:b.j.smith@ieee.org

1 0

New Server Recommendation
by Mike Kercher 15 Jun '05

15 Jun '05

I'm about to deploy a new server for hosting sites and email for a number of small individuals using a CentOS 4 box. I've been looking for a recommended installation guide for RHEL4/CentOS4 giving recommended disk partitioning as well as quotas. I've not used quotas with LVM yet. This box is going to have an 80 IDE system drive, an 80G SATA and a 250G SATA for everything else. One thing I want to be sure of is that I don't run out of space for the mail spools in /var/spool/mail. Does anyone know of a guide for this online? I wish Johnny had a guide like this on his site :) Mike

1 0

CentOS-announce Digest, Vol 4, Issue 8
by centos-announce-request＠centos.org 15 Jun '05

15 Jun '05

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-2005:415 Low CentOS 4 ia64 squid - security update (Pasi Pirhonen) 2. CESA-2005:504 Moderate CentOS 4 ia64 telnet - security update (Pasi Pirhonen) 3. CESA-2005:415 Low CentOS 3 ia64 squid - security update (Pasi Pirhonen) 4. CESA-2005:504 Moderate CentOS 3 ia64 telnet - security update (Pasi Pirhonen) 5. CESA-2005:504 Moderate CentOS 3 s390(x) telnet - security update (Pasi Pirhonen) 6. CESA-2005:415 Low CentOS 4 x86_64 squid - security update (Johnny Hughes) 7. CESA-2005:415 Low CentOS 4 i386 squid - security update (Johnny Hughes) 8. CESA-2005:504 Moderate CentOS 4 i386 telnet - security update (Johnny Hughes) 9. CESA-2005:504 Moderate CentOS 4 x86_64 telnet - security update (Johnny Hughes) 10. CESA-2005:415 Low CentOS 3 s390(x) squid - security update (Pasi Pirhonen) 11. CESA-2005:504 Moderate CentOS i386 telnet - security update (Tru Huynh) 12. CESA-2005:415 Low CentOS i386 squid - security update (Tru Huynh) 13. CESA-2005:504 Moderate CentOS x86_64 telnet - security update (Tru Huynh) 14. CESA-2005:415 Low CentOS x86_64 squid - security update (Tru Huynh) 15. CESA-2005:504-00: Moderate CentOS 2 i386 telnet security update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Tue, 14 Jun 2005 23:28:53 +0300 From: Pasi Pirhonen <upi(a)iki.fi> Subject: [CentOS-announce] CESA-2005:415 Low CentOS 4 ia64 squid - security update To: centos-announce(a)centos.org Message-ID: <20050614202853.GV21054(a)core.upi.iki.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2005:415 https://rhn.redhat.com/errata/RHSA-2005-415.html The following updated files have been uploaded and are currently syncing to the mirrors: files: updates/ia64/RPMS/squid-2.5.STABLE6-3.4E.9.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://iki.fi/upi/

1 0

Centos 3.x telnet update problem
by Les Mikesell 15 Jun '05

15 Jun '05

A 'yum update' on a Centos 3.x machine is giving: Getting telnet-0.17-26.EL3.3.i386.rpm telnet-0.17-26.EL3.3.i386 100% |=========================| 48 kB 00:00 Error: Unsigned Package /var/cache/yum/update/packages/telnet-0.17-26.EL3.3.i386.rpm Is this a bad package? -- Les Mikesell lesmikesell(a)gmail.com

2 1

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