ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Magical non-existent drive in Array Configuration Utility

 
Occasional Advisor

Magical non-existent drive in Array Configuration Utility

I have been tearing my hair out over this one. Using RAID card 5i to mirror two 36GB drives in a DL360, we suffered a drive failure. We removed the failed drive and put in a new one while the system was up, hoping for it to rebuild itself.

The Array Configuration Utility is now showing there to be three drives: ID0 (the working drive), ID1 (the new drive) and ID5 (a drive that does not exist). In the ACU, drives indicated at ID0 and ID5 are shown to be in the array configured for mirroring, whereas the drive at ID1 is not in an array at all.

So far as I can tell, I need to remove ID5 first and then re-introduce ID1 to the array, but because the drive at ID5 is not there, I can't just yank it out.

If requested, I can drop in portions of the Array Daigs Utility output.

Thank you for any help in advance!
9 REPLIES 9
Frequent Advisor

Re: Magical non-existent drive in Array Configuration Utility

Is there a possibility that you can reboot the server and log directly into the raid card? you should be able to run a consistency check from there and add the other disk.

On a 36GB drive a consistency check may take over an hour. there are other tools in there also that may help you remove the incorrectly reported drives.

Hope the above is useful.

Marcus
BOFH since 1999
Occasional Advisor

Re: Magical non-existent drive in Array Configuration Utility

Thanks for the suggestion. I will give this a go at the earliest opportunity and let you know how I get on.
Valued Contributor

Re: Magical non-existent drive in Array Configuration Utility

Hi,

could you kindly attach the ADU report from the server.

Andy.
Occasional Advisor

Re: Magical non-existent drive in Array Configuration Utility

The new drive is currently not in the system, so this is how the ADU looks without it.

I've edited out a lot of HEX stuff and line relating to Drive IDs beyond ID3...

-----------------------

Array Diagnostic Utility Version 7.31.2.0
Array Diagnostic Utility Inspection Report Version 7.31.0.1

Date/Time: Thursday, October 09, 2008 9:33:40AM
Computer Model: HP Server


SLOT SUMMARY:
Slot Num Slot Type Array Controllers and Host Adapters Detected
-------- --------- --------------------------------------------
SLOT 0 PCI Smart Array 5i Controller

SLOT 0 Smart Array 5i Controller ERROR REPORT:

Logical drive 1 status = Interim recovery (volume functional, but not fault tolerant)
SCSI Port 1, drive ID 3 failed - REPLACE (Drive timeout)
Error occurred reading RIS copy from SCSI Port 1 Drive ID 3

SUBSYSTEM INFORMATION:

Chassis Serial Num: J00KLGP52P
This Controller
Array Serial Number: Not Available
Cache Serial Number: Not Available
Other Controller
Array Serial Number: Not Available
Cache Serial Number: Not Available

CONTROLLER IDENTIFICATION:
Configured Logical Drives: 1
Configuration Signature: 0xa0000351
Controller Firmware Rev: 2.58
Controller ROM Revision: 2.76
Controller Hardware Rev: 0x01
Boot Block Version: 0.18
Board ID: 0x40800e11
Cable or Config Error: 0x00 (No)
Invalid Host RAM Address: No
CPU Revision: 0xc0
CPU to PCI ASIC Rev: 0x00
Cache Controller ASIC Rev: 0x01
PCI to Host ASIC Rev: 0x00
Marketing Revision: 0x42 (Rev B)
Expand Disable Code: 0x01
SCSI Chip Count: 2
Max SCSI IDs per Bus: 16
Big Drive Map: 0x0001 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Ext Drive Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Non-Disk Drive Map: 0x0080 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Host I2C Autorev: 0x00 (level of hardware and programmable logic devices)
CPLD Revision: 0x08 (code level used in the programmable logic devices)
Fibre Chip Count: 0
LKS: 0x00
AMS: 0x00
FS: 0x00 0x00 0x00 0x00 0x00 0x00
0x2e32 0x3637 0x01 0x00 0x00 0x4000
Recovery ROM Inactive
Image Revision: 2.76
Recovery ROM Active Image
Flags Status: 0x01
Percent Write Cache: 0
Daughterboard Size(MB): 64
Cache Battery Count: 0

LOGICAL DRIVE IDENTIFICATION:

Logical Drive 1:
Sector Size: 512
Sectors Available: 71122560
Fault Tolerance Mode: Mirroring
Logical Param Table: cyl=8716 heads=255 sec/track=32 xlate sig=0x0
BIOS Disabled: No

LOGICAL DRIVE CONFIGURATION:

Logical Drive 1:
Configuration Signature: 0xa0000351
Mapping Scheme: Multiple Block
Physical Drives: 2 (number not valid after drive movement)
This Logical Drive: 2 (excluding spare drives)
Fault Tolerance Mode: Mirroring
Logical Param Table: cyl=8716 heads=255 sec/track=32 xlate sig=0x0
Distribution Factor: 256
Operating System: 64768
Controller Order: 0
Additional Information: 0
Offset to Data: 0
Int 13h Support Enabled: Yes
Sectors on Volume: 71122560
Sectors per Drive: 71122560
Big Drive Assignment Map: 0x0009 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Spare Assignment Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Array Accelerator is enabled for this logical drive.

LOGICAL DRIVE STATUS:

Logical Drive 1:
Drive Status: Interim recovery (volume functional, but not fault tolerant)
Blocks to Rebuild: 0
Blocks Re-mapped:
Spare Status Flags: 0x00
Spare to Replaced Map: See Big Spare to Replace Map:
Media Was Exchanged: No
Cache Failure: No
Expand Failure: 0x00
Unit Flags: 0x10
Big Remap Count: All Counts Zero
Big Drive Failure Map: 0x0008 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Replacement Drive Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Active Spare Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
Big Spare to Replace Map: No spares have replaced any drives
Big Spare Marked OK Map: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000

MONITOR AND PERFORMANCE DATA:

SCSI Port 1, Drive ID 0
Factory: Serial #, Firmware Rev, and Mfg/Model #:
33 4a 41 37 4b 32 30 48 30 30 30 30 37 34 34 30 3JA7K20H00007440
44 50 45 36 48 50 42 36 00 00 00 00 43 4f 4d 50 DPE6HPB6....COMP
41 51 20 20 42 44 30 33 36 38 35 41 32 34 20 20 AQ BD03685A24
20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00 ............
00 00 00 00 ....
Since Power: Serial #, Firmware Rev, and Mfg/Model #:
33 4a 41 37 4b 32 30 48 30 30 30 30 37 34 34 30 3JA7K20H00007440
44 50 45 36 48 50 42 36 00 00 00 00 43 4f 4d 50 DPE6HPB6....COMP
41 51 20 20 42 44 30 33 36 38 35 41 32 34 20 20 AQ BD03685A24
20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00 ............
00 00 00 00 ....
Threshold Flags: 0x0001
Serial Number Control: 0x8054
Firmware Revision Control: 0x8248
Mfg/Model Number Control: 0x8268

<--- edit --->

DRIVE ERROR LOG:
No errors logged.

SCSI Port 1, Drive ID 1
Not Available

DRIVE ERROR LOG:
Not Available

SCSI Port 1, Drive ID 2
Not Available

DRIVE ERROR LOG:
Not Available

SCSI Port 1, Drive ID 3
Factory: Serial #, Firmware Rev, and Mfg/Model #:
55 50 4c 31 50 34 35 30 4a 36 4b 38 30 34 32 30 UPL1P450J6K80420
00 00 00 00 48 50 42 36 00 00 00 00 43 4f 4d 50 ....HPB6....COMP
41 51 20 20 42 44 30 33 36 38 36 32 32 33 20 20 AQ BD03686223
20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00 ............
00 00 00 00 ....
Threshold Flags: 0x0001
Serial Number Control: 0x8054
Firmware Revision Control: 0x8248
Mfg/Model Number Control: 0x8268


DRIVE ERROR LOG:
Error Log Header:
Parameter Length = 0x14
Entry Size = 0x0014
Current Entry = 0x06
Total Errors Logged = 0x00000006


<---- edit ---->

PHYSICAL DRIVE IDENTIFICATION:

SCSI Port 1, Drive ID 0
Vendor Id: COMPAQ
Product Id: BD03685A24
Product Rev: HPB6
Vendor Specific: 3JA7K20H
Serial Number: 3JA7K20H00007440DPE6
SCSI Inquiry Header: 00 00 03 12 8b 00 01 3e
Device Supports: Tagged Command Queueing
Linked Commands
Synchronous Data Transfer
16-bit Wide Data Transfer
Drive Type: 0x00 Parallel SCSI
Block Size: 512 bytes/sector
Total Blocks: 71123808 sectors/disk
Reserved Blocks: 1088 reserved sectors/disk
SCSI Inquiry Bits: 0x3E
Stamped for M&P: yes
Last Failure Reason: 0x00 (Drive has not failed)
Phys Drive Flags: 0xcd 0x25 0x95 0x01
Drive present and operational
Wide SCSI transfers Enabled
Ultra3 SCSI Enabled
S.M.A.R.T. Supported
S.M.A.R.T. Enabled
Quick Arbitration and Selection Capable
Configured as part of Logical Drive
Drive write cache setting is changeable and safe
SCSI LUN: 0
Spi Speed Rules: 0x00800000
Physical Connector: J1 (controller connector attached to drive)
Physical Box on Bus: 0 (number of the physical enclosure in which drive resides)

Physical Bay in Box: 0 (number of the physical drive bay in the enclosure)

<---- edit ---->

SCSI Port 1, Drive ID 1 ---> Not available
SCSI Port 1, Drive ID 2 ---> Not available
SCSI Port 1, Drive ID 3

Drive Model:
Product Rev:
Serial Number:
Drive Type: 0x00 Parallel SCSI
Block Size: 0 bytes/sector
Total Blocks: 0 sectors/disk
Reserved Blocks: 1088 reserved sectors/disk
SCSI Inquiry Bits: 0x00
Stamped for M&P: yes
Last Failure Reason: 0x07 (Drive timeout)
Phys Drive Flags: 0x00 0x20 0x00 0x00
Narrow SCSI transfers Enabled
Asynchronous SCSI Enabled
Configured as part of Logical Drive
SCSI LUN: 0
Spi Speed Rules: 0x00800000
Physical Connector: J1 (controller connector attached to drive)
Physical Box on Bus: 0xFF (unknown)
Physical Bay in Box: 0xFF (unknown)
Occasional Advisor

Re: Magical non-existent drive in Array Configuration Utility

This looks promising. I will have a look into this also and leet you guys know how I get on:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1223547335896+28353475&threadId=964494
Occasional Advisor

Re: Magical non-existent drive in Array Configuration Utility

PLEASE NOTE: My apologies, in my previous post I referred to the failed ID as ID5, whereas I meant to say ID3.

Just had the chance to visit the customer site. Had a look in the boot time array config utility, and it contained nothing of any use.

I then used the information I linked to in my last post, involving jumper settings. To recap: the server thinks I need to replace a failed drive on ID3, and when the failed drive is swapped out it comes up as ID1, which it won't accept. I statically set the drive to ID3 on the jumpers on the drive, and now what happens is during the boot process - while it is building the array - it recognizes a drive in ID3 (ie the green arrow starts to flash) but then errors out (the red crossed-out drive light comes on).

Go into the boot time ACU, and it shows that there as being a drive at ID3, but it shows as failed.

At this point the server won't boot as it appears to try and boot from the fresh drive, reporting that it can't find the Windows files (it comes up with the repair Windows installation prompt). If I take the drive out, boot into Windows, then insert the disk, the Windows ADU shows there to be an error at ID3.

What is more bizaare is if I go into Device Manager, under the SCSI Raid adapter, it shows each time I add the drive as an event - but it shows the drive at ID1, not ID3...

Any other suggestions or links would be massively appreciated. Thanks for the help so far, guys.

Marcus: sorry, but I can't see the option to boot into the RAID card, unless it's the F8 > ACU you are referring to, or is there something else?
New Member

Re: Magical non-existent drive in Array Configuration Utility

Hiya,

I have a related issue, but unfortunately no new light to shed on the OP's problem - I just can't get into the raid controller at boot either. Is there a keyboard shortcut or something? BIOS utilities yes, ILO, stuff like that - but nothing for the RAID config.

Thoughts?
Frequent Advisor

Re: Magical non-existent drive in Array Configuration Utility

I think its Ctrl+R or Ctrl+M cant remember
BOFH since 1999
Occasional Advisor

Re: Magical non-existent drive in Array Configuration Utility

HexworksAndrew,

Did you have any luck with accessing the array controller? I've not had a chance to get back on site to try it.

Cheers,
David