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

Subject: error in disk

Original Message
Name: ajmal
Date: April 18, 2003 at 04:09:38 Pacific
Subject: error in disk
OS: vms
CPU/Ram: 3400
Comment:

basically two years before different users retrieve data from VAX.they retrieve data from following
disks..
1) D$6:[SABIR]

2) D$9:[SABIR]

now after two years when i use this command

$ show dveice D:
so the system can not show D$6:[sabir] and D$9:[sabir].
its means the disk are not attached with system????.
or some thing else???

the system shows only one disk that is

device name device status error
$2$dia1 mounted 0

plz tell me how i can access
D$:[sabir] and D$9:[sabir] ...both disk...from system



Report Offensive Message For Removal

Response Number 1
Name: ME
Date: April 18, 2003 at 17:45:26 Pacific
Subject: error in disk
Reply: (edit)
D$6 and D$9 are logical names for a disk, not a physical (hardware) name like $2$dia1
When you mount a disk with the MOUNT command you can add this second name. Using logical names, you can make your disknames independant from your hardware.

What worries me, is that you see only one disk. And I guess that that is a system disk, not one with user data. It could be, that both logical names would map to this same physical disk $2$DIA1, and that it is used for both system and user data. That would mean, that there is a directory [.SABIR] somewhere on that disk.

But another option would be, that you have a clustered system. And that by booting with VAXCLUSTER=0, you took this VAX out of the cluster.
When the user disks are connected to the other part of the cluster, it would explain why you don't see any more disks. It could also mean that you have to be very careful with what you're doing because doing the wrong things could be harmful to data on the disks.

Without knowing more about your configuration we can't help you much. Isn't there a system manager nearby to assist you ?


Report Offensive Follow Up For Removal

Response Number 2
Name: ajmal
Date: April 20, 2003 at 21:45:34 Pacific
Subject: error in disk
Reply: (edit)
basically when i boot vax from console
the systen will halt at this line..

%TMSCPLOAD-I-LOADINGTMSCP,LOADING THE TMSCP TAPE SERVER
so what i did,i use following commands at
SYSBOOT prompt.
SYSBOOT> SET TMSCP_LOAD 0
SET VAXCLUSTER 0
continue
now the system will not halt at any point.
and i got $ prompt.
now plz tell me what command i should use
to go ahead,
waiting for ur reply..
thaks
ajmal


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: error in disk

Comments:

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


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



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