Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!uc!shamash!ewm@punjab.udev.cdc.com
From: ewm@punjab.udev.cdc.com (Eric Markwardt)
Newsgroups: comp.sys.mips
Subject: Imprimis Wren V's on an RS2030?
Keywords: RS2030, Wren V, no-go
Message-ID: <14783@shamash.cdc.com>
Date: 13 Dec 89 03:35:53 GMT
Sender: news@shamash.cdc.com
Reply-To: ewm@punjab.udev.cdc.com (Eric Markwardt)
Distribution: na
Organization: Control Data Corp., Arden Hills, MN
Lines: 34

I'm trying to stick some Wren V's (94181-702) on our 2030s we 
just got in.  We've been having trouble getting the defect list 
read off the disk and think this may be resulting in some of the 
read and/or write errors we've been getting on the disks.

When I boot /stand/format and try to read the defect list from
the disk, I get nothing but ioctl error messages.  Similarily,
scanning the disk for defects results in more ioctl errors on 
every block.

TFM hasn't been exactly helpful in what all of the parameters
are when format is asking you what type of disk you have, since
the Wren V-702 isn't in the "known disk" list -- a side note
here.. does anyone know where format pulls the "known disk" list
from?  I made some changes in /etc/disktab and they didn't seem
to show up the next time I booted format.  Are these hard-coded
into format??

Anyway, has anyone put a 702MB Wren V on a 2030 and had it work
successfully?  If so, what did you use for disk parameters, 
enabling of sector slipping, track slipping, reading disk defects, etc.?

BTW - the word from Mips support is that the 94181-702 is "not officially
supported".  Seems to me that if other Wrens are supported, the
Wren V shouldn't be much different..

Thanks in advance for any insite anyone can shed.

   -Eric
--
Eric Markwardt		ewm@punjab.udev.cdc.com

Disclaimer: All opinions/thoughts above are my own and in no way 
represent those of my employer or fellow employees.