how to revoke update_firmware?
Dear all, I have tried to setup updates for firmware on R610 with PERC6e and PERC6i following the wiki http://linux.dell.com/wiki/index.php/Repository/firmware All went well, including the command update_firmware. This means that on the next reboot, firmware updates will be flashed. However, if I want to withdraw that command how can I do that? I would like to reboot without updating the firmware next time (or if the server unexpectedly reboots), and then try update_firmware plus reboot at a later time. Regards, Gernot Hassenpflug ___ 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: R710: clear SEL
Hmm, to clear the sel, I think you'd want racadm, ala "racadm clrsel". The omconfig equivalent would be "omconfig system esmlog". One or the other should work on an R710. DP - Original Message - From: "Steve Thompson" To: linux-powere...@lists.us.dell.com Sent: Wednesday, March 24, 2010 3:18:47 PM GMT -08:00 US/Canada Pacific Subject: R710: clear SEL Anyone know of a way to clear the event log of an R710 using OMSA? I know that it can be done with ipmitool, but I'm looking for a solution using omconfig (and not via the web interface). The documentation appears silent on this point. TIA, Steve ___ 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: "/" full
yep.. I just threw that out there just in case.. I have seen a lot of people still do that.. Kevin This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e- mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. On Mar 25, 2010, at 1:45 PM, Jefferson Ogata wrote: > On 2010-03-25 18:21, Kevin Coleman wrote: >> yum clean all to get rid of the possible cache from the >> repository ? >> or the usual..check your log files in /var/log/ * for hugh logs >> that can >> be purged.. > > Well, yeah, if you have /var on /, you deserve what you get... > > There's a reason why the practice of filesystem partitioning evolved; > seems to be more of a lost art these days with newbie sysadmins just > creating a giant /. > > ___ > 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: "/" full
> -Original Message- > There's a reason why the practice of filesystem partitioning evolved; > seems to be more of a lost art these days with newbie sysadmins just > creating a giant /. Even more so for /home if you have multiple users on the system. Somebody downloads some monster file and fills up your / partition, bad news. ___ 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: openmanage 6.2 / missing controller issue fixed ?
Not sure, I just added OpenIPMI to my kickstart. Would be nice to limit it to just the required package, but I don't have time to dig (maybe someone familiar with OMSA's dependencies can spot the package easily? :) On 03/25/2010 02:30 PM, Ryan Miller wrote: > Do we have any idea what package that actually is so I can make sure it's in > my builds/Dell can add it to the dependency tree? > > Ryan > ___ 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: "/" full
On 2010-03-25 18:21, Kevin Coleman wrote: > yum clean all to get rid of the possible cache from the repository ? > or the usual..check your log files in /var/log/ * for hugh logs that can > be purged.. Well, yeah, if you have /var on /, you deserve what you get... There's a reason why the practice of filesystem partitioning evolved; seems to be more of a lost art these days with newbie sysadmins just creating a giant /. ___ 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: Changing BIOS Boot Order from Linux Command Line w/out Complete OM Install
dmidecode -s system-serial-number
gives me the Service tag number on my host. RHEL 5, M610...
or:
dmidecode | grep -A4 'System Information' | tail -n1 | awk '{print $NF}'
if you have an older version of dmidecode.
Now, resetting it is a different ball of wax...
don
--
Don Harper, RHCE
Unix Systems Group - Americas
Macquarie Holdings - Houston
Phone: +1.713.275.6294
Cell: +1.832.235.8374
-Original Message-
From: linux-poweredge-boun...@dell.com
[mailto:linux-poweredge-boun...@dell.com] On Behalf Of J. Epperson
Sent: Thursday, March 25, 2010 11:38 AM
To: linux-poweredge@dell.com
Subject: Re: Changing BIOS Boot Order from Linux Command Line w/out
Complete OM Install
On Thu, March 25, 2010 11:00, Dameon Wagner wrote:
>
> Does your distro have the SMBios tools? I use Debian, and with the
> libsmbios-bin package I have a tool called `serviceTag` which spits
> out, and allows you to change, the Dell service tag for the box.
>
That sounds like what I want (although it appears that libsmbios-bin
package has been replaced with smbios-utils package). But if I
bootstrap
from the instructions on
http://linux.dell.com/libsmbios/main/index.html,
with smbios-utils-bin installed I end up with no serviceTag tool,
although
although it's listed as one of the supported binaries on
http://linux.dell.com/libsmbios/main/cmdlinetools.html.
Dell has done a better job than most vendors in Linux support, and Matt
Domsch in particular is a blessing on the Linux community, but their
repo
collection ought to be called the "Dell Ducktape Repositories".
Dependencies and obsolescences aren't dealt with consistently, presence
of
old repo files on a system can wreck the bus (and are not dealt with by
later bootstraps), etc
Maybe I can get some IP cameras installed in the data center so I can
read
the asset tags off the front of the 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
Unless otherwise indicated, this message is intended only for the personal and
confidential use of the designated recipient(s) named above. If you are not the
intended recipient of this message you are hereby notified that any review,
dissemination, distribution or copying of this message is strictly prohibited.
This communication is for information purposes only and should not be regarded
as an offer to sell or as a solicitation of an offer to buy any financial
product or service, an official confirmation of any transaction, or as an
official statement of the entity sending this message. Email transmission
cannot be guaranteed to be secure or error-free. Therefore, we do not represent
that this information is complete or accurate and it should not be relied upon
as such. All information is subject to change without notice.
___
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: openmanage 6.2 / missing controller issue fixed ?
Do we have any idea what package that actually is so I can make sure it's in my builds/Dell can add it to the dependency tree? Ryan > -Original Message- > From: Ryan Pugatch [mailto:li...@ryanp.com] On Behalf Of Ryan Pugatch > Sent: Thursday, March 25, 2010 2:30 PM > To: Ryan Miller > Cc: Brandon Ooi; Nielsen, Steve; linux-poweredge@dell.com > Subject: Re: openmanage 6.2 / missing controller issue fixed ? > > On 03/24/2010 09:48 PM, Ryan Miller wrote: > > I don't have any rpms installed with "ipmi" or "IPMI" in the name, > and > > no ipmi service defined. It's just strange because I can't reproduce > the > > need for this dependency, so I'm not surprised Dell hasn't defined > it, > > yet it's clearly causing issues for folks... > > > > > It isn't OpenIPMI that is solving the problem.. it is a dependency of > OpenIPMI..or a dependency of a dependency that is. > > > Ryan ___ 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: Changing BIOS Boot Order from Linux Command Line w/out Complete OM Install
On Thu, March 25, 2010 14:15, Donald Harper wrote:
> dmidecode -s system-serial-number
>
> gives me the Service tag number on my host. RHEL 5, M610...
>
> or:
> dmidecode | grep -A4 'System Information' | tail -n1 | awk '{print $NF}'
>
> if you have an older version of dmidecode.
>
> Now, resetting it is a different ball of wax...
>
And that's the ball of wax I need to melt. Original post stated that, I
guess I trimmed too much in my rant about the Dell repos. I have means of
querying service tag, but it's blank on systems where MB has been
replaced, under warranty, by Dell field support.
___
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: "/" full
yum clean all to get rid of the possible cache from the repository ? or the usual..check your log files in /var/log/ * for hugh logs that can be purged.. Regards, Kevin Coleman On Mar 25, 2010, at 1:05 PM, Jefferson Ogata wrote: > On 2010-03-25 17:07, Dimitri Yioulos wrote: >> At this point, we don't want to add more space to >> the partition. Can anyone suggest any other >> things we can try? > > Does this condition survive a reboot? > > Is /boot on /, or is it a separate filesystem? One thing that > happens on > Red Hat and derivatives is that as you patch the kernel you need to > remove older kernels to avoid filling up whichever filesystem /boot > resides on. > > ___ > 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: "/" full
On 2010-03-25 17:07, Dimitri Yioulos wrote: > At this point, we don't want to add more space to > the partition. Can anyone suggest any other > things we can try? Does this condition survive a reboot? Is /boot on /, or is it a separate filesystem? One thing that happens on Red Hat and derivatives is that as you patch the kernel you need to remove older kernels to avoid filling up whichever filesystem /boot resides on. ___ 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: "/" full
cd / du -sm * This will tell you the disk usage of each directory under /, and you can then track down which directory is filling up. -- tzd. On Thu, Mar 25, 2010 at 10:07 AM, Dimitri Yioulos wrote: > All, > > A colleague at a very small company has CentOS 5.x > running on a R200. The other day, he tried to > add a new user, but got an error. His pptpd VPN > also stopped working. The long-and-short of it > is that "/" (in its own partition) on his system > is 100% full. I've been helping him look for a > solution to the problem: we've looked at files > and file sizes for (a) culprit(s), checked > available inodes, and a few other things and, of > course, googled for a solution. We've come up > empty. > > At this point, we don't want to add more space to > the partition. Can anyone suggest any other > things we can try? > > Many thanks. > > Dimitri > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > ___ > 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: "/" full
Dimitri, 1. possibly some process is holding a open file handle (lsof should be able to show this too) 2. some versions of the kernel had a bug where the filesystem accounting ; this will require a reboot to clear HTH, -prasana prasana.iyen...@gmail.com Lord Kelvin said, "If you can not measure it, you can not improve it." On Mar 25, 2010, at 10:07 AM, Dimitri Yioulos wrote: All, A colleague at a very small company has CentOS 5.x running on a R200. The other day, he tried to add a new user, but got an error. His pptpd VPN also stopped working. The long-and-short of it is that "/" (in its own partition) on his system is 100% full. I've been helping him look for a solution to the problem: we've looked at files and file sizes for (a) culprit(s), checked available inodes, and a few other things and, of course, googled for a solution. We've come up empty. At this point, we don't want to add more space to the partition. Can anyone suggest any other things we can try? Many thanks. Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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
"/" full
All, A colleague at a very small company has CentOS 5.x running on a R200. The other day, he tried to add a new user, but got an error. His pptpd VPN also stopped working. The long-and-short of it is that "/" (in its own partition) on his system is 100% full. I've been helping him look for a solution to the problem: we've looked at files and file sizes for (a) culprit(s), checked available inodes, and a few other things and, of course, googled for a solution. We've come up empty. At this point, we don't want to add more space to the partition. Can anyone suggest any other things we can try? Many thanks. Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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: Alternatives to Dell storage?
On Wednesday 24 March 2010 16:39:08 James Bensley wrote: > One thing I particularly like about this list is that there are Dell > employee's on the list such as the server tech support guys who have > worked in the industry and thusly know their stuff. Funny that none > have chimed in on this thread? ;) Well, sriously, what do you expect them to do? To be honest questions like this are totally off-topic cause there no relationship at all with PowerEdges. They don't say nothing and IMO this is something really good, it shows that we are dealing with technical staff and not sales people. -- Davide Ferrari Atrapalo.com System Administrator ___ 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: Changing BIOS Boot Order from Linux Command Line w/out Complete OM Install
On Thu, March 25, 2010 11:00, Dameon Wagner wrote: > > Does your distro have the SMBios tools? I use Debian, and with the > libsmbios-bin package I have a tool called `serviceTag` which spits > out, and allows you to change, the Dell service tag for the box. > That sounds like what I want (although it appears that libsmbios-bin package has been replaced with smbios-utils package). But if I bootstrap from the instructions on http://linux.dell.com/libsmbios/main/index.html, with smbios-utils-bin installed I end up with no serviceTag tool, although although it's listed as one of the supported binaries on http://linux.dell.com/libsmbios/main/cmdlinetools.html. Dell has done a better job than most vendors in Linux support, and Matt Domsch in particular is a blessing on the Linux community, but their repo collection ought to be called the "Dell Ducktape Repositories". Dependencies and obsolescences aren't dealt with consistently, presence of old repo files on a system can wreck the bus (and are not dealt with by later bootstraps), etc Maybe I can get some IP cameras installed in the data center so I can read the asset tags off the front of the 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: Changing BIOS Boot Order from Linux Command Line w/out Complete OM Install
On Thu, Mar 25, 2010 at 09:55:51AM -0400, J. Epperson scribbled in "Re: Changing BIOS Boot Order from Linux Command Line w/out Complete OM Install": > On Wed, March 17, 2010 23:06, Matt Domsch wrote: > > On Wed, Mar 17, 2010 at 09:07:49PM -0400, Roehrig, Jack (John) wrote: > >> Does anyone know of a utility that exists that will allow me to modify > >> the BIOS boot order for Dell servers (specifically Poweredge > >> [126][6789]50s and R[4567]10) from the Linux command line? I need a > >> tool that is very non-intrusive, minimal, script-friendly, and will > >> allow me to configure a machine to attempt a network boot before any > >> other devices. I cannot install a full copy of OpenManage on these > >> machines, but am not opposed to using a precompiled binary or making > >> the nvram device. The distributions vary, but all will have Linux > >> 2.[46] kernels. > > > > OK, so the syscfg program from dell-toolkit.rpm will allow setting the > BIOS boot order from the command line. But it will not set the BIOS > service tag, which is often the only way I can track down an error when > someone mungs the inventory (short of the long drive and intense physical > security to eyeball the physical asset tags). When Dell replaces a > motherboard, they do not set the service tag on the new board, so this is > an issue with a number of machines. > > Is there a way to set the BIOS service tag from a Linux command line? I > know about the asset.com "/s" switch, but booting each box into DOS is not > really a reasonable solution. Does your distro have the SMBios tools? I use Debian, and with the libsmbios-bin package I have a tool called `serviceTag` which spits out, and allows you to change, the Dell service tag for the box. The package also has many other useful tools in it, so it's worth installing. Cheers. Dameon. -- ><> ><> ><> ><> ><> ><> ooOoo <>< <>< <>< <>< <>< <>< Dr. Dameon Wagner, Senior ICT Specialist, Depts. of Computer Science & Information Systems, Rhodes University, Grahamstown, South Africa. :Beta tester for Pegasus & Mercury/32 (www.pmail.com): ><> ><> ><> ><> ><> ><> ooOoo <>< <>< <>< <>< <>< <>< ___ 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 error on R410s
On 25/03/10 13:54, jeffrey_l_mend...@dell.com wrote: > > Do you have the firmware repo configured? It is obsoleted by the OM > 6.2 version of the hardware repo, this is where you are finding > 1.1.5. Go ahead and remove the firmware repo. To get all the > updates, follow the instructions on the repo page: > http://linux.dell.com/repo/hardware/latest/ "yum install > dell_ft_install" instead of firmware-tools. Ah, thanks - that was it. I did the following: yum remove firmware-tools yum install dell_ft_install yum -y install $(bootstrap_firmware) update_firmware -y I now get firmware 1.2.4 - still not 1.3.8. > If you see that bios update issue, post the output with the verbose, > -v, option. I did. Here you go: # update_firmware -y -v Checking Plugin (bootstrap_pci) Loaded bootstrap_pci plugin Checking Plugin (bootstrap_cmd) Loaded bootstrap_cmd plugin Checking Plugin (mock_inventory_bootstrap) Plugin mock_inventory_bootstrap not loaded: doesnt match load type ((4,)) Checking Plugin (dell_ft_ie_interface) Loaded dell_ft_ie_interface plugin Checking Plugin (update_cmd) Loaded update_cmd plugin Checking Plugin (listplugins_cmd) Loaded listplugins_cmd plugin Checking Plugin (dellbios) Loaded dellbios plugin Checking Plugin (mock_repository) Plugin mock_repository not loaded: doesnt match load type ((4,)) Checking Plugin (inventory_cmd) Loaded inventory_cmd plugin Checking Plugin (dellbios_extract) Plugin raised DisablePlugin exception. skipping. hello world from update module doCheck() Running system inventory... loading xml from: /usr/libexec/dell_dup/PERC6_PERC/PIEConfig.xml loaded. not verbose --> INFO: hi there verobse INFO: hi there Running IE Submodule for /usr/libexec/dell_dup/dell_ie_tape_prostor-1.0.8 Plugin command is DUPwrapper -s -i inv.xml Output file is inv.xml Plugin timeout is 300 output from the cmd was: Running IE Submodule for /usr/libexec/dell_dup/dell_ie_imc-1.0.8 Module not for this system, disabling module. Running IE Submodule for /usr/libexec/dell_dup/dell_ie_zappa-1.0.8 Plugin command is PV2XX -i -x > inv.xml Output file is inv.xml Plugin timeout is 600 output from the cmd was: inventory successful Running IE Submodule for /usr/libexec/dell_dup/dell_ie_nic_broadcom-1.0.8 Plugin command is dup_inv Output file is brcmfwinventory.xml Plugin timeout is 300 output from the cmd was: Added DEVICE: pci_firmware(ven_0x14e4_dev_0x163b_subven_0x1028_subdev_0x028c) Added DEVICE: pci_firmware(ven_0x14e4_dev_0x163b_subven_0x1028_subdev_0x028c) Running IE Submodule for /usr/libexec/dell_dup/dell_ie_rac_4-1.0.8 Module not for this system, disabling module. Running IE Submodule for /usr/libexec/dell_dup/dell_ie_bmc-1.0.8 Module not for this system, disabling module. Running IE Submodule for /usr/libexec/dell_dup/dell_ie_tape_ibm-1.0.8 Plugin command is IbmDupwrapper -silent Output file is scsiInv.txt Plugin timeout is 500 output from the cmd was: Running IE Submodule for /usr/libexec/dell_dup/dell_ie_sas-1.0.8 Plugin command is sasdupie -i -o inv.xml Output file is inv.xml Plugin timeout is 600 output from the cmd was: Added DEVICE: pci_firmware(ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0b) Added DEVICE: dell_dup_componentid_20513 Added DEVICE: dell_dup_componentid_20513 Added DEVICE: dell_dup_componentid_20513 Added DEVICE: dell_dup_componentid_20513 Added DEVICE: dell_dup_componentid_11204 Running IE Submodule for /usr/libexec/dell_dup/dell_ie_maser_inv_lcl-1.0.8 Plugin command is MaserIE -i -o=inv.xml Output file is inv.xml Plugin timeout is 1200 output from the cmd was: Inventory Failure: This Operating System is not supported Running IE Submodule for /usr/libexec/dell_dup/dell_ie_bios-1.0.8 Plugin command is biosie.bin -i inv.xml Output file is inv.xml Plugin timeout is 300 output from the cmd was: Added DEVICE: dell_dup_componentid_00159 Running IE Submodule for /usr/libexec/dell_dup/dell_ie_bp-1.0.8 Module not for this system, disabling module. Running IE Submodule for /usr/libexec/dell_dup/dell_ie_rac_5-1.0.8 Module not for this system, disabling module. Running IE Submodule for /usr/libexec/dell_dup/dell_ie_tape_tandberg-1.0.8 Plugin command is dupswrapper -c Output file is scsiInv.txt Plugin timeout is 400 output from the cmd was: loading xml from: /usr/libexec/dell_dup/BROADCOM_FRMW/PIEConfig.xml loaded. loading xml from: /usr/libexec/dell_dup/BIOS_NONE/PIEConfig.xml loaded. loading xml from: /usr/libexec/dell_dup/SASHDD_SASHDD/PIEConfig.xml loaded. loading xml from: /usr/libexec/dell_dup/SASBP_SASBP/PIEConfig.xml loaded. Searching storage directory for available BIOS updates.
Re: Changing BIOS Boot Order from Linux Command Line w/out Complete OM Install
On Wed, March 17, 2010 23:06, Matt Domsch wrote: > On Wed, Mar 17, 2010 at 09:07:49PM -0400, Roehrig, Jack (John) wrote: >> Does anyone know of a utility that exists that will allow me to modify >> the BIOS boot order for Dell servers (specifically Poweredge >> [126][6789]50s and R[4567]10) from the Linux command line? I need a >> tool that is very non-intrusive, minimal, script-friendly, and will >> allow me to configure a machine to attempt a network boot before any >> other devices. I cannot install a full copy of OpenManage on these >> machines, but am not opposed to using a precompiled binary or making >> the nvram device. The distributions vary, but all will have Linux >> 2.[46] kernels. > OK, so the syscfg program from dell-toolkit.rpm will allow setting the BIOS boot order from the command line. But it will not set the BIOS service tag, which is often the only way I can track down an error when someone mungs the inventory (short of the long drive and intense physical security to eyeball the physical asset tags). When Dell replaces a motherboard, they do not set the service tag on the new board, so this is an issue with a number of machines. Is there a way to set the BIOS service tag from a Linux command line? I know about the asset.com "/s" switch, but booting each box into DOS is not really a reasonable solution. ___ 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 error on R410s
> Hmmm, I've "fixed" things as follows: > > yum remove firmware-tools > yum install firmware-tools > yum -y install $(bootstrap_firmware) > update_firmware -y > > However, I no longer get BIOS version 1.2.4 installed - 1.1.5 seems to > be the latest. > > Looking on the website, there seems to be a version 1.3.8 available for > the R410 [1]. > > It certainly seems that a couple of later firmware versions have been > released since 1.1.5 [2] > > Is the yum firmware repository not kept up-to-date? Do you have the firmware repo configured? It is obsoleted by the OM 6.2 version of the hardware repo, this is where you are finding 1.1.5. Go ahead and remove the firmware repo. To get all the updates, follow the instructions on the repo page: http://linux.dell.com/repo/hardware/latest/ "yum install dell_ft_install" instead of firmware-tools. If you see that bios update issue, post the output with the verbose, -v, option. Thanks, 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: R900 RAM Configuration
> -Original Message- > From: jens_he...@dell.com [mailto:jens_he...@dell.com] > Sent: 25 March 2010 08:49 > To: Nick Lunt > Cc: linux-powere...@lists.us.dell.com > Subject: RE: R900 RAM Configuration > > You have 4x memory risers named A, B, C, D. > Every riser is capable to hold up to 8x DIMMs (ie. A1, A2, ... A8) > That makes a total of 32x DIMMs in your system. In other words your > system is full. > > If you swap DIMM A1 you'll have to swap B1, C1 and D1 as well. > For optimum configuration you shouldn't mix DIMMs of different sizes. > > So one solution might be, to remove all 2GB DIMMs, fill up first 4x > slots of every with 8GB DIMMs. That'll leave you spare slot to expand > further in future. > Or you just replace all your 2GB DIMMs with 4GB DIMMs. > > Jens > > -Original Message- > From: Nick Lunt [mailto:nick.l...@patech-solutions.com] > Sent: 25 March 2010 09:37 > To: Heinz, Jens > Cc: linux-poweredge-Lists > Subject: RE: R900 RAM Configuration > > > -Original Message- > > From: jens_he...@dell.com [mailto:jens_he...@dell.com] > > Sent: 24 March 2010 15:19 > > To: Nick Lunt > > Subject: RE: R900 RAM Configuration > > > > This link might help > > > > > http://support.dell.com/support/edocs/systems/per900/en/hom/_sectioc.ht > > m > > #wp1082885 > > > > Jens > > > > -Original Message- > > From: linux-poweredge-boun...@dell.com > > [mailto:linux-poweredge-boun...@dell.com] On Behalf Of Nick Lunt > > Sent: 24 March 2010 16:09 > > To: linux-poweredge-Lists; linux-poweredge-Lists > > Subject: R900 RAM Configuration > > > > Hi > > > > we have an R900 with 32 x 2GB DIMMs in, so the server has no free > DIMM > > slots. > > All the DIMMs are DDR2 FB-DIMM-SYNCHRONOUS . > > > > We need to increase the RAM from 64GB to a minimum of 103GB (based on > > our calculations), so really I guess we'd be looking at increasing > the > > RAM to 104GB, or just going for a nice round 128GB :) > > > > Can anyone recommend the best upgrade method for this ? > > Do we need to keep RAM in banks all the same size ? > > How many DIMMs are in each bank ? > > > > Basically is there anything we need to be aware of when removing some > > DIMMs and adding larger ones ? > > Right, that doc says 4 risers must be installed at all times. > Seen as we have 32 DIMMs does that mean we have 8 risers ? > I.e. A1,B1,C1,D1 is a full riser. A1,B2,C2,D2 is another riser, etc ? > > Status: OKDIMM A1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM B1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM C1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM D1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM A2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM B2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM C2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM D2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM A3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM B3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM C3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM D3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM A4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM B4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM C4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM D4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM A5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM B5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM C5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM D5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM A6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM B6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM C6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM D6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM A7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM B7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM C7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM D7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM A8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM B8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM C8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > Status: OKDIMM D8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB > > So if I changed A1 to a 4GB DIMM then I should change A2, A3, A4, A5, > A6, A7 and A8 to 4GB DIMMs too ? Thanks Jens, I think I've got it now :) Cheers Nick. __ Information from ESET NOD32 Antivirus, version of virus signature database 4972 (20100324)
RE: R900 RAM Configuration
You have 4x memory risers named A, B, C, D. Every riser is capable to hold up to 8x DIMMs (ie. A1, A2, ... A8) That makes a total of 32x DIMMs in your system. In other words your system is full. If you swap DIMM A1 you'll have to swap B1, C1 and D1 as well. For optimum configuration you shouldn't mix DIMMs of different sizes. So one solution might be, to remove all 2GB DIMMs, fill up first 4x slots of every with 8GB DIMMs. That'll leave you spare slot to expand further in future. Or you just replace all your 2GB DIMMs with 4GB DIMMs. Jens -Original Message- From: Nick Lunt [mailto:nick.l...@patech-solutions.com] Sent: 25 March 2010 09:37 To: Heinz, Jens Cc: linux-poweredge-Lists Subject: RE: R900 RAM Configuration > -Original Message- > From: jens_he...@dell.com [mailto:jens_he...@dell.com] > Sent: 24 March 2010 15:19 > To: Nick Lunt > Subject: RE: R900 RAM Configuration > > This link might help > > http://support.dell.com/support/edocs/systems/per900/en/hom/_sectioc.ht > m > #wp1082885 > > Jens > > -Original Message- > From: linux-poweredge-boun...@dell.com > [mailto:linux-poweredge-boun...@dell.com] On Behalf Of Nick Lunt > Sent: 24 March 2010 16:09 > To: linux-poweredge-Lists; linux-poweredge-Lists > Subject: R900 RAM Configuration > > Hi > > we have an R900 with 32 x 2GB DIMMs in, so the server has no free DIMM > slots. > All the DIMMs are DDR2 FB-DIMM-SYNCHRONOUS . > > We need to increase the RAM from 64GB to a minimum of 103GB (based on > our calculations), so really I guess we'd be looking at increasing the > RAM to 104GB, or just going for a nice round 128GB :) > > Can anyone recommend the best upgrade method for this ? > Do we need to keep RAM in banks all the same size ? > How many DIMMs are in each bank ? > > Basically is there anything we need to be aware of when removing some > DIMMs and adding larger ones ? Right, that doc says 4 risers must be installed at all times. Seen as we have 32 DIMMs does that mean we have 8 risers ? I.e. A1,B1,C1,D1 is a full riser. A1,B2,C2,D2 is another riser, etc ? Status: OK DIMM A1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB So if I changed A1 to a 4GB DIMM then I should change A2, A3, A4, A5, A6, A7 and A8 to 4GB DIMMs too ? Thanks Nick. __ Information from ESET NOD32 Antivirus, version of virus signature database 4972 (20100324) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ___ 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: R900 RAM Configuration
> -Original Message- > From: jens_he...@dell.com [mailto:jens_he...@dell.com] > Sent: 24 March 2010 15:19 > To: Nick Lunt > Subject: RE: R900 RAM Configuration > > This link might help > > http://support.dell.com/support/edocs/systems/per900/en/hom/_sectioc.ht > m > #wp1082885 > > Jens > > -Original Message- > From: linux-poweredge-boun...@dell.com > [mailto:linux-poweredge-boun...@dell.com] On Behalf Of Nick Lunt > Sent: 24 March 2010 16:09 > To: linux-poweredge-Lists; linux-poweredge-Lists > Subject: R900 RAM Configuration > > Hi > > we have an R900 with 32 x 2GB DIMMs in, so the server has no free DIMM > slots. > All the DIMMs are DDR2 FB-DIMM-SYNCHRONOUS . > > We need to increase the RAM from 64GB to a minimum of 103GB (based on > our calculations), so really I guess we'd be looking at increasing the > RAM to 104GB, or just going for a nice round 128GB :) > > Can anyone recommend the best upgrade method for this ? > Do we need to keep RAM in banks all the same size ? > How many DIMMs are in each bank ? > > Basically is there anything we need to be aware of when removing some > DIMMs and adding larger ones ? Right, that doc says 4 risers must be installed at all times. Seen as we have 32 DIMMs does that mean we have 8 risers ? I.e. A1,B1,C1,D1 is a full riser. A1,B2,C2,D2 is another riser, etc ? Status: OK DIMM A1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D1 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D2 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D3 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D4 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D5 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D6 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D7 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM A8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM B8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM C8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB Status: OK DIMM D8 DDR2 FB-DIMM-SYNCHRONOUS2048 MB So if I changed A1 to a 4GB DIMM then I should change A2, A3, A4, A5, A6, A7 and A8 to 4GB DIMMs too ? Thanks Nick. __ Information from ESET NOD32 Antivirus, version of virus signature database 4972 (20100324) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com ___ 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
