Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Hard disk size Limit Open VMS 7.1

Original Message
Name: Nadeem Aziz
Date: October 10, 2007 at 04:08:51 Pacific
Subject: Hard disk size Limit Open VMS 7.1
OS: Win Xp Sp2
CPU/Ram: Celeron 2666 /256
Comment:
I tried to copy a running hardisk by standard backup commands to a 73 GB seagate SCSI harddisk . Although there were no errors , target hardisk failed to complete boot sequence . If i perform same operation on an older 9.1 GB compac harddisk i get proper working copy . Can anybody guide me how to use newer hardisks of 18 GB or 73 GB capacity to make a working backup of my DCS system harddisk .?

Report Offensive Message For Removal


Response Number 1
Name: SKStewart
Date: October 10, 2007 at 06:49:34 Pacific
Subject: Hard disk size Limit Open VMS 7.1
Reply: (edit)
Nadeem,

You may need to use a newer version of OpenVMS (current VAX version is 7.3-1, current Alpha/Integrity version is 8.4) or apply a patch ("ECO"). I found this in the OpenVMS FAQ:

"Some SCSI disks with capacities larger than 8.58 gigabytes (GB) will require the use of an OpenVMS ECO kit (eg: ALPSCSI04_062 or later) for new SCSI device drivers. Failure to use this ECO can cause "rounding errors" on the SCSI disk device capacity-OpenVMS will not use nor display the full capacity of the drive-and "%sysinit-e-error mounting system device status equals 000008C4" (8C4 -> "%SYSTEM-?-FILESTRUCT, unsupported file structure level") errors during bootstrap. One workaround for the bootstrap when the bitmap is located far into the disk is the use of INIT/INDEX=BEGIN.) The problem here involves the particular extensions and fields used for larger capacity disks within the SCSI specifications and within the various intepretations of same."

You could also try the workaround this hints at: Initialize the large disk before you run the backup with /INDEX=BEGIN; then, when you run the image backup, use the /NOINITIALIZE qualifier so backup will not relocate the index file.

Also note that there are some restrictions in the console ROMS of certain older systems.


Report Offensive Follow Up For Removal




Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Hard disk size Limit Open VMS 7.1

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




ZoneAlarm Question. Blocked Connect

Windows Live Messenger Problem

Delete $Uninstall after SP3 updates

help for hp compaq laptop

Seagate HD works only as slave...


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC