failed disk & Debian / Ubuntu OMSA

[Ben Vinger]

Thanks - I know about this diagnostics program, because the Dell
support tech also suggested it.  The problem is that the machine is
remote, so I really need to be able to do this remotely, from within
Linux.  Rebooting to a floppy is not a possibility even if I was
running Redhat or SuSE.


On 9/19/06, Patrick_Boyd at dell.com <Patrick_Boyd at dell.com> wrote:
> You can get a version of diags off the dell support site that will boot
> the system and then run.
>
> Its here:
> http://support.dell.com/support/downloads/format.aspx?c=us&l=en&s=gen&Sy
> stemID=PWE_P4_850&os=NAA&osl=en&deviceid=196&typecnt=1&libid=13&releasei
> d=R127049&vercnt=4
>
> This should make tech support happy, running supported software on an
> unsupported opertating system probably wouldn't.
>
> Patrick Boyd
> Dell Storage Software Engineer
> (512)728-3182
>
>
> -----Original Message-----
> From: linux-poweredge-bounces at dell.com
> [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Ben Vinger
> Sent: Tuesday, September 19, 2006 4:42 AM
> To: linux-poweredge-Lists
> Subject: failed disk & Debian / Ubuntu OMSA
>
> Hello
>
> I'm completely new to OMSA, so if someone can suggest a better way
> please do.
> I have a failed SATA disk in a PE 850 (this I can see from the kernel
> messages and the fact that it dropped out of the Linux Software RAID).
>   I need to "prove" to the Dell engineer that the disk is dead "using
> Dell supported software".
> I installed OMSA 5 from:  ftp://ftp.sara.nl/pub/outgoing/dell
> Then I tried omdiag to see if it talks to the disk, but I get a load
> of Java errors instead (see below).   What can I do next?  Thanks
>
>  /opt/dell/srvadmin/oldiags/bin/omdiag storage -?
>
> omdiag           Executes component diagnostics.
>
> The available command(s) are:
>
> Command          Description
> Exception in thread "DiagnosticEngine" java.lang.UnsatisfiedLinkError:
> initialize
>         at
> com.dell.diagnostic.obj.diagcontroller.DiagnosticController.initialize(N
> ative
> Method)
>         at
> com.dell.diagnostic.vendor.diagcontroller.DiagControllerDiagnosticVendor
> .<init>(DiagControllerDiagnosticVendor.java:129)
>         at
> com.dell.diagnostic.engine.DiagnosticEngine.run(DiagnosticEngine.java:29
> 0)
>         at java.lang.Thread.run(Unknown Source)
>
>
> The kernel messages:
> [45439663.050000] ata1: command 0x35 timeout, stat 0x51 host_stat 0x21
> [45439663.050000] ata1: translated ATA stat/err 0x51/04 to SCSI
> SK/ASC/ASCQ 0xb/00/00 [45439663.050000] ata1: status=0x51 { DriveReady
> SeekComplete Error } [45439663.050000] ata1: error=0x04 {
> DriveStatusError } [45439663.050000] sd 0:0:0:0: SCSI error: return code
> = 0x8000002 [45439663.050000] sda: Current: sense key: Aborted Command
> [45439663.050000]     Additional sense: No additional sense information
> [45439663.050000] end_request: I/O error, dev sda, sector 2217018
> [45439663.050000] raid1: Disk failure on sda4, disabling device.
> [45439663.050000]       Operation continuing on 1 devices
> [45439663.240000] RAID1 conf printout:
> [45439663.240000]  --- wd:1 rd:2
> [45439663.240000]  disk 0, wo:1, o:0, dev:sda4 [45439663.240000]  disk
> 1, wo:0, o:1, dev:sdb4 [45439663.260000] RAID1 conf printout:
> [45439663.260000]  --- wd:1 rd:2
> [45439663.260000]  disk 1, wo:0, o:1, dev:sdb4
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
>