Disk - model

[Josh26]

Hey guys,

I've had a disk fail in a 3PAR 7200.

I can see the size (272GiB), speed (15K) and connection type (FC) of the disk from various interfaces, but HP now tell me they need me to drive onsite and look at the model number on the disk label before they do anything.

First they asked for an InSplor, then they claimed this information isn't stored in an InSplor.

Is there any method by which I can obtain this without a 14 hour drive?

[Richard Siemers]

I think (going from memory, impaired by some Capt Morgans) the IMC, System, Disks, one of the columns all the way to the right shows disk model? Alternatively to the IMC, lookup the options for the showpd command.

Secondly... I have never been asked to look at the front of a disk for a part number. Are you at a secure site that does not permit phone home/remote support?

[Josh26]

Hi Richard,

Thanks for the advice.

I think (going from memory, impaired by some Capt Morgans) the IMC, System, Disks, one of the columns all the way to the right shows disk model?

I can get the manufacturer (SEAGATE) in this case, but I can't see a complete model number there.

lookup the options for the showpd command

Thanks, I'm hunting through the various options right now.

Are you at a secure site that does not permit phone home/remote support?

Whilst I've configured the site not to allow remote login, the phone home service is fully operational. The technician on my case has advised she "doesn't have access to the logs" however. I asked who they even go to and she tells me she doesn't know.

[Richard Siemers]

Here you go!

SS7200-1 cli% showpd -i
Id CagePos State ----Node_WWN---- --MFR-- -----Model------ -Serial- -FW_Rev- Protocol MediaType
0 1:0:0 normal 5000CCA03EA221DB HITACHI HMRSK3000GBAS07K YVJW55HD 3P02 SAS Magnetic
1 1:1:0 normal 5000CCA03EA2216F HITACHI HMRSK3000GBAS07K YVJW54MD 3P02 SAS Magnetic
2 1:2:0 normal 5000CCA03E8EC1E3 HITACHI HMRSK3000GBAS07K YVJJHVKD 3P02 SAS Magnetic
3 1:4:0 normal 5000CCA03EA22183 HITACHI HMRSK3000GBAS07K YVJW54TD 3P02 SAS Magnetic
4 1:5:0 normal 5000CCA03EA25717 HITACHI HMRSK3000GBAS07K YVJW8RDD 3P02 SAS Magnetic
5 1:6:0 normal 5000CCA03E91322F HITACHI HMRSK3000GBAS07K YVJKVEED 3P02 SAS Magnetic
6 1:8:0 normal 5000CCA03EA22147 HITACHI HMRSK3000GBAS07K YVJW549D 3P02 SAS Magnetic
7 1:9:0 normal 5000CCA03EA2B7BB HITACHI HMRSK3000GBAS07K YVJWH4XD 3P02 SAS Magnetic
8 1:10:0 normal 5000CCA03E923DF7 HITACHI HMRSK3000GBAS07K YVJLE88D 3P02 SAS Magnetic
9 1:12:0 normal 5000CCA03EA221E3 HITACHI HMRSK3000GBAS07K YVJW55KD 3P02 SAS Magnetic
10 1:13:0 normal 5000CCA03EA287F7 HITACHI HMRSK3000GBAS07K YVJWBZ9D 3P02 SAS Magnetic
11 1:14:0 normal 5000CCA03E910FAB HITACHI HMRSK3000GBAS07K YVJKT45D 3P02 SAS Magnetic
12 1:16:0 normal 5000CCA03EA2725F HITACHI HMRSK3000GBAS07K YVJWAJRD 3P02 SAS Magnetic
13 1:17:0 normal 5000CCA03E910E73 HITACHI HMRSK3000GBAS07K YVJKT1ND 3P02 SAS Magnetic
14 1:20:0 normal 5000CCA03EA287A3 HITACHI HMRSK3000GBAS07K YVJWBYMD 3P02 SAS Magnetic
15 1:21:0 normal 5000CCA03E910FFB HITACHI HMRSK3000GBAS07K YVJKT4UD 3P02 SAS Magnetic
------------------------------------------------------------------------------------------------
16 total

[Josh26]

Fantastic!

Thanks for that, now I've got a part on the way.

[Davidkn]

Seems crazy that hp wouldn't know this info and how to obtain it rather than going onsite and removing the disk to see.

Do you not think that it's phoning home then? Did they contact you about the disk failure or did you contact them?

[Josh26]

Do you not think that it's phoning home then? Did they contact you about the disk failure or did you contact them?

The phone home is working fine. You can access the "log transfer queue" in your SP and verify the last successful transfer. Mine is never more than a few hours old.

If it misses just one phone home, I get an email at three in the morning, followed by an email two hours later with a "gentle reminder" that I investigate it. They take getting their logs seriously.

They emailed me about the "alert", but multiple people on this ticket all advised they did not have access to the logs or any information about how the alert was generated.