HP3000-L Archives

April 2009, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Hawkins, Jim (ESS TCE Q&W)" <[log in to unmask]>
Reply To:
Hawkins, Jim (ESS TCE Q&W)
Date:
Fri, 1 May 2009 01:11:10 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
18 GB & support for ST318416N

Paul wrote:
Always look in the IODFAULT.PUB.SYS file for which drives are supported on
your release. If there is an entry for the ST318416N drive under the SE and
18gb area, then you should be able to use it. As has been pointed out you
will waste 14gb if you use it as LDEV 1. Release 7.5 removed that
restriction.   

David Wrote:
I don't think the ST318416N is specifically supported.  18 Gb drives are
supported on 5.5 PowerPatch 5, so the drive will probably work without
problems even though it may not be "supported" by HP.

Paul & David are both on the right track.

Minor quibble, my sources say 5.5 PPT7 for first 18GB but won't argue PP5 vs. PP7

Really from an MPE disk volume software level any release after 4.0 will configure stuff from 4.0 to 512 GB but you'll need "Large Disk" patches (7.x only) to make decent use of anything over 72GB; 7.5 for >4GB LDEV1.  From driver software standpoint larger and later gen devices do require patches so best approached by getting to 6.5 or 7.x with "top of path tree" patches. 

Checking IODFAULT is a good enough for officially supported devices. 

What about non-supported, unlisted devices?   Best approached on 7.X.   For those with HP support IIRC there was a "generic device" patch which may have made it out of the Bangalore lab into BT status?   It attempted to smooth over a number of "bad device" behaviors we'd seen over the years (& typically requested a firmware change) PLUS one or two changes SCSI function returns which are part of the specification but HP device firmware didn't typically use. 

My opinions and not that of my employer, no guarantees on accuracy of data as I am a human being,

Jim 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2