Disk mounts only in write-locked mode

Why does this disk mount only write-locked? Not a major problem -- we are replacing this disk anyway. I'm just curious as to why I can't mount it write-enabled? Even with MOUNT/WRITE it comes up write-locked. It is an RZ26L inside a MicroVAX 3100 Model 80 running VMS v6.1. The disk is bad with unreadable portions as shown below. I discovered this during a disk to disk BACKUP/IMAGE/VERIFY to this disk and the verification pass showed numerous errors (sorry, I don't still have the actual BACKUP verification error messages). Yes, it was the system disk as source but the errors showed up in a static application .EXE file. So the disk is going bad. But why does VMS insist on mounting it write-locked? Just curious. $ SH SYM MOUNT MOU*NT == "MOUNT/NOASSIST" $ $ SH DEV D Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt ABCDEF$DKA200: Mounted 0 OPENVMS061 992142 330 1 ABCDEF$DKA300: Online 4 $ MOUNT DKA300 DATA1 %MOUNT-I-WRITELOCK, volume is write locked %MOUNT-I-MOUNTED, DATA1 mounted on _ABCDEF$DKA300: $ SH DEV DKA300/FULL Disk ABCDEF$DKA300:, device type RZ26L, is online, allocated, deallocate on dismount, mounted, software write-locked, file-oriented device, shareable, error logging is enabled. Error count 4 Operations completed 730 Owner process "_NTA1:" Owner UIC [SYSTEM] Owner process ID 000004A1 Dev Prot S:RWPL,O:RWPL,G:R,W Reference count 2 Default buffer size 512 Total blocks 2050860 Sectors per track 83 Total cylinders 3089 Tracks per cylinder 8 Volume label "DATA1" Relative volume number 0 Cluster size 9 Transaction count 1 Free blocks 994500 Maximum files allowed 205086 Extend quantity 5 Mount count 1 Mount status Process Cache name "_ABCDEF$DKA200:XQPCACHE" Extent cache size 64 Maximum blocks in extent cache 99450 File ID cache size 64 Blocks currently in extent cache 0 Quota cache size 0 Maximum buffers in FCP cache 458 Volume owner UIC [SYSTEM] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD Volume status: subject to mount verification, file high-water marking, write- back caching enabled. ! [Sorry about the wrap on this SH DEV/FULL output.] ! $ SH DEV D Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt ABCDEF$DKA200: Mounted 0 OPENVMS061 992142 329 1 ABCDEF$DKA300: Mounted alloc 4 DATA1 994500 1 1 wrtlck $ DIR DKA300:[VMS$COMMON.SYSMSG] %DIRECT-E-OPENIN, error opening DKA300:[VMS$COMMON.SYSMSG]*.*;* as input -RMS-E-FND, ACP file or directory lookup failed -SYSTEM-F-PARITY, parity error $ These are sample error entries from during the BACKUP/IMAGE/VERIFY operation: ******************************* ENTRY 1736. ******************************* ERROR SEQUENCE 7990. LOGGED ON: SID 12000003 DATE/TIME 30-APR-2004 19:05:33.97 SYS_TYPE 04010001 SYSTEM UPTIME: 0 DAYS 00:00:30 SCS NODE: ABCDEF VAX/VMS V6.1 DEVICE ERROR KA47 CPU FW REV# 3. CONSOLE FW REV# 0.1 RZ26L SUB-SYSTEM, UNIT _ABCDEF$DKA200:, CURRENT LABEL "OPENVMS061" HW REVISION 44323434 HW REVISION = 442D ERROR TYPE 05 EXTENDED SENSE DATA RECEIVED SCSI ID 02 SCSI ID = 2. SCSI LUN 00 SCSI LUN = 0. SCSI SUBLUN 00 SCSI SUBLUN = 0. PORT STATUS 00000001 %SYSTEM-S-NORMAL, NORMAL SUCCESSFUL COMPLETION SCSI CMD 1B671508 0001 READ SCSI STATUS FF NO STATUS RECEIVED UCB$B_ERTCNT 19 25. RETRIES REMAINING UCB$B_ERTMAX 27 39. RETRIES ALLOWABLE ORB$L_OWNER 00010004 OWNER UIC [001,004] UCB$L_CHAR 1C4D4008 DIRECTORY STRUCTURED FILE ORIENTED SHARABLE AVAILABLE MOUNTED ERROR LOGGING CAPABLE OF INPUT CAPABLE OF OUTPUT RANDOM ACCESS UCB$W_STS 0000 UCB$L_OPCNT 000005D9 1497. QIO'S THIS UNIT UCB$W_ERRCNT 0001 1. ERRORS THIS UNIT IRP$W_BCNT 0200 TRANSFER SIZE 512. BYTE(S) IRP$W_BOFF 0000 TRANSFER PAGE ALIGNED IRP$L_PID 00010009 REQUESTOR "PID" V A X / V M S SYSTEM ERROR REPORT COMPILED 4-MAY-2004 18:08:14 PAGE 3. IRP$Q_IOSB 008A4E35 00000000 IOSB, 138. BYTE(S) TRANSFERRED V A X / V M S SYSTEM ERROR REPORT COMPILED 4-MAY-2004 18:08:14 PAGE 4. ******************************* ENTRY 1737. ******************************* ERROR SEQUENCE 7991. LOGGED ON: SID 12000003 DATE/TIME 30-APR-2004 19:05:34.70 SYS_TYPE 04010001 SYSTEM UPTIME: 0 DAYS 00:00:31 SCS NODE: ABCDEF VAX/VMS V6.1 DEVICE ERROR KA47 CPU FW REV# 3. CONSOLE FW REV# 0.1 RZ26L SUB-SYSTEM, UNIT _ABCDEF$DKA200:, CURRENT LABEL "OPENVMS061" HW REVISION 44323434 HW REVISION = 442D ERROR TYPE 07 REASSIGN BLOCK SCSI ID 02 SCSI ID = 2. SCSI LUN 00 SCSI LUN = 0. SCSI SUBLUN 00 SCSI SUBLUN = 0. PORT STATUS 00000001 %SYSTEM-S-NORMAL, NORMAL SUCCESSFUL COMPLETION SCSI CMD 00000007 0000 REASSIGN BLOCKS SCSI STATUS FF NO STATUS RECEIVED REASSIGN BLOCK DATA 414F1500 DEFECT LOGICAL BLK ADDR = 00154F41(X) UCB$B_ERTCNT 19 25. RETRIES REMAINING UCB$B_ERTMAX 27 39. RETRIES ALLOWABLE ORB$L_OWNER 00010004 OWNER UIC [001,004] UCB$L_CHAR 1C4D4008 DIRECTORY STRUCTURED FILE ORIENTED SHARABLE AVAILABLE MOUNTED ERROR LOGGING CAPABLE OF INPUT CAPABLE OF OUTPUT RANDOM ACCESS UCB$W_STS 0000 UCB$L_OPCNT 000005E4 1508. QIO'S THIS UNIT UCB$W_ERRCNT 0002 2. ERRORS THIS UNIT IRP$W_BCNT 0200 TRANSFER SIZE 512. BYTE(S) V A X / V M S SYSTEM ERROR REPORT COMPILED 4-MAY-2004 18:08:14 PAGE 5. IRP$W_BOFF 0000 TRANSFER PAGE ALIGNED IRP$L_PID 00010009 REQUESTOR "PID" IRP$Q_IOSB 008A4E35 00000000 IOSB, 138. BYTE(S) TRANSFERRED followed by numerous EXTENDED SENSE DATA EXTENDED SENSE 000300F0 0AA9FD0F 00000000 00030011 0000 MEDIUM ERROR UNRECOVERED READ ERROR messages. [end of post]

In article <b096a4ee.0405041039.6c9111df@posting.google.com>, spamsink2001@yahoo.com (Alan E. Feldman) writes: :Why does this disk mount only write-locked? Not a major problem -- we :are replacing this disk anyway. I'm just curious as to why I can't :mount it write-enabled? Even with MOUNT/WRITE it comes up :write-locked. I'm mildly surprised there were no other messages during the mount (though the V6.1 SCSI driver stack and the supporting code is hugely ancient, and pre-dates extensive SCSI work in V6.2 and numerous SCSI updates and SCSI improvements made in subsequent OpenVMS releases), but OpenVMS can and does occasionally bring a volume on-line when it cannot access certain of the disk structures, or when the responses back from the disk are unexpected. :So the disk is going bad. But why does VMS insist on mounting it :write-locked? Just curious. Bad hardware causes weird software behavour. This is why constructs such as RAID, volume shadowing, and (if you think about it) lock-step hardware all exist. Those block re-assigns are ranges of blocks "going away", and being replaced with spares. For some related bad block processing details, see Ask The Wizard topic (6926). Since you are at an OpenVMS VAX V6 release, I'd tend to encourage an upgrade to a supported or more current release, such as V7.3. (V7.0 was not a major release on OpenVMS VAX, unlike V7.0 on OpenVMS Alpha.) ---------------------------- #include <rtfaq.h> ----------------------------- For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq --------------------------- pure personal opinion --------------------------- Hoff (Stephen) Hoffman OpenVMS Engineering hoff[at]hp.com

"Alan E. Feldman" wrote: > > Why does this disk mount only write-locked? Not a major problem -- we > are replacing this disk anyway. I'm just curious as to why I can't > mount it write-enabled? Even with MOUNT/WRITE it comes up > write-locked. > .... > $ SH DEV D > > Device Device Error Volume Free > Trans Mnt > Name Status Count Label Blocks > Count Cnt > ABCDEF$DKA200: Mounted 0 OPENVMS061 992142 > 330 1 > ABCDEF$DKA300: Online 4 > $ MOUNT DKA300 DATA1 > %MOUNT-I-WRITELOCK, volume is write locked > %MOUNT-I-MOUNTED, DATA1 mounted on _ABCDEF$DKA300: .... I've seen this before, and it is usually due to hardware errors. (Note error count). I would back it up NOW and I'd also tend to use BACKUP/PHYSICAL (for recovery to an identical replacement) if there is anything on there you want to recover. The error log most likely contains extended sense errors, which could only be properly decoded by reviewing manufacturers data. Despite what Hoff says, I like the way VMS deals with the situation, because it's not causing any "further damage" to the device yet making it (hopefully) available. -- Regards, Nic Clews a.k.a. Mr. CP Charges, CSC Computer Sciences nclews at csc dot com

Similiar Articles:

booting solaris in single user mode with root filesystems read ...
... Solaris 10 on a SunFIRE 280R not to mount its fileystems rw in single user mode ... system was coming up in read only mode. I had ... filesystem before it remounts read-write ...

snapshot error: File system could not be write locked - comp.unix ...
I assumed that I >could mount / with logging ... >The only problem here is that it's working ... error: File system could not be write locked - comp.unix ... On the new disk I just ...

Inconsistent UFS Filesystem after DiskSuite write error on ...
SDS reports that there is a write error on the disk and that the disk needs maintenance. What I can=B4t understand is why the ufs filesystem /data (with mount option ...

ufsdump root without /var or /usr - comp.unix.solaris
Otherwise, pre-create /var and /usr mount ... you could use exclude files to tar up only ... what are my options for disk cleanup? boot to single user mode and delete /var ...

Odd BACKUP error: unsupported file structure ! - comp.os.vms ...
It is documented that MOUNT will ... So I decided to backup the disk and restore it to make it "clean". It is only in ... on dismount, mounted, software write-locked ...

fastest way to copy a disk - comp.unix.solaris
... start up in single user mode (Before shutting down, modify /etc/vfstab to only ... For the disk merging, I will simply mount the old devices ... You would have to write some ...

ufsdump on remote tape drive. - comp.unix.solaris
... the file sytems other > than root and mount them in Read Only mode. Then ... If you do not want to actually load a new disk, than at least run ufsrestore in interactive mode ...

LVM Problems - HP UX 10.10 10.20 11.00 - comp.sys.hp.hpux ...
- I'm able to mount the disk but I do not see any data on ... Booting an LVM system in maintenance mode Marc ... --> The problem is that I do have only one of the 2 disk working, the ...

Issue: Adding new disk from SAN (EMC) to Solaris 10 OS - comp.sys ...
If disk from SAN added correctly, will it change "sd.conf" file automatically? ... snapshot error: File system could not be write locked - comp.unix ... I should add that we ...

meta device sys rebuild - comp.sys.sun.admin
Each server has a primary boot and a mirror boot disk ... rebuild - comp.sys.sun.admin how to remove a stale mount ... CDROM drive in single user mode - comp.unix.solaris ...

comp.os.vms: Disk mounts only in write-locked mode
Disk mounts only in write-locked mode. From: Alan E. Feldman (spamsink2001_at_yahoo.com) Date: 05/04/04 Next message: Tom Linden: "RE: Print HTML files directly from VMS"

Mount a trashed hard drive using Target Disk mode - Mac OS X Hints
Mount the iBook disk in read-only mode by typing: ... at the repair centre to WRITE DOWN that you wiped the disk. ... up to a G4 ibook in Target Disk Mode, only ...

7/25/2012 7:44:27 PM