topic Re: VA7410 device not ready in Disk Enclosures

VA7410 device not ready

Timothy P. Jackson — Tue, 25 Sep 2007 16:18:05 GMT

Hello everyone,

I am working on a system that has been shut down for a while, maybe weeks. When I boot the system the LUNs don't seem to be there. If I do a armdsp /dev/dsk/c4t0d0 I get the message "Device not Ready"

The VA7410 is powered up, any ideas on how to get the HP server to see it again?

HP rp5470 - HP-UX 11.11 Version 1

Any help would be greatly appreciated!

Tim

Re: VA7410 device not ready

Timothy P. Jackson — Tue, 25 Sep 2007 17:30:25 GMT

I have dug out a little more information. If I do a cvui and look at the status I found that none of the disk drives are included.

I also have a warning stating that the batteries that backup the NVRAM in the array controllers have been depleted to the point where removing power from the controller may cause data loss.

Is this bad?

I looked in the cvui under diagnostics and there is a rebuild function. I am looking for a little guidance on where to go from here.

Rebuilding the entire array would be bad. Evidently there is archived data on this array and it needs to be available.

Tim

Re: VA7410 device not ready

tkc — Tue, 15 Oct 2024 01:44:37 GMT

hi tim,

pls refer to these links :

~~http://h20000.www2.hp.com/bizsupport/TechSupport/SupportTaskIndex.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=89018&taskId=110~~

~~http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=89018&prodTypeId=12169&objectID=lpg60204~~

[Moderator edit: Removed the broken link. Please refer to https://support.hpe.com/]

Re: VA7410 device not ready

Timothy P. Jackson — Tue, 25 Sep 2007 20:29:30 GMT

Thanks for the respose TKC.

I checked out these two links and the first one had some trouble shooting help but I didn't find any thing that would tell me how to rebuild the LUNs or if the disks not being included meant anything.

The second link doesn't seem to go any where, I could be doing something wrong.

Tim

Re: VA7410 device not ready

tkc — Tue, 25 Sep 2007 22:36:35 GMT

i would suggest to connect the serial port and use vfp commands to check the status of the disk array first :

vfpdsp -s (to check the status)
vfpdsp -c (to check the controller)
vfpdsp -d (to check the disks)
vfpdsp -e (to check the enclosure)
vfpdsp -L (to check the luns)

Re: VA7410 device not ready

tkc — Tue, 25 Sep 2007 22:39:12 GMT

i am not sure if your host though can't see the disk device file, but can you get any output when running the armdsp command?

#armdsp -i (to get the array id)
#armdsp -a (to get the status of the array)

Re: VA7410 device not ready

Timothy P. Jackson — Wed, 26 Sep 2007 07:55:46 GMT

Hey tkc,

The cvui interface actually runs these commands from it's menu. So I am getting plenty of out put from the array. I can look at anything I want to.

Every thing seems to look good except when I look at the disks and none of them show include and non of my LUN's are showing any more.

The output of the #armdsp -a is "Device not ready"

Re: VA7410 device not ready

Torsten. — Wed, 26 Sep 2007 09:31:58 GMT

If cvui works, then
armdsp -a
will work too.
Try it again.

Better to know the current status before running any "diag" function.

The "rebuild" option will not help you at the moment, I guess.

Re: VA7410 device not ready

Timothy P. Jackson — Wed, 26 Sep 2007 09:58:48 GMT

Thanks for the reply Torsten!

This is the odd part. cvui works just fine unless I try to look at the LUN status armdsp -L va7400 and it comes back with the following.

Status: Array Status
Device is not ready

The armdsp -a va7400 returns the same message. I am pretty sure that the batteries on the controllers NVRAM went dead while it was powered off. The only warning light that is on is for the battery

I did start another thread looking for information on the cvui utility. i was wondering what the "Rebuild" does or what the "Recover when NVRAM contents are lost" functions do. Maybe I am heading in the wrong direction.

Re: VA7410 device not ready

Torsten. — Wed, 26 Sep 2007 10:05:34 GMT

I would do this:

Shutdown and power off the array.
Take out the controllers, remove the battery for a while (I think they are empty anyway).

After some minutes put everythink back and start the array.

Connect a terminal to the serial ports, watch the status.

The controllers should get the config from the map-disks.

Do you have the commandview user guide?

It says about recovery:

"The armrecover reconstructs data mapping and array configuration in the
event of the loss of NVRAM contents. The data maps are reconstructed using
the latest copy of mapping information stored on the disk drives. Part of the
recovery operation includes performing a parity scan on the contents of the
entire array to validate the accuracy of the maps and to correct any drive
parity inconsistencies...."

Maybe this action is not needed at the moment.

Try to get some status information and post, I have no idea how the status looks like at the moment.

Re: VA7410 device not ready

Timothy P. Jackson — Tue, 15 Oct 2024 01:53:50 GMT

Here are some status prints from the cvui.

armdsp -s

2

Exec command: armdsp -s 50060b0000092a9c

Vendor ID:______________________________HP
Product ID:_____________________________A6189A
Array World Wide Name:__________________50060b0000092a9c
Array Serial Number:____________________**~~removed~~**
Alias:__________________________________va7400
------------------------------------------------------------

SUB-SYSTEM SETTINGS

RAID Level:___________________________HPAutoRAID
Auto Format Drive:____________________On
Hang Detection:_______________________On
Capacity Depletion Threshold:_________100%
Queue Full Threshold Maximum:_________4096
Enable Optimize Policy:_______________True
Enable Manual Override:_______________False
Manual Override Destination:__________False
Read Cache Disable:___________________False
Rebuild Priority:_____________________Low
Security Enabled:_____________________False
Shutdown Completion:__________________0
Subsystem Type ID:____________________1
More([Enter]=Next Page, q=Quit, v=View)>

Unit Attention:_______________________True
Volume Set Partition (VSpart):________False
Write Cache Enable:___________________True
Write Working Set Interval:___________8640
Enable Prefetch:______________________False
Disable Secondary Path Presentation:__False

RESILIENCY SETTINGS

Simplified Resiliency Setting:________Normal Performance (Default)
Enable Secure Mode:___________________True
Disable NVRAM on UPS Absent:__________False
Disable NVRAM on WCE False:___________False
Disable Read Hits:____________________False
Force Unit Access Response:___________1
Lock Write Cache On:__________________True
Performance Goal Configuration:_______Normal Performance
Resiliency Threshold:_________________4
Single Controller Warning:____________True

DISK SETTINGS

Auto Include:_________________________On
More([Enter]=Next Page, q=Quit, v=View)>

Auto Rebuild:_________________________On
Hot Spare:____________________________Automatic
Max Drives per Loop Pair:_____________105
Max Drives per Subsystem:_____________105

ENCLOSURE SETTINGS

Max Enclosures per Loop Pair:_________6
Max Enclosures per Subsystem:_________6

LUN SETTINGS

LUN Creation Limit:___________________1024
Maximum LUN Creation Limit:___________1024
Migrating Write Destination:__________False

SCRUB SETTINGS

Scrub Restart Period:_________________7190 minutes
Scrub State:__________________________Idle, initialized

OPERATIONS IN PROGRESS

More([Enter]=Next Page, q=Quit, v=View)>

None

WARNINGS

WARNING: The subsystem cannot identify any disks suitable for storing metadata.

armdsp -d

Storage->HpArrayMain->Properties->Disk
DeviceID: 50060b0000092a9c

If FRU location is a disk, display properties for that disk.

If FRU location is an enclosure, display properties for all disks
in the enclosure.

If FRU location is blank, display properties for all disks.

FRU location can be identified using the syntax, /[]

where,
can be M for main.

can be D1-D15 for disk.

(FRU location, b=Back, h=Help, [Enter]=All Disks)>

Exec command: armdsp -d 50060b0000092a9c

Vendor ID:______________________________HP
Product ID:_____________________________A6189A
Array World Wide Name:__________________50060b0000092a9c
Array Serial Number:____________________~~**removed**~~
Alias:__________________________________va7400
------------------------------------------------------------

Disk at M/D1:
Status:_______________________________Good
Disk State:___________________________Previously used
Vendor ID:____________________________HP 18.2G
Product ID:___________________________ST318452FC
Product Revision:_____________________HP05
Data Capacity:________________________16.689 GB (35000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________111
Node WWN:_____________________________20000004cf75de2f
Initialize State:_____________________Ready
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________**~~removed~~**
Serial Number:________________________**~~removed~~**
Firmware Revision:____________________HP05
More([Enter]=Next Page, q=Quit, v=View)>

Disk at M/D2:
Status:_______________________________Good
Disk State:___________________________Previously used
Vendor ID:____________________________HP 18.2G
Product ID:___________________________ST318452FC
Product Revision:_____________________HP05
Data Capacity:________________________16.689 GB (35000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________112
Node WWN:_____________________________20000004cf75df4c
Initialize State:_____________________Ready
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________**~~removed~~**
Serial Number:________________________**~~removed~~**
Firmware Revision:____________________HP05

Disk at M/D3:
Status:_______________________________Good
Disk State:___________________________Previously used
Vendor ID:____________________________HP 18.2G
Product ID:___________________________ST318452FC
Product Revision:_____________________HP05
More([Enter]=Next Page, q=Quit, v=View)>

Data Capacity:________________________16.689 GB (35000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________113
Node WWN:_____________________________20000004cf75dc9e
Initialize State:_____________________Ready
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________**~~removed~~**
Serial Number:________________________**~~removed~~**
Firmware Revision:____________________HP05

Disk at M/D5:
Status:_______________________________Good
Disk State:___________________________Previously used
Vendor ID:____________________________HP 18.2G
Product ID:___________________________ST318451FC
Product Revision:_____________________HPC4
Data Capacity:________________________16.689 GB (35000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________115
Node WWN:_____________________________2000002037f5c6f1
Initialize State:_____________________Ready
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________**~~removed~~**
More([Enter]=Next Page, q=Quit, v=View)>

Serial Number:________________________**~~removed~~**
Firmware Revision:____________________HPC4

Disk at M/D6:
Status:_______________________________Good
Disk State:___________________________Previously used
Vendor ID:____________________________HP 18.2G
Product ID:___________________________ST318452FC
Product Revision:_____________________HP06
Data Capacity:________________________16.689 GB (35000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________116
Node WWN:_____________________________20000004cf75de68
Initialize State:_____________________Ready
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________**~~removed~~**
Serial Number:________________________**~~removed~~**
Firmware Revision:____________________HP06

Disk at M/D7:
Status:_______________________________Good
Disk State:___________________________Previously used
Vendor ID:____________________________HP 18.2G
More([Enter]=Next Page, q=Quit, v=View)>

Product ID:___________________________ST318452FC
Product Revision:_____________________HP06
Data Capacity:________________________16.689 GB (35000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________117
Node WWN:_____________________________20000004cf7538bc
Initialize State:_____________________Ready
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________**~~removed~~**
Serial Number:________________________**~~removed~~**
Firmware Revision:____________________HP06

Disk at M/D8:
Status:_______________________________Good
Disk State:___________________________Previously used
Vendor ID:____________________________HP 18.2G
Product ID:___________________________ST318451FC
Product Revision:_____________________HPC4
Data Capacity:________________________16.689 GB (35000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________118
Node WWN:_____________________________2000002037fa48a1
Initialize State:_____________________Ready
More([Enter]=Next Page, q=Quit, v=View)>

Redundancy Group:_____________________65536
Volume Set Serial Number:_____________**~~removed~~**
Serial Number:________________________**~~removed~~**
Firmware Revision:____________________HPC4

Disk at M/D9:
Status:_______________________________Good
Disk State:___________________________Previously used
Vendor ID:____________________________HP 18.2G
Product ID:___________________________ST318452FC
Product Revision:_____________________HP06
Data Capacity:________________________16.689 GB (35000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________119
Node WWN:_____________________________20000004cf8c73e3
Initialize State:_____________________Ready
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________**~~removed~~**
Serial Number:________________________**~~removed~~**
Firmware Revision:____________________HP06

Disk at M/D10:
Status:_______________________________Good
More([Enter]=Next Page, q=Quit, v=View)>

Disk State:___________________________Previously used
Vendor ID:____________________________HP 18.2G
Product ID:___________________________ST318451FC
Product Revision:_____________________HP10
Data Capacity:________________________16.689 GB (35000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________120
Node WWN:_____________________________2000002037f56721
Initialize State:_____________________Ready
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________**~~removed~~**
Serial Number:________________________**~~removed~~**
Firmware Revision:____________________HP10

Disk at M/D11:
Status:_______________________________Good
Disk State:___________________________Previously used
Vendor ID:____________________________HP 18.2G
Product ID:___________________________ST318452FC
Product Revision:_____________________HP06
Data Capacity:________________________16.689 GB (35000000 blocks)
Block Length:_________________________520 bytes
Address:______________________________121
More([Enter]=Next Page, q=Quit, v=View)>

Node WWN:_____________________________20000004cf9cd2ec
Initialize State:_____________________Ready
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________**~~removed~~**
Serial Number:________________________**~~removed~~**
Firmware Revision:____________________HP06

armdsp -e

Storage->HpArrayMain->Properties->Enclosure
DeviceID: 50060b0000092a9c

If FRU location is an enclosure, display properties for that enclosure.

If FRU location is blank, display properties for all enclosures.

FRU location can be identified using the syntax,

where,
can be M for main.

(FRU location, b=Back, h=Help, [Enter]=All Enclosures)>

Exec command: armdsp -e 50060b0000092a9c

Vendor ID:______________________________HP
Product ID:_____________________________A6189A
Array World Wide Name:__________________50060b0000092a9c
Array Serial Number:____________________**~~removed~~**
Alias:__________________________________va7400
------------------------------------------------------------

FRU HW COMPONENT IDENTIFICATION ID STATUS
===========================================================================
M Enclosure 00SG149G0102 Good

armdsp -L

Storage->HpArrayMain->Properties->LUNs
DeviceID: 50060b0000092a9c

Enter an existing LUN number, or press the enter key to list all LUNs.

(LUN number, a=App menu, b=Back, h=Help, [Enter]=All LUNs)>

Exec command: armdsp -L 50060b0000092a9c

Status : Array Status
Device is not ready.

armdsp -t

Exec command: armdsp -t 50060b0000092a9c

Vendor ID:______________________________HP
Product ID:_____________________________A6189A
Array World Wide Name:__________________50060b0000092a9c
Array Serial Number:____________________**~~removed~~**

Alias:__________________________________va7400
------------------------------------------------------------

(addresses are 0 based)
Disk Controller paths to Encl Hard Assigned
Fru disks Addr Addr Addr
------- ------------------- ---- ---- --------
M/D1 (M/C1.J1, M/C2.J1)* 0x6f 0x6f 0x6f
M/D2 (M/C1.J1, M/C2.J1)* 0x70 0x70 0x70
M/D3 (M/C1.J1, M/C2.J1)* 0x71 0x71 0x71
M/D5 (M/C1.J1, M/C2.J1)* 0x73 0x73 0x73
M/D6 (M/C1.J1, M/C2.J1)* 0x74 0x74 0x74
M/D7 (M/C1.J1, M/C2.J1)* 0x75 0x75 0x75
M/D8 (M/C1.J1, M/C2.J1)* 0x76 0x76 0x76
M/D9 (M/C1.J1, M/C2.J1)* 0x77 0x77 0x77
M/D10 (M/C1.J1, M/C2.J1)* 0x78 0x78 0x78
M/D11 (M/C1.J1, M/C2.J1)* 0x79 0x79 0x79

More([Enter]=Next Page, q=Quit, v=View)>

Note: "*" indicates the drive is physically present
in the specified enclosure.

"#" indicates that one or more addresses do not match the
enclosure address (Encl Addr).

===================================================
Drives Listed in Physical Loop Order
===================================================

M/C1.J1 M/C2.J2 M/C1.J2 M/C2.J2
------- ------- ------- -------
M/D1 M/D1 ------- -------
M/D2 M/D2 ------- -------
M/D3 M/D3 ------- -------
M/D5 M/D5 ------- -------
M/D6 M/D6 ------- -------
M/D7 M/D7 ------- -------
M/D8 M/D8 ------- -------
M/D9 M/D9 ------- -------
M/D10 M/D10 ------- -------
M/D11 M/D11 ------- -------

More([Enter]=Next Page, q=Quit, v=View)>

I don't really see anything in here that is obviously wrong.

[Moderator edit: Removed the confidential info.]

Re: VA7410 device not ready

Torsten. — Wed, 26 Sep 2007 11:03:52 GMT

But I can see something

Disk State:___________________________Previously used

This normally happens when you move a disk from one VA to another. The VA "think" now - wow a disk, but I'm not the owner.

Did you change anythink while the VA was off?

Where is M/D4?

And BTW, what gives

armdsp -a 50060b0000092a9c

Re: VA7410 device not ready

Timothy P. Jackson — Wed, 26 Sep 2007 11:12:37 GMT

Nothing was changed while the power was off.

"Where is M/D4", thats a good question, I did notice that before. I will go take another look at the hard drives.

The "armdsp -a 50060b0000092a9c" is what it used when I used the cvui menu. It doesn't give you a choice to use the alias versus the world wide address.

Re: VA7410 device not ready

Torsten. — Wed, 26 Sep 2007 11:23:06 GMT

If you do a full reset or power up, you should see something like this on the serial console:

HP Virtual Array 7410
Firmware Image 2 selected
Testing internal SRAM: Passed
Activating DDR DRAM: Success
Testing L1 cache: Passed
Testing NVSRAM: Passed
DDR DRAM decode test: Passed
DDR DRAM pattern test: Passed
DDR DRAM ECC test: Passed
Copying firmware image to DRAM
38370A130P1008000000: Initializing:
02 04 06 08 0A 0C 0E 12 16 18 1A 1C 1D 1E 20 22 24 26
Ready >

What can you see?

Re: VA7410 device not ready

Timothy P. Jackson — Wed, 26 Sep 2007 11:33:23 GMT

I am not in that building right at the momemt, so I will head over there in just a couple of minutes.

I don't have a commandview manual, do you know where I can down load it.

Re: VA7410 device not ready

Torsten. — Tue, 15 Oct 2024 01:42:28 GMT

Try this:

http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&prodSeriesId=64112&targetPage=http%3A%2F%2Fh20000.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00662561%2Fc00662561.pdf

from here

~~http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&prodClassId=-1&contentType=SupportManual&docIndexId=179166&prodTypeId=18964&prodSeriesId=64112~~

[Moderator edit: Removed the broken link. Please refer to https://support.hpe.com/]

Re: VA7410 device not ready

tkc — Thu, 27 Sep 2007 00:26:38 GMT

not easy to determine the originality of the disks. they could have been moved around withing the enclosure.

Re: VA7410 device not ready

tkc — Thu, 27 Sep 2007 00:26:44 GMT

not easy to determine the originality of the disks. they could have been moved around within the enclosure.

Re: VA7410 device not ready

Timothy P. Jackson — Thu, 27 Sep 2007 15:27:24 GMT

I appologize for the delay in continuing this thread!!! My boss caught me and sent me off on another critical problem.

So I did take a look at the array and here is what it is doing now. All the disks drives are flashing orange. The Battery light is now on green . When I attach to the serial port and boot the array it starts it's initialization process then with out any other messages it goes straight to a the following prompt.

No Map>

Re: VA7410 device not ready

Torsten. — Thu, 27 Sep 2007 16:57:20 GMT

You have now a disk array without disks.

The disks are not included, so the array don't "own" the disks. The maps in the controllers are lost (due to the empty batteries), the controllers cannot read the maps from the disks, because they don't own the disks for any reason.

Do you still need the data?

Consider to use your backup.
You can try the "recover" command.
You can include the disks manually and format the array.
Finally, you can hope for someone have a better solution - sorry.