[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | HSZ40 Product Conference |
|
| Moderator: | SSDEVO::EDMONDS |
|
| Created: | Mon Apr 11 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 902 |
| Total number of notes: | 3319 |
791.0. "Adding disk to hsz40" by ROMTSS::MATTACCHIONE () Tue Mar 04 1997 08:27
Hi,
I have installed several new disk rz29b-va in a ba350 connected to Hsz40.
I have followed the following procedure to add the device:
In an empty Ba350 I have pushed the relative port and wait to
blink the yellow led.
Then have inserted six disks.
Apparently nothing is happened.
Then I have repeated the same operation on another Ba350 with one disk
installed and inserted five disks.
Here is appeared the problem.
A device is gone NOT READY.
A device that is on another BA350 then on another HSZ port.
Same operation repeated have produced same problem.
I have also reset device incriminated using a false warm swap.
Nothing is changed. The only way is been to shut the hsz40 and restart it.
---------------------------------
I ask:
Is my procedure correct or I have make mistakes somewhere?
Is disk installation supported without shut hsz and/or host connected?
Thanks Gabriele
---------------------------------
HSZ40 is in dual redudancies and have firmware version 2.7
Hosts are DEC Unix Version 3.2g
Follow the host console output and Decevent related entry.
advfs I/O error: setId 0x3014ec9d.0008cd30.3.8003 tag 0x00002012.8001u
page 0
vd 1 blk 1033376 blkCnt 16
read error = 5
...................................................
................................................
AT FOLLOWING REBOOT
cam_logger: CAM_ERROR packet
cam_logger: bus 4 target 0 lun 1
cdisk_op_spin
Start Unit failed
DEC HSZ4
Active CCB at time of error
CCB request completed with an error
Error, exception, or abnormal condition
NOT READY -Logical unit is not ready
..............................
..............................
cam_logger: CAM_ERROR packet
cam_logger: bus 4 target 1 lun 0
cdisk_op_spin
Start Unit failed
DEC HSZ4
Active CCB at time of error
CCB request completed with an error
Error, exception, or abnormal condition
NOT READY -Logical unit is not ready
...............................
...............................
cam_logger: CAM_ERROR packet
cam_logger: bus 4 target 0 lun 2
cdisk_op_spin
Start Unit failed
DEC HSZ4
Active CCB at time of error
CCB request completed with an error
Error, exception, or abnormal condition
NOT READY -Logical unit is not ready
Decevent v2.1
******************************** ENTRY 5 ********************************
Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 108.
Timestamp of occurrence 03-MAR-1997 17:44:01
Host name osra02
System type register x0000000C AlphaServer 8x00
Number of CPUs (mpnum) x00000004
CPU logging event (mperr) x00000000
Event validity 1. O/S claims event is valid
Event severity 5. Low Priority
Entry type 199. CAM SCSI Event Type
------- Unit Info -------
Bus Number 4.
Unit Number x010C Target = 1.
LUN = 4.
------- CAM Data -------
Class x00 Disk
Subsystem x00 Disk
Number of Packets 10.
------ Packet Type ------ 258. Module Name String
Routine Name cdisk_check_sense
------ Packet Type ------ 256. Generic String
Event - Unit Attention
------ Packet Type ------ 262. Info Error String
Error Type Information Message Detected (recovered)
------ Packet Type ------ 257. Device Name String
Device Name DEC HSZ4
------ Packet Type ------ 256. Generic String
Active CCB at time of error
------ Packet Type ------ 256. Generic String
CCB request completed with an error
------ Packet Type ------ 1. SCSI I/O Request CCB(CCB_SCSIIO)
Packet Revision 37.
CCB Address xFFFFFC007F1B8728
CCB Length x00C0
XPT Function Code x01 Execute requested SCSI I/O
Cam Status x84 CCB Request Completed WITH Error
Autosense Data Valid for Target
Path ID 4.
Target ID 1.
Target LUN 4.
Cam Flags x00000442 SIM Queue Actions are Enabled
Data Direction (01: DATA IN)
Disable the SIM Queue Frozen State
*pdrv_ptr xFFFFFC007F1B8428
*next_ccb x0000000000000000
*req_map xFFFFFC00396E4900
void (*cam_cbfcnp)() xFFFFFC000051A530
*data_ptr xFFFFFC000F25E000
Data Transfer Length 8192.
*sense_ptr xFFFFFC007F1B8450
Auotsense Byte Length 160.
CDB Length 6.
Scatter/Gather Entry Cnt 0.
SCSI Status x02 Check Condition
Autosense Residue Length x00
Transfer Residue Length x00002000
(CDB) Command & Data Buf
15--<-12 11--<-08 07--<-04 03--<-00 :Byte Order
0000: 00000000 00000010 40250008 * ..%@........*
Timeout Value x0000003C
*msg_ptr x0000000000000000
Message Length 0.
Vendor Unique Flags x4000
Tag Queue Actions x20 Tag for Simple Queue
------ Packet Type ------ 256. Generic String
Error, exception, or abnormal condition
------ Packet Type ------ 256. Generic String
UNIT ATTENTION - Medium changed or target
reset
------ Packet Type ------ 768. SCSI Sense Data
Packet Revision 0.
------- HSZ Data -------
Instance Code x02062301 The CACHE backup battery has been declared
bad. Either it failed testing performed by
the Cache Diagnostics during system
startup or it was low (insufficently
charged) for longer than the expected
duration. The Memory Address field
contains the starting physical address of
the CACHEA0 memory.
Component ID = Value Added Services.
Event Number = x00000006
Repair Action = x00000023
NR Threshold = x00000001
Template Type x12 Backup Battery Failure.
Template Flags x00 HCE = 0, Event did not occur during Host
Command Execution.
Ctrl Serial # ZG51901083
Ctrl Software Revision V27Z
RAIDSET State x00 NORMAL. All members present and
reconstructed, IF LUN is configured as a
RAIDSET.
Error Code x70 Current Error
Sense Key x06 Unit Attention
ASC & ASCQ xA002 ASC = x00A0
ASCQ = x0002
Backup battery event report.
Memory Address x00000000
******************************** ENTRY 6 ********************************
Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 107.
Timestamp of occurrence 03-MAR-1997 17:21:42
Host name osra02
System type register x0000000C AlphaServer 8x00
Number of CPUs (mpnum) x00000004
CPU logging event (mperr) x00000003
Event validity 1. O/S claims event is valid
Event severity 3. High Priority
Entry type 199. CAM SCSI Event Type
------- Unit Info -------
Bus Number 4.
Unit Number x0108 Target = 1.
LUN = 0.
------- CAM Data -------
Class x00 Disk
Subsystem x00 Disk
Number of Packets 4.
------ Packet Type ------ 258. Module Name String
Routine Name cdisk_reset_rec_err
------ Packet Type ------ 256. Generic String
Recovery failed
------ Packet Type ------ 260. Hardware Error String
Error Type Hard Error Detected
------ Packet Type ------ 257. Device Name String
Device Name DEC HSZ4
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 791.1 | | SSDEVO::T_GONZALES | | Thu Mar 13 1997 12:51 | 9 |
| I think what you are seeing is the result of losing access to
the raid 5 and mirror sets due to battery failure, if you are using
v2.7. To add disks to the hsz just insert the disks and then do
run config from the hsz cli interface. Of course you probably want to
do this at periods of lite i/o since the insertion of the disks cause
a unit attention to the host system, which results in informational
error log entries, also don't insert the disks all at one time, wait at
least 30 seconds between insertions.
|