On Thu, Jul 29, 2010 at 01:57:25PM -0500, Michael E Brown scribbled
in Re: Dell OpenManage 6.3 for Ubuntu:
snip
Thanks Michael, and thanks Dell (official or not ;)
Any chance of a similar set for real Debian?
I really hope the ubuntu packages just work on Debian. If you care
to try
On Fri, 30 Jul 2010, Mark Watts wrote:
I've never, personally, got very far with this. I know Adaptec have a
Java based management tool if you dig hard enough. I'm not sure if OMSA
supports these cards (they're also known as CERC cards).
I'm pretty sure afacli will do what you need. Adaptec
Hi !
Maybe stupid question ..
Where can i get the OMSA Live 6.3 CD ?
cheers,
martin
On Sun, 1 Aug 2010, Tom Rockwell wrote:
Hi,
Those append options worked for me.
Thanks,
Tom
On 7/31/10 3:10 PM, rayford_john...@dell.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Upps, great show :-)
Thanks a lot Cheers,
martin
On Mon, 2 Aug 2010, Sam Kuonen wrote:
http://linux.dell.com/files/openmanage-contributions/omsa-63-live/
Sam
On 08/02/2010 09:10 AM, Martin Flemming wrote:
Hi !
Maybe stupid question ..
Where can i get the OMSA Live 6.3
This follows the SNIA DDF standard. More information can be found here:
http://www.snia.org/tech_activities/standards/curr_standards/ddf/
OMSA will interpret these values for you. Or you can do it yourself according
to the DDF standard.
From: linux-poweredge-bounces-Lists On Behalf Of Geoff
Hi,
I have the same problem on a brand new R410
Centos 5.5
I can see this is cropping up more than once on this forum
Has anyone a solution?
Thanks
Stuart
-
___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
(sorry for the attribution depth, deleted the original message).
Anyway, i have no H800 series controllers yet, so i'm just throwing
this out, in case it applies, but the PERC5/6
can be updated via MegaCLI with:
MegaCli -AdpFwFlash -f filename [-NoSigChk] [-NoVerChk] -aN|-a0,1,2|-aALL
I'd
I have recently replaced a bad disk in a 2950 (PD 04) and reviewing the PERC6
eventlog after the rebuild completed I noticed several strange errors (the
array was rebuilt for a couple of days by the time of this log):
08/02/10 8:32:46: EVT#05993-08/02/10 8:32:46: 113=Unexpected sense: PD
Have a R710 running RHEL4.8 with a internal H700 supporting two virtual
drives using internal disks and a H800 supporting two virtual drives
in an external MD1200 enclosure.
It seems that the device name (/dev/sd?) that is assigned to each virtual
drive is somewhat arbitrary. It was in order of
The recommendations I've seen are to avoid using /dev/sdx for exactly this
reason. Instead you can use either file system labels or otherwise persistent
names generated by udev based on parameters that won't change.
--
Thank You
Jefferson Cowart
Network and Systems Administrator
Claremont
Ken,
Refer this link. This might help you in locking a device name to disk.
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/html/Online_St
orage_Reconfiguration_Guide/persistent_naming.html
--
Ashokan Vellimalai
Linux Engineering
Dell | Product Group, Bangalore Development Center
On 02.08.2010 18:50, Stuart Marsden wrote:
I have the same problem on a brand new R410
Centos 5.5
I can see this is cropping up more than once on this forum
Has anyone a solution?
what does omreport storage controller say?
I got that problem once and it was caused by missing libraries
Jefferson Cowart wrote:
The recommendations I've seen are to avoid using /dev/sdx for exactly this
reason. Instead you can use either file system labels or otherwise persistent
names generated by udev based on parameters that won't change.
Another (better?) solution is to use LVM logical
Alex and others -
Thanks. I think I will go with LVM. It has some nice other properties
as well. I assume that making a few large virtual disks (mostly segregated
by disk type and enclosure location) and using LVM to slice and dice
is the way to go?
Thx,
Ken
---
Jefferson
On 02.08.2010 18:50, Stuart Marsden wrote:
I have the same problem on a brand new R410
Centos 5.5
I can see this is cropping up more than once on this forum
Has anyone a solution?
what does omreport storage controller say?
I got that problem once and it was caused by
Dell is planning a release to address this issue but no accurate date
has been supplied as yet.
For anyone still following, there is still no ETA on the firmware fix
(i.e. it probably won't happen.) So much for Dell-branded drives being
more reliable and better tested than the non-Dell
16 matches
Mail list logo
