Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP Path: utzoo!watmath!clyde!cbosgd!cbdkc1!desoto!packard!hoxna!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!timeinc!phri!pesnta!amd!vecpyr!lll-crg!gymble!umcp-cs!chris From: chris@umcp-cs.UUCP (Chris Torek) Newsgroups: net.unix-wizards Subject: Re: Revectoring bad blocks on RA81 disks Message-ID: <538@umcp-cs.UUCP> Date: Sat, 29-Jun-85 23:49:33 EDT Article-I.D.: umcp-cs.538 Posted: Sat Jun 29 23:49:33 1985 Date-Received: Tue, 2-Jul-85 05:44:33 EDT References: <421@carina.noao.UUCP> Organization: U of Maryland, Computer Science Dept., College Park, MD Lines: 24 Important announcement: I have set up a new mailing list, info-uda50@maryland, a.k.a umcp-cs!info-uda50. Anyone who wants to subscribe, please send mail to info-uda50-request@maryland (or umcp-cs!info-uda50-request). ------ (enough of that) Speaking of forced error data errors, I found that doing a replace operation with a forced error modifier made our UDA50 controller say "yes, I did the replacement", but the bad block descriptors were unchanged. Removing the forced error modifier made it work. Since then the controller microcode has been "upgraded", so I suppose it could have been just another UDA50 bug.... The cylinder group summary information must (obviously) be rewritten every time the cylinder groups change, which is certain to be very often, but it can be regenerated, so I wouldn't worry about losing it. Interesting that the sectors containing that info are the ones to first start showing errors. Perhaps the oxide is getting attracted to the disk heads :-). -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251) UUCP: seismo!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@maryland