Xref: utzoo comp.unix.wizards:5736 comp.sys.dec:420 Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!eneevax!mimsy!chris From: chris@mimsy.UUCP (Chris Torek) Newsgroups: comp.unix.wizards,comp.sys.dec Subject: Re: UDA-50 error messages Message-ID: <9780@mimsy.UUCP> Date: 15 Dec 87 02:59:05 GMT References: <682@entropy.ms.washington.edu> Distribution: na Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 29 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