hard disks failure

[Learn_1]

Hi All,
i am having problem with one of the disk installed in DS10 runnig tru64unix.quite new to try64unix. need ur guidance to resolve this issue.i dont know whether this disk is mirrored or not with other disk installed in this server. i am attaching the sys_check out. i need complete procedure to resolve this issue. Thanks

[Hein van den Heuvel]

Hmmm, that seems an old syscheck.

Anyway, it nicely captured the disk layout.
Search for "Storage Map for DIVR2A"

And yes, the disks are mirrored.
There are the physical disks dsk0 and dsk1 and which are mirrored into lsm plexes.

dsk0 seems to have IO problems, as per same from log below.

Try to re-seat it or just outright replace it.
Be sure to read up on the volume manager.
Just start with man volintro
Or... consider this... read the documentation!
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51_HTML/ARH9BBTE/TITLE.HTM


Also, your OS version is relatively old:
OSF1 DIVR2A V5.1 1885 alpha
Please consider updating.

Good luck,
Hein.


19-Dec-2005 13:57:39 [200] vmunix: lsm:volio: read error on object root01-01 of mirror rootvol-01 in volume rootvol (start 9584 length 16) corrected
19-Dec-2005 13:57:39 [200] LSM volnotify: change dg rootdg dgid 1062248149.1025.ipaeo1
19-Dec-2005 13:57:39 [300] LSM volnotify: detach plex vol-dsk0g-01 volume vol-dsk0g dg rootdg dgid 1062248149.1025.ipaeo1
19-Dec-2005 13:57:39 [300] LSM volnotify: relocate subdisk dsk0g-01 plex vol-dsk0g-01 volume vol-dsk0g dg rootdg dgid 1062248149.1025.ipaeo1

[Vladimir Fabecic]

You can also see this:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=983782

[Learn_1]

hi guys,
thanks. how can i check the hard disk part number without removing the hard disk from bay.

[Johan Brusche]

The details of the procedure to remove a failed root plex are in:
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51_HTML/ARH9BBTE/CHPTRBLX.HTM#replace-failed-boot-disk

Be sure to execute below 3 steps BEFORE the
disk is physically removed.

# volplex -o rm dis rootvol-01 swapvol-01 vol-dsk0g-01

# voldg rmdisk dsk0a dsk0b dsk0g

# voldisk rm dsk0a dsk0b dsk0g

Rgds,
___ Johan.

[Arch_Muthiah]

Anwar,

Use hwmgr commands with these options...

#hwmgr -show scsi -full
Without the -full flag, you won't get the serial number

# hwmgr -view dev -cat disk
# hwmgr â get attributes â id nnn


Archunan

[Hein van den Heuvel]

What disk?
Just rip it out... you'll have to anyway, but be sure to read the earlier comments on suggested lsm commands

The SYSCHECK you posted already has all details that the software can give. Just look around in there. You'll find for example:

hwmgr -show scsi -full
... dsk0 ...
"Maxtor 6E040L0 E1FJG11E"
... dsk1 ...
"Maxtor 6E040L0 E1C0WQDE"

http://maxtor.custhelp.com/cgi-bin/maxtor.cfg/php/enduser/olh_adp.php?p_faqid=1226

Elsewhere you'll find that is a 39/40GB disk.

So there you have it!
Just look around.

hth,
Hein.

[Learn_1]

Hi All,
Thanks for the update. Somehow attached the wrong sys_check output for analysis. My apology. Now attaching the original sys_check for analysis. Please check and suggest.

P.S: i can not see the 2nd disk anywhere in this report even not the device file for 2nd disk.

[Hein van den Heuvel]

>> Thanks for the update. Somehow attached the wrong sys_check output for analysis.

No duh!
(That's teenager american for 'I kid you not' / 'No kidding huh?' )

Isn't that what the first line in the first reply suggested?


This syscheck is more recent, but the system is much older: V4.0f.
hwmgr did not exist back then.
Look for:
"Disk Drives and Disk Labels"

You find:
Disk rz0 disk label: Bus 0 Target 0 Lun 0
/dev/rrz0a: character special (8/0) EIDE #0 6E040L0 disk #0 (SCSI ID #0) (SCSI LUN #0)

So it is in fact the same physical maxtor 40GB 6E040L0 drive type.
But this time there is no hardware/software mirror.
LSM is not active.

Good luck,
Hein.