• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1214
  • Last Modified:

How to Diagnose issue with Disk on STOREDGE A1000 Array

Hello, apologies for being vague on this, but I have limited experience with SUN. I have a SUN Fire V440 Machine which has storage array STOREDGE A1000 connected to it.  There is amber light one of the disks which is on the array. Im trying to figure out where to look on the machine for any diagnostics that can be run for the storage array (actually not sure if there is such a thing). Im just trying to figure out what to do next and steps to resolve. Im sure that I can just replace the disk with similar disk and hope for the best, but want to know more about it. Any information leading to resolution would be appreciated.
Thanks in advance!
0
smi-admin
Asked:
smi-admin
  • 5
  • 4
1 Solution
 
robocatCommented:

Run the rm6 admin utility:

/usr/lib/osa/bin/rm6

There's an option to perform a system healthcheck.

0
 
smi-adminAuthor Commented:
I ran it and it returned nothing back

[oracle@dbsperf2 oracle]$/usr/lib/osa/bin/rm6
bash: /usr/lib/osa/bin/rm6: bad interpreter: Permission denied
[oracle@dbsperf2 oracle]$su
Password:
# /usr/lib/osa/bin/rm6
#
0
 
robocatCommented:

Did you start this in an X-Windows session ?
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

 
smi-adminAuthor Commented:
Yes I started this in X-Windows session. I do get the admin console for managing. There are no apparent logs in the rmlog.log file. When I click on the 'Module Profile' button, I am able to see 'Drives', 'Luns', and 'Controllers' buttons; however only the 'LUNS' yield any result.
Im not able to get any further deatils about the drives. Am I missing something?

0
 
robocatCommented:

From the rm6 app, choose "Recovery", then click on the "Recovery guru and health check" icon.

0
 
smi-adminAuthor Commented:
I recieve the following Result "Unable to Scan Module".

I checked the following per the help items mentioned:
Detailed Status

 Host: dbsperf2

 Module: E6500_001

 Affected Tray: Controller Tray

 Affected Components: Unable To Scan Module

 Controller A:  1T10305474 ( c3t5d0 )



 Probable Cause

 A failure occurred while attempting to obtain information about the RAID
Module.



 CAUTION

 The Recovery Guru cannot detect any problems and your storage management
applications will not function properly while this condition persists.



 Recovery Steps

 1. If a firmware download operation is in progress or the controller(s) in the
RAID Modules are initializing after a reset (for example, the RAID Module was
turned off and then on again), wait for these operations to complete and then
re-run the Recovery Guru. If the problem persists, go to step 2.



 2. Try the following actions:
 - Run the command line utility "lad" to verify the controller(s) are visible
to the storage management software.

c3t5d0 1T10305474 LUNS: 0 1 2

 -  Run the appropriate 'clean' utility or reboot the operating system to fix
any temporary problem with the storage management software.
# ./clean
Stopping array monitor daemon and all osa applications
Array monitor daemon and all symsm applications stopped
Cleaning the osa locks
Locks successfully cleaned
Restarting array monitor daemon


 - Check the 'System_MaxLunsPerController' parameter in the rmparams file to
make sure that there are not too many LUNs existing on the controller(s) in
this RAID Module (that is, more than your operating system can handle).

<where is this located?>

- Check and fix any unterminated cables (SCSI connection only).

looks good.

- Check for any problems with the adapter or drivers in your host system.

<where can I look for this?> not notcing in the bin directory
0
 
robocatCommented:

Perhaps you should power down server and array and see if you can run diagnostics after power up.

0
 
smi-adminAuthor Commented:
I tried rebooting the machine already :( same issue persists upon power up.
0
 
robocatCommented:

Did you actually power down the A1000 and server for at least a minute or so ? There's a difference between rebooting and powering down.

>Check the 'System_MaxLunsPerController' parameter in the rmparams file

This is located in  /usr/lib/osa/rmparams

-What's the value for System_MaxLunsPerController in that file ?

-Also check if you've got /usr/lib/osa/bin/add16lun.sh

-is this a production system, do you have a maintenance contract ?

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now