I wrote:
>Hello all,
>I have a disk problem. The setting is as follows: AlphaStation 200, dU 3.2C,
>KZPAA SCSI-PCI card and a StorageWorks shelf. In the SW shelf there were
>already three disks that behaved OK, I decided to slot in two more RZ29B-VA
>while I was at it. I created the devices, and powercycled to make sure
>everything was coming up (do I really need to do that?). Now the problem is I
>cannot make an advfs domain on those new disks; dxadvfs doesn't recognize
>them, and if I try to do it by hand with mkfdmn, the computer hangs and
>eventually got tunnel vision (I never saw a computer *faint* before, this one
>did). I should mention that it works perfectly fine to make ufs file systems
>on the disk, mount, write and read.
>Earlier, I had a problem with the KZPAA card that it and the disks would show
>up at console level, but not after bootup. That was cured, for unknown
reason,
>but still, after upgrading firmware and upgrading to dU 3.2C.
>Looking into the uerf-log I find this event related to the disk I was
>toying with (I don't know if it is of any relevance):
>********************************* ENTRY 3. *******************************
*
>*
>----- EVENT INFORMATION -----
>EVENT CLASS ERROR EVENT
>OS EVENT TYPE 199. CAM SCSI
>SEQUENCE NUMBER 429.
>OPERATING SYSTEM DEC OSF/1
>OCCURRED/LOGGED ON Tue Oct 24 20:28:03 1995
>OCCURRED ON SYSTEM sysman
>SYSTEM ID x0002000D CPU TYPE: DEC 7000
>SYSTYPE x00000000
>----- UNIT INFORMATION -----
>CLASS x0000 DISK
>SUBSYSTEM x0000 DISK
>BUS # x0001
> x0040 LUN x0
> TARGET x0
>
>----- CAM STRING -----
>ROUTINE NAME cdisk_complete
>----- CAM STRING -----
> Retries Exhausted
>----- CAM STRING -----
>ERROR TYPE Hard Error Detected
>----- CAM STRING -----
>DEVICE NAME DEC RZ29B
>----- CAM STRING -----
> Active CCB at time of error
>----- CAM STRING -----
> Bus phase sequence failure
>ERROR - os_std, os_type = 11, std_type = 10
>----- ENT_CCB_SCSIIO -----
>*MY ADDR x03FFC728
>CCB LENGTH x00C0
>FUNC CODE x01
>CAM_STATUS x0014 CAM_SEQUENCE_FAIL
>PATH ID 1.
>TARGET ID 0.
>TARGET LUN 0.
>CAM FLAGS x00000482
> CAM_QUEUE_ENABLE
> CAM_DIR_OUT
> CAM_SIM_QFRZDIS
>*PDRV_PTR x03FFC428
>*NEXT_CCB x00000000
>*REQ_MAP x028BC100
>VOID (*CAM_CBFCNP)() x005114B0
>*DATA_PTR x83D04000
>DXFER_LEN x00010000
>*SENSE_PTR x03FFC450
>SENSE_LEN x40
>CDB_LEN x06
>SGLIST_CNT x0000
>CAM_SCSI_STATUS x0000 SCSI_STAT_GOOD
>SENSE_RESID x00
>RESID x00010000
>CAM_CDB_IO x0000000000000080F007000A
>CAM_TIMEOUT x0000003C
>MSGB_LEN x0000
>VU_FLAGS x4000
>TAG_ACTION x20
>= = = = =
And got the following excellent answer from Dave <golden_at_falcon.invincible.com>
:
>It sounds like you have two problems.
>In order to get dxadvfs to "see" the disks, wipe out the disklabel
>with disklabel -z /dev/rrz#c. Then write a new disklabel with
>disklabel -wr /dev/rrz#c rz29b. You should see the disks in dxadvfs
>(in all their glory with all the partions listed).
>It also looks like you are having problems with your SCSI bus. Are
>you sure that your storageworks shelf is set up properly, with the
>jumper and the terminator configured for a single bus w/termination?
>If you don't have the ba350 docs, I can probably look up which
>connectors you need to put the terminator and jumper into. You also
>want to disable the storageworks shelf status signals, since the kzpaa
>doesn't support them.
>You probably "found" the disks when you upgraded because part of the
>upgrade process rebuilds the kernel from the generic kernel, which has
>been built with all the possible disk devices in it. See the system
>administration manual section that talks about adding disks.
>Good Luck,
>Dave
Received on Fri Oct 27 1995 - 17:07:35 NZDT