Re: [CentOS] livemedia-creator --make-pxe-live CentOS 7
Oh, alright my specific issue is just about creating the actual pxe image.. not what happens after -Original Message- From: CentOS On Behalf Of R C Sent: Thursday, December 26, 2019 12:18 PM To: centos@centos.org Subject: Re: [CentOS] livemedia-creator --make-pxe-live CentOS 7 I have "issues" with later versions of Centos/RHEL 7 also. PXE boot seems to work, but after the new kernel kexec's, it seems to drop the NICS and further in the process for some reason, the nics never come up, which leads to all kindsof issues of course (trying to boot a cluster that way). I also have the impression that it is a dracut issue, however, I have not pinpointed it yet. Ron On 12/26/19 9:57 AM, Drew Weaver wrote: > Hello, > > I am trying to build a PXE boot image for CentOS 7. > > livemedia-creator --make-pxe-live --ks=ks --no-virt > > It runs the entire process and then it says: > > losetup: /dev/: detach failed: Inappropriate ioctl for device > 2019-12-26 11:49:47,293: Disk Image install successful > 2019-12-26 11:49:47,293: working dir is /var/tmp/tmpKwqC77 > mount: /dev/loop0 is write-protected, mounting read-only > mount: unknown filesystem type '(null)' > 2019-12-26 11:49:52,301: Command '['mount', '-o', 'loop', > '/var/tmp/diskJVpsJd.img', '/var/tmp/lorax.imgutils.OtV8Yh']' returned > non-zero exit status 32 > > I then tried it on CentOS 8 and had the same problem until I installed the > dracut-live package but that package doesn't exist on CentOS 7. > > I will point out that it seems to work fine with make-iso, just not > make-pxe-live. So there is probably a package it needs that I don't know > about. Has anyone gotten this to work at all? > > Since it is a disk/image issue this is the part of the ks relevant to disks: > > # Disk partitioning information > reqpart > part / --fstype="ext4" --size=4000 > part swap --size=1000 > zerombr > clearpart --all > bootloader --location=mbr > > Below is my packages part of my kickstart: > > %packages > # Packages needed by anaconda, but not directly required. > # Includes all of the grub2 and shim packages needed, except > # for the grub2-efi-*-cdboot package > @anaconda-tools --optional > @core > anaconda > isomd5sum > kernel > memtest86+ > syslinux > -dracut-config-rescue > dell-system-update > # This package is needed to boot the iso on UEFI > grub2-efi-*-cdboot > grub2-efi-ia32 > %end > > Thanks, > -Drew > > ___ > 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 mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] livemedia-creator --make-pxe-live CentOS 7
Hello, I am trying to build a PXE boot image for CentOS 7. livemedia-creator --make-pxe-live --ks=ks --no-virt It runs the entire process and then it says: losetup: /dev/: detach failed: Inappropriate ioctl for device 2019-12-26 11:49:47,293: Disk Image install successful 2019-12-26 11:49:47,293: working dir is /var/tmp/tmpKwqC77 mount: /dev/loop0 is write-protected, mounting read-only mount: unknown filesystem type '(null)' 2019-12-26 11:49:52,301: Command '['mount', '-o', 'loop', '/var/tmp/diskJVpsJd.img', '/var/tmp/lorax.imgutils.OtV8Yh']' returned non-zero exit status 32 I then tried it on CentOS 8 and had the same problem until I installed the dracut-live package but that package doesn't exist on CentOS 7. I will point out that it seems to work fine with make-iso, just not make-pxe-live. So there is probably a package it needs that I don't know about. Has anyone gotten this to work at all? Since it is a disk/image issue this is the part of the ks relevant to disks: # Disk partitioning information reqpart part / --fstype="ext4" --size=4000 part swap --size=1000 zerombr clearpart --all bootloader --location=mbr Below is my packages part of my kickstart: %packages # Packages needed by anaconda, but not directly required. # Includes all of the grub2 and shim packages needed, except # for the grub2-efi-*-cdboot package @anaconda-tools --optional @core anaconda isomd5sum kernel memtest86+ syslinux -dracut-config-rescue dell-system-update # This package is needed to boot the iso on UEFI grub2-efi-*-cdboot grub2-efi-ia32 %end Thanks, -Drew ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [OT] PXE Boot / image server for non-profit's computers
-Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of m.r...@5-cent.us Sent: Tuesday, April 08, 2014 3:21 PM To: CentOS mailing list Subject: Re: [CentOS] [OT] PXE Boot / image server for non-profit's computers Jason Pyeron wrote: This is the best collection of minds I can think of on this topic, that's why it is on this list. I think it is too subjective for stackoverflow. So here is the problem: The community center has multiple computers for the children (and adult students) to use. These computer are always donated and the hardware is all different. Currently the systems are running Windows (but this may change). Most days the systems are hacked by the kids and all is well, but sometimes the changes to the systems requires a reinstall. The staff are not presently qualified to diagnose any problems. Here is the draft idea: 1. Have a CentOS image / PXE server. This works *really* well - it's how I build/rebuild new servers and workstations. We've got a cgi script that creates a ks file, and we get it started, choose what we're building, and walk away. In somewhere between a dozen and 30 min, it's up, knowing its name, etc. 2. Make a (bootable) utility CD that: * has a program to save the state of the computer to the image server You *really* might want to do that before pxeboot rebuilding it... for legal reasons. He could also always just chain pxeboot the imager to create the backup and then the installer to install the new OS. -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6.5 install
You can simply create two virtual disks from the single RAID-5 volume. Create one that is like 500GB for the OS volume and then create a 2nd one which uses the remainder of the space. -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Kenny Noe Sent: Wednesday, February 26, 2014 3:02 PM To: centos@centos.org Subject: [CentOS] CentOS 6.5 install Hello, I'm a newbie so here's my question. I'm trying to install CentOS 6.5 on a HP Proliant 350e server. This server has 4x 1TB hard drives. I'd like to enable the hardware RAID 5 and stripe all 4 disk into one 3TB logical volume. Then install CentOS on the 3TB volume. However after I install I can't get the server to boot. I know about the MDOS vs GPT labeling issue. I've successfully installed on one (singular) 3TB disk on other servers. I have modified the partition tables, relabeling them to GPT, prior to completing the installs. However I've read that the Anaconda installer still tries to format as MDOS and after installing a Basic server I cannot get it to boot. So, what am I missing? Can I load CentOS on a hardware RAID 5 volume that is 3TB (usable) or am I stuck with what most Google searches say and load the OS on one disk and then after use software RAID to RAID 5 the remaining 3 disk into a /data directory? All help is appreciated. Thanks--Kenny ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LSI MegaRAID experience...
If these drives do not have TLER do not use them with LSI controllers. -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of John Doe Sent: Friday, July 19, 2013 5:13 AM To: CentOS mailing list Subject: Re: [CentOS] LSI MegaRAID experience... The thing that bothers me is that the ctrl sees all the drives at first, later does not see some anymore, and he just forgets about them like they never existed. I would have expected to still see them but in a failed state... Here, megacli just lists info for the remaining drive(s). So I miss all the post mortem info like the SMART status or the error counts if they had any... Am I missing an option to add to megacli to show the failed ones too maybe? Having used HP raid ctrls, I am used to see all drives, even failed ones. Anyway, Ill have to check the drives, backplane and cabling... Thx for all the answers, JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LSI MegaRAID experience...
Not sure about TLER on those Plextors... This is what megacli says: Enclosure Device ID: 252 Slot Number: 0 Drive's position: DiskGroup: 0, Span: 0, Arm: 0 Enclosure position: N/A Device Id: 0 WWN: 4154412020202020 Sequence Number: 2 Media Error Count: 0 Other Error Count: 0 Predictive Failure Count: 0 Last Predictive Failure Event Seq Number: 0 PD Type: SATA Raw Size: 119.242 GB [0xee7c2b0 Sectors] Non Coerced Size: 118.742 GB [0xed7c2b0 Sectors] Coerced Size: 118.277 GB [0xec8e000 Sectors] Sector Size: 0 Logical Sector Size: 0 Physical Sector Size: 0 Firmware state: Online, Spun Up Commissioned Spare : No Emergency Spare : No Device Firmware Level: 1.02 Shield Counter: 0 Successful diagnostics completion on : N/A SAS Address(0): 0x44332211 Connected Port Number: 0(path0) Inquiry Data: P02302103634 PLEXTOR PX-128M5Pro 1.02 FDE Capable: Not Capable FDE Enable: Disable Secured: Unsecured Locked: Unlocked Needs EKM Attention: No Foreign State: None Device Speed: 6.0Gb/s Link Speed: 6.0Gb/s Media Type: Solid State Device Drive: Not Certified Drive Temperature : N/A PI Eligibility: No Drive is formatted for PI information: No PI: No PI Port-0 : Port status: Active Port's Linkspeed: 6.0Gb/s Drive has flagged a S.M.A.R.T alert : No Apart from that, I found the lsi events logs... Command timeout on PD 00(e0xfc/s0) . . . PD 00(e0xfc/s0) Path ... reset Error on PD 00(e0xfc/s0) State change on PD 00(e0xfc/s0) from ONLINE(18) to FAILED State change on VD 00/0 from OPTIMAL(3) to DEGRADED(2) Command timeout on PD 00(e0xfc/s0) PD 00(e0xfc/s0) Path ... reset State change on PD 00(e0xfc/s0) from FAILED(11) to UNCONFIGURED_BAD(1) . . . Exact same behavior for the 2 servers and 3 SSDs... So it seems the ctrl changes them first to failed and then to unconfigured... --- We have experienced similar behavior with (to be blunt, non Intel) SSDs and with spinning rust (without TLER) on Dell PERC controllers (which are the same as LSI controllers) the drives simply fall out of the raid arrays they are in after a random period of time. This seems to just happen with certain SSDs, in the beginning we pushed very hard to try and understand why; now we just use different SSDs. The ones we've had problems with are: OCZ Vertex, Samsung 840/840 pro, etc Ones we've never had issues with are: Intel 520, Intel S3700 I know this doesn't really help you, but you could see if using a different SSD makes the problem go away. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] LSI MegaRAID experience...
John Doe wrote: From: Drew Weaver drew.wea...@thenap.com If these drives do not have TLER do not use them with LSI controllers. Not sure about TLER on those Plextors... snip TLER would only show up on something that looks at a *very* low level on the physical drive. What I know is that you can see it with smartctl - from the man page: scterc[,READTIME,WRITETIME] - [ATA only] prints values and descriptions of the SCT Error Recovery Control settings. These are equivalent to TLER (as used by Western Digital), CCTL (as used by Samsung and Hitachi) and ERC (as used by Seagate). READ- TIME and WRITETIME arguments (deciseconds) set the specified values. Values of 0 disable the feature, other values less than 65 are probably not supported. For RAID configurations, this is typically set to 70,70 deciseconds. Note that knowing this was the result of a *lot* of research a couple-or so years ago. One *good* thing *seems* to be WD's new Red line, which is targeted toward NAS, they say... because they've put TLER back to something appropriate, like 7 sec or so, where it was 2 *minutes* for their desktop drives, and they disallowed changing it in firmware around '09, and the other OEMs followed suit. What makes Red good, if they work, is that they're only about one-third more than the low-cost drives, where the server-grade drives are 2-3 *times* the cost (look at the price of Seagate Constellations, for example). I would also like to note that up until Red were released to had to use RE to get TLER, and now apparently RE, SE, and RED (cost in that order) all support TLER. The thing that worries me about RED is that they're listed as only supporting up to 5 drives in an array, -- how are they limiting that? I think they probably could've just merged RED and SE into one line of drives but I guess they limited RED to 3TB so if you want a 4TB part you have to get the SE. Something in the back of my mind tells me that RE, SE, and Red are the exact same hardware with different FW. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Kickstart just create /boot, recommended swap and / with whatever is left.
Howdy, The default partitioning scheme appears to be: swap /boot / small amount of space /home remainder of space. Is there any way via kickstart to have it just create swap with the recommended size, /boot, and then just / with the remainder without manually specifying the names of the lvs/vgs etc? I figured there would be an autopart -atomic option but that doesn't seem to exist. Any advice? Thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Kickstart just create /boot, recommended swap and / with whatever is left.
Drew Weaver wrote: Howdy, The default partitioning scheme appears to be: swap /boot / small amount of space /home remainder of space. Is there any way via kickstart to have it just create swap with the recommended size, /boot, and then just / with the remainder without manually specifying the names of the lvs/vgs etc? I figured there would be an autopart -atomic option but that doesn't seem to exist. --- Where'd you get the kickstart? You can certainly set it up any way you want, though a large /home seems reasonable if you've only got one drive, unless you want /boot, swap, and /. Btw, the old received wisdom was that swap should be 2-2.5 times RAM; for some years now, though, it's been just 2G, and leave it at that. I just used the 'autopart' command in the kickstart and it automatically put most of the storage in /home. I believe in CentOS 5 the autopart command just did swap /boot and / I realize I can manually partition all 60 of these servers but I'm trying to avoid that also like I said I would prefer not to set the lv/vg names in the kickstart.. Would've been cool if you could just do autopart -atomic like you can with Ubuntu. Thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Unplugging DVI causes Disabling IRQ #11
I posted this as a bug to redhat's bugzilla I think in January of 2011. -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Scott Johnson Sent: Friday, December 09, 2011 11:39 PM To: centos@centos.org Subject: [CentOS] Unplugging DVI causes Disabling IRQ #11 I have some new PC hardware I'm using with the Intel H67 chipset. I created a bzImage I use for a PXE environment for a recovery mode, installing OS images, etc. The new mobo doesn't have a VGA port but instead DVI. Everytime I unplug the DVI cable it seems to cause Disabling IRQ #11. After that the PC is basically unusable. The /proc/interrupts shows that hdd, usb, nic, RAID controller for some reason all share the same interrupt. What the heck? I tried booting with acpi=off and the bios doesn't seem to offer any IRQ/PnP options. Am I missing a specific driver in my bzImage for the H67 chipset or any ideas of what I could try next? It's been a sad day. bash-2.05b# cat /proc/interrupts CPU0 0: 15185951XT-PIC-XTtimer 1: 4XT-PIC-XTi8042 2: 0XT-PIC-XTcascade 7: 75XT-PIC-XTehci_hcd:usb2 8: 1XT-PIC-XTrtc 11:2090574XT-PIC-XTahci, ehci_hcd:usb1, eth0, rr172x I even see a similar error on a fresh CentOS 5.7 install: irq 169: nobody cared (try booting with the irqpoll option) Call Trace: IRQ [800bdf66] __report_bad_irq+0x30/0x7d [800be1a4] note_interrupt+0x1f1/0x232 [800bd6a5] __do_IRQ+0xfa/0x140 [8006d4c1] do_IRQ+0xe9/0xf7 [8005d615] ret_from_intr+0x0/0xa EOI [801a2220] acpi_safe_halt+0x25/0x36 [801a2a88] acpi_processor_idle_simple+0xe6/0x31c [801a29a2] acpi_processor_idle_simple+0x0/0x31c [80048fe2] cpu_idle+0x95/0xb8 [80078a9a] start_secondary+0x479/0x488 handlers: [801fc748] (usb_hcd_irq+0x0/0x55) Disabling IRQ #169 Thanks for any help. -ScottEJ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS5 with Dell Broadcom iSCSI Offload, does it work ?
Hi, I could be wrong here but don't you go into the Broadcom NIC configuration while the server is booting and add the iSCSI target in there and then it should appear as Just Another Volume (TM) to the operating system? I've never tried it but I assume thats how the 'offloading' works. thanks, -Drew -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Antonio da Silva Martins Junior Sent: Friday, September 09, 2011 8:01 AM To: CentOS mailing list Subject: [CentOS] CentOS5 with Dell Broadcom iSCSI Offload, does it work ? Hi all, After finding multiples answers to this question via google, but without making it work on my servers. Has anybody iSCSI Offload working on a Dell Server with Broadcom NICs ? My environment: I'm running CentOS 5.6 CR, on a Dell PowerEdge R710 with Broadcom Corporation NetXtreme II BCM5709 conecting to an EMC CX4-120 SAN, via 2x Cisco 2960G-24TC-L switches. It's working without the iSCSI offload. Thanks in advance, Antonio. -- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Antonio S. Martins Jr. - Support Analyst | Only The Shadow Knows | | Universidade Estadual de Maringá - Brasil| what evil lurks in the | | NPD - Núcleo de Processamento de Dados | Heart of Men! | | E-Mail: asmart...@uem.br / sha...@uem.br | !!! Linux User: 52392 !!! | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Real Programmers don’t need comments — the code is obvious. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS and Bandwidth
-Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Michael Peterson Sent: Sunday, July 10, 2011 9:15 AM To: centos@centos.org Subject: [CentOS] CentOS and Bandwidth I am looking forward to using CentOS 6 soon. I have the torrent running to download and help others download it. I am trying out Scientific Linux 6 while awaiting the arrival of CentOS 6. It took a lot of work to get it installed and configured on a system. I plan to run them both on 2 systems and see what happens. I look forward to the release of CentOS 6.1 soon also. Let me know where I can browse to see if I can help in any areas other than the torrent. If I have a T1 size pipe going out what is my max possible kB out? I have the torrent turned up to 100kB and my VPN still seems responsive. Thanks for all the hard working in getting this release ready. Good job on getting CentOS 5.6 out first however. == 1,540,000 (bps) / 8 * .90 = your maximum throughput in Bps. thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL 6.1 beta
Original Message Subject: Re: [CentOS] RHEL 6.1 beta From: Steve Clark scl...@netwolves.commailto:scl...@netwolves.com To: CentOS mailing list centos@centos.orgmailto:centos@centos.org Date: Tuesday, May 03, 2011 10:40:51 AM On 05/02/2011 10:47 AM, Les Mikesell wrote: On 5/2/2011 8:57 AM, Steve Clark wrote: On 05/02/2011 09:38 AM, Lamar Owen wrote: On Monday, May 02, 2011 06:48:37 AM Christopher Chan wrote: biosdevname for nics...bye bye eth0! Not by default, and according to the release notes only for certain Dell servers ATM. But, yes, a different way of looking at NICs is coming down the pipe. It's about time. EGADS Why? After working with FreeBSD for ten years it so nice not to have to worry is this rl0, vr0, em0, fxp0, bge0, ed0, etc in networking scripts. Why would you want to go back to that? The numbers chosen in the eth? scheme are more or less randomized even on identical hardware, so it is pretty much impossible to prepare a disk to ship to a remote site and have it come up working unattended or clone disk images for a large rollout. If this gives predictable names in bios-detection order it will be very useful. Remote-site support is expensive and typically not great at the quirks of Linux distributions that you need to know to do IP assignments. In my experience with Linux over the last 3 years using Centos and RH I have never seen the ethn device numbering change, and it always corresponds to the hardware vendor marking on the units we use. I'm doing platform validation on a SuperMicro X9SCL and on everything except for RHEL 6 the NIC I am connected to is seen as eth0, on RHEL only it is seen as eth1. These kinds of wacky inconsistencies drive people crazy =) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Hi, Just an update to the list. This issue is still present, I even tried it on a different Intel socket 1155 motherboard (DH61WW) which is about as plain vanilla as it gets. It must be something to do with the onboard video and PCI Express. Has anyone been able to get around this? -Drew -Original Message- From: Kenni Lund [mailto:ke...@kelu.dk] Sent: Thursday, January 20, 2011 6:46 AM To: CentOS mailing list Cc: Drew Weaver Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared 2011/1/18 Drew Weaver drew.wea...@thenap.com: Because the installer doesn't have drivers for the onboard and all of our installs are PXE and in general it removes a lot of confusion by just disabling the onboard NIC and having one single NIC for everything. Drew, out of curiosity (I have a similar motherboard in backorder), does the latest CentOS kernel have drivers for the onboard NIC after the installation? If not, I'll probably cancel my order and try a Gigabyte board insteadthanks in advance! Best regards Kenni ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Btw, this is the complete error. Jan 16 07:03:23 server kernel: irq 177: nobody cared (try booting with the irqpoll option) Jan 16 07:03:23 server kernel: [c044d886] __report_bad_irq+0x2b/0x69 Jan 16 07:03:23 server kernel: [c044da73] note_interrupt+0x1af/0x1e8 Jan 16 07:03:23 server kernel: [c044d081] handle_IRQ_event+0x45/0x8c Jan 16 07:03:23 server kernel: [c044d163] __do_IRQ+0x9b/0xd6 Jan 16 07:03:23 server kernel: [c044d0c8] __do_IRQ+0x0/0xd6 Jan 16 07:03:23 server kernel: [c040749e] do_IRQ+0x99/0xc3 Jan 16 07:03:23 server kernel: [c0405946] common_interrupt+0x1a/0x20 Jan 16 07:03:23 server kernel: [c05302c0] acpi_processor_idle_simple+0x0/0x254 Jan 16 07:03:23 server kernel: [c052fc0b] acpi_safe_halt+0x14/0x20 Jan 16 07:03:23 server kernel: [c0530367] acpi_processor_idle_simple+0xa7/0x254 Jan 16 07:03:23 server kernel: [c053007b] acpi_processor_get_power_info+0x464/0x510 Jan 16 07:03:23 server kernel: [c0403ca8] cpu_idle+0x9f/0xb9 Jan 16 07:03:23 server kernel: === Jan 16 07:03:23 server kernel: handlers: Jan 16 07:03:23 server kernel: [c058afd1] (usb_hcd_irq+0x0/0x50) Jan 16 07:03:23 server kernel: [f8964b7f] (e1000_intr+0x0/0x10b [e1000]) Jan 16 07:03:23 server kernel: Disabling IRQ #177 In case again anyone is interested. I just tried updating the bios, if it freezes again I will boot with acpi=off and then retest. acpi=off in the kernel options has allowed the machine to run for over 12 hours without crashing, we'll see what happens. doesn't seem like a hardware problem. thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Jan 16 07:03:23 server kernel: irq 177: nobody cared (try booting with the irqpoll option) Jan 16 07:03:23 server kernel: [c044d886] __report_bad_irq+0x2b/0x69 Jan 16 07:03:23 server kernel: [c044da73] note_interrupt+0x1af/0x1e8 Jan 16 07:03:23 server kernel: [c044d081] handle_IRQ_event+0x45/0x8c Jan 16 07:03:23 server kernel: [c044d163] __do_IRQ+0x9b/0xd6 Jan 16 07:03:23 server kernel: [c044d0c8] __do_IRQ+0x0/0xd6 Jan 16 07:03:23 server kernel: [c040749e] do_IRQ+0x99/0xc3 Jan 16 07:03:23 server kernel: [c0405946] common_interrupt+0x1a/0x20 Jan 16 07:03:23 server kernel: [c05302c0] acpi_processor_idle_simple+0x0/0x254 Jan 16 07:03:23 server kernel: [c052fc0b] acpi_safe_halt+0x14/0x20 Jan 16 07:03:23 server kernel: [c0530367] acpi_processor_idle_simple+0xa7/0x254 Jan 16 07:03:23 server kernel: [c053007b] acpi_processor_get_power_info+0x464/0x510 Jan 16 07:03:23 server kernel: [c0403ca8] cpu_idle+0x9f/0xb9 Jan 16 07:03:23 server kernel: === Jan 16 07:03:23 server kernel: handlers: Jan 16 07:03:23 server kernel: [c058afd1] (usb_hcd_irq+0x0/0x50) Jan 16 07:03:23 server kernel: [f8964b7f] (e1000_intr+0x0/0x10b [e1000]) Jan 16 07:03:23 server kernel: Disabling IRQ #177 == I spoke too soon, the problem wasn't fixed but I found the cause of the issue. The above error occurs when you unplug the video cable from the onboard video. As our machines are mainly headless terminals, this will not do at all. I am going to retest with RHEL 6. thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Jan 16 07:03:23 server kernel: irq 177: nobody cared (try booting with the irqpoll option) I spoke too soon, the problem wasn't fixed but I found the cause of the issue. The above error occurs when you unplug the video cable from the onboard video. As our machines are mainly headless terminals, this will not do at all. Does the BIOS allow you to disable the video hardware completely? Does that enable your kernel to boot? If not, grab the kernel source and build a kernel without console support (which is what I had to do for our headless embedded systems) sshd is the only way to talk to my target machines. The kernel boots fine, and everything works ok until you unplug the monitor from the DVI port on the motherboard. When you unplug the monitor, that IRQ/ACPI message is displayed, and it screws up the USB and the e1000 card in the system. These machines aren't always headless, sometimes we need to plug monitors into them. thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
On Wednesday, January 19, 2011 12:35:18 pm Drew Weaver wrote: The kernel boots fine, and everything works ok until you unplug the monitor from the DVI port on the motherboard. When you unplug the monitor, that IRQ/ACPI message is displayed, and it screws up the USB and the e1000 card in the system. These machines aren't always headless, sometimes we need to plug monitors into them. Can you disable the video card's use of an IRQ? I've seen that before, where the video card had an IRQ whether the driver needed it or not. If you use a DVI to VGA/analog adapter and unplug an analog monitor, does it still happen? = It doesn't look like there is an option to assign an IRQ to this card or not. If I use a DVI-VGA adapter and leave the adapter connected but unplug the vga cord from the adapter it still freaks out. It looks like Intel is trying to be handy and detect the state of the video port, but it's really freaking annoying it turns out =) Just FYI, I tried this on RHEL 6 and Debian 5 as well, and it does the exact same thing. Motherboard doesn't support Linux so I am guessing Intel has no interest in fixing this problem, but just a cautionary tale to everyone =) -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Hello, We have built a couple of CentOS 5.5 systems on the Intel DH67BL (Sandy Bridge) motherboard and overall they work pretty well. I'm having one problem which keeps cropping up and that is an error message that says: IRQ 177 nobody cared (try booting with the irqpoll option) report bad irq, references CPU idle then it references usb_hcd_irq and e1000_intr then it disables the add-on PCI E1000 card and disconnects itself from the network. I'm assuming what is happening here is the USB controller and the add-on E1000 controller we put in are having an old school IRQ conflict, the question is why and how can I avoid it? I have tried disabling all of the extra stuff in the BIOS that I could, and this still happens fairly frequently. Any advice would be great. thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Ah, it is a PCI card and there is only one PCI slot.. -Drew -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Giles Coochey Sent: Tuesday, January 18, 2011 9:24 AM To: centos@centos.org Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared On 18/01/2011 15:22, Drew Weaver wrote: Hello, We have built a couple of CentOS 5.5 systems on the Intel DH67BL (Sandy Bridge) motherboard and overall they work pretty well. I'm having one problem which keeps cropping up and that is an error message that says: IRQ 177 nobody cared (try booting with the irqpoll option) report bad irq, references CPU idle then it references usb_hcd_irq and e1000_intr then it disables the add-on PCI E1000 card and disconnects itself from the network. I'm assuming what is happening here is the USB controller and the add-on E1000 controller we put in are having an old school IRQ conflict, the question is why and how can I avoid it? I have tried disabling all of the extra stuff in the BIOS that I could, and this still happens fairly frequently. Any advice would be great. Have you tried putting one of the cards in a different slot? -- Best Regards, Giles Coochey NetSecSpec Ltd NL T-Systems Mobile: +31 681 265 086 NL Mobile: +31 626 508 131 Email/MSN/Live Messenger: gi...@coochey.net Skype: gilescoochey ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Why don't you use the mother board incorporated NIC? it does have one right? --- Because the installer doesn't have drivers for the onboard and all of our installs are PXE and in general it removes a lot of confusion by just disabling the onboard NIC and having one single NIC for everything. thanks, -Drew From: Drew Weaver drew.wea...@thenap.com To: CentOS mailing list centos@centos.org Sent: Tuesday, 18 January, 2011 2:22:04 PM Subject: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared Hello, We have built a couple of CentOS 5.5 systems on the Intel DH67BL (Sandy Bridge) motherboard and overall they work pretty well. I'm having one problem which keeps cropping up and that is an error message that says: IRQ 177 nobody cared (try booting with the irqpoll option) report bad irq, references CPU idle then it references usb_hcd_irq and e1000_intr then it disables the add-on PCI E1000 card and disconnects itself from the network. I'm assuming what is happening here is the USB controller and the add-on E1000 controller we put in are having an old school IRQ conflict, the question is why and how can I avoid it? I have tried disabling all of the extra stuff in the BIOS that I could, and this still happens fairly frequently. Any advice would be great. thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Hi, It doesn't appear to, it simply shows a little ASCII diagram of what is set for each slot. thanks, -Drew -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Giles Coochey Sent: Tuesday, January 18, 2011 9:39 AM To: centos@centos.org Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared On 18/01/2011 15:34, Drew Weaver wrote: Ah, it is a PCI card and there is only one PCI slot.. -Drew -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Giles Coochey Sent: Tuesday, January 18, 2011 9:24 AM To: centos@centos.org Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared On 18/01/2011 15:22, Drew Weaver wrote: Hello, We have built a couple of CentOS 5.5 systems on the Intel DH67BL (Sandy Bridge) motherboard and overall they work pretty well. I'm having one problem which keeps cropping up and that is an error message that says: IRQ 177 nobody cared (try booting with the irqpoll option) report bad irq, references CPU idle then it references usb_hcd_irq and e1000_intr then it disables the add-on PCI E1000 card and disconnects itself from the network. I'm assuming what is happening here is the USB controller and the add-on E1000 controller we put in are having an old school IRQ conflict, the question is why and how can I avoid it? I have tried disabling all of the extra stuff in the BIOS that I could, and this still happens fairly frequently. Any advice would be great. Have you tried putting one of the cards in a different slot? Does the BIOS allow you to manually set a IRQ to the PCI line? -- Best Regards, Giles Coochey NetSecSpec Ltd NL T-Systems Mobile: +31 681 265 086 NL Mobile: +31 626 508 131 GIB Mobile: +350 5401 6693 Email/MSN/Live Messenger: gi...@coochey.net Skype: gilescoochey ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Hi, There does not appear to be a 'Plug and Play OS' option in the BIOS like on previous Intel motherboards. I have disabled all of the USB ports except for the rear panel ones and so far it has been running for awhile. I will see what happens. thanks, -Drew From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of compdoc Sent: Tuesday, January 18, 2011 10:57 AM To: 'CentOS mailing list' Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared IRQ 177 nobody cared (try booting with the irqpoll option) report bad irq, references CPU idle I'm assuming what is happening here is the USB controller and the add-on E1000 controller we put in are having an old school IRQ conflict, the question is why and how can I avoid it? IRQ177 means you are using APIC, which gives you over 250 interrupts - far more than there were in the olden days. There should be enough that nothing has to share IRQs. But even before APIC came along, devices had gotten pretty good at sharing IRQs. As someone suggested, disable the Plug and Play option in the bios. Try a different brand of Ethernet card? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Issue still persists, anyway I thought I'd let you guys know in case someone is thinking about getting one or more of these boards. -Drew From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Drew Weaver Sent: Tuesday, January 18, 2011 11:42 AM To: 'CentOS mailing list' Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared Hi, There does not appear to be a 'Plug and Play OS' option in the BIOS like on previous Intel motherboards. I have disabled all of the USB ports except for the rear panel ones and so far it has been running for awhile. I will see what happens. thanks, -Drew From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of compdoc Sent: Tuesday, January 18, 2011 10:57 AM To: 'CentOS mailing list' Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared IRQ 177 nobody cared (try booting with the irqpoll option) report bad irq, references CPU idle I'm assuming what is happening here is the USB controller and the add-on E1000 controller we put in are having an old school IRQ conflict, the question is why and how can I avoid it? IRQ177 means you are using APIC, which gives you over 250 interrupts - far more than there were in the olden days. There should be enough that nothing has to share IRQs. But even before APIC came along, devices had gotten pretty good at sharing IRQs. As someone suggested, disable the Plug and Play option in the bios. Try a different brand of Ethernet card? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
Btw, this is the complete error. Jan 16 07:03:23 server kernel: irq 177: nobody cared (try booting with the irqpoll option) Jan 16 07:03:23 server kernel: [c044d886] __report_bad_irq+0x2b/0x69 Jan 16 07:03:23 server kernel: [c044da73] note_interrupt+0x1af/0x1e8 Jan 16 07:03:23 server kernel: [c044d081] handle_IRQ_event+0x45/0x8c Jan 16 07:03:23 server kernel: [c044d163] __do_IRQ+0x9b/0xd6 Jan 16 07:03:23 server kernel: [c044d0c8] __do_IRQ+0x0/0xd6 Jan 16 07:03:23 server kernel: [c040749e] do_IRQ+0x99/0xc3 Jan 16 07:03:23 server kernel: [c0405946] common_interrupt+0x1a/0x20 Jan 16 07:03:23 server kernel: [c05302c0] acpi_processor_idle_simple+0x0/0x254 Jan 16 07:03:23 server kernel: [c052fc0b] acpi_safe_halt+0x14/0x20 Jan 16 07:03:23 server kernel: [c0530367] acpi_processor_idle_simple+0xa7/0x254 Jan 16 07:03:23 server kernel: [c053007b] acpi_processor_get_power_info+0x464/0x510 Jan 16 07:03:23 server kernel: [c0403ca8] cpu_idle+0x9f/0xb9 Jan 16 07:03:23 server kernel: === Jan 16 07:03:23 server kernel: handlers: Jan 16 07:03:23 server kernel: [c058afd1] (usb_hcd_irq+0x0/0x50) Jan 16 07:03:23 server kernel: [f8964b7f] (e1000_intr+0x0/0x10b [e1000]) Jan 16 07:03:23 server kernel: Disabling IRQ #177 In case again anyone is interested. I just tried updating the bios, if it freezes again I will boot with acpi=off and then retest. -Drew From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Drew Weaver Sent: Tuesday, January 18, 2011 3:25 PM To: 'CentOS mailing list' Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared Issue still persists, anyway I thought I'd let you guys know in case someone is thinking about getting one or more of these boards. -Drew From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Drew Weaver Sent: Tuesday, January 18, 2011 11:42 AM To: 'CentOS mailing list' Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared Hi, There does not appear to be a 'Plug and Play OS' option in the BIOS like on previous Intel motherboards. I have disabled all of the USB ports except for the rear panel ones and so far it has been running for awhile. I will see what happens. thanks, -Drew From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of compdoc Sent: Tuesday, January 18, 2011 10:57 AM To: 'CentOS mailing list' Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared IRQ 177 nobody cared (try booting with the irqpoll option) report bad irq, references CPU idle I'm assuming what is happening here is the USB controller and the add-on E1000 controller we put in are having an old school IRQ conflict, the question is why and how can I avoid it? IRQ177 means you are using APIC, which gives you over 250 interrupts - far more than there were in the olden days. There should be enough that nothing has to share IRQs. But even before APIC came along, devices had gotten pretty good at sharing IRQs. As someone suggested, disable the Plug and Play option in the bios. Try a different brand of Ethernet card? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared
The keyboard that I use to ctrl-alt-del it is USB, but there was no keyboard connected until after it locked up, so it's a chicken and egg thing. -Drew -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of m.r...@5-cent.us Sent: Tuesday, January 18, 2011 3:59 PM To: CentOS mailing list Subject: Re: [CentOS] Intel DH67BL + CentOS 5.5 IRQ #177 nobody cared Drew Weaver wrote: Btw, this is the complete error. snip Hmmm... here's a thought: do you have anything plugged into a USB port? If so, try booting with it out; if not, try booting with one in. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DP55WG centos 5.5 support?
we evaluated this board but instead decided to go with the SuperMicro X8SIL-F. It doesn't support the core i5 and core i7 but it has VGA and there are Xeon parts that match the core i5 and core i7 specs. -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Coert Waagmeester Sent: Monday, October 18, 2010 5:05 AM To: CentOS mailing list Subject: [CentOS] Intel DP55WG centos 5.5 support? Hello all, I have looked around on the HCL and on other hardware sites. Do any of you have experience with Centos 5.5 64 bit on these motherboards? Regards, Coert Waagmeester ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ip address from range script
?php
$ranges = array(
array(ip2long('63.31.63.0'), ip2long('63.31.63.255')),
array(ip2long('64.65.0.0'), ip2long('64.65.31.255')));
$ips = array(63.31.63.2, 64.66.5.4);
function checkip($ip, $range) {
$ip = (integer) ip2long($ip);
if(($ip = $range[0]) and ($ip = $range[1])) {
return true;
}
}
foreach ($ips as $ip) {
echo Checking $ip!\n;
foreach ($ranges as $range) {
$rd_displaya = long2ip($range[0]);
$rd_displayb = long2ip($range[1]);
echo Checking for $ip in $rd_displaya - $rd_displayb;
if (checkip($ip, $range) === TRUE) {
echo Match\n;
} else {
echo No Match\n;
}
}
}
?
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of
Jozsi Vadkan
Sent: Thursday, July 29, 2010 9:54 AM
To: Centos Mailing List
Subject: [CentOS] ip address from range script
TEST-A.txt: list of ip address ranges [AS/isp's in a country]
TEST-B.txt: list of ip addresses
I just need to know, if an ip in the TEST-B.txt is in a range of
TEST-A.txt
cat TEST-A.txt
63.31.63.0/24;9007;44536
64.65.0.0/19;9000;8263
62.64.14.0/21;9001;6852
cat TEST-B.txt
63.31.63.2
64.66.5.4
63.31.63.66
62.64.14.231
output:
63.31.63.0/24;9007;44536
63.31.63.2
63.31.63.66
62.64.14.0/21;9001;6852
62.64.14.231
- so is an ip address [in TEST-B.txt] is from my country [TEST-A.txt]
or not?
thanks:\
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] can't update CENTOS - mirrore issue? or what?
Perhaps he has an invalid URL specified only for addons and not base/updates? thanks, -Drew -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Karanbir Singh Sent: Monday, May 24, 2010 3:17 PM To: CentOS mailing list Subject: Re: [CentOS] can't update CENTOS - mirrore issue? or what? On 05/20/2010 09:57 PM, Ryan Manikowski wrote: Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=5arch=i386repo=addons error was [Errno 4] IOError:urlopen error (-3, 'Temporary failure in name resolution') Error: Cannot find a valid baseurl for repo: addons Disable the 'addons' repo and your problem will be resolved. That sounds like a bit of very random advice, given that Dave's dns is not responding - how would disabling the addons repo have an impact on Dave's nameserver ? - KB ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DNSSEC
Hi, It's enabled by default if BIND is the right version nothing needs to be done. I found it kind of sad that the version of BIND that comes with the latest version of CentOS 4 is so old that it doesn't support DNSSEC. thanks, -Drew XLHost.com -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of m.r...@5-cent.us Sent: Friday, April 30, 2010 1:07 PM To: CentOS mailing list Subject: [CentOS] DNSSEC Well, folks, There's an article on slashdot, http://tech.slashdot.org/article.pl?sid=10/04/30/1258234 Excerpt: ...the coming milestone of May 5, at 17:00 UTC - at this time DNSSEC will be rolled out across all 13 root servers. Some Internet users, especially those inside corporations and behind smaller ISPs, may experience intermittent problems. The reason is that some older networking equipment is pre-configured to block any reply to a DNS request that exceeds 512 bytes in size. DNSSEC replies are typically four times as large. --- end excerpt --- I followed the link from the story to https://www.dns-oarc.net/oarc/services/replysizetest, a coordinating organization, and tried their test (as root): dig +short rs.dns-oarc.net txt And see that where I work, we're not ready. Is anyone following this, and/or have a HOWTO on enabling it for CentOS? mark (need to check this at home, too) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 12-15 TB RAID storage recommendations
Those drives are likely fading out of the array because they aren't meant to be in arrays in the first place, Adaptec has told us that if you use consumer drives with their cards you are operating at your own risk. -Drew -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Don Krause Sent: Tuesday, April 13, 2010 3:20 PM To: CentOS mailing list Subject: Re: [CentOS] 12-15 TB RAID storage recommendations On Apr 13, 2010, at 11:57 AM, nate wrote: John R Pierce wrote: well, IF your controller totally screams and can rebuild the drives at wire speeds with full overlap, you'll be reading 7 * 2TB of data at around 100MB/sec average and writing the XOR of that to the 8th drive in a 8 spindle raid5 (14tb total). just reading one drive at wirespeed is 2000,000MB / 100MB == 20,000 seconds, or about 5.5 hours, so thats about the shortest it possibly could be done. More likely your looking at 24+ hours, because really no disk system is going to read your SATA disks at 100MB/second. If your really lucky perhaps you can get 10MB/second. With the fastest RAID controllers in the industry my own storage array(which does heavy amounts of random I/O) averages about 2.2MB/second for a SATA disk, with peaks at around 4MB/second. Our previous storage array averaged about 4-6 hours to rebuild a RAID 5 12+1 array with 146GB 10k RPM disks, on an array that was in excess of 90% idle. Rebuilding a 400GB SATA-I array often took upwards of 48 hours. nate For a real life example, we have a 3 year old 12x 1TB SATA box using an Adaptec RAID controller, doing RAID 6 that takes about 3 days to rebuild the array each time a drive fails. Which, to date, has happened 10 times... (Fortunately, this is only a BackupPC box.) FWIW, we've not experienced a second drive failure during the rebuild process, yet. But we have had drives fail within a few weeks of each other, so it's probably going to happen one of these days.. -- Don Krause Head Systems Geek, Waver of Deceased Chickens. Optivus Proton Therapy, Inc. www.optivus.com This message represents the official view of the voices in my head. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SATA Switch
I know with Ubuntu if it detects Windows is installed it automatically does all of this. Never tried with CentOS because we don't use it as a desktop OS. thanks, -Drew -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Tim Nelson Sent: Tuesday, March 30, 2010 10:22 AM To: CentOS mailing list Subject: Re: [CentOS] SATA Switch - Matt lm7...@gmail.com wrote: Does anyone know of a front panel SATA switch? I would like to have one drive with 'Windows 7' and another with linux on my PC but do not want them on the same drive. There are definitely more elegant ways of doing this, specifically by configuring your bootloader properly. BUT, if you must have a physical mechanism for switching drives, see here: http://www.cooldrives.com/4posaiisw3ba.html For that kind of money, I'd spend a few hours getting (more) intimately familiar with GRUB. :-) --Tim ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] OT: free DNS service?
I believe I now know how to flush that cache and will do that, before I change the A record to point to the IP of the new server again. Hoping MyDomain.com will lower the TTL from 3600 to 300 for a few days, so I can do the testing/migration I need to do a lot faster. - Even if your DNS provider lowers your TTL to 300 it doesn't mean other peoples servers (like ours) are going to expire their cache that quickly. thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.4? anyone?
Jeremy Rosengren wrote: On Thu, Oct 15, 2009 at 7:07 AM, Miguel Di Ciurcio Filho mig...@ic.unicamp.br mailto:mig...@ic.unicamp.br wrote: mbneto wrote: Hi, The last status (from twitter) is 2 days old with the '5.4 is baked! centos internal network will start syncing up today. Release ~ soon!'. Any ETA? Just relax and wait, this is a _volunteer_ based project. Want a release date? Go pay for RHEL. This response is just as annoying as the request for an update. -- j +1 Annoying and rude. This might be why the Linux community as a whole gets such a bad rap. -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Feature list between 5.2 and 5.3
does anyone know if (and where) a feature list of the changes between CentOS 5.2 and 5.3 can be found? All of the documentation that I could find on centos.org is related to 5.2 and 5.1 thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] That RTL8169 thing...
Motherboard - Intel DG41TY Device: RealTek: 8111D Driver: RTL8169 Causes Kernel panic during install and boot. -- It seems that the newer the card that uses this driver, the worse the problems are. Is there any plan to roll a newer version into the installer or the actual distribution itself? Thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Support for i7 architecture?
It is trivial to create an initrd for the installer which has support the x58 chipset. If you would like my copy which also works with atom boards just e-mail me off-list. -Drew -Original Message- From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of Michael St. Laurent Sent: Thursday, January 22, 2009 5:18 PM To: centos@centos.org Subject: [CentOS] Support for i7 architecture? What is the status of i7 architecture support for CentOS-5? Do the latest updates support it? -- This e-mail may contain technical information which is controlled by the United States Government, Department of State, International Traffic Arms Regulations (ITAR) (22 CFR 120-130) which requires an export license prior to sharing with foreign persons. Lacking such license, ITAR technical data is limited to US Legal Residents only. It is the responsibility of the organization and individual in control of this data to abide by US export laws. If you are not a US Legal Resident, immediately forward this e-mail to not...@hartwellcorp.com or reply to sender without reading any further. Take no other action with this e-mail until contacted. Notice: The information in this document and document itself, in whole or in part, in any form (Information) is proprietary and/or confidential property of Hartwell Corporation, Placentia, California. Hartwell Corporation and its successors and assignees retain and reserve all right, title and interest in this information in whole or in part and in all forms. This Information is provided to the original recipient only for confidential use, with the understanding that it will not be used in any manner detrimental to the interests of Hartwell Corporation, and subject to return on request. Reproduction, transmission, distribution or publication of this Information in any form, in whole or in part, for any purpose without prior written permission of Hartwell Corporation is strictly prohibited. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Don't suppose
Anyone has gone to the trouble of creating an install initrd for 5.2 that has (a working) r8169 module built into it? Mainly for kickstarts. -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Don't suppose
Oh, I'm sorry the one I need is actually r8168, I apologize. -Drew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Farkas Levente Sent: Tuesday, December 09, 2008 4:22 PM To: CentOS mailing list Subject: Re: [CentOS] Don't suppose Drew Weaver wrote: Anyone has gone to the trouble of creating an install initrd for 5.2 that has (a working) r8169 module built into it? yes, many:-( the solution to use nicdelay=5 kernel param too and the latest 5.3 beta kernel... -- Levente Si vis pacem para bellum! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Adding new drivers to the pxeboot initrd/kernel
Does anyone have a howto or documentation on how to add new drivers to the pxeboot initrd/kernel? It appears that although some newer dells (t300) have Broadcom NetXtreme IIs in them, 4.6 won't recognize them for some reason (possibly because they're dual port?) -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] 1333/8GB Intel motherboard for C5.1
Hi there, has anyone run into any Desktop/Workstation Intel brand motherboards that work with CentOS 5.1 (4.6/3.9 out of box compatibility is a very large plus) and work with the 1333MHZ cpus such as the 8400/9450 and accept 8GB of RAM? The closest we've found so far is the DG31PR which is alright but it has the limitation of 4GB of RAM and an unsupported Realtek NIC. The DQ35JO is also ok, but requires quite a bit of 'jostling' to get to work such as pci=nommconf and other tweaks, we need something that will work out of box, anyone found anything recently? Thanks in advance if anyone has any hints. -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Updating Dovecot package?
Does anyone know if upstream ever plans on updating the dovecot package to a non RC version or to even one of the RC versions that isn't so insecure, And by insecure, I of course refer to the recent rash of bugs which have been found. Thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Intel (brand) Penryn (8xxx) motherboard which works natively with CentOS 4/5?
Has anyone stumbled across an Intel brand motherboard which both works with the 8000 series of CPUs and with CentOS 4/5 out of the box? (by works I mean the NIC/Disk controllers without fudgery) The DG31 board kind of works but unfortunately it has 2 DIMM slots, the realtek NIC isn't supported (don't know why, its just a standard realtek NIC, although it might be some new PCI-E one). Has anyone found the Holy Grail yet? Please let me know :) -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Chipset support for 6750 Intel CPUs
Howdy, We've noticed that the new chipsets required for the **50 series of intel processors is not supported in CentOS 5. We've tried the DG31 board which (realtek nic unsupported) DG33 no support for disk controller or NICs. We also tried the dx38bt and there was no support. Fedora 8 apparently works great with all of the boards we tried. My question is, will there these boards not be supported via the installer until CentOS 6? I realize that the driver support comes from upstream, but it would be cool if they made a easy way to use a newer/updated kernel in the installer. Thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] what happened to netconfig in 5.1
I also noticed that minicom isn't installed, although not a big deal it was nice to know it was there in a pinch and it couldn't have been very heavy weight... -Drew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jerry Geis Sent: Monday, December 03, 2007 2:17 PM To: centos@centos.org Subject: [CentOS] what happened to netconfig in 5.1 I am doing a yum install netconfig on the new 5.1 and nothing gets installed. Was it removed? replaced with something else? yum provides netconfig does not show a bin command just false matches. Is there a new command? Thanks, Jerry Looks like system-config-network has replaced it. AHHH! when I run this command it does not show my eth0 as forcedeth it is showing my T1 digium card as eth0. Very shocked this command was removed from 5.0 to 5.1 release. What are they thinking? Jerry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Quick query about LVM in 4.5
Howdy, Does anyone know if anything has changed with the LVM system from CentOS 4.4 to CentOS 4.5? I'm having kind of a funky issue. I've mounted LVM partitions manually quite a few times and I've never had this issue before: --- Logical volume --- LV Name/dev/VolGroup00/LogVol00 VG NameVolGroup00 LV UUIDd6ksUI-Gha1-vC62-6eQS-2YtX-iQVJ-aMNkQC LV Write Accessread/write LV Status available # open 0 LV Size146.97 GB Current LE 4703 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:2 [EMAIL PROTECTED] /]# mount /dev/VolGroup00/LogVol00 /old mount: special device /dev/VolGroup00/LogVol00 does not exist [EMAIL PROTECTED] /]# I'm not sure why, but when I do fdisk -l I get: Disk /dev/dm-0: 160.0 GB, 160038912000 bytes 255 heads, 63 sectors/track, 19456 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/dm-0p1 * 1 13 104391 83 Linux /dev/dm-0p2 14 19457 156183930 8e Linux LVM Now, /dev/VolGroup00/LogVol00 should be /dev/dm-0p2. Is there a new way to 'address' these partitions in 4.5? Thanks, -Drew ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
RE: [CentOS] Reg:Checking HDD Badblocks on kickstart CentOS installation
We have all of the disk tools (seatools, etc) on the same PXE loader that we use to do our kickstarts, so we simply use the disktools from the manufacturer to test the drives before kickstarting a system. If you tell me what manufacturer's HDs you use I can email you a .img file for their particular 'disk tool' that you can use memdisk to boot over the network. Thanks, -Drew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Balaji Sent: Wednesday, August 01, 2007 9:45 AM To: CentOS@centos.org Subject: [CentOS] Reg:Checking HDD Badblocks on kickstart CentOS installation Hi All, Is there a way to check the harddisk health before CentOS installation.? One way I used to do was by using --badblocks check in ks.cfg file while using RH 7.2. This is not working (atleast not with the same syntax as in RH 7.2) in CentOS. Is there an alternate (correct) syntax or is there a new (better) way to check harddisk health before CentOS installation? Please help me and it is very urgent requirement for me --Regards S.Balaji ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
