bossert@entropy.ms.washington.edu (John Bossert) (12/11/87)
I've been seeing the following occasionally:
uda0: hard error, disk transfer, unit 1
grp 0x0, hdr 0x540
uda0: hard error, SDI error, unit 1
event 0353 hdr 0x0
uda0: hard error, disk transfer, unit 1
grp 0x0, hdr 0x2d0
uda0: hard error, SDI error, unit 1
event 0353 hdr 0x0
From looking at the code for uda.c, I see that they're MSCP
error log packets. Unfortunately, I can't find info on the
particulars. Doctors, the prognosis?
VAX 750, 4.2bsd, UDA50, RA81's. Thanks.
--
In-Real-Life: John Bossert, Thalatta Corporation, (+1 206 643 7187)
Domain: bossert@Thalatta.COM Path: uw-beaver!uw-entropy!thebes!bossertchris@mimsy.UUCP (Chris Torek) (12/15/87)
In article <682@entropy.ms.washington.edu> bossert@entropy.ms.washington.edu (John Bossert) writes: > uda0: hard error, disk transfer, unit 1 > grp 0x0, hdr 0x540 The important value (`event') is missing from this one. > uda0: hard error, SDI error, unit 1 > event 0353 hdr 0x0 I have no idea what an `SDI error' is (although one can imagine the missiles coming in, and the harried army technician staring at `bus error (core dumped)', or, more likely, Array subscript error: index 5121798 not in range Begin traceback: VerifyRadarScan in module RadarScanner CheckMissileProfile in module AnalyzeProfile ... End traceback Do you want an image dump? [yn] but never mind that). The `event 0353', however, decodes as `drive error (drive detected error)'. `hdr 0x540' indicates logical block number 1344; for this kind of error, the block number is usually irrelevant. -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690) Domain: chris@mimsy.umd.edu Path: uunet!mimsy!chris