[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference star::wizards

Title: "ASK THE WIZARDS"
Moderator:QUARK::LIONEL
Created:Mon Oct 30 1995
Last Modified:Mon May 12 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1857
Total number of notes:3728

1523.0. "Open: source of error messages?" by STAR::JKEENAN () Tue Feb 11 1997 08:16

Return-Path: "VMS001::WWW"@vms001.das-x.dec.com
Received: by vmsmkt.zko.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX);
	Tue, 4 Feb 1997 11:24:30 -0500
Received: from vms001 by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV)
	id LAA11077; Tue, 4 Feb 1997 11:16:13 -0500 (EST)
Date: Tue, 4 Feb 1997 11:16:37 -0500
Message-Id: <[email protected]>
From: "VMS001::WWW"@vms001.das-x.dec.com (04-Feb-1997 1116)
To: [email protected], [email protected], [email protected]
Subject: Ask the Wizard: '[email protected]'
X-VMS-To: [email protected]

Remote Host: (null)
Browser Type: Mozilla/3.0 (Win95; I)
Remote Info: <null>
Name: Reginald Tole
Email Address: [email protected]
CPU Architecture: VAX and Alpha
Version: v 6.1
Questions: 

Have been getting error message bootstrap failure when trying to perform the standalone backup. 
What could have failed to cause this ?

Could not perform backup. Getting error message "fatal drive error: backup/lo/ignore=interlock/rewind dsk1:[file*.*]etpo:daly00.bck.
Have tried using new tapes and this hasn't appeared again. What is the possible cause of this error ?

Have been using cassette tapes spec. TLZ07.

Please assist.
T.RTitleUserPersonal
Name
DateLines
1523.1Contact Hardware Support If Problem PersistsXDELTA::HOFFMANSteve, OpenVMS EngineeringTue Feb 11 1997 09:4259
:Remote Host: (null)
:Browser Type: Mozilla/3.0 (Win95; I)
:Remote Info: <null>
:Name: Reginald Tole
:Email Address: [email protected]
:CPU Architecture: VAX and Alpha
:Version: v 6.1
:Questions: 

:Have been getting error message bootstrap failure when trying to perform
:the standalone backup.  What could have failed to cause this ?

  What is the bootstrap command, and what are the error(s) reported?

  OpenVMS Alpha V6.1 does not support standalone BACKUP, one uses
  the CD-ROM included in the distribution kit -- copies of the BACKUP
  CD-ROM are available for about US$12 -- or a bootstrap of a seperate
  copy of OpenVMS.

  OpenVMS VAX does (still) support standalone BACKUP.  Unlike OpenVMS
  Alpha, the use of standalone BACKUP means that access to DCL and
  file-level BACKUPs and restorations, as well as specific repairs
  to the target system disk that might be needed, are not available.

  Without the error messages and without the platform, it is difficult
  to determine the particular problem bootstrapping.

:Could not perform backup. Getting error message "fatal drive error:
:backup/lo/ignore=interlock/rewind dsk1:[file*.*]etpo:daly00.bck.

  The /IGNORE=INTERLOCK qualifier -- a qualifier that tells backup
  to attempt to copy the data, regardless of the potential for data
  consistency and validity problems -- is not necessary for a
  standalone BACKUP, as there is implicitly no file access conflict
  possible when standalone BACKUP is running.  A file-level BACKUP
  is not permissable under standalone BACKUP.

  If this command was used under on-line BACKUP -- which is much more
  likely, as I'd expect standalone BACKUP would not accept the command
  as shown -- then one can look in the system error log for information
  on the tape error.  This information can be decoded by your hardware
  support organization.

:Have tried using new tapes and this hasn't appeared again. What is
:the possible cause of this error ?

  It is possible there is a bad tape cassette, or a transient problem
  with the tape drive.  Consider using the cleaning cassette -- one is
  usually provided with the drive, and cleaning cassettes are also
  available seperately -- if you have not already done so.

  The error log -- as mentioned -- will have more information on the
  reported fault.  (Assuming on-line BACKUP was used.)

:Have been using cassette tapes spec. TLZ07.

  If you wish to pursue this, please contact your hardware support
  organization.