Disk $1$DUA1: (HSD000), device type (type not yet identified)

[Rob Kersey]

We have recently moved an OpenVms system 5.52h4 onto A pair of dual redundant HSD50's.

Controller:
HSD50-AX ZG83301912 Firmware V51D-3, Hardware A03
Configured for dual-redundancy with ZG71301258
In dual-redundant configuration
SCSI address 6
Time: 23-JAN-1993 21:52:08


From VMS all disk are presnted correctly and seem to be working fine.

However when you do a SHOW/DEVICE DUA2:/FULL
you get the following.

Disk $1$DUA2: (HSD001), device type (type not yet identified), is online,
mounted, file-oriented device, shareable, available to cluster, error
logging is enabled.

Error count 0 Operations completed 892
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWED,O:RWED,G:RWED,W:RWED
Reference count 1 Default buffer size 512
Total blocks 8218940 Sectors per track 85
Total cylinders 3022 Tracks per cylinder 32
Host name "HSD001" Host type, avail HSD5, yes
Alternate host name "HSD000" Alt. type, avail HSD5, yes
Allocation class 1

Volume label "DATA1" Relative volume number 0
Cluster size 8 Transaction count 1
Free blocks 8218464 Maximum files allowed 456607
Extend quantity 5 Mount count 1
Mount status System Cache name "_$1$DUA0:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 821846
File ID cache size 64 Blocks currently in extent cache 821816
Quota cache size 0 Maximum buffers in FCP cache 4590

Volume status: subject to mount verification, file high-water marking, write-
through caching enabled.

My only concern is that VMS is unable to identify the device type:

Disk $1$DUA1: (HSD000), device type (type not yet identified)

Does any one know why this is.

Under 7.1 vms shows these disc as below.

Disk $1$DUA12:, device type MSCP served SCSI disk array

Is this a 5.5-2H4 thing?

I know this gear is old and we should seriously consider upgrading our architecture.

However we are tied to 5.5-2H4 due to no source code for the application running on it.

We have inherrited this turd and are trying to polish it into a diamond.

[Ian Miller. · Accepted solution]

I think its a disk type that VMS V5.5-2 does not know but as long as it works whyworry. If its a non-priv app parhaps you could translate it using DECmigrate and run it on a current alpha?

[Jan van den Ende]

Rob,

Welcome to the VMS forum!

Since you don't indicate the machine type, nor the amount of memory, this advice COULD be too much to ask, but I would start to investigate to cure a 10+ years OS backlog.

Devices, when queried, identify themselves by returning a number.
The OS has tables which translate those numbers into descriptions.
That also allows to find all kind of other parameters.
VMS is resilient enough to accept unidentified devices, but then, of necessity, assumes them to have only minimal abilities.
Known devices with extra capabilities allows the OS to take advantage thereoff.

One limitation that will quickly strike you in modern times is the maximum disk size.
I am not really sure about the real amounts, but I thing V5.5 can only address 2 or maybe 4 GB per drive. The rest is simply not seen.

So, for various reasions, if you can, get to V6.2 the least, but preferably to V7.3.


hth


Jan

[Rob Kersey]

Jan.

Thanks.

Unfortunatley (as I said earlier in my posting) we have been given the 'challenge' of supporting this system from another company and are dreaming one day of having it running on Itanium on vms 8.1!! ;-)

Although I do find 5.5-2H4 a seminal release and one of my personal favourites.

What is your favourite?

As I said we do not have the source for the majority of the application so an upgrade is looking unlikely.

We are running 4000-108 which have 512 mb of Ram.

VMS -- "Live The Dream"

[Jan van den Ende]

Rob,

looks like your system could well 'pull' the load, so __I__ would make sure of a good backup and try for a V.7-3 upgrade.
Chances are way above average that your software WILL just run unmodified -- no guarantee though :-(

btw, Planning to move to Itanium?? Guess you should forget 8.1 and wait for 8.2 (due shortly), but..... if you do NOT have the sources, how do you figure THAT???

Jan

[Ian Miller.]

a move to itanium could be done with VEST then AEST to translate VAX-Alpha-Itanium.