HZ70 failed disk

[admin1979]

Hello,

One of the disk in the HSZ70 Cluster is showing amber light. It have moved the disk to failedset.
We are not able to connect to any controllers using hsxterm command. Hence we have
connected using CONSOLE terminal and could see the failedset.
We have 2 disks in the sparesets.

HSZ70 > show sparesets

Name Storageset Uses Used by
------------------------------------------------------------------------------

SPARESET spareset DISK30100
DISK50200


Previously we had this output ,

HSZ70 > show failedsets

Name Storageset Uses Used by
------------------------------------------------------------------------------

FAILEDSET failedset
Switches:
NOAUTOSPARE



Now the question is , did the system automatically have replaced the failed disks (and synced the data)?
Or do we have to do it manually?

How to check this?

if its not automatically done then how do we do it manually?

Thanx,
admin

[cnb]

What's in the failedset now?

Your controller is not set up for AUTOSPARE.

See this reference:

http://sup.xenya.si/sup/info/digital/MDS/jun99/Cd3/STORAGE/CLI70RMA.PDF

Search for autospare.

HTH,

[admin1979]

You are rite. So I did remove 1 disk from spareset and added the same into the required Mirrored Set. The mirroring is completed and now things look ok EXCEPT 1 important thing. And that is , whenever we are trying to connect to HSZ70 using hsxterm, it is goint to FMU mode rather than HSZ70.

FMU>

We really want to know why is it happenin this?

Now you may ask how did me replace the hard disk then. We connected HSZ70 using CONSOLE and it could connect to HSZ70> prompt where we replaced the disk.

But the problem is like said , hsxterm is falling in FMU mode and not HSZ70 mode.

Any ideas/help would be appreciated please.


Thanx,
admin

[cnb]

When you see "FMU>", just type exit and you will be back to the HSZ70 prompt. FMU is Fault Management Utility.


PS. Points welcomed :)


HTH,

[admin1979]

No ...i dont think its that simple.

Immeiately after hsxterm command , HSZ70 should come and then if we do "run fmu"
system should show FMU> prompt.
But here the problem is , it directly goes to
FMU> and if we run exit , it comes out to the normal system prompt.

Thanx,
admin

[Nick Bishop (Kiwi)]

First thing first: points, points, points.

Go into your forums profile and click on the My question(s) -> Unassigned points, and assign points to whatever shows up (you should assign zero (0) to trivial replies). Don't worry, we're not doing a TRW on you, but your "46 of 130" is a little lacking.

Now to the real action ...
Your hsxterm is behaving a bit strange.

May I ask, do you have hszterm (note Z not X)?

Also, if you ...
# type hsxterm
# type hszterm
# file /bin/hszterm (or whatever shows up)
(and if necessary, follow any symlinks and execute "file" on the referrent).

# /bin/hszterm "show this"

What the "type" command should show is whether it is an alias or not, and if not, where it's getting the command from the $PATH.

The file command will show if its a script or a COFF (binary) file. Maybe someone jerrymandered your system.

The /bin/hszterm (or /bin/hsxterm) with whatever options you use to specify the HSZ70 (what I call the btlopts) with the argument "show this" should execute the "show this" command (hopefully not in FRU context). My example (HSZ50) is attached as text file (yes my battery is shot!).

You might have to open a separate thread for this, you should try to get your hs?term working, as you might need it if you can't front up with a serial cable one day.

Nick.

[admin1979]

As mentioned above.