Compatible drives for a DS2405?

[S. Allen Young]

This is a followup question to a previously closed thread:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1253228

The author of that thread reported output from the diskinfo command for a 146 Gb drive:

# diskinfo /dev/rdsk/c25t12d0
SCSI describe of /dev/rdsk/c25t12d0:
vendor: HP 0146G
product id: ST3146807FC
type: direct access
size: 143374744 Kbytes
bytes per sector: 512

Well I have a similar situation. DS2405 JBODs, HP rp4440, HP-UX 11.11.

I added some 146 Gb drives to my DS2405 enclosure and my diskinfo command is as follows:

# diskinfo -v /dev/rdsk/c4t14d0
SCSI describe of /dev/rdsk/c4t14d0:
vendor: HP 0146G
product id: ST3146807FC
type: direct access
size: 35566480 Kbytes
bytes per sector: 512
rev level: HP05
blocks per disk: 71132960
ISO version: 0
ECMA version: 0
ANSI version: 3
removable media: no
response format: 2

My system is seeing this drive as a 36 Gb drive, and not a 146 Gb drive. Additionally, LVM also sees this drive as as 36 Gb drive.

I have not rebooted the server since installing the drives. I did run vgscan -a, without removing /etc/lvmtab.

I have 73 Gb drives in this enclosure which are in production with no issues.

[Torsten.]

Was there another 36GB drive installed in the same slot? Maybe your system misses some patches.

Try "dd" and count the read blocks to check.

[Víctor Cespón]

Can you check that the disk is:

A7289A

A7289-69002 146GB 'hot swap' Fiber Channel (FC) hard drive module - 10,000 RPM

This is the list of compatible disks:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=lpg60161

[S. Allen Young]

I installed four 146 Gb drives, all show as 36 Gb drives and yes all four slots were previously occupied by 36 Gb drives.

The machine was last patched fully May 2009.

The four drives are all A7289A 146GB 10K FC HDD.

I ran #vgscan -a again, but this time I removed the /etc/lvmtab file so that it would be rebuilt. It did not help.

I will try the "dd" command and see how many blocks are available.

[Torsten.]

Did you use "rmsf" when the old drives were removed???

If not, please do so now and recreate the device files.

[S. Allen Young]

Thank you. I ran the follwoing commands:

# rmsf -av /dev/dsk/c4t3d0
rmsf: Removing special file /dev/dsk/c4t3d0
rmsf: Removing special file rdsk/c4t3d0

# rmsf -av /dev/dsk/c5t3d0
rmsf: Removing special file /dev/dsk/c5t3d0
rmsf: Removing special file rdsk/c5t3d0

# mksf -vH 0/2/1/0.8.0.255.0.3.0
making dsk/c4t3d0 b 31 0x043000
# mksf -vrH 0/2/1/0.8.0.255.0.3.0
making rdsk/c4t3d0 c 188 0x043000
# mksf -vH 0/6/1/0.8.0.255.0.3.0
making dsk/c5t3d0 b 31 0x053000
# mksf -vrH 0/6/1/0.8.0.255.0.3.0
making rdsk/c5t3d0 c 188 0x053000

# diskinfo -v /dev/rdsk/c4t3d0
SCSI describe of /dev/rdsk/c4t3d0:
vendor: HP 0146G
product id: ST3146807FC
type: direct access
size: 35566480 Kbytes
bytes per sector: 512
rev level: HP05
blocks per disk: 71132960
ISO version: 0
ECMA version: 0
ANSI version: 3
removable media: no
response format: 2

Still showing as a 36 Gb drive.

[S. Allen Young]

Interesting...if I view this drive in Support Tools Manager it shows as the correct size:

-- Information Tool Log for SCSI Disk on path 0/2/1/0.8.0.255.0.3.0 --

Log creation time: Tue May 25 14:12:43 2010

Hardware path: 0/2/1/0.8.0.255.0.3.0


Product Id: ST3146807FC Vendor: HP 0146G
Device Type: SCSI Disk Firmware Rev: HP05
Device Qualifier: HP0146GST3146807FC Logical Unit: 0
Serial Number: 3HY129N2
Capacity (M Byte): 140014.41
Block Size: 512
Max Block Address: 286749487
Smart Enabled: TRUE
Error Logs
Read Errors: 0 Buffer Overruns: N/A
Read Reverse Errors: N/A Buffer Underruns: N/A
Write Errors: 0 Non-Medium Errors: 96
Verify Errors: 0

But LVM and the diskinfo command show 36 Gb.

[Torsten.]

Patches? Patches!

I remember several patches for "diskinfo" in the past.

[S. Allen Young]

I found one patch for diskinfo...PHCO_27618

But I already have it on the machine. Perhaps there are more.

[S. Allen Young]

I applied all of the current patches and rebooted the machine. One of those things fixed my problem. I am guessing rebooting the machine was the key, as the machine was not very far behind on patches.

[S. Allen Young]

I applied all of the current patches and rebooted the machine. One of those things fixed my problem. I am guessing rebooting the machine was the key, as the machine was not very far behind on patches.