Thanks to all who replied to my previous posting (which follows below my
signature lines here). There were 8 responses to the posting, but
unfortunately I still haven't been able to install my new 18Gb Quantum
drive. With your kind advice, I think I am much closer to diagnosing if
not solving the problem. My best guess now is that I've got a hardware
problem (of some sort). I'm ready to send the disks back and get
something else, but I would appreciate some additional feedback on these
diagnostics just to make sure I'm not missing something.
I have two of these Quantum disks and have tried the following
diagnostics on both with the same results:
___________________________________________________________
Thing 1: The main stumbling block is an inability for disklabel to write
to the disk. (Without a disklabel I cannot finish the disk installation
and partitioning):
# disklabel -W rz19
(this command returns successfully)
# disklabel -z rz19c
Disk is unlabeled or, /dev/rrz18c does not start at block 0 of the disk
# disklabel -rw rz19 rzxx
write: I/O error
___________________________________________________________
Thing 2: The utility diskx tells the same story as disklabel, a problem
writing to the disk:
# /usr/field/diskx -d -f /dev/rrz19c
DISKX - DEC OSF/1 Disk Exerciser.
Testing disk device /dev/rrz19c.
Fri Apr 9 14:22:33 1999
--------------------------------------------------
Disktab Testing
This test verifies the disklabel entry associated with this
disk device. The verification involves comparing the entry
returned by getdiskbyname(3x) to the entry dynamically
generated by creatediskbyname(3x).
This operating system release does not support the
creatediskbyname(3x) library routine. For this reason
it is not possible to perform the disklabel test.
--------------------------------------------------
Fri Apr 9 14:22:33 1999
Disk exercising completed.
# /usr/field/diskx -w -f /dev/rrz19c
DISKX - DEC OSF/1 Disk Exerciser.
Testing disk device /dev/rrz19c.
Fri Apr 9 14:24:00 1999
--------------------------------------------------
Write Transfer Testing
This test verifies that writes will succeed. The data is first
written to disk. After all writes have completed the data will be
read back for validation. Since this test writes to the disk
there is potential for file system corruption if a file system
exists on the disk that is being tested.
Writes will be done using random size transfers. The write
size will be randomly selected from the range 512 to 65536 bytes.
Writes will be issued to random locations on the disk. To accomplish
this
a seek will be issued before each write to force a write of a different
disk region.
Testing will continue until an interrupt signal is received.
part_overlap: DIOCGDINFO failed
Aborting this test due to failure in obtaining
partition layout (disk label) from /dev/rrz18c.
___________________________________________________________
Thing 3: Strangely it seems like I can write directly to the disks using
dd:
# dd if=/dev/rrz19c of=/dev/null
35566499+0 records in
35566499+0 records out
___________________________________________________________
Thing 4: The output from scu is:
# scu -f /dev/rrz19c
Warning: Inquiry (QM318000TD-SCA) and system (QM318000) device names are
different.
scu> verify media
Verifying 35566499 blocks (0 - 35566498) on /dev/rrz18c
(QM318000TD-SCA), please be patient...
scu>
___________________________________________________________
Thing 5: I checked for real hardware errors with uerf (I don't have
DECevent on my machine) and found MANY. Here are two samples:
# uerf -R -o full
********************************* ENTRY 1.
*********************************
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 41.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Fri Apr 9 13:52:44 1999
OCCURRED ON SYSTEM swell
SYSTEM ID x0007001E
SYSTYPE x00000000
----- UNIT INFORMATION -----
CLASS x0000 DISK
SUBSYSTEM x0000 DISK
BUS # x0002
x0080 LUN x0
TARGET x0
----- CAM STRING -----
ROUTINE NAME cdisk_check_sense
----- CAM STRING -----
Device aborted command
----- CAM STRING -----
ERROR TYPE Hard Error Detected
----- CAM STRING -----
DEVICE NAME DEC RZ1DB-BA (C)
DEC.RZ1DB-BA (
----- CAM STRING -----
Active CCB at time of error
----- CAM STRING -----
CCB request completed with an error
ERROR - os_std, os_type = 11, std_type = 10
----- ENT_CCB_SCSIIO -----
*MY ADDR x1FE40380
CCB LENGTH x00C0
FUNC CODE x01
CAM_STATUS x0084 CAM_REQ_CMP_ERR
AUTOSNS_VALID
PATH ID 2.
TARGET ID 0.
TARGET LUN 0.
CAM FLAGS x00000482
CAM_QUEUE_ENABLE
CAM_DIR_OUT
CAM_SIM_QFRZDIS
*PDRV_PTR x1FE40028
*NEXT_CCB x00000000
*REQ_MAP x00F886E0
VOID (*CAM_CBFCNP)() x0053C8F8
*DATA_PTR x9F9D6000
DXFER_LEN x00002000
*SENSE_PTR x1FE40050
SENSE_LEN x40
CDB_LEN x06
SGLIST_CNT x0000
CAM_SCSI_STATUS x0002 SCSI_STAT_CHECK_CONDITION
SENSE_RESID x2E
RESID x00002000
CAM_CDB_IO x000000000000001030D3000A
CAM_TIMEOUT x0000003C
MSGB_LEN x0000
VU_FLAGS x0000
TAG_ACTION x20
----- CAM STRING -----
Error, exception, or abnormal_condition
----- CAM STRING -----
ABORTED COMMAND - Target aborted_command
----- ENT_SENSE_DATA -----
ERROR CODE x0070 CODE x70
SEGMENT x00
SENSE KEY x000B ABORTED CMD
INFO BYTE 3 x00
INFO BYTE 2 x00
INFO BYTE 1 xD3
INFO BYTE 0 x3F
ADDITION LEN x0A
CMD SPECIFIC 3 x00
CMD SPECIFIC 2 x00
CMD SPECIFIC 1 x00
CMD SPECIFIC 0 x00
ASC x47
ASQ x00
FRU x00
SENSE SPECIFIC x000000
ADDITIONAL SENSE
0000: 00000000 00000000 00000000 00000000 *................*
0010: 00000000 00000000 00000000 00000000 *................*
0020: 00000000 00000000 00000000 00000000 *................*
0030: 7E250000 00005E3C 00000000 00000000 *..%~<^..........*
****************** ENTRY 2. *********************************
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 40.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Fri Apr 9 11:03:33 1999
OCCURRED ON SYSTEM swell
SYSTEM ID x0007001E
SYSTYPE x00000000
----- UNIT INFORMATION -----
CLASS x0000 DISK
SUBSYSTEM x0000 DISK
BUS # x0002
x0090 LUN x0
TARGET x3
----- CAM STRING -----
ROUTINE NAME cdisk_complete
----- CAM STRING -----
Retries Exhausted
----- CAM STRING -----
ERROR TYPE Hard Error Detected
----- CAM STRING -----
DEVICE NAME QUANTUM QM318000TD-SCA .QM318000TD
----- CAM STRING -----
Active CCB at time of error
----- CAM STRING -----
CCB request completed with an error
ERROR - os_std, os_type = 11, std_type = 10
----- ENT_CCB_SCSIIO -----
*MY ADDR x1FE3F100
CCB LENGTH x00C0
FUNC CODE x01
CAM_STATUS x0084 CAM_REQ_CMP_ERR
AUTOSNS_VALID
PATH ID 2.
TARGET ID 3.
TARGET LUN 0.
CAM FLAGS x00000482
CAM_QUEUE_ENABLE
CAM_DIR_OUT
CAM_SIM_QFRZDIS
*PDRV_PTR x1FE3EDA8
*NEXT_CCB x00000000
*REQ_MAP x1FE09400
VOID (*CAM_CBFCNP)() x0053C8F8
*DATA_PTR x40004490
DXFER_LEN x00002000
*SENSE_PTR x1FE3EDD0
SENSE_LEN x40
CDB_LEN x06
SGLIST_CNT x0000
CAM_SCSI_STATUS x0002 SCSI_STAT_CHECK_CONDITION
SENSE_RESID x2E
RESID x00002000
CAM_CDB_IO x00000000000000100000000A
CAM_TIMEOUT x0000003C
MSGB_LEN x0000
VU_FLAGS x4000
TAG_ACTION x20
----- CAM STRING -----
Error, exception, or abnormal
_condition
----- CAM STRING -----
ABORTED COMMAND - Target aborted
_command
----- ENT_SENSE_DATA -----
ERROR CODE x0070 CODE x70
SEGMENT x00
SENSE KEY x000B ABORTED CMD
INFO BYTE 3 x00
INFO BYTE 2 x00
INFO BYTE 1 x00
INFO BYTE 0 x00
ADDITION LEN x0A
CMD SPECIFIC 3 x00
CMD SPECIFIC 2 x00
CMD SPECIFIC 1 x00
CMD SPECIFIC 0 x00
ASC x47
ASQ x00
FRU x00
SENSE SPECIFIC x000000
ADDITIONAL SENSE
0000: 00000000 00000000 00000000 00000000 *................*
0010: 00000000 00000000 00000000 00000000 *................*
0020: 00000000 00000000 00000000 00000000 *................*
0030: 7E250000 00005E3C 00000000 00000000 *..%~<^..........*
___________________________________________________________
Thing 6: The file command didn't seem to have any problems though Š
# file /dev/rrz18a
/dev/rrz18a: character special (8/34816)
SCSI #2 QM318000 disk #144 (SCSI ID#3) (SCSI LUN #0)
errors = 0/52
___________________________________________________________
___________________________________________________________
So it seems I have a mixed bag of results. On the one hand I can write
directly to the disk with dd, but on the other hand disklabel and uerf
tell me I have problems. I'm afraid that I'm too feeble to put the
pieces of this puzzle together and I would appreciate any help you could
offer. In sum, my questions are:
A. What is the problem with these disks?
B. What do the messages from uerf mean (they're a bit cryptic to me)?
C. Am I missing something in the installation?
D. Any specific recommendations on 18GB disks that people have used on
their machines and know will work (I'll try to exchange what I've got
for one of these.)
Thanks so much,
Jim
________________________________________________________________
Jim Hench
UNC Institute of Marine Sciences tel: (252) 726-6841 ext.162
3431 Arendell Street fax: (252) 726-2426
Morehead City, NC 28557 email: hench_at_marine.unc.edu
________________________________________________________________
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
original message follows below Š
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I'm having some trouble installing a new disk for our Digital PWS 500au.
The disk in question goes into an 80-pin slot in an Andataco tower which
is attached via SCSI directly to the CPU. The tower presently has
another 21Gb Seagate in it which runs fine. The new disk is a Quantum
QM318200-SCA, an 18.2 Gb SCSI. We're running Digital Unix 4.0c.
So here's my sad installation tale:
!. Shutdown the system and power the CPU and disktower down. Stuff the
new disk into a free slot and power up the tower and then the CPU up. So
far so good.
2. Now run: # /sbin/scu show edt
and get:
device QM318000TD-SCA
bus: 2
target: 3
So using the rule: bus*8 + target = 2*8 + 3 = 19
Which implies the new disk is rz19
3. Next, # /dev/MAKEDEV rz19
4. Rebuild kernal, doconfig -e MY_HOST_NAME
and moving the new kernal to the acitve kernal location /vmunix
and reboot, # /sbin/reboot
so far, so good.
5. Next, I go the the Disk Configuration widget within the CDE and set
the disk
up as one 18Gb partition (c) using a 4.2 BSD file system. [This is
the same setup
I've got for the existing 21Gb Seagate.]
6. Here's where I get stuck. Upon commiting to the disk setup, I get an
error message
stating that, "disklabel failed to write label"
7. Here is the output of: # disklabel -p rz19c
type: SCSI
disk: QM318000
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 228
tracks/cylinder: 20
sectors/cylinder: 4560
cylinders: 8057
sectors/unit: 35566499
rpm: 7200
interleave: 1
trackskew: 27
cylinderskew: 47
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg]
a: 131072 0 unused 0 0 # (Cyl. 0 -
28*)
b: 262144 131072 unused 0 0 # (Cyl. 28*-
86*)
c: 35566499 0 unused 0 0 # (Cyl. 0 -
7799*)
d: 0 0 unused 0 0 # (Cyl. 0 -
-1)
e: 0 0 unused 0 0 # (Cyl. 0 -
-1)
f: 0 0 unused 0 0 # (Cyl. 0 -
-1)
g: 17586641 393216 unused 0 0 # (Cyl. 86*-
3942*)
h: 17586642 17979857 unused 0 0 # (Cyl. 3942*-
7799*)
8. This disk appears to be too new to appear in my disktab table. I
tried to get
this info using: # disklabel -rw /dev/rrz19c unknown
But the result was: "write: I/O error"
I also tried: # newfs /dev/rrz19c /dev/rrz19c
But the result was: Error: the disklabel for /dev/rrz19c does not
exist
or it is corrupted
9. The disktab entries in Digital Unix 4.0d are identical to the ones I
have
in 4.0c, so upgrading to the more recent OS doesn't appear to be the
fix here.
10. Soooo ... at this point it appears the system can see the new disk
on
the SCSI chain, but cannot put a "disklabel" on it, which is
apparently
a prerequisite for going any further with the installation.
My questions are:
A. Is this particular Quantum disk compatible with Digital Unix 4.0c?
B. If it is compatible, what am I doing wrong, and what should I do to
get this puppy to work?
C. If this disk will not work, why not, and is there a comparable
18Gb disk that does work that I should exchange the my present
disk for?
Thanks muchly,
- Jim
Received on Mon Apr 12 1999 - 19:57:03 NZST