RE: cannot find correct attribute for omconfig BIOS mod
Check if the services are running - srvadmin-services.sh status. The dsm_sa_datamgrd needs to be running. -Original Message- From: linux-poweredge-boun...@dell.com [mailto:linux-poweredge-boun...@dell.com] On Behalf Of Rahul Nabar Sent: Tuesday, February 02, 2010 12:10 AM To: Vanush Misha Cc: linux-poweredge-Lists Subject: Re: cannot find correct attribute for omconfig BIOS mod On Mon, Feb 1, 2010 at 11:39 AM, Vanush Misha wrote: useful for you? > another one tro try would be "omreport chassis biossetup" and see > what's showing up there. I've used "omconfig chassis biossetup" to > enable "CPU Virtualization Technology (cpuvt)" and "AC power recovery > mode (acpwrrecovery)" on PE2900 in the past. > omconfig chassis biossetup -? Error! BIOS setup feature unavailable on this system. I just don't get it! -- Rahul ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Debian Lenny on R610 with PERC 6/i
I have dumbed down the config to just root, swap, and home on primary partitons. It still hangs immediately after the DRAC. Any other ideas? I am going to grab Ubuntu and SuSE iso's just to test. Unfortunately the app developer we are working with insists on Debian Lenny. While I do like Debian it never has been a great choice for "new" hardware configs... Rob Heilman via mobile On Feb 1, 2010, at 9:19 AM, "Daniel Robitaille" wrote: > Could it be a problem grub trying to boot from a LVM partition. A > quick Google search > turns up this, so it can be done using Grub 2 and Lenny: > > http://jim.studt.net/depository/index.php/debian-lenny-and-grub-with-boot-in-lvm > > But he does mention the extra option he had to add to the grub > config file. Maybe something > similar needs to be done in the grub "legacy" setup? > > Daniel > > > On Mon, 01 Feb 2010, Rob Heilman wrote: > >> I chose the legacy GRUB option. >> >> I built a 4+1 (500GB Seagates) RAID 5 group in the PERC BIOS and >> left another disk for a hot spare. >> >> -Rob Heilman >> >> On Feb 1, 2010, at 3:48 AM, ROUSSEL Kévin wrote: >> >>> Rob Heilman a écrit : I am attempting to install Debian Lenny on a Dell R610 equipped with a PERC 6/i controller. I built a 4+1 (500GB Seagates) RAID 5 group in the PERC BIOS and left another disk for a hot spare. I was able to boot from the Debian DVD, create LVM, partitions, etc. Other than the bnx2 firmware it was a very non-eventful install process. When the machine attempts to boot from the PERC based drive it simply hangs. The last thing I see is from the DRAC: Press for Remote Access Setup within 5 sec. After that just a line wrap or two when the 5 seconds lapses. My assumption is that something is wrong with the boot loader process. Is the 1.8TB LUN/SD exceeding a size limit I am unaware of? Do I need any particular modules/drivers in the initrd to allow it to boot? Any other ideas? >>> >>> During the Debian Lenny install, which version of GRUB did you >>> choose to >>> install? I would recommend install the "legacy" version (GRUB >>> 0.9x), the >>> newer version of GRUB (1.9x) is still not considered stable by >>> Debian. >>> >>> Other question, could you give us more precision on how you >>> configured >>> the PERC and disks (like RAID level, for example) ? >>> -- >>> >>> >>> Kévin Roussel >>> Ingénieur-expert, projet OPEN-PEOPLE >>> Équipe TRIO, INRIA Nancy Grand-Est >>> >>> ___ >>> Linux-PowerEdge mailing list >>> Linux-PowerEdge@dell.com >>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge >>> Please read the FAQ at http://lists.us.dell.com/faq >> >> >> ___ >> Linux-PowerEdge mailing list >> Linux-PowerEdge@dell.com >> https://lists.us.dell.com/mailman/listinfo/linux-poweredge >> Please read the FAQ at http://lists.us.dell.com/faq > > -- > Daniel Robitaille > ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Help with ISCSI SAN
Hi Paul, Thanks for the response. I actually now have physical access to the kit we have bought and it turns out I mis-understood exactly what we have. Rather than purchasing HBA's we have purchased network cards that do ISCSI offloading I believe its called iSOE. I have been able to set up one system using software ISCSI initiation and ignoring iSOE so now the plan for this week is to see if I can get iSOE working and compare the two systems :) Paul M. Dyer wrote: > Hi Clint, > > My feeling is that the NIC on the server is not where most multipath happens. > You could use bonding for 2 NICs to have a secondary NIC take over if the > path from server NIC-1 gets disconnected. > > On the other end is where multipath takes place. On a setup that I have, > multipath logs in to 4 different paths on the SAN, and shows the paths with > "multipath -l": > > xr (36006016025302300a2f50e7c0981de11) dm-10 DGC,RAID 1 > [size=24G][features=1 queue_if_no_path][hwhandler=1 emc][rw] > \_ round-robin 0 [prio=0][active] > \_ 1:0:0:6 sdz 65:144 [active][undef] > \_ 3:0:0:6 sdaa 65:160 [active][undef] > \_ round-robin 0 [prio=0][enabled] > \_ 2:0:0:6 sdab 65:176 [active][undef] > \_ 4:0:0:6 sdac 65:192 [active][undef] > > > Paul > > > > - Original Message - > From: "Clint Dilks" > To: linux-poweredge@dell.com > Sent: Tuesday, January 12, 2010 9:09:09 PM (GMT-0600) America/Chicago > Subject: Help with ISCSI SAN > > Hello Everyone > > I am wanting feed back from people familiar with Dell Equallogic ISCSI SANS. > > Our organization has just purchased a Dell Equallogic ISCSI SAN with > all the equipment required to allow a host to have fully redundant paths > to this SAN. > > We have also purchased PowerEdge Servers with Broadcom NetXtremeII Nics > /ISCSI HBA's. On some of these servers we want to run Redhat Enterprise > Linux 5.4 or CentOS 5.4 > > I can find documentation on using Software ISCSI initiators, but nothing > on using Broadcom Hardware HBA's so I am assuming it is a case of go > into the BIOS of the server put in the license key for the Hardware HBA > and then another device that looks like a Nic will be present once RHEL > or CentOS is installed. Is this correct ? > > If this is the case I am assuming I still use the open iscsi initiator > tools to manage things ? > > To ensure redundancy each Linux host will have two nics going connected > to the ISCSI network. And I am aware that I can use dmsetup / multipath > to setup a redundant device but one thing that confuses me is that if > the two nics (each connected to a separate switch) are on the same > subnet (as Dell have instructed me to do) how can you guarantee that > the two connections you see are using the appropriate redundant paths ? > Or is this not really an issue ? > > > Thank you for any thoughts or experiences that you can share related to > a setup like this, and have a nice day :) > > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq > > ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: cannot find correct attribute for omconfig BIOS mod
On Mon, Feb 1, 2010 at 11:39 AM, Vanush Misha wrote: useful for you? > another one tro try would be "omreport chassis biossetup" and see > what's showing up there. I've used "omconfig chassis biossetup" to > enable "CPU Virtualization Technology (cpuvt)" and "AC power recovery > mode (acpwrrecovery)" on PE2900 in the past. > omconfig chassis biossetup -? Error! BIOS setup feature unavailable on this system. I just don't get it! -- Rahul ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Help with ISCSI SAN
Hi Clint, My feeling is that the NIC on the server is not where most multipath happens. You could use bonding for 2 NICs to have a secondary NIC take over if the path from server NIC-1 gets disconnected. On the other end is where multipath takes place. On a setup that I have, multipath logs in to 4 different paths on the SAN, and shows the paths with "multipath -l": xr (36006016025302300a2f50e7c0981de11) dm-10 DGC,RAID 1 [size=24G][features=1 queue_if_no_path][hwhandler=1 emc][rw] \_ round-robin 0 [prio=0][active] \_ 1:0:0:6 sdz 65:144 [active][undef] \_ 3:0:0:6 sdaa 65:160 [active][undef] \_ round-robin 0 [prio=0][enabled] \_ 2:0:0:6 sdab 65:176 [active][undef] \_ 4:0:0:6 sdac 65:192 [active][undef] Paul - Original Message - From: "Clint Dilks" To: linux-poweredge@dell.com Sent: Tuesday, January 12, 2010 9:09:09 PM (GMT-0600) America/Chicago Subject: Help with ISCSI SAN Hello Everyone I am wanting feed back from people familiar with Dell Equallogic ISCSI SANS. Our organization has just purchased a Dell Equallogic ISCSI SAN with all the equipment required to allow a host to have fully redundant paths to this SAN. We have also purchased PowerEdge Servers with Broadcom NetXtremeII Nics /ISCSI HBA's. On some of these servers we want to run Redhat Enterprise Linux 5.4 or CentOS 5.4 I can find documentation on using Software ISCSI initiators, but nothing on using Broadcom Hardware HBA's so I am assuming it is a case of go into the BIOS of the server put in the license key for the Hardware HBA and then another device that looks like a Nic will be present once RHEL or CentOS is installed. Is this correct ? If this is the case I am assuming I still use the open iscsi initiator tools to manage things ? To ensure redundancy each Linux host will have two nics going connected to the ISCSI network. And I am aware that I can use dmsetup / multipath to setup a redundant device but one thing that confuses me is that if the two nics (each connected to a separate switch) are on the same subnet (as Dell have instructed me to do) how can you guarantee that the two connections you see are using the appropriate redundant paths ? Or is this not really an issue ? Thank you for any thoughts or experiences that you can share related to a setup like this, and have a nice day :) ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: cannot find correct attribute for omconfig BIOS mod
Rahul, On Mon, 1 Feb 2010 11:24:43 -0600 Rahul Nabar wrote: > I was told by Dell support that I could use "omconfig system biossetup > attribute=cpucore setting=all" to change a BIOS setting that restricts > my cores to half. > > Problem is I haven't gotten this to work I get an error message each > time: Error! Invalid command: biossetup > > If I try "omconfig chassis biossetup attribute=cpucore setting=all" it > still throws > Error! This BIOS setup feature is not present on this system. does "omconfig chassis biossetup -? " show anything useful for you? another one tro try would be "omreport chassis biossetup" and see what's showing up there. I've used "omconfig chassis biossetup" to enable "CPU Virtualization Technology (cpuvt)" and "AC power recovery mode (acpwrrecovery)" on PE2900 in the past. Misha. -- Vanush "Misha" Paturyan Senior Technical Officer Computer Science Department NUI Maynooth ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: R410's shipped out with BIOS showing 4 cores instead of 8
Rahul Nabar wrote: > I dried dmidecode but cannot figure out the exact setting line I need. > Rahul, FWIW, this will give you an indication of the settings of the system's core enabled status & Symmetric Multi-Threading (SMT)/ HyperThreading (HT) settings # dmidecode -t processor |egrep '(Socket Des|Version|Core|Thread)' Socket Designation: CPU1 Version: Intel(R) Xeon(R) CPU X5550 @ 2.67GHz Core Count: 4 Core Enabled: 4 Thread Count: 8 Socket Designation: CPU2 Version: Intel(R) Xeon(R) CPU X5550 @ 2.67GHz Core Count: 4 Core Enabled: 4 Thread Count: 8 This shows two sockets, each with X5550 cpus, all cores (4) enabled on each and SMT enabled (twice as many threads as cores) For Windows: C:\> WMIC CPU Get Name, NumberOfCores, NumberOfLogicalProcessors /format:list Name=Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz NumberOfCores=4 NumberOfLogicalProcessors=4 These obviously can't be used to set/change the values, use sysdtk or activateCmosToken, as Tim Small says. --stephen ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
cannot find correct attribute for omconfig BIOS mod
I was told by Dell support that I could use "omconfig system biossetup attribute=cpucore setting=all" to change a BIOS setting that restricts my cores to half. Problem is I haven't gotten this to work I get an error message each time: Error! Invalid command: biossetup If I try "omconfig chassis biossetup attribute=cpucore setting=all" it still throws Error! This BIOS setup feature is not present on this system. Unfortunately I cannot find the attribute "cpucore" anywhere in the documentation for Open Manage. Is this atribute really present and documented somewhere or am I barking up the wrong tree? -- Rahul ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: R410's shipped out with BIOS showing 4 cores instead of 8
On Mon, Feb 1, 2010 at 11:02 AM, Robert von Bismarck wrote: >> R410's R710 and R510 all are doing this currently (says my TAM). >> >> I can't say why but I was told it's a "feature" not a "bug". >> Very non-intuitive to me. I can't see why an 8 core server >> defaulting to 4 core makes sense. >> > > We got two R410 exhibiting the same "feature" here. > It's probably a "feature" for some alternative OS's that require > licensing on a per-core basis. > For higher performance, is it better to have two quad-core acting as > dual-core processors due to bios setting, or one quad-core ? I have no clue. I always worked with Linux and HPC and these systems are capable of using all the cores I throw at them. Cheers! -- Rahul ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: R410's shipped out with BIOS showing 4 cores instead of 8
Hi Robert, On Mon, Feb 01, 2010 at 06:02:10PM +0100, Robert von Bismarck wrote: [...] > > R410's R710 and R510 all are doing this currently (says my TAM). > > > > I can't say why but I was told it's a "feature" not a "bug". > > Very non-intuitive to me. I can't see why an 8 core server > > defaulting to 4 core makes sense. > > > > We got two R410 exhibiting the same "feature" here. > It's probably a "feature" for some alternative OS's that require > licensing on a per-core basis. > For higher performance, is it better to have two quad-core acting as > dual-core processors due to bios setting, or one quad-core ? I suppose, the only valid answer is: Do your own benchmarks. It depends on such a lot of factors (data locality, hardware architecture details, cache coherency, bus contention etc. pp) that you simply cannot predict how your particular application will perform. HTH, Tino. -- "What we nourish flourishes." - "Was wir nähren erblüht." www.lichtkreis-chemnitz.de www.tisc.de ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: R410's shipped out with BIOS showing 4 cores instead of 8
> > Thanks guys for helping out! I got the official answer from > Dell just a few minutes ago. Apparently the Dell servers are > doing this strange BIOS setting by design. I quote my > Technical Account Manager below. > > ## > [snip] > My apologies we were quite busy today, and I was just about > to email you with the results. I have been able to check our > tools, and with several technicians. The bios setting by > default is set to dual. This is the same for the R710, R410, > and R510 servers. As of right now it looks like the only way > to change that is by either physically going to each server, > and booting into the bios and changing the processor settings. > [snip] > ### > > > R410's R710 and R510 all are doing this currently (says my TAM). > > I can't say why but I was told it's a "feature" not a "bug". > Very non-intuitive to me. I can't see why an 8 core server > defaulting to 4 core makes sense. > We got two R410 exhibiting the same "feature" here. It's probably a "feature" for some alternative OS's that require licensing on a per-core basis. For higher performance, is it better to have two quad-core acting as dual-core processors due to bios setting, or one quad-core ? Cheers, -- Robert ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: R410's shipped out with BIOS showing 4 cores instead of 8
On Mon, Feb 1, 2010 at 3:23 AM, Tim Small wrote: > You can use "dumpCmos" from the smbios utilities to dump all of the BIOS > settings from the Linux commandline. Do a diff of the two sets of dumps > with the dual-core/quad-core setting having been manually changed... > You can then use "activateCmosToken" to change the same setting on all > your servers - which should be trivial to automate. Thanks Tim! What's the exact command again? I see the following on my system,: smbios-get-ut-data smbios-rbu-bios-update smbios-sys-info-lite smbios-wakeup-ctl smbios-lcd-brightness smbios-state-byte-ctl smbios-token-ctl smbios-wireless-ctl smbios-passwd smbios-sys-info smbios-upflag-ctl Am I missing a Dell repo that needs to be installed! I dried dmidecode but cannot figure out the exact setting line I need. > I'd also push for financial compensation, I think! I wish! :) Is there Dell management lurking on the list? -- Rahul ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
How to downgrade bnx2 nic driver on r610 w/ rhel 5
Hey Guys - I have an R610 that's giving me a lot of errors on the nic interface eth1. I ran ethtool -i eth1 and found that it's running a more recent bnx2 driver than my other R610. ethtool -i eth1 driver: bnx2 version: 1.9.3 firmware-version: 5.0.6 NCSI 2.0.3 bus-info: :01:00.1 I'd like to downgrade the driver to version: 1.6.9 - which runs fine on my other machine. How would I do accomplish this? This message (and any attachments) is intended solely for the addressee and its content may be confidential, privileged or otherwise protected from disclosure. Nothing herein should be construed as an offer or solicitation to do business with Capstone Holdings Group L.L.C. or its affiliates (together, "Capstone"). If you receive this message in error, please delete it and immediately notify the sender. Any dissemination, duplication, or publication to unauthorized third parties or other use of the contents of this message (or its attachments) is strictly forbidden. Capstone reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept any messages (and attachments) to and from any Capstone systems. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: update_firmware not showing updates ?
> After running this command (Is this a one time command, or should I run > this before updating the firmwares ?) One time to install rpms, after that 'up2date -u' will keep you updated. > Not sure why It's reporting the bios 2 times and no update for eth1 ? Not sure about eth1. The BIOS is there 2 times because firmware-addon-dell can update the bios using lisbmios, however, the bios updates in the repo are configured to use dell_ie_bios which is a little different. -Jeff ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: update_firmware not showing updates ?
>-Original Message- >From: jeffrey_l_mend...@dell.com [mailto:jeffrey_l_mend...@dell.com] >Sent: maandag 1 februari 2010 16:31 >To: Stephan van Hienen; linux-powere...@lists.us.dell.com >Subject: RE: update_firmware not showing updates ? > >Looks like you have firmware-tools installed, but no firmware. Try: > ># up2date --solvedeps=$(bootstrap_firmware -u) After running this command (Is this a one time command, or should I run this before updating the firmwares ?) I'm getting the following output : = Running system inventory... Searching storage directory for available BIOS updates... Checking BIOS - 2.3.1 Available: dell_dup_componentid_00159 - 2.6.1 Found Update: dell_dup_componentid_00159 - 2.6.1 Checking SAS/SATA Backplane 0:0 Backplane Firmware - 1.05 Available: dell_dup_componentid_11204 - 1.05 Did not find a newer package to install that meets all installation checks. Checking System BIOS for PowerEdge 1950 - 2.3.1 Did not find a newer package to install that meets all installation checks. Checking NetXtreme II BCM5708 Gigabit Ethernet rev 11 (eth0) - 4.6.0 Did not find a newer package to install that meets all installation checks. Checking PERC 5/i Integrated Controller 0 Firmware - 5.2.1-0067 Available: pci_firmware(ven_0x1028_dev_0x0015_subven_0x1028_subdev_0x1f03) - 5.2.2-0072 Found Update: pci_firmware(ven_0x1028_dev_0x0015_subven_0x1028_subdev_0x1f03) - 5.2.2-0072 Checking NetXtreme II BCM5708 Gigabit Ethernet rev 11 (eth1) - 1.8.0 Did not find a newer package to install that meets all installation checks. Checking BMC - 2.37 Available: dell_dup_componentid_05814 - 2.37 Did not find a newer package to install that meets all installation checks. Checking MAY2036RC Firmware - d108 Did not find a newer package to install that meets all installation checks. Found firmware which needs to be updated. Not sure why It's reporting the bios 2 times and no update for eth1 ? Think I'll stick to SUU for the moment ;) Stephan ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: update_firmware not showing updates ?
> -Original Message- > From: linux-poweredge-bounces-Lists On Behalf Of Stephan van Hienen > Sent: Sunday, January 31, 2010 11:23 AM > To: linux-poweredge-Lists > Subject: update_firmware not showing updates ? > > I tried running update_firmware on an outdated PE1950 system today, but it > didn't have any updates ? > Output from update_firmware below (system is running RHEL 4.8) > Looks like you have firmware-tools installed, but no firmware. Try: # up2date --solvedeps=$(bootstrap_firmware -u) -Jeff ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: Firmware updates not being applied to PE2950
From: linux-poweredge-bounces-Lists On Behalf Of Brandon Ooi Sent: Saturday, January 30, 2010 8:16 PM To: linux-poweredge-Lists Subject: Firmware updates not being applied to PE2950 Here are the steps I've followed to get to this point... yum -y install procmail OpenIPMI chkconfig --level 345 ipmi on service ipmi start wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash yum -y install srvadmin-all #relogin srvadmin-services.sh enable srvadmin-services.sh start wget -q -O - http://linux.dell.com/repo/community/bootstrap.cgi | bash wget -q -O - http://linux.dell.com/repo/firmware/bootstrap.cgi | bash yum -y install firmware-addon-dell yum -y install dell_ft_install yum -y install $(bootstrap_firmware) --- I wouldn't configure both the old firmware repo and the current hardware repo. Try: Removing the firmware repo Removing firmware-tools and everything that depends on it. Redo: yum -y install dell_ft_install yum -y install $(bootstrap_firmware) Run: update_firmware --yes -v Capture: /var/log/firmware-updates.log Send the output of the update command and the log. -Jeff ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
RE: PERC 6/i Integrated / High "Other Error Count":
This is why Dell doesn't want you using the LSI tools, because they are often hard to understand. :) That being said, "Other Error Count" is just a bucket for anything wrong with the drive that doesn't include the actual media. So if the firmware returns certain SENSE codes or if the SMART for temperature problems is raised, etc. Unless you have these errors on multiple drives, I'd say it's pretty safe to assume it's just a single drive failure/problem. To be sure you can look at the controller log (called TTY log in the LSI utilities) this should list all the failure events for the drive and the cause. -Original Message- From: linux-poweredge-bounces-Lists On Behalf Of Jacques Marneweck Sent: Sunday, January 31, 2010 11:00 PM To: linux-poweredge-Lists Subject: PERC 6/i Integrated / High "Other Error Count": Hi, I'm seeing a high "Other Error Count" on a drive on a Dell PowerEdge R710. PD: 3 Information Enclosure Device ID: 32 Slot Number: 5 Device Id: 5 Sequence Number: 3 Media Error Count: 0 Other Error Count: 789965 Predictive Failure Count: 0 Last Predictive Failure Event Seq Number: 0 Raw Size: 572325MB [0x45dd2fb0 Sectors] Non Coerced Size: 571813MB [0x45cd2fb0 Sectors] Coerced Size: 571776MB [0x45cc Sectors] Firmware state: Failed What does "Other Error Count" mean? Nothing useful is coming up while I'm googling on this subject - I've never seen an "Other Error Count" on Dell boxes before that is > 0 Does this mean that I have a hardware issue with the raid controller in the PER710? Regards --jm -- Jacques Marneweck http://www.powertrip.co.za/ http://www.powertrip.co.za/blog/ http://www.ataris.co.za/ ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Debian Lenny on R610 with PERC 6/i
Could it be a problem grub trying to boot from a LVM partition. A quick Google search turns up this, so it can be done using Grub 2 and Lenny: http://jim.studt.net/depository/index.php/debian-lenny-and-grub-with-boot-in-lvm But he does mention the extra option he had to add to the grub config file. Maybe something similar needs to be done in the grub "legacy" setup? Daniel On Mon, 01 Feb 2010, Rob Heilman wrote: > I chose the legacy GRUB option. > > I built a 4+1 (500GB Seagates) RAID 5 group in the PERC BIOS and left another > disk for a hot spare. > > -Rob Heilman > > On Feb 1, 2010, at 3:48 AM, ROUSSEL Kévin wrote: > > > Rob Heilman a écrit : > >> I am attempting to install Debian Lenny on a Dell R610 equipped with a > >> PERC 6/i controller. I built a 4+1 (500GB Seagates) RAID 5 group in the > >> PERC BIOS and left another disk for a hot spare. I was able to boot from > >> the Debian DVD, create LVM, partitions, etc. Other than the bnx2 firmware > >> it was a very non-eventful install process. > >> > >> When the machine attempts to boot from the PERC based drive it simply > >> hangs. The last thing I see is from the DRAC: > >> > >> Press for Remote Access Setup within 5 sec. > >> > >> After that just a line wrap or two when the 5 seconds lapses. > >> > >> My assumption is that something is wrong with the boot loader process. Is > >> the 1.8TB LUN/SD exceeding a size limit I am unaware of? Do I need any > >> particular modules/drivers in the initrd to allow it to boot? Any other > >> ideas? > > > > During the Debian Lenny install, which version of GRUB did you choose to > > install? I would recommend install the "legacy" version (GRUB 0.9x), the > > newer version of GRUB (1.9x) is still not considered stable by Debian. > > > > Other question, could you give us more precision on how you configured > > the PERC and disks (like RAID level, for example) ? > > -- > > > > > > Kévin Roussel > > Ingénieur-expert, projet OPEN-PEOPLE > > Équipe TRIO, INRIA Nancy Grand-Est > > > > ___ > > Linux-PowerEdge mailing list > > Linux-PowerEdge@dell.com > > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > > Please read the FAQ at http://lists.us.dell.com/faq > > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq -- Daniel Robitaille ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Debian Lenny on R610 with PERC 6/i
I chose the legacy GRUB option. I built a 4+1 (500GB Seagates) RAID 5 group in the PERC BIOS and left another disk for a hot spare. -Rob Heilman On Feb 1, 2010, at 3:48 AM, ROUSSEL Kévin wrote: > Rob Heilman a écrit : >> I am attempting to install Debian Lenny on a Dell R610 equipped with a PERC >> 6/i controller. I built a 4+1 (500GB Seagates) RAID 5 group in the PERC >> BIOS and left another disk for a hot spare. I was able to boot from the >> Debian DVD, create LVM, partitions, etc. Other than the bnx2 firmware it >> was a very non-eventful install process. >> >> When the machine attempts to boot from the PERC based drive it simply hangs. >> The last thing I see is from the DRAC: >> >> Press for Remote Access Setup within 5 sec. >> >> After that just a line wrap or two when the 5 seconds lapses. >> >> My assumption is that something is wrong with the boot loader process. Is >> the 1.8TB LUN/SD exceeding a size limit I am unaware of? Do I need any >> particular modules/drivers in the initrd to allow it to boot? Any other >> ideas? > > During the Debian Lenny install, which version of GRUB did you choose to > install? I would recommend install the "legacy" version (GRUB 0.9x), the > newer version of GRUB (1.9x) is still not considered stable by Debian. > > Other question, could you give us more precision on how you configured > the PERC and disks (like RAID level, for example) ? > -- > > > Kévin Roussel > Ingénieur-expert, projet OPEN-PEOPLE > Équipe TRIO, INRIA Nancy Grand-Est > > ___ > Linux-PowerEdge mailing list > Linux-PowerEdge@dell.com > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
IPMI temperature sensors
I have a question about IPMI temperature monitoring, and I'm hoping that someone on the list can help. We have various Dell Poweredge servers which we want to shut down cleanly when the temperature gets too high. The idea is to do a clean shutdown before any damage is done and before they would reach the point at which the systems would start cutting off their own power to preserve the hardware. The servers mostly run Scientific Linux 5. What's the appropriate temperature at which to shut down the machine? I'm guessing that the ambient temperature would be the thing to look at. When I query the ambient temperature sensor on an R710 with '/usr/sbin/ipmi-sensors -v -s 5' I see something like this: Record ID: 5 Sensor Name: Ambient Temp Group Name: Temperature Sensor Number: 7 Event/Reading Type Code: 1h Lower Critical Threshold: 3.00 degrees C Upper Critical Threshold: 47.00 degrees C Lower Non-Critical Threshold: 8.00 degrees C Upper Non-Critical Threshold: 42.00 degrees C Lower Non-Recoverable Threshold: NA Upper Non-Recoverable Threshold: NA Sensor Min. Reading: -128.00 degrees C Sensor Max. Reading: 127.00 degrees C Normal Min.: 11.00 degrees C Normal Max.: 69.00 degrees C Nominal reading: 23.00 degrees C Sensor Reading: 25.00 degrees C Sensor Status: [OK] What exactly is the Upper Critical Threshold? Is this the temperature at which the machine may shut its power off? Should I be thinking of starting a clean shutdown when the ambient temperature reaches the level of the Upper Non-Critical Threshold? And what exactly is the Upper Non-Critical Threshold anyway? I've been looking for an explanation of these terms and haven't yet found one. I've looked in various Intel and Dell and IPMI docs but with no success so far, unfortunately. Can anyone point me at sources of help, or have you tried this already? If you're wondering, we're in a shiny new building and they haven't entirely ironed out the problems with the server room's cooling system! -- Chris Cooke. Computing Officer, School of Informatics, University of Edinburgh. -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Debian Lenny on R610 with PERC 6/i
Rob Heilman a écrit : > I am attempting to install Debian Lenny on a Dell R610 equipped with a PERC > 6/i controller. I built a 4+1 (500GB Seagates) RAID 5 group in the PERC BIOS > and left another disk for a hot spare. I was able to boot from the Debian > DVD, create LVM, partitions, etc. Other than the bnx2 firmware it was a very > non-eventful install process. > > When the machine attempts to boot from the PERC based drive it simply hangs. > The last thing I see is from the DRAC: > > Press for Remote Access Setup within 5 sec. > > After that just a line wrap or two when the 5 seconds lapses. > > My assumption is that something is wrong with the boot loader process. Is > the 1.8TB LUN/SD exceeding a size limit I am unaware of? Do I need any > particular modules/drivers in the initrd to allow it to boot? Any other > ideas? During the Debian Lenny install, which version of GRUB did you choose to install? I would recommend install the "legacy" version (GRUB 0.9x), the newer version of GRUB (1.9x) is still not considered stable by Debian. Other question, could you give us more precision on how you configured the PERC and disks (like RAID level, for example) ? -- Kévin Roussel Ingénieur-expert, projet OPEN-PEOPLE Équipe TRIO, INRIA Nancy Grand-Est ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Debian Lenny on R610 with PERC 6/i
I am attempting to install Debian Lenny on a Dell R610 equipped with a PERC 6/i controller. I built a 4+1 (500GB Seagates) RAID 5 group in the PERC BIOS and left another disk for a hot spare. I was able to boot from the Debian DVD, create LVM, partitions, etc. Other than the bnx2 firmware it was a very non-eventful install process. When the machine attempts to boot from the PERC based drive it simply hangs. The last thing I see is from the DRAC: Press for Remote Access Setup within 5 sec. After that just a line wrap or two when the 5 seconds lapses. My assumption is that something is wrong with the boot loader process. Is the 1.8TB LUN/SD exceeding a size limit I am unaware of? Do I need any particular modules/drivers in the initrd to allow it to boot? Any other ideas? Thanks, Rob Heilman ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
