Re: [CentOS] Dell PERC H800 commandline RAID monitoring tools
On Mon, Mar 07, 2011 at 12:43:03PM -0800, Dr. Ed Morbius wrote: > OMSA conflicts with mega-cli, though we may find that the latter is the > more useful package. Both are pretty byzantine, the Dell stuff simply > doesn't have docs (in particular: docs on how to interpret the omconfig > log output). We're using megacli wrapped by perl to provide information about Perc events. It works quite well as far. -- Dominik Zyla pgp8bhjUch9zV.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On Wed, Mar 9, 2011 at 7:40 PM, Tom H wrote: > On Wed, Mar 9, 2011 at 11:51 AM, wrote: >> Peter Peltonen wrote: >>> On Wed, Mar 9, 2011 at 6:33 PM, wrote: Peter Peltonen wrote: > > Based on that info I assume the board having a "8x SAS Ports via LSI > 1068E Controller". We received the server with 3 drives + 1 spare as > hw RAID-5 preinstalled. During bootup I see that the drives are > initialised and everything seems ok. > > The issue I am facing is that when trying to install CentOS no hard > drives are recognised. I recently had a problem like that with a Dell box. The trick is that with a hardware controller, it supercedes software RAID. What you need >> to do is go into the firmware controller configuration on boot, before you >> get to grub, and make sure everything's visible and correct. The controller can see the drives, but not present them to the o/s if you don't. >>> >> Nope. They may have said they "pre-installed the RAID, but you really need >> to go into the setup (, or -f, or whatever), and see what it >> presents ->logically<- (key buzzword). If it hasn't been initialized, or >> put into logical configuration, then it simply will not present the >> logical drives to the o/s, and AFAIK, it will *not* present the physical >> drives at all. > > I think that it's ctrl-r and that you have to set up "virtual disks" > using the "physical disks". Here are some pics of the RAID configuration: http://www.knuka.org/raid1.jpg http://www.knuka.org/raid2.jpg For me it seems that the drives are initialized and virtual disks setup, so it is not a hardware configuration issue? I also received confirmation from the vendor that the controller is "LSI 1068E". Should this controller be supported by CentOS5.5 without a driver disk? Regards, Peter Regards, Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
On Wed, 9 Mar 2011, compdoc wrote: > +36C and +39C are likely your cpu and motherboard temps. You have to look at > the temps in the cmos and match them. > > The +87C is likely just a miss-reading by lm_sensors. Anything running that > hot won't be stable. In testing nVidia graphics cards to destruction (not entirely deliberately) we found that anything up to about 110C was likely to work fine, anything past that was likely to cause visual corruption. Anything past 125C was pretty much guaranteed to cause permanent damage. But you're right, I doubt that's correct, and lm_sensors is prone to reporting duff information. AMD list 70C as the max recommended for that chip. In the past it'd also depend a lot on where the temperature probe was (so varied a lot motherboard by motherboard), but they're on package now aren't they? jh ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
> compdoc wrote: >>> According to the man page, it apparently needs a kernel driver >>> named OpenIMPI, which it claims is installed in standard >>> distributions. I don't find it on my system. >> >> >> lm_sensors is another, and I think installs ready to use from the repos. > > sensors says that the three temp sensors read +36C, +39C, and +87C. > These appear to be AMD K10 temp sensors, although I might be > misreading sensors-detect. Low/highs are (+127/+127, +127/+90, > +127/+127) respectively. (I'm not sure if these are alarm set > points or something else.) > > One fan is listed as 0 rpm. Something to look into. Hmm, much has been said now in this thread and I know how difficult it can be to find such an issue. However, I suggest not to throw in too many new tools in parallel. And, be careful of how to interpret any information gathered by tools like lm_sensors. They can only report as good as the mainboard and it's sensors were designed and built, both can be suboptimal. I've seen all kind of things like temp sensors not mounted where they should. Of course, builtin sensors like thiose of a CPU should be taken very serious. So, may I give some more tips how I'd try to find what is wrong: - Take a vacuum cleaner and *carefully* clean the whole box. Dust can really do bad things because it is not a perfect insulator. - If you feel you have to remove any device like CPU, make sure you up everything, have a good quality heat sink paste at hand and make sure everything is seated well after mounting it again. - For the memory part, do you have ECC? If not, then it is really a problem and if the box is used as a server, ECC is a must, if yes, then most errors will be corrected by ECC but what is more important, memory errors are usually logged. You should be able to find a list of those errors in the BIOS, you may see how many times errors occur and where, does something like that exist? - For the temparatures, 87C is not so uncommon, but yes, it looks a little bit high. Someone else posted 80C to be the max for your CPU, that seems correct, at least our 12core Opterons have "Caution: 75C; Critical: 80C" but they usually run at 45C-55C under normal load. So if 87C is really correct, under normal load, that may be already too much, and then consider what happens at peak times? - When you look at the lm_sensors values, do they correspund with what is shown in the BIOS (if is has this kind of diagnostics)? Simon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
On Thu, 10 Mar 2011, Simon Matter wrote: > - Take a vacuum cleaner and *carefully* clean the whole box. Dust can > really do bad things because it is not a perfect insulator. Take the wrong vacuum cleaner and static your machine to death. jh ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating the symbolic links in the /boot and /boot/grub/
> Unfortunately, I live out with the cows, so I am using DSL to > download the latest - it will take awhile. It has been awhile > since I downloaded the four disks, however I assume disk 1 > contains all that I need to do a "rescue". Yes that's correct, you need to download only disk 1. > > Once I get that down, I will use torrent to get all four disks. > > Hey, guys, many thanks. Any of you live in the SF Bay Area? > Love to treat you to a beer. Thanks, but it may be a bit difficult. Just let us know if you have been able to boot successfully. Simon > > Todd > > On 3/9/2011 1:03 PM, Simon Matter wrote: >>> And here are the contents of grub.conf: >>> >>> # grub.conf generated by anaconda >>> # >>> # Note that you do not have to rerun grub after making changes to >>> this file >>> # NOTICE: You have a /boot partition. This means that >>> # all kernel and initrd paths are relative to /boot/, eg. >>> # root (hd0,0) >>> # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 >>> # initrd /initrd-version.img >>> #boot=/dev/hdc >>> default=0 >>> timeout=5 >>> splashimage=(hd0,0)/grub/splash.xpm.gz >>> hiddenmenu >>> title CentOS (2.6.9-100.EL) >>> root (hd0,0) >>> kernel /vmlinuz-2.6.9-100.EL ro >>> root=/dev/VolGroup00/LogVol00 rhgb quiet >>> initrd /initrd-2.6.9-100.EL.img >> OK, the file listing of /boot from your last mail and now grub.conf, >> they >> look quite good. grub.conf has been updated by the kernel update, and >> also >> a new initrd-2.6.9-100.EL.img has been created, so that doesn't look >> bad. >> >> The only thing I'm not really sure is if grub is installed correctly >> now. >> Maybe you have to run grub-install again to be sure but I'm just not so >> sure about grubs internals. Maybe someone can tell you more about this. >> >> As someone else mentioned, it's a very good idea to have a current >> CentOS >> 4.8 disk at hand so you could boot into rescue mode with 'linux rescue' >> at >> the boot prompt if somethings goes wrong. >> >> Simon >> >>> Todd >>> >>> On 3/9/2011 12:23 AM, Simon Matter wrote: > I inadvertently missed using the list...here are my recent messages. As Nico suggested, download the kernel but also grub and redhat-logos, like so wget http://mirrors.kernel.org/centos/4.9/updates/i386/RPMS/kernel-2.6.9-100.EL.i686.rpm wget http://mirrors.kernel.org/centos/4.9/os/i386/CentOS/RPMS/redhat-logos-1.1.26-1.centos4.4.noarch.rpm wget http://mirrors.kernel.org/centos/4.9/os/i386/CentOS/RPMS/grub-0.95-3.8.i386.rpm Then do a rpm -Uvh --replacepkgs --replacefiles kernel-2.6.9-100.EL.i686.rpm redhat-logos-1.1.26-1.centos4.4.noarch.rpm grub-0.95-3.8.i386.rpm And the show us the contents of 'ls -laR /boot' and 'cat /etc/grub.conf' Simon > On 3/8/2011 8:39 PM, Nico Kadel-Garcia wrote: >> On Tue, Mar 8, 2011 at 11:31 PM, Todd Cary >> wrote: >>> reinstall is not an option for yum. I ran "yum install kernel" and >>> it >>> completed without errors however there are no links created. >> Oh, dear. Can you grab the RPM and do "rpm -U -replacepkgs >> [kernel-whatver].rpm"? You should be able to use "yum remove" on the >> old kernel packages, consistent with freeing up the space, and now >> install your new kernel with yum. >> >>> Would this be the correct ln command for vmlinuz-2.6.9-89.35.1 >>> >>> # /boot/vmlinuz-2.6.9-89.35.1 /boot/vmlinuz >>> >>> Todd >>> >>> On 3/8/2011 7:04 PM, Nico Kadel-Garcia wrote: On Tue, Mar 8, 2011 at 9:58 PM, Todd Cary wrote: > I started a new thread since the original one is getting rather > long. > > I have retrieved the files I deleted in /boot and /boot/grub, > however I need to make links for > > /boot/System.map (System.map -> System.map-2.6.9-89.35.1) > /boot/vmlinuz (vmlinuz -> vmlinuz-2.6.9-89.35.1) > /boot/grub/menu.lst (menu.lst -> ./grub.conf) Instead, re-install your kernel. "yum reinstall kernel". This should regenerate your symlinks correctly, except possibly the grub.conf. > If it was not so important to get it correct, I would appreciate > the syntax for the command. Usually I would figure it out. > > Since I have restored the files (I will double check to make sure > they are all there), do I need to run grub-install? i think yes. The old location of the boot loader is listed in /boot/grub/grub.conf, and should be used as the argument to that command. grub is much smarter than LILO used to be, but I think the bootstrap procedure relies on knowing details of where the fiddly bits of grub live on the relevant ex2 compatible filesytem. > My apologies for bothering
Re: [CentOS] Server hangs on CentOS 5.5
On Thu, Mar 10, 2011 at 12:10 PM, John Hodrien wrote: > On Thu, 10 Mar 2011, Simon Matter wrote: > >> - Take a vacuum cleaner and *carefully* clean the whole box. Dust can >> really do bad things because it is not a perfect insulator. > > Take the wrong vacuum cleaner and static your machine to death. > > jh > ___ I prefer to use a dust blower instead. It doesn't risk pulling loose components with "dry" or loose "soldering" -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
Am 03/10/2011 11:04 AM, schrieb Simon Matter: > - Take a vacuum cleaner and *carefully* clean the whole box. Dust can > really do bad things because it is not a perfect insulator. Never ever do that. Especially not inside the machine. There is a real risk of simply vacuuming smaller components like smd-resistors of the board. And, as already mentioned, you also have the chance of killing components by electrostatic discharge. Always use compressed air, even if just using canned one. Vacuuming is a pretty bad advice. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL4 EOL
On Thu, Mar 3, 2011 at 8:12 PM, Johnny Hughes wrote: > On 03/03/2011 05:57 PM, Kwan Lowe wrote: >> Just curious... CentOS4 lifetime tracks RHEL4 somewhat... Since RedHat >> has announced LTS (Long Term Support) for RHEL4, are there plans to >> extend the CentOS 4 support window? > > No, BECAUSE ... Red Hat does not publicly release the sources for their > Long Term Support packages. > > They are not releasing the Long Term packages for EL3 now, they won't be > doing it for EL4 either. > > Now, if they DID release them, then CentOS would produce them. Ahhh.. thanks for the info... It's just as well in any case. Gives me some more leverage when I push to upgrade the 4.x systems... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Deduplication
Has anyone played with SDFS on CentOS? Is it usable? http://www.opendedup.org/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Deduplication
On Thu, Mar 10, 2011 at 9:28 PM, Lars Hecking wrote: > > Has anyone played with SDFS on CentOS? Is it usable? > > http://www.opendedup.org/ I haven't tried SDFS, but I've been using LessFS for our fileserver for few months now. Beside dedup, it also gives file compression. So far so good. I'll take a look at SDFS. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Deduplication
> I haven't tried SDFS, but I've been using LessFS for our fileserver > for few months now. How do you do backup and archiving? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Deduplication
On Thu, Mar 10, 2011 at 10:01 PM, Lars Hecking wrote: > >> I haven't tried SDFS, but I've been using LessFS for our fileserver >> for few months now. > > How do you do backup and archiving? It's a VM. I back it up to encrypted external HDD then off to offsite location. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
On Thursday, March 10, 2011 05:35:29 am Rudi Ahlers wrote: > I prefer to use a dust blower instead. It doesn't risk pulling loose > components with "dry" or loose "soldering" I use both: antistatic canned air to blow the dust and a metal-tubed vacuum rested on a part of the case away from any boards to grab the dust that's being blown. Works great, and you don't 'recycle' the dust. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
> Here are some pics of the RAID configuration: > >http://www.knuka.org/raid1.jpg >http://www.knuka.org/raid2.jpg It does indeed look configured... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating the symbolic links in the /boot and /boot/grub/
Well, I have the disks in hand - all 4, but there is the overriding level of apprehension. Is there a reference to what I should do *if* I cannot reboot that I should read? Also, after reading the responses to my query about using FAT32 to store data, I decided to follow the suggestions to use Samba to copy the data that needs to be shared with others to my Windows connected NTFS external. So, I am in the process of doing that first even though I have an ext3 backup of the same data. Preparing to jump as I look for my spare parachute Todd On 3/10/2011 2:15 AM, Simon Matter wrote: >> Unfortunately, I live out with the cows, so I am using DSL to >> download the latest - it will take awhile. It has been awhile >> since I downloaded the four disks, however I assume disk 1 >> contains all that I need to do a "rescue". > Yes that's correct, you need to download only disk 1. > >> Once I get that down, I will use torrent to get all four disks. >> >> Hey, guys, many thanks. Any of you live in the SF Bay Area? >> Love to treat you to a beer. > Thanks, but it may be a bit difficult. Just let us know if you have been > able to boot successfully. > > Simon > >> Todd >> >> On 3/9/2011 1:03 PM, Simon Matter wrote: And here are the contents of grub.conf: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hdc default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.9-100.EL) root (hd0,0) kernel /vmlinuz-2.6.9-100.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-100.EL.img >>> OK, the file listing of /boot from your last mail and now grub.conf, >>> they >>> look quite good. grub.conf has been updated by the kernel update, and >>> also >>> a new initrd-2.6.9-100.EL.img has been created, so that doesn't look >>> bad. >>> >>> The only thing I'm not really sure is if grub is installed correctly >>> now. >>> Maybe you have to run grub-install again to be sure but I'm just not so >>> sure about grubs internals. Maybe someone can tell you more about this. >>> >>> As someone else mentioned, it's a very good idea to have a current >>> CentOS >>> 4.8 disk at hand so you could boot into rescue mode with 'linux rescue' >>> at >>> the boot prompt if somethings goes wrong. >>> >>> Simon >>> Todd On 3/9/2011 12:23 AM, Simon Matter wrote: >> I inadvertently missed using the list...here are my recent messages. > As Nico suggested, download the kernel but also grub and redhat-logos, > like so > wget > http://mirrors.kernel.org/centos/4.9/updates/i386/RPMS/kernel-2.6.9-100.EL.i686.rpm > wget > http://mirrors.kernel.org/centos/4.9/os/i386/CentOS/RPMS/redhat-logos-1.1.26-1.centos4.4.noarch.rpm > wget > http://mirrors.kernel.org/centos/4.9/os/i386/CentOS/RPMS/grub-0.95-3.8.i386.rpm > > Then do a > > rpm -Uvh --replacepkgs --replacefiles kernel-2.6.9-100.EL.i686.rpm > redhat-logos-1.1.26-1.centos4.4.noarch.rpm grub-0.95-3.8.i386.rpm > > And the show us the contents of 'ls -laR /boot' and 'cat > /etc/grub.conf' > > Simon > >> On 3/8/2011 8:39 PM, Nico Kadel-Garcia wrote: >>> On Tue, Mar 8, 2011 at 11:31 PM, Todd Cary >>> wrote: reinstall is not an option for yum. I ran "yum install kernel" and it completed without errors however there are no links created. >>> Oh, dear. Can you grab the RPM and do "rpm -U -replacepkgs >>> [kernel-whatver].rpm"? You should be able to use "yum remove" on the >>> old kernel packages, consistent with freeing up the space, and now >>> install your new kernel with yum. >>> Would this be the correct ln command for vmlinuz-2.6.9-89.35.1 # /boot/vmlinuz-2.6.9-89.35.1 /boot/vmlinuz Todd On 3/8/2011 7:04 PM, Nico Kadel-Garcia wrote: > On Tue, Mar 8, 2011 at 9:58 PM, Todd Cary > wrote: >> I started a new thread since the original one is getting rather >> long. >> >> I have retrieved the files I deleted in /boot and /boot/grub, >> however I need to make links for >> >> /boot/System.map (System.map -> System.map-2.6.9-89.35.1) >> /boot/vmlinuz (vmlinuz -> vmlinuz-2.6.9-89.35.1) >> /boot/grub/menu.lst (menu.lst -> ./grub.conf) > Instead, re-install your kernel. "yum reinstall kernel". This > should > regenerate your symlinks correctly, except possibly the grub.conf. >
Re: [CentOS] Creating the symbolic links in the /boot and /boot/grub/
> Well, I have the disks in hand - all 4, but there is the > overriding level of apprehension. Is there a reference to what I > should do *if* I cannot reboot that I should read? As I said before, you may need to run grub-install, but I don't know for sure. And then, you have to know where to install grub, and I don't know where you have installed it. In fact I don't know how we could know because it really depends on how your BIOS boots the box. It can be that it's installed into the MBR of /dev/hdc, then you should be able to install it using 'grub-install /dev/hdc'. But, since the disk is named /dev/hdc, it's most likely that there is also /dev/hda and /dev/hdb, and then it's also likely that grub has been installed into the MBR of /dev/hda. Who knows? That said, check disk 1 by putting it into another computer, and chose 'linux rescue' at the boot prompt. Then it will boot using a root filesystem in ram, and configure network if you want and then tries to find any CentOS installation in the disks, and mount them if it finds one. Maybe it wont find one but it should find it on your server. Then it will mount it as something like /mnt/sysimage. You can then 'chroot /mnt/sysimage' and fix things. Good luck! Simon > > Also, after reading the responses to my query about using FAT32 > to store data, I decided to follow the suggestions to use Samba > to copy the data that needs to be shared with others to my > Windows connected NTFS external. So, I am in the process of > doing that first even though I have an ext3 backup of the same data. > > Preparing to jump as I look for my spare parachute > > Todd > > On 3/10/2011 2:15 AM, Simon Matter wrote: >>> Unfortunately, I live out with the cows, so I am using DSL to >>> download the latest - it will take awhile. It has been awhile >>> since I downloaded the four disks, however I assume disk 1 >>> contains all that I need to do a "rescue". >> Yes that's correct, you need to download only disk 1. >> >>> Once I get that down, I will use torrent to get all four disks. >>> >>> Hey, guys, many thanks. Any of you live in the SF Bay Area? >>> Love to treat you to a beer. >> Thanks, but it may be a bit difficult. Just let us know if you have been >> able to boot successfully. >> >> Simon >> >>> Todd >>> >>> On 3/9/2011 1:03 PM, Simon Matter wrote: > And here are the contents of grub.conf: > > # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to > this file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 > # initrd /initrd-version.img > #boot=/dev/hdc > default=0 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title CentOS (2.6.9-100.EL) >root (hd0,0) >kernel /vmlinuz-2.6.9-100.EL ro > root=/dev/VolGroup00/LogVol00 rhgb quiet >initrd /initrd-2.6.9-100.EL.img OK, the file listing of /boot from your last mail and now grub.conf, they look quite good. grub.conf has been updated by the kernel update, and also a new initrd-2.6.9-100.EL.img has been created, so that doesn't look bad. The only thing I'm not really sure is if grub is installed correctly now. Maybe you have to run grub-install again to be sure but I'm just not so sure about grubs internals. Maybe someone can tell you more about this. As someone else mentioned, it's a very good idea to have a current CentOS 4.8 disk at hand so you could boot into rescue mode with 'linux rescue' at the boot prompt if somethings goes wrong. Simon > Todd > > On 3/9/2011 12:23 AM, Simon Matter wrote: >>> I inadvertently missed using the list...here are my recent >>> messages. >> As Nico suggested, download the kernel but also grub and >> redhat-logos, >> like so >> wget >> http://mirrors.kernel.org/centos/4.9/updates/i386/RPMS/kernel-2.6.9-100.EL.i686.rpm >> wget >> http://mirrors.kernel.org/centos/4.9/os/i386/CentOS/RPMS/redhat-logos-1.1.26-1.centos4.4.noarch.rpm >> wget >> http://mirrors.kernel.org/centos/4.9/os/i386/CentOS/RPMS/grub-0.95-3.8.i386.rpm >> >> Then do a >> >> rpm -Uvh --replacepkgs --replacefiles kernel-2.6.9-100.EL.i686.rpm >> redhat-logos-1.1.26-1.centos4.4.noarch.rpm grub-0.95-3.8.i386.rpm >> >> And the show us the contents of 'ls -laR /boot' and 'cat >> /etc/grub.conf' >> >> Simon >> >>> On 3/8/2011 8:39 PM, Nico Kadel-Garcia wrote: On Tue, Mar 8, 2011 at 11:31 PM, Todd Cary wrote: > reinstall is not an option for yum. I ran "yum install kernel" > and > it > completed without
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On 03/09/11 16:55, Peter Peltonen wrote: > I need to do a new CentOS net install on a new server having the > Supermicro X7DVL-3 motherboard: > >http://www.supermicro.com/products/motherboard/xeon1333/5000V/X7DVL-3.cfm > > Based on that info I assume the board having a "8x SAS Ports via LSI > 1068E Controller". We received the server with 3 drives + 1 spare as > hw RAID-5 preinstalled. During bootup I see that the drives are > initialised and everything seems ok. > > The issue I am facing is that when trying to install CentOS no hard > drives are recognised. > *snip* > Best regards, > Peter That controller doesn't really support RAID, what you're getting is commonly called FakeRAID. It basically helps the BIOS to boot from the RAID arrays you create but leaves the actual RAID calculations etc... to the driver. Configure the board in IT mode (Initiator/Target). That will disable the FakeRAID. It's jumper JPA2 just above the SAS ports. Once you've done that, clean the drives (dd if=/dev/zero of=/dev/sd? bs=1M) so no signatures from the FakeRAID BIOS remain. After that install CentOS as you would normally and use software RAID (which is better anyway). By the way, the X7DVL-3 is a pretty old board, you say this is a new server? I hope you didn't pay alot of money for it. Glenn ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Apache/Active Directory authentication
John, Thank you for all your pointers! You are right.. I was able to create a keytab file. Still having some issues with getting apache to work the way I wan to, but will continue troubleshooting it. Thank you! Asya On Mar 9, 2011, at 10:09 AM, John Hodrien wrote: > On Wed, 9 Mar 2011, John Hodrien wrote: > >> On Wed, 9 Mar 2011, Dvorkin, Asya wrote: >> >>> Thank you, John. >>> >>> I forgot to add that we cannot generate keytab from AD server for various >>> reasons that I have no control over. > > And are you really sure this is the case? If you can join to a domain, you > can get a keytab (you don't need AD admin rights to do this). > > If you were just using Samba to do the join, something like: > > use kerberos keytab = yes > > in your smb.conf > > and a: > > net ads keytab create > net ads keytab add http > > on the joined machine would get you a keytab suitable for web auth. > > klist -k would then show you what you'd got. > > jh > ___ > 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] Server hangs on CentOS 5.5
Simon Matter wrote: >> One fan is listed as 0 rpm. Something to look into. > > Hmm, much has been said now in this thread and I know how difficult it can > be to find such an issue. However, I suggest not to throw in too many new > tools in parallel. And, be careful of how to interpret any information > gathered by tools like lm_sensors. They can only report as good as the > mainboard and it's sensors were designed and built, both can be > suboptimal. I've seen all kind of things like temp sensors not mounted > where they should. Of course, builtin sensors like thiose of a CPU should > be taken very serious. Thanks for the suggestions. > So, may I give some more tips how I'd try to find what is wrong: > - Take a vacuum cleaner and *carefully* clean the whole box. Dust can > really do bad things because it is not a perfect insulator. > - If you feel you have to remove any device like CPU, make sure you up > everything, have a good quality heat sink paste at hand and make sure > everything is seated well after mounting it again. > - For the memory part, do you have ECC? If not, then it is really a > problem and if the box is used as a server, ECC is a must, if yes, then > most errors will be corrected by ECC but what is more important, memory > errors are usually logged. You should be able to find a list of those > errors in the BIOS, you may see how many times errors occur and where, > does something like that exist? The MB docs/website don't mention ECC support, but I presume it is as part of the DDR2 spec. I'll check whether the memory has ECC. If not, this is a reasonable upgrade. > - For the temparatures, 87C is not so uncommon, but yes, it looks a little > bit high. Someone else posted 80C to be the max for your CPU, that seems > correct, at least our 12core Opterons have "Caution: 75C; Critical: 80C" > but they usually run at 45C-55C under normal load. So if 87C is really > correct, under normal load, that may be already too much, and then > consider what happens at peak times? The most recent crash was overnight and not discovered until morning. Probably not related to load. But if it really is running over temp, then almost anything can happen. > - When you look at the lm_sensors values, do they correspund with what is > shown in the BIOS (if is has this kind of diagnostics)? Something I'll check when the system is taken down. -- Michael Eagerea...@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
Alexander Arlt wrote: > Am 03/10/2011 11:04 AM, schrieb Simon Matter: >> - Take a vacuum cleaner and *carefully* clean the whole box. Dust can >> really do bad things because it is not a perfect insulator. > > Never ever do that. Especially not inside the machine. There is a real > risk of simply vacuuming smaller components like smd-resistors of the > board. And, as already mentioned, you also have the chance of killing > components by electrostatic discharge. Always use compressed air, even > if just using canned one. Vacuuming is a pretty bad advice. Previous cleaning have been with canned compressed air. Thanks for the caution about vacuums and static. I may use the vacuum on the case fans from the outside. The case should provide an adequate static shield. -- Michael Eagerea...@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
Peter Peltonen wrote on Thu, 10 Mar 2011 10:12:48 +0200: > Should this controller be supported by CentOS5.5 without a driver disk? Yes, but maybe not in this specific card. For instance, I get this from lspci: 02:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI- Express Fusion-MPT SAS (rev 08) See, it mentions MPT. The built-in MPT driver works fine with it. This one may need an LSI-provided MegaRAID driver. You should ask SuperMicro about this. Assuming that they support RHEL they should be able to tell you if you need exctra drivers or you can use the driver coming with the system. Kai ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
Peter Peltonen wrote on Wed, 9 Mar 2011 17:55:04 +0200: > http://www.supermicro.com/products/motherboard/xeon1333/5000V/X7DVL-3.cfm > > Based on that info I assume the board having a "8x SAS Ports via LSI > 1068E Controller". Well, did you check at the LSI site for the controller/card that *is* detected (MegaRAID 3028)? Maybe it's not a 1068E. There is no mention of it anywhere just on that product page. Maybe that info is wrong. Also, you should be aware that the 1068E sits usually on a PCI-Express card. If that is not present or if you use the SATA ports on the MB that is *not* the 1068E! Kai ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
RedShift wrote on Thu, 10 Mar 2011 17:05:02 +0100: > That controller doesn't really support RAID, what you're getting is > commonly called FakeRAID If you are referring to the 1068E, that is completely wrong. Kai ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
centos-boun...@centos.org wrote: > Simon Matter wrote: > > The MB docs/website don't mention ECC support, but I presume > it is as part of the DDR2 spec. > I'll check whether the memory has ECC. If not, this is a reasonable upgrade. Your board does not support DDR2. See http://service.msicomputer.com/index.php?func=proddesc&maincat_no=1&cat2 _no=&cat3_no=&prod_no=273 "Support 2.5v DDR200/266/333 DDR SDRAM DIMM " That's straight old DDR. 3 slots of up to 3GB. No ECC. BIOS listed is A6380VMS.570 So many "instrumentation" suggestions have been made, that I think to note: The CPU bandwidth is rather modest, and might not support all that instrumentation *and* its previous job load. Also, some instrumentation packages suggested might not support socket A (pre-Barton) motherboards, verify VIA(r) KT333 (552 BGA) Chipset and VIA(r) VT8233A (376 BGA) Chipset are "comprehended" Insert spiffy .sig here: Life is complex: it has both real and imaginary parts. //me *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
centos-boun...@centos.org wrote: > On Thu, Mar 10, 2011 at 12:31 AM, Michael Eager > wrote: >> Dr. Ed Morbius wrote: >> >>> If the issue is repeated but rare system failures on one of a set of >>> similarly configured hosts, I'd RMA the box and get a replacement. >>> End of story. >> >> I'll repeat: this is a house-made system. There's no vendor to RMA >> to. > > I don't know where you are, His signature list CA/USA. > but in our country we can RMA anything and > everything. Apart from CPU's. So, even a cheap desktop mobo could be > RMA'd, as long as I can prove to the suppliers it's faulty, and it's > within the warrenty period Here in the USA we can RMA stuff if we can show it is dysfunctional. Michael's position is that he has no evidence of a dysfunctional part, which could be RMA'd. He has evidence of a dysfunctional gestalt, comprising hardware, software, environment, and data stream. Insert spiffy .sig here: Life is complex: it has both real and imaginary parts. //me *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 73, Issue 3
Send CentOS-announce mailing list submissions to centos-annou...@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-requ...@centos.org You can reach the person managing the list at centos-announce-ow...@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-2011:0337 Important CentOS 4 x86_64 vsftpd - security update (Johnny Hughes) 2. CESA-2011:0337 Important CentOS 4 i386 vsftpd - security update (Johnny Hughes) -- Message: 1 Date: Thu, 10 Mar 2011 03:59:53 -0600 From: Johnny Hughes Subject: [CentOS-announce] CESA-2011:0337 Important CentOS 4 x86_64 vsftpd -security update To: CentOS-Announce Message-ID: <4d78a119.2000...@centos.org> Content-Type: text/plain; charset="iso-8859-1" CentOS Errata and Security Advisory CESA-2011:0337 vsftpd security update for CentOS 4 x86_64: https://rhn.redhat.com/errata/RHSA-2011-0337.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: vsftpd-2.0.1-9.el4.x86_64.rpm src: vsftpd-2.0.1-9.el4.src.rpm -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 253 bytes Desc: OpenPGP digital signature Url : http://lists.centos.org/pipermail/centos-announce/attachments/20110310/9113ce11/attachment-0001.bin -- Message: 2 Date: Thu, 10 Mar 2011 03:59:56 -0600 From: Johnny Hughes Subject: [CentOS-announce] CESA-2011:0337 Important CentOS 4 i386 vsftpd -security update To: CentOS-Announce Message-ID: <4d78a11c.3020...@centos.org> Content-Type: text/plain; charset="iso-8859-1" CentOS Errata and Security Advisory CESA-2011:0337 vsftpd security update for CentOS 4 i386: https://rhn.redhat.com/errata/RHSA-2011-0337.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: vsftpd-2.0.1-9.el4.i386.rpm src: vsftpd-2.0.1-9.el4.src.rpm -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 253 bytes Desc: OpenPGP digital signature Url : http://lists.centos.org/pipermail/centos-announce/attachments/20110310/f6fbc730/attachment-0001.bin -- ___ CentOS-announce mailing list centos-annou...@centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 73, Issue 3 ** ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
>Your board does not support DDR2. (url for MSI KT3 Ultra) >"Support 2.5v DDR200/266/333 DDR SDRAM DIMM The OP says this: >House-built, Gigabyte MB, AMD Phenom II X6, 6Gb RAM. Somehow, info has gotten crossed... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On Thu, Mar 10, 2011 at 6:35 PM, Kai Schaetzl wrote: > RedShift wrote on Thu, 10 Mar 2011 17:05:02 +0100: > >> That controller doesn't really support RAID, what you're getting is >> commonly called FakeRAID > > If you are referring to the 1068E, that is completely wrong. The vendor who built the server confirmed that the controller card should be LSI 1068E. I found a driver for RHEL5.5 from LSI's page. And some more digging revealed that I should be able to use linux dd=url format for loading the driver from network as the machine has no floppy. I will test that next week when I get my hands on that machine again. A few questions though I would like to get answered: 1) What is the best way to find out if a certain controller etc is supported by the kernel? Do I need to download the kernel src rpm, install it and look for some documentation/source somewhere? 2) If I need to use the binary driver by LSI, how do I proceed with kernel updates? Best regards, Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
centos-boun...@centos.org wrote: >> Your board does not support DDR2. (url for MSI KT3 Ultra) >> "Support 2.5v DDR200/266/333 DDR SDRAM DIMM > > The OP says this: > >> House-built, Gigabyte MB, AMD Phenom II X6, 6Gb RAM. > > Somehow, info has gotten crossed... Possibility... Please excuse... Insert spiffy .sig here: Life is complex: it has both real and imaginary parts. //me *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Apache/Active Directory authentication
On Thu, 10 Mar 2011, Dvorkin, Asya wrote: > John, > > Thank you for all your pointers! You are right.. I was able to create a > keytab file. Still having some issues with getting apache to work the way I > wan to, but will continue troubleshooting it. No problem, and I'll be interested to hear about any other problems you have. I don't get the feeling many people use kerberised Apache. jh ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how to control sftp's user file folder
On Mon, Feb 28, 2011 at 05:53:34PM +0200, Eero Volotinen wrote: > 2011/2/28 Yang Yang : > > hi,i have a question want to ask > > > > if i add a user like: > > > > useradd test > > groupadd test -g www > > > > and how to control user test only can see and write only folder(like > > /home/htdocs/test,he can not see /home/htdocs or other folder) > > for example using chrooted scponly or tweaking filesystem acls and > selinux settings. > > scponly chrooted is the easiest way. I agree. Using scponly and some mount-binds would do the trick. The best way to do this, is to set scponly directory somewhere outside the /home/htdocs, and mount-bind only those directories from /home/htdocs, that that user can write to. -- Dominik Zyla pgpMkPmDN1LR2.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
Peter Peltonen wrote on Thu, 10 Mar 2011 19:08:14 +0200: > 2) If I need to use the binary driver by LSI, how do I proceed with > kernel updates? The download is quite large and you will notice that there is a dkms rpm in it, amongst a lot of other stuff. dkms can cater with updates, AFAIK. It rebuilds the module if it detects a newer kernel or on every reboot or so (others will know better). For this you need to have the build requirements installed on the machine! dkms isn't the preferred method anymore, but I don't think that package contains a "weak update". Kai ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dell PERC H800 commandline RAID monitoring tools
Dominik Zyla wrote on Thu, 10 Mar 2011 09:10:37 +0100: > We're using megacli wrapped by perl to provide information about Perc > events. It works quite well as far. Do you have a megacli rpm that works with the CentOS-provided drivers, which is MPT 3.something? I googled about this some time ago and there's an rpm mentioned here and there that contains only the megacli utility, but it's not downloadable anymore from anywhere. I got hold of a package that cotnains the 4 version, but that doesn't work with the CentOS drivers. LSI themselves provide only the complete MegaRAID driver/package for download and it's not clear if the singe megacli utility is included or if installing it may overwrite the built-in driver. Kai ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
Google for "LSI M1068E". There are a few interesting postings on the first result page, all people with heavy problems to get it working. You have an M1068E which doesn't seem to be the same as 1068E, at least not on the firmware side. You *need* the MegaRAID driver. The built-in won't work. Kai ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On 03/10/11 8:35 AM, Kai Schaetzl wrote: > RedShift wrote on Thu, 10 Mar 2011 17:05:02 +0100: > >> That controller doesn't really support RAID, what you're getting is >> commonly called FakeRAID > If you are referring to the 1068E, that is completely wrong. They do have basic hardware raid, with an embedded control processor, but they don't have any battery back write-back cache, which negates any real advantages of hardware raid. I always configure those as simple SAS controllers and use the OS native software raid (mdraid mirroring in the case of Linux). I also almost never use any raid level above raid1 or 10 (mirror or stripe/mirror). ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On 3/10/2011 12:19 PM, John R Pierce wrote: > >>> That controller doesn't really support RAID, what you're getting is >>> commonly called FakeRAID >> If you are referring to the 1068E, that is completely wrong. > > They do have basic hardware raid, with an embedded control processor, > but they don't have any battery back write-back cache, which negates any > real advantages of hardware raid. How important is the card-level battery if you have a UPS and a scheme to monitor it and do a graceful shutdown before it fails? > I always configure those as simple > SAS controllers and use the OS native software raid (mdraid mirroring in > the case of Linux). I also almost never use any raid level above raid1 > or 10 (mirror or stripe/mirror). I like raid 1 myself because you can recover data from any remaining disk after a failure and software raid because you can use any vendor's controller for that recovery, but if you use raid 5 you might want the hardware controller to do the parity computation work. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On 03/10/11 10:56 AM, Les Mikesell wrote: > How important is the card-level battery if you have a UPS and a scheme > to monitor it and do a graceful shutdown before it fails? how important is your data? if your system *never* crashes, and you're not running something like a database server dependent on committed writes, I'm sure you'd be fine. me, personally, I've had to recover from DC total UPS failures. I like to put redundant power supplies on alternate UPS's, but with datacenter sized UPS's thats often not an option. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dell PERC H800 commandline RAID monitoring tools
On Thu, Mar 10, 2011 at 06:47:09PM +0100, Kai Schaetzl wrote: > Dominik Zyla wrote on Thu, 10 Mar 2011 09:10:37 +0100: > > > We're using megacli wrapped by perl to provide information about Perc > > events. It works quite well as far. > > Do you have a megacli rpm that works with the CentOS-provided drivers, > which is MPT 3.something? I googled about this some time ago and there's > an rpm mentioned here and there that contains only the megacli utility, > but it's not downloadable anymore from anywhere. I got hold of a package > that cotnains the 4 version, but that doesn't work with the CentOS > drivers. LSI themselves provide only the complete MegaRAID driver/package > for download and it's not clear if the singe megacli utility is included > or if installing it may overwrite the built-in driver. It's some single binary version, compiled statically. -- Dominik Zyla pgp8OGyzxf3Vs.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On 3/10/2011 1:01 PM, John R Pierce wrote: > On 03/10/11 10:56 AM, Les Mikesell wrote: >> How important is the card-level battery if you have a UPS and a scheme >> to monitor it and do a graceful shutdown before it fails? > > how important is your data? if your system *never* crashes, and you're > not running something like a database server dependent on committed > writes, I'm sure you'd be fine. > > me, personally, I've had to recover from DC total UPS failures. I like > to put redundant power supplies on alternate UPS's, but with datacenter > sized UPS's thats often not an option. Sure, UPS's fail, plugs get pulled, etc., but the cards and internal batteries most likely have their own failure modes. Or the whole box can fry at once. Did you have any way to tell if your battery-backed saved any data as the disks lost power or did the filesystems just back out the incomplete writes anyway? -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On 03/10/11 11:36 AM, Les Mikesell wrote: > Sure, UPS's fail, plugs get pulled, etc., but the cards and internal > batteries most likely have their own failure modes. Or the whole box > can fry at once. Did you have any way to tell if your battery-backed > saved any data as the disks lost power or did the filesystems just back > out the incomplete writes anyway? battery backed writeback caches on raid controllers flush any pending data to the disks when power is restored. if for some reason they can't, they flag an error when an application (such as database server) or file system issues a fdatasync or fsync, it expects that when that operation returns success, all data has been committed to non-volatile storage.BBWC exist to speed up that critical operation, as actualy committing data to disk is slow and expensive. This is of particular importance to a transactional database server, each COMMIT; has to be committed to disk. I am intentionally sidestepping the issue of cheap desktop grade storage that ignores buffer flush commands as these really aren't suitable for transactional database servers unless your data just isn't that important. IDE and SATA stuff has always been 'soft' on this, while SCSI, FC, and SAS drives are much more consistent. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
John R Pierce wrote on Thu, 10 Mar 2011 10:19:00 -0800: > but they don't have any battery back write-back cache not true, there's a slot on the card to plug a battery pack. Kai ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Can anyone help me understand Apache Errors?
on 07:45 Thu 10 Mar, Todd (slackmoehrle.li...@gmail.com) wrote: > LogWatch reports items like: > > Connection attempts using mod_proxy: >83.167.123.83 -> 205.188.251.1:443: 1 Time(s) >83.167.123.83 -> 64.12.202.36:443: 2 Time(s) > > Requests with error response codes >403 Forbidden > 205.188.251.1:443: 1 Time(s) > 64.12.202.36:443: 2 Time(s) >404 Not Found > //jmx-console/HtmlAdaptor: 1 Time(s) > /VINT_1984_THINK_DIFFERENT: 1 Time(s) > /mobo.png: 1 Time(s) > /player.swf: 1 Time(s) > /robots.txt: 4 Time(s) > > Now, I know mod_proxy is turned off by default, but is there a way to "play > games" with those that attempt a proxy connection? Like a ReWrite rule or > some sort? > > For the 404's, Obviously these don't exist, but robots.txt so I am not sure > why that has a 404. > > What are 406 errors? Some Googling say they are due to mod_security issues > and that an .htaccess fix can turn it off. But I don't understand the issue > and the solution to be honest. HTTP status codes generally: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Slightly more user-friendly descriptive guide: http://www.addedbytes.com/for-beginners/http-status-codes/ 406 indicates an unacceptable request. Bumping up your apache debug levels and watching the error log may help, as could snooping the traffic generating the request (packet/GET request). -- Dr. Ed Morbius, Chief Scientist /| Robot Wrangler / Staff Psychologist| When you seek unlimited power Krell Power Systems Unlimited| Go to Krell! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On 3/10/2011 1:50 PM, John R Pierce wrote: > > battery backed writeback caches on raid controllers flush any pending > data to the disks when power is restored. if for some reason they > can't, they flag an error I know what they are supposed to do - I was just wondering if it happens in practice under real-world conditions. > when an application (such as database server) or file system issues a > fdatasync or fsync, it expects that when that operation returns success, > all data has been committed to non-volatile storage.BBWC exist to > speed up that critical operation, as actualy committing data to disk is > slow and expensive. This is of particular importance to a > transactional database server, each COMMIT; has to be committed to disk. But if you didn't just do the fsync (i.e. you are running just about anything but a transactional db), odds are that the directory update won't match the data and journal recovery will drop it anyway. > > I am intentionally sidestepping the issue of cheap desktop grade storage > that ignores buffer flush commands as these really aren't suitable for > transactional database servers unless your data just isn't that > important. IDE and SATA stuff has always been 'soft' on this, while > SCSI, FC, and SAS drives are much more consistent. I thought there were also problems in layers like lvm that keep the OS from knowing exactly what happened. And a lot of software that should fsync at certain points probably doesn't because linux has historically handled it badly. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Any reliable way to determine LVM snapshot creation time?
We utilize LVM snapshots for some periodic maintenance. They're manually created and, usually, manually destroyed. But not always. So there's now a nightly script monitoring for open snapshots. Which raises the question of when a given snapshot was created. Absent good practices of, say, using sudo to create snapshots (leaving a /var/log/secure message), is there any reasonably reliable way to determine when an LVM was created? There's a timestamp on the /dev/mapper/ file. I'm presuming that's somewhat useful for this purpose? Ah: just found /var/log/messages also indicates: lvm[2314]: Monitoring snapshot lvm[2314]: No longer monitoring snapshot ... which I think answers my own question. Posting here for Google's sake and/or discussion. -- Dr. Ed Morbius, Chief Scientist /| Robot Wrangler / Staff Psychologist| When you seek unlimited power Krell Power Systems Unlimited| Go to Krell! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On 03/10/11 12:40 PM, Les Mikesell wrote: > I thought there were also problems in layers like lvm that keep the OS > from knowing exactly what happened. And a lot of software that should > fsync at certain points probably doesn't because linux has historically > handled it badly. thats another problem entirely. both the MD and LVM layers of linux tend to drop write barriers which are supposed to ensure that key writes occur in the correct order. this is one reason we tend to run our mission critical database servers on Solaris or AIX rather than Linux. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] mkswap - unable to relabel, operation not supported
Hi,
I am getting following error on creating a swap fs. CentOS 5.5
{{{
mkswap: unable to relabel /srv/cloud/one/var/25/images/disk.1 to
system_u:object_r:swapfile_t: Operation not supported
}}}
The selinux is configured in permissive mode. Any clues on what might
be wrong here and how to fix it?
{{{
# /bin/dd if=/dev/zero of=/srv/cloud/one/var/25/images/disk.1 bs=1
count=1 seek=512M
# sudo /sbin/mkswap /srv/cloud/one/var/25/images/disk.1
Setting up swapspace version 1, size = 536866 kB
mkswap: unable to relabel /srv/cloud/one/var/25/images/disk.1 to
system_u:object_r:swapfile_t: Operation not supported
# file /srv/cloud/one/var/25/images/disk.1
/srv/cloud/one/var/25/images/disk.1: Linux/i386 swap file (new style)
1 (4K pages) size 131071 pages
}}}
--
thanks,
neuby.r
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] mkswap - unable to relabel, operation not supported
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2011 04:02 PM, neubyr wrote:
> Hi,
>
> I am getting following error on creating a swap fs. CentOS 5.5
> {{{
> mkswap: unable to relabel /srv/cloud/one/var/25/images/disk.1 to
> system_u:object_r:swapfile_t: Operation not supported
> }}}
>
> The selinux is configured in permissive mode. Any clues on what might
> be wrong here and how to fix it?
>
> {{{
> # /bin/dd if=/dev/zero of=/srv/cloud/one/var/25/images/disk.1 bs=1
> count=1 seek=512M
>
> # sudo /sbin/mkswap /srv/cloud/one/var/25/images/disk.1
> Setting up swapspace version 1, size = 536866 kB
> mkswap: unable to relabel /srv/cloud/one/var/25/images/disk.1 to
> system_u:object_r:swapfile_t: Operation not supported
>
> # file /srv/cloud/one/var/25/images/disk.1
> /srv/cloud/one/var/25/images/disk.1: Linux/i386 swap file (new style)
> 1 (4K pages) size 131071 pages
> }}}
>
> --
> thanks,
> neuby.r
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
Are you doing this on an NFS partition?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk15QXwACgkQrlYvE4MpobP5VACeNEP3g4OJ0ATA040L8w78He2v
9pkAnAuPlGSVHWPoYmIy/BAiekFgeuD+
=1orM
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] mkswap - unable to relabel, operation not supported
On Thu, Mar 10, 2011 at 3:24 PM, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/10/2011 04:02 PM, neubyr wrote:
>> Hi,
>>
>> I am getting following error on creating a swap fs. CentOS 5.5
>> {{{
>> mkswap: unable to relabel /srv/cloud/one/var/25/images/disk.1 to
>> system_u:object_r:swapfile_t: Operation not supported
>> }}}
>>
>> The selinux is configured in permissive mode. Any clues on what might
>> be wrong here and how to fix it?
>>
>> {{{
>> # /bin/dd if=/dev/zero of=/srv/cloud/one/var/25/images/disk.1 bs=1
>> count=1 seek=512M
>>
>> # sudo /sbin/mkswap /srv/cloud/one/var/25/images/disk.1
>> Setting up swapspace version 1, size = 536866 kB
>> mkswap: unable to relabel /srv/cloud/one/var/25/images/disk.1 to
>> system_u:object_r:swapfile_t: Operation not supported
>>
>> # file /srv/cloud/one/var/25/images/disk.1
>> /srv/cloud/one/var/25/images/disk.1: Linux/i386 swap file (new style)
>> 1 (4K pages) size 131071 pages
>> }}}
>>
>> --
>> thanks,
>> neuby.r
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
> Are you doing this on an NFS partition?
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk15QXwACgkQrlYvE4MpobP5VACeNEP3g4OJ0ATA040L8w78He2v
> 9pkAnAuPlGSVHWPoYmIy/BAiekFgeuD+
> =1orM
> -END PGP SIGNATURE-
>
Yup, the 'var' directory in path above is a nfs mount. Is there anyway
I can enable this?
Thanks,
neuby.r
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] mkswap - unable to relabel, operation not supported
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2011 04:37 PM, neubyr wrote:
> On Thu, Mar 10, 2011 at 3:24 PM, Daniel J Walsh wrote:
> On 03/10/2011 04:02 PM, neubyr wrote:
Hi,
I am getting following error on creating a swap fs. CentOS 5.5
{{{
mkswap: unable to relabel /srv/cloud/one/var/25/images/disk.1 to
system_u:object_r:swapfile_t: Operation not supported
}}}
The selinux is configured in permissive mode. Any clues on what might
be wrong here and how to fix it?
{{{
# /bin/dd if=/dev/zero of=/srv/cloud/one/var/25/images/disk.1 bs=1
count=1 seek=512M
# sudo /sbin/mkswap /srv/cloud/one/var/25/images/disk.1
Setting up swapspace version 1, size = 536866 kB
mkswap: unable to relabel /srv/cloud/one/var/25/images/disk.1 to
system_u:object_r:swapfile_t: Operation not supported
# file /srv/cloud/one/var/25/images/disk.1
/srv/cloud/one/var/25/images/disk.1: Linux/i386 swap file (new style)
1 (4K pages) size 131071 pages
}}}
--
thanks,
neuby.r
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
> Are you doing this on an NFS partition?
>>
> Yup, the 'var' directory in path above is a nfs mount. Is there anyway
> I can enable this?
> Thanks,
> neuby.r
Not sure you want to swap on top of NFS. Not sure why it is trying to
label. You could try to specify the nfs label.
mkswap -l system_u:object_r:nfs_t:s0
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk15UMMACgkQrlYvE4MpobMr0ACg1ReIR13nJ4x6XbOlVGul1jcW
kDgAnRNo6MCmkwQvb0fERFGUzykHc5s3
=KzKt
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
On Thu, Mar 10, 2011 at 11:13 AM, Michael Eager wrote: > Previous cleaning have been with canned compressed air. > Thanks for the caution about vacuums and static. I may > use the vacuum on the case fans from the outside. The > case should provide an adequate static shield. I've had good results with a damp, soft cloth or Q-tip with distilled water for awkward bits. and filters, and that cloth for the case itself. It also looks noticeably newer, which helps with walking investors through a small machine room. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On Mar 10, 2011, at 3:49 PM, John R Pierce wrote: > On 03/10/11 12:40 PM, Les Mikesell wrote: >> I thought there were also problems in layers like lvm that keep the OS >> from knowing exactly what happened. And a lot of software that should >> fsync at certain points probably doesn't because linux has historically >> handled it badly. > > thats another problem entirely. both the MD and LVM layers of linux > tend to drop write barriers which are supposed to ensure that key writes > occur in the correct order. this is one reason we tend to run our > mission critical database servers on Solaris or AIX rather than Linux. I think LVM respecting barriers is in RHEL6. The lack of barrier support is mitigated by the battery backed write-back cache, as far as volatility is concerned, though barriers also preserve ordering which BBWBC doesn't guarantee, though advanced RAID controllers should support FUA (forced unit access) which allows properly written scsi subsystems to preserve ordering. An FUA will make sure all pending data is flushed to disk, then the data that the FUA covers is written direct to disk. The barrier support was revised recently to only support FUA devices I believe because non-FUA based devices were too expensive (performance wise) to cludge barrier support for, so if your device doesn't do FUA then it's barriers are basically a no-op. -Ross ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
B.J. McClure keepert...@bellsouth.net Sent from MacBook-Air On Mar 10, 2011, at 5:28 PM, Nico Kadel-Garcia wrote: > On Thu, Mar 10, 2011 at 11:13 AM, Michael Eager wrote: > >> Previous cleaning have been with canned compressed air. >> Thanks for the caution about vacuums and static. I may >> use the vacuum on the case fans from the outside. The >> case should provide an adequate static shield. > > I've had good results with a damp, soft cloth or Q-tip with distilled > water for awkward bits. and filters, and that cloth for the case > itself. It also looks noticeably newer, which helps with walking > investors through a small machine room. I must respectfully disagree with any application of water, distilled or otherwise to things electronic. I was taught in the Navy, and my engineering career has confirmed, that cleaning of electronic components should be done with low pressure, dried, compressed air. 50 psi max. If some solvent must be used, try alcohol. Evaporates quickly, leaves no residue and has an affinity for water. Just my $0.02. Cheers, B.J. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5.5 does not recognise SAS drives with LSI 1068E Controller
On Mar 10, 2011, at 6:33 PM, Ross Walker wrote: > On Mar 10, 2011, at 3:49 PM, John R Pierce wrote: > >> On 03/10/11 12:40 PM, Les Mikesell wrote: >>> I thought there were also problems in layers like lvm that keep the OS >>> from knowing exactly what happened. And a lot of software that should >>> fsync at certain points probably doesn't because linux has historically >>> handled it badly. >> >> thats another problem entirely. both the MD and LVM layers of linux >> tend to drop write barriers which are supposed to ensure that key writes >> occur in the correct order. this is one reason we tend to run our >> mission critical database servers on Solaris or AIX rather than Linux. > > I think LVM respecting barriers is in RHEL6. > > The lack of barrier support is mitigated by the battery backed write-back > cache, as far as volatility is concerned, though barriers also preserve > ordering which BBWBC doesn't guarantee, though advanced RAID controllers > should support FUA (forced unit access) which allows properly written scsi > subsystems to preserve ordering. An FUA will make sure all pending data is > flushed to disk, then the data that the FUA covers is written direct to disk. > > The barrier support was revised recently to only support FUA devices I > believe because non-FUA based devices were too expensive (performance wise) > to cludge barrier support for, so if your device doesn't do FUA then it's > barriers are basically a no-op. Let me correct myself that the drives need to support 'sync', FUA is a nice optional as it negates the need for sync-write-sync, but still for cheap drives that don't respect 'sync' it's a no-op where before it use to do a drain-stop (painfully slow). -Ross ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] mod_encoding
I'm trying to setup the Janrain implementation of OpenID in a dev box running CentOS 5.5. The detect.php script is telling me, "Your web server seems to corrupt queries. Received , expected a=%26b. Check for mod_encoding." Does anyone know what package provides this? Thanks ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Server hangs on CentOS 5.5
On Thu, Mar 10, 2011 at 6:49 PM, B.J. McClure wrote: > > B.J. McClure > keepert...@bellsouth.net > > Sent from MacBook-Air > > > On Mar 10, 2011, at 5:28 PM, Nico Kadel-Garcia wrote: > >> On Thu, Mar 10, 2011 at 11:13 AM, Michael Eager wrote: >> >>> Previous cleaning have been with canned compressed air. >>> Thanks for the caution about vacuums and static. I may >>> use the vacuum on the case fans from the outside. The >>> case should provide an adequate static shield. >> >> I've had good results with a damp, soft cloth or Q-tip with distilled >> water for awkward bits. and filters, and that cloth for the case >> itself. It also looks noticeably newer, which helps with walking >> investors through a small machine room. > > I must respectfully disagree with any application of water, distilled or > otherwise to things electronic. I was taught in the Navy, and my engineering > career has confirmed, that cleaning of electronic components should be done > with low pressure, dried, compressed air. 50 psi max. If some solvent must > be used, try alcohol. Evaporates quickly, leaves no residue and has an > affinity for water. Typical drug-store alcohol is "rubbing alcohol", and is 30% water. I designed medical electronics for a dozen years. Acohol has its uses, but water is much cheaper, safer, and you don't have fumes to deal with. Shall we discuss the effectives of surface etch resist and cladding in protecting circuit boards from damage, and the effects of alcohol on low cost electronic sockets? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Creating the symbolic links in the /boot and /boot/grub/
On Thu, Mar 10, 2011 at 10:43 AM, Simon Matter wrote: >> Well, I have the disks in hand - all 4, but there is the >> overriding level of apprehension. Is there a reference to what I >> should do *if* I cannot reboot that I should read? > > As I said before, you may need to run grub-install, but I don't know for > sure. And then, you have to know where to install grub, and I don't know > where you have installed it. In fact I don't know how we could know This information is normally stored, commented out, in /boot/grub/grub.conf. > because it really depends on how your BIOS boots the box. It can be that > it's installed into the MBR of /dev/hdc, then you should be able to > install it using 'grub-install /dev/hdc'. But, since the disk is named > /dev/hdc, it's most likely that there is also /dev/hda and /dev/hdb, and > then it's also likely that grub has been installed into the MBR of > /dev/hda. Who knows? Don't assume this. If the PATA cable is plugged into a second PATA controller port, and nothing or a CD drive on the first controller port, it would explain how he wound up with /dev/hdc has his hard drive. > That said, check disk 1 by putting it into another computer, and chose > 'linux rescue' at the boot prompt. Then it will boot using a root > filesystem in ram, and configure network if you want and then tries to > find any CentOS installation in the disks, and mount them if it finds one. > Maybe it wont find one but it should find it on your server. Then it will > mount it as something like /mnt/sysimage. You can then 'chroot > /mnt/sysimage' and fix things. Yeah, I love the live CD's for this as well. > Good luck! > Simon ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Installing odbtp on CentOS 5.5
I have just bought a new machine and of course installed CentOS 5.5 x86_64 from a recently created DVD. So the machine has: PHP Version => 5.2.17 MySQL Client API version => 5.0.77 Apache/2.2.3 Does anyone know how to get odbtp installed? I have followed all the INSTALL and README instructions that came with the odbtp package including the README.64bitOS file. There has got to be a trick some where that I am missing. TIA. Regards, Ron Young 919-621-9015 http://www.linkedin.com/in/ronhyoung +++ Little tiny dreams require little tiny thoughts and little tiny steps. Great big dreams require great big thoughts and little tiny steps. +++ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Race condition with mdadm at boot [still mystifying]
This is a bit long-winded, but I wanted to share some info Regarding my earlier message about a possible race condition with mdadm, I have been doing all sorts of poking around with the boot process. Thanks to a tip from Steven Yellin at Stanford, I found where to add a delay in the rc.sysinit script, which invokes mdadm to assemble the arrays. Unfortunately it didn't help, so it likely wasn't a race condition after all. However, on close examination of dmesg, I found something very interesting. There were missing 'bind' statements for one or the other hot spare drive (or sometimes both). These drives are connected to the last PHYs in each SATA controller ... in other words they are the last devices probed by the driver for a particular controller. It would appear that the drivers are bailing out before managing to enumerate all of the partitions on the last drive in a group, and missing partitions occur quite randomly. So it may or may not be a timing issue between the WD Caviar Black drives and both the LSI and Marvell SAS/SATA controller chips. So, I replaced the two drives (SATA-300) with two faster drives (SATA-600) on the off chance they might respond fast enough before the drivers move on to other duties. That didn't help either. Each group of arrays uses completely drivers (mptsas and sata_mv) but both exhibit the same problem, so I'm mystified as to where the real issue lies. Anyone care to offer suggestions? Chuck ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Installation failure
I'm trying to reinstall CentOS on a machine I've reconditioned for it, but for reasons I can't fathom, when the installation disk comes up and prompts for the install type, and I type either (graphics isntall) or "linux text", after it loads the initrd image, the machine shuts off. It's an older machine I built myself (and ran CentOS on for a number of years), AMD Athlon 64 x2, 2GB of memory, 2 SATA hard drives, ECS GE6100PM-M2 motherboard. I should probably even know the answer to this one, but I'm stumped. Any suggestions? Thanks. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Installation failure
2011/3/11 Mark : > I'm trying to reinstall CentOS on a machine I've reconditioned for it, is it really working? check for broken memory chips and so.. > but for reasons I can't fathom, when the installation disk comes up > and prompts for the install type, and I type either (graphics > isntall) or "linux text", after it loads the initrd image, the > machine shuts off. > > It's an older machine I built myself (and ran CentOS on for a number > of years), AMD Athlon 64 x2, 2GB of memory, 2 SATA hard drives, ECS > GE6100PM-M2 motherboard. > What error messages it displays? -- Eero ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Race condition with mdadm at boot [still mystifying]
On 3/10/11 9:25 PM, Chuck Munro wrote: > However, on close examination of dmesg, I found something very > interesting. There were missing 'bind' statements for one or the > other hot spare drive (or sometimes both). These drives are connected > to the last PHYs in each SATA controller ... in other words they are the > last devices probed by the driver for a particular controller. It would > appear that the drivers are bailing out before managing to enumerate all > of the partitions on the last drive in a group, and missing partitions > occur quite randomly. > > So it may or may not be a timing issue between the WD Caviar Black > drives and both the LSI and Marvell SAS/SATA controller chips. I've seen some weirdness in powering up 6 or more SATA drives but never completely pinned down whether it was the controller, drive cage, or particular drives causing the problem. But I think my symptom was completely failing to detect some drives when certain combinations of disks were installed although each would work individually. Do you have any options about whether they power up immediately or wait until accessed? -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Installation failure
On Thu, Mar 10, 2011 at 8:18 PM, Eero Volotinen wrote: > 2011/3/11 Mark : >> I'm trying to reinstall CentOS on a machine I've reconditioned for it, > > is it really working? check for broken memory chips and so.. > The memory was working perfectly before I put it into this boc (came out of another one that's been running for months). >> but for reasons I can't fathom, when the installation disk comes up >> and prompts for the install type, and I type either (graphics >> isntall) or "linux text", after it loads the initrd image, the >> machine shuts off. >> >> It's an older machine I built myself (and ran CentOS on for a number >> of years), AMD Athlon 64 x2, 2GB of memory, 2 SATA hard drives, ECS >> GE6100PM-M2 motherboard. > > What error messages it displays? > None - the dots print out, then the screen goes black and the machine shuts off. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Installation failure
Try checking the power supply, swap in another one from a different pc. Chris -Original Message- From: Mark Sent: Thursday, March 10, 2011 10:50 PM To: CentOS mailing list Subject: Re: [CentOS] Installation failure On Thu, Mar 10, 2011 at 8:18 PM, Eero Volotinen wrote: > 2011/3/11 Mark : >> I'm trying to reinstall CentOS on a machine I've reconditioned for it, > > is it really working? check for broken memory chips and so.. > The memory was working perfectly before I put it into this boc (came out of another one that's been running for months). >> but for reasons I can't fathom, when the installation disk comes up >> and prompts for the install type, and I type either (graphics >> isntall) or "linux text", after it loads the initrd image, the >> machine shuts off. >> >> It's an older machine I built myself (and ran CentOS on for a number >> of years), AMD Athlon 64 x2, 2GB of memory, 2 SATA hard drives, ECS >> GE6100PM-M2 motherboard. > > What error messages it displays? > None - the dots print out, then the screen goes black and the machine shuts off. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos - No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1204 / Virus Database: 1497/3499 - Release Date: 03/10/11 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Installation failure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark said the following on 11/03/11 04:51: > Any suggestions? If is not an issue related to the hardware try with linux text acpi=off Ciao, luigi - -- / +--[Luigi Rosa]-- \ You can tune a filesystem, but you can't tuna fish. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk15tNAACgkQ3kWu7Tfl6ZT8SgCfRTV0BSZNFDl/lNbNCZyPX77b SWUAniECY404s3LFW1D4EsyUYho3PfWF =bx2u -END PGP SIGNATURE- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Cannot %include in CentOS 5.5 kickstart
I've previously used includes in CentOS 4.4 and they worked fine. But in CentOS 5.5, trying to specify a driver disk via an include does not work. If I instead specify it directly, it loads fine. When it fails (because it can't see the disk drive - needs the driver disk to see the hard disk), in Console 2 I can see that /tmp/drvdisk exists and has the line I wrote to it. I see nothing that looks wrong in any log or kickstart file/fragment in /tmp. Any ideas? Here's my complete kickstart to show/test this: # Minimal Kickstart test for CentOS 5.5 to show %include problem url --url=http://10.0.4.157/cblr/links/CentOS5.5-i386 text lang en_US.UTF-8 keyboard us timezone --utc America/New_York install bootloader --location=mbr clearpart --all --initlabel network --device eth0 --bootproto dhcp firewall --disabled selinux --disabled rootpw --iscrypted \$1\$x6z.qvwE\$7Zg9g1rCEgvOBoA7Oo/HF1 zerombr authconfig --useshadow --enablemd5 part /boot --fstype ext3 --size 100 --asprimary part / --fstype ext3 --size 1 --grow --asprimary part /var --fstype ext3 --size 1 part swap --recommended # This does not work %include /tmp/drvdisk # This works #driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img %packages @base @core %pre --erroronfail echo "driverdisk --source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img" > /tmp/drvdisk # (end of kickstart file) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Installation failure
On Thu, Mar 10, 2011 at 9:01 PM, Chris Weisiger wrote: > Try checking the power supply, swap in another one from a different pc. > Yeah, I figured that out about half an hour ago and got it going. Shoulda thought of that up front. Interestingly, I have a power supply tester I bought at CompUSA before they left SoCal, and it said that power supply was fine. Ha ha ha. I think I need a new one, one that actually works Thanks, everyone. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
