Following a system crash this morning, the following indications of a bad
block are found in '/usr/adm/messages':
Mar 4 11:52:47 infiniti vmunix: cam_logger: CAM_ERROR packet
Mar 4 11:52:47 infiniti vmunix: cam_logger: bus 0 target 0 lun 0
Mar 4 11:52:47 infiniti vmunix: cdisk_check_sense
Mar 4 11:52:47 infiniti vmunix: Medium Error bad block number: 1794094
Mar 4 11:52:47 infiniti vmunix: Hard Error Detected
Mar 4 11:52:47 infiniti vmunix: DEC RZ1CC-BA (C) DECRZ1CC-BA (
Mar 4 11:52:47 infiniti vmunix: Active CCB at time of error
Mar 4 11:52:47 infiniti vmunix: CCB request completed with an error
Mar 4 11:52:47 infiniti vmunix: Error, exception, or abnormal condition
Mar 4 11:52:47 infiniti vmunix: MEDIUM ERROR - Nonrecoverable medium error
A study of the 'scu' documentation - printed, 'man' page, online help -
unfortunately gives very little help in the way of assistance with bad
block reassigment. Since the 'grown' defect list appears to have a number
of entries, I'm curious why this particular bad block has not been
automatically handled by the device.
Further, is the command below sufficient to reassign this bad block?
scu> reassign lba 1794094
A check of the mailing list archives shows a number of similar queries
over the years, but no summary of useful responses to the list. I'll
be happy to summarize any useful procedures sent to me. Of course, if
they don't work, I'll have nothing to summarize but my own acute sense
of dispair.
Supporting info: Alphastation 500 5/400, DU 4.0B, disk is DEC RZ1CC-BA
(4.3 GB 7200 RPM Ultra SCSI). Sysadmin is 52, 5'10", 180#, with only one
oar in the water at the present time.
Thanks for any pointers.
Received on Thu Mar 04 1999 - 21:10:56 NZDT