[Linux-PowerEdge] DSU: "Could not parse the inventory"
Scenario: two R610s, both running CentOS 6.8, fully updated. One seems to be fine with a DSU run, reporting all firmware up to date (although it doesn't list the iDRAC, is that normal?) The other does this: # dsu Verifying catalog installation ... Installing catalog from repository ... Fetching dsucatalog ... Reading the catalog ... Verifying inventory collector installation ... Getting System Inventory ... Could not parse the inventory Troubleshooting guidance would be welcome. -- Philip J. Tait http://subarutelescope.org ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Re: Consistent Network Device Naming for LOMs coming...
On Sat, Nov 13, 2010 at 18:55, Matt Domsch matt_dom...@dell.com wrote: Fedora 15 is expected to contain the newly agreed upon udev rules to name those pesky LAN-on-Motherboard NICs lomN instead of ethX for new installs, or any time /lib/udev/rules.d/70-persistent-net.names is deleted. biosdevname, a Dell-developed program, is the udev helper which obtains the proper value N in lomN, corresponding to the labels on the system chassis, N=1..4. https://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming Yes, this means to guarantee you use LOM 1 for something, you have to stop guessing at which ethX is actually LOM 1, you now will use lom1 in your kickstart files and other scripts, no longer ethX. Like? Dislike? I'd love to hear your comments. The non-installer parts should hit Fedora Rawhide within a few days, for your testing pleasure. The installer bits may take a bit longer. This is a nice improvement. Will the components be readily available for installation on other distros? Sounds like it is possible to get this working on RHEL5/CentOS5, for example. -- Philip J. Tait, Software Engineer (FMOS,HSC) http://subarutelescope.org ___ 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
Third-party drives not permitted on Gen 11 servers
I just received my first Gen11 server, R710, with H700 PERC. I removed the supplied drives, and installed 4 Barracuda ES.2s. After doing a Clear Configuration in the pre-boot RAID setup utility, I can perform no operation with the drives - they are marked as blocked. Is Dell preventing the use of 3rd-party HDDs now? Thanks for any enlightenment. Philip J. Tait http://subarutelescope.org ___ 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
Poweredge servers running in low temperature environment
We are installing a couple of PE servers (2900 and R710) at our summit facility. Ambient temperature can be as low as 1C (dewpoint at -15C). Apart from annoying low ambient temperature warnings from OMSA, is there anything to be concerned about? Is it feasible to adjust fan RPM settings? Thanks for any comments/suggestions, Philip J. Tait http://subarutelescope.org ___ 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: SAS5/E with MD1000 for JBOD
On 12/17/2009 11:39 AM, Jose-Marcio Martins da Cruz wrote: Philip Tait wrote: We want to attach an MD1000 to a PE2900 in a non -RAID configuration. The Dell sales people are very convinced that we have to have a PERC6/E to connect an MD1000, but they are doing further research. We have two MD1000 attached to a PE2950. We have a PERC5/E. With the PERC5/E you can have RAID 0 (stripe). So, if I understood what you're wanting, you shall be able to create one RAID 0 volume for each disk, or a single RAID0 for all disks. Thanks for the response, but I believe this would not work for our application because the disks would require a PERC-equipped computer for them to be readable. We want these drives to be readable on any PC with a SATA interface. In the meantime, I wondered if anyone on the list is actually using a SAS5/E to attach an MD1000, and can relate their experience? (Note that we want the drives to have standard partitioning, which would seem to make a PERC6/E unsuitable for this application.) Thanks for any comments, Philip J. Tait http://subarutelescope.org ___ 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: OpenManage and OpenSuse 11
Patrick, See if any of the information on this page helps: http://en.opensuse.org/Installation_of_Dell_OpenManage_%28OMSA%29_for_Poweredge_servers Updates and corrections welcome. Philip J. Tait http://subarutelescope.org Patrick de Groot wrote: OpenManage 5.5 web interface doesn't run on OpenSuse 11 (you may handle it like Suse 11 if you like). It installs fine, but the web part does not run. -command omreport about works -/etc/init.d/dsm_om_connsvc status displays running -natstat -nat doesn't display a row with port 1311 so clearly the service isn't up and running. Problem seems similar to this one: http://lists.us.dell.com/pipermail/linux-poweredge/2008-October/037482.html So what can I try or how do I debug this? Thanks! Send instant messages to your online friends http://uk.messenger.yahoo.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 ___ 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
