disks from hsg80 not appearing

[penelope_1]

Hello,

I am working with an EMA8000/HSG80 controller/Tru64 5.1B OS with ES40 Server. My array had been successfully built with raidsets and all were recognized by the OS.

Then I swapped 3 - 36G drives for 72G drives and rebuilt the 3 arrays associated with those drives. Everything appears correctly when I run my show commands (show raidset/show storage), but on the OS side it is not recognizing the new disks (raidsets). I ran hwmgr -scan scsi and when I run hwmgr -view devices I still don't see the new identifiers. The system has been rebooted several times. Not sure what else to try - any ideas as to why the OS can't see the new raidsets??

Thanks in advance for any info.

[Rob Leadbeater]

Hi,

Can you see the new raidsets if when you run "show units" from the HSG80...?

If yes, did you enable access to the units ?

Hope this helps,

Regards,

Rob

[penelope_1]

I can see them when I run show units and everything is Normal. Also, the access is All, same as the other raidsets. Any other ideas?

[Ivan Ferreira]

Can you post the commands that you have run in the HSG controller?

Can you post the show unit command?

Have you enabled host access?

[yves le bot]

Hello Penelope


is it you configure wwidmgr on the server

refer to this page on itrc



http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1075061&admit=-682735245+1181641021383+28353475

[penelope_1]

I have attached a document with the show units full/show storage full and hwmgr -view devices from the OS. Any ideas are greatly appreciated!
At this point my only thought of next step is to delete the 3 raidsets and re-add them, but it doesn't look like there is anything wrong with them so I don't know if that would even make a difference.

[Rob Leadbeater]

Hmmm... Everything would appear to be set up correctly.

The rebuilt arrays might have been known to the OS with a different LUN ID, but as they have the same Identifier things are getting confused.

Do you see any stale devices if you look at "hwmgr show scsi -full" ?

If yes, then try deleting them with hwmgr and dsfmgr, and rescan the SCSI bus.

Hope this helps,

Regards,

Rob

[Vladimir Fabecic]

As Rob said, output of "hwmgr show scsi -full" will give more information.
Please post it.

[penelope_1]

Thanks - I'm making progress! There were stale HWID's which I removed with hwmgr. I didn't know the previous/current dsk's, so I didn't use the dsfmgr command. When I run hwmgr view hierarchy I can see the raidsets, but they don't show up in hwmgr -view devices or diskconfig. Do you know how I can get the dsk# now for each of the 3 identifiers so that I can use them?

69: disk IDENTIFIER=2 dsk9
112: disk IDENTIFIER=5 SCSI-WWID:01000010:6000-1fe1-0010-5f90-0009-1130-5225-0063
110: disk IDENTIFIER=3 SCSI-WWID:01000010:6000-1fe1-0010-5f90-0009-1130-5225-0069
73: disk IDENTIFIER=6 dsk13
74: disk IDENTIFIER=7 dsk14
75: disk IDENTIFIER=8 dsk15
76: disk IDENTIFIER=9 dsk16
81: disk IDENTIFIER=11 dsk21
80: disk IDENTIFIER=12 dsk20
113: disk IDENTIFIER=4 dsk28
111: disk IDENTIFIER=10 SCSI-WWID:01000010:6000-1fe1-0010-5f90-0009-1130-5225-0071

[Rob Leadbeater]

Hi,

Use dsfmgr to delete the devices by the hardware identifier...

So as an example for your IDENTIFIER=5 disk...

hwmgr delete component -id 112
dsfmgr -R hwid 112

...repeat for the others then...

hwmgr scan scsi

And hopefully everything will be back on a dsk device.

Cheers,

Rob

[penelope_1]

Thanks Rob, the dsfmgr command worked using hwid #, but when i do a scan it still doesn't see them (and a reboot). When I read the man page for dsfmgr it seems to say to relink the old device special files to the new one. I'm wondering what's the other option if I don't know what the new ones are?

from the dsgmgr man page

The following command shows how you might restore previous device spe-
cial file names after a configuration change. This example assumes
that you know the previous device names and HWIDs

a. Assuming that the former device name was dsk0, and the new device
name is dsk5, use the /sbin/hwmgr command to delete the old data-
base entries for each device. Specify the former HWID for a dev-
ice as shown in the following example:

# # /sbin/hwmgr delete component -id 25

b. After the component is removed, you can delete the kernel's
record its device special files as follows:

# /sbin/dsfmgr -R delete hwid 25
-dsk0a -dsk0b -dsk0c -dsk0d ... dsk0h

c. You can now move the existing device special files to their new
locations as follows:

# /sbin/dsfmgr -m dsk5 dsk0

[Rob Leadbeater]

I wouldn't have thought you'd need to do the "dsfmgr -m" bit. When you rescan the disks should pick up new dsk devices.

Any chance you can post the output of "hwmgr show scsi" and "hwmgr show scsi -full"

Cheers,

Rob

P.S. There is a typo in the man page for dsfmgr.

# /sbin/dsfmgr -R delete hwid 25

should read

# /sbin/dsfmgr -R hwid 25

[penelope_1]

Here is the output from hwmgr show scsi and hwmgr show scsi -full - it shows the devices as valid, but null. I also included the hwmgr view hierarchy.
Thanks for your time with this.

[Rob Leadbeater · Accepted solution]

Odd... If they'd deleted properly, I'd have expected the devices to pick up new Hardware Identifiers after the rescan...

I seem to recall that the example in the dsfmgr man page is also the wrong way round, in that you should do the dsfmgr delete before the hwmgr delete.

Try this:

# dsfmgr -R hwid 112
# hwmgr delete component -id 112
# hwmgr show scsi

Check that HWID 112 has now disappeared.

If so, repeat for IDs 110 and 111.
If not, then you might need to run dsfmgr with the verify and fix option.

# dsfmgr -v -F

Once your sure the references to the old devices have gone:

# hwmgr scan scsi

Hopefully that will get things working !

Cheers,

Rob

[penelope_1]

Success! Thank you so much Rob.

[penelope_1]

See above