topic Re: Identify internal disk. in Operating System - Tru64 Unix

Identify internal disk.

Ryan Phlip — Wed, 23 Jul 2008 09:40:30 GMT

Hi,

I have a failed internal disk on my DS20 Tru64 Alpha Server. I want to physically identify this disk on the server. This is to make sure I am removing the correct disk from the server.

This is a cluster system.

Many Thanks,
Ryan Philip

Re: Identify internal disk.

Vladimir Fabecic — Wed, 23 Jul 2008 11:09:01 GMT

Please post output of:
# hwmgr -show scsi | grep dsk42
# hwmgr -view device | grep dsk42

Re: Identify internal disk.

Venkatesh BL — Wed, 23 Jul 2008 11:12:57 GMT

I think you can use:
# hwmgr -flash light -dsf /dev/disk/dsk42c

This will make the disklight blink.

Re: Identify internal disk.

Vladimir Fabecic — Wed, 23 Jul 2008 11:53:30 GMT

Not all disk can flash lights.
You can also try this and see on which disk activity led flashes:
# dd if=/dev/rdisk/dsk24c of=/dev/zero

Re: Identify internal disk.

Ryan Phlip — Wed, 23 Jul 2008 14:37:00 GMT

Hi,

I had read the administration guide and tried the flash and dd commands but there are no lights on the internal disk, so it becomes difficult. There are 4 9GB disk and 2 18GB disk. By using the Hwmgr flash command I cannot identify because the lights are not there.

Can someone explian to me the how to Identify the bus 0. Is there a way to do that5?

Regards,
Ryan Philip

Re: Identify internal disk.

Rob Leadbeater — Wed, 23 Jul 2008 19:37:44 GMT

Hi,

Can you post the output of the commands previously requested by Vladimir ?

dsk42 could be a single disk, or it might be part of a hardware RAID disk.... With the information provided so far, it's impossible to know...

Cheers,

Rob

Re: Identify internal disk.

Kapil Jha — Thu, 24 Jul 2008 02:31:18 GMT

If flash light is not there....only esacpe from hardware engineer is to use dd command and put hands on disk and u can feel which disk is working.
There would be 2 internal disks so chance are bright ;)

BR,
Kapil+

Re: Identify internal disk.

Vladimir Fabecic — Thu, 24 Jul 2008 08:51:08 GMT

Can someone explian to me the how to Identify the bus 0. Is there a way to do that5?

In SRM it should be bus "a".
For example DKA100 (in "console mode") should be BUS 0 ID 1 LUN 0. So, for example, if you are looking for disk in BUS 0 and SCSI ID 1, it should be DKA100.
As far as I know bus 0 should be "built in" controler bus.
In DS20 bus "b" or BUS 1 is usually a PCI SCSI controller.
If you need more details, first post what I asked for.

Re: Identify internal disk.

Ryan Phlip — Thu, 24 Jul 2008 09:00:29 GMT

Hi,

Firstly dsk42c is a single disk. It is not in any raid. The disk is spoiled so it does not respond. the output of the dd command is

dd if=/dev/disk/dsk42c of=/dev/zero
/dev/disk/dsk42c: Device busy

The other output is attached.

Regards,
Ryan Philip

Re: Identify internal disk.

Vladimir Fabecic — Thu, 24 Jul 2008 09:52:16 GMT

Command should be:
dd if=/dev/rdisk/dsk42c of=/dev/zero
not
dd if=/dev/disk/dsk42c of=/dev/zero
Try again.
So it is disk DKA100 in SRM.
And view in your disk shelf:
----dkao-----
----DKA100--- FAILED DISK
----dka200---
----dka300---
----dka400---
----dka500---
-------------

Re: Identify internal disk.

Ryan Phlip — Thu, 24 Jul 2008 15:17:45 GMT

Hi,

Vladimir that command works. Thanks.

How do I find out given the h/w path if the disk is in used or not.

Example : I know the disk H/W like /dev/rdsk/dsk42c how do i find out if its in use or already configured.

I have been told that a long time back spare disks have been lying in the server which are not in use. So I could use one of those.

Kind Regards,
Ryan Philip

Re: Identify internal disk.

Rob Leadbeater — Thu, 24 Jul 2008 15:23:59 GMT

Hi Ryan,

If you're using AdvFS, if the disk is being used, then it will be referenced somewhere under /etc/fdmns. So this will give some output if it is being used:

# ls -lR /etc/fdmns | grep dsk42

If you're using UFS then you'll see it in /etc/fstab.

You should also sanity check that the disk isn't being used as a swap disk with

# swapon -s

Cheers,

Rob

Re: Identify internal disk.

Vladimir Fabecic — Fri, 25 Jul 2008 06:42:02 GMT

Rob answered your question.
So post output of:
# ls -lR /etc/fdmns
# cat /etc/fstab
# swapon -s
if you want us to check if there are unused disks.

Re: Identify internal disk.

Venkatesh BL — Fri, 25 Jul 2008 07:02:28 GMT

>dd if=/dev/disk/dsk42c of=/dev/zero
>/dev/disk/dsk42c: Device busy

You should not see this error unless the block device is currently mounted. Are you sure that the AdvFS domain representing this device is unmounted now?

Re: Identify internal disk.

Ryan Phlip — Fri, 25 Jul 2008 11:52:24 GMT

Hi,

Firstly, nothing has been done on the system. I mean I identified the disk is spoiled its in a domain with one fileset mounted but you cannot do anything as the disk is totally gone. It not mirrored.

I am sending the outout as requested.

Regards,
Ryan

Re: Identify internal disk.

Vladimir Fabecic — Fri, 25 Jul 2008 12:38:25 GMT

dsk107 , dsk108 and dsk109 do look free for use.
Check again.
Send output of:
# disklabel -r dsk107
# disklabel -r dsk108
# disklabel -r dsk109

Re: Identify internal disk.

Ryan Phlip — Fri, 25 Jul 2008 13:33:01 GMT

Hi,

It does not look free to me. I am sending you the output.

Yes there is no entry in /etc/fdmns/

Thanks,
Ryan

Re: Identify internal disk.

Ryan Phlip — Fri, 25 Jul 2008 13:33:16 GMT

Hi,

It does not look free to me. I am sending you the output.

Yes there is no entry in /etc/fdmns/

Thanks,
Ryan

Re: Identify internal disk.

Vladimir Fabecic — Mon, 28 Jul 2008 06:27:02 GMT

Yes, these disks are labeled and have advfs created.
But do not see entries for them in /etc/fdmns.
Manually create entries for advfs domains, scan for file sets and try to mount them.
Do you know how to do it?

Re: Identify internal disk.

Venkatesh BL — Mon, 28 Jul 2008 07:02:38 GMT

1) If you can find a _really_ free disk on the system, use it.

2) It is possible that there was an AdvFS domain created earlier using these disks (dsk107, 108 etc) and that they forgot to 'rmfdmn' when the domain was no longer required. Or, they reinstalled the OS which left these disks to remain marked as 'AdvFS'