Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!mcvax!kth!draken!tut!santra!kampi!alo
From: alo@kampi.hut.fi (Antti Louko)
Newsgroups: comp.unix.ultrix
Subject: Re: Emulex SC 7003, Ultrix 3.0, Emulex TC11, VAX 8650, & Ultrix v2.2
Keywords: Emulex controllers
Message-ID: <20931@santra.UUCP>
Date: 29 Mar 89 20:49:18 GMT
References: <88316@felix.UUCP> <913@atanasoff.cs.iastate.edu> <23161@ames.arc.nasa.gov> <6424@cbmvax.UUCP>
Sender: news@santra.UUCP
Reply-To: alo@kampi.hut.fi (Antti Louko)
Organization: Helsinki University of Technology, Finland
Lines: 22

In article <6424@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
>We have CDC service here, and they service both Emulex and the CDC
>drives, though anything but VMS seems to be black magic to them.  They
>were very helpful in resolving problems I had with a bad adapter board
>and screwed up cables.  They also had the Emulex formatter package, but
>for some reason although it claimed to have formatted the drive, it
>didn't write out the bad sector file correctly.  Probably operator error,
>but it didn't show up immediately and I only realized things were screwed
>proper only after laying committing  my news spool to the minefield of
>bad spots.  Ouch.

A couple of years ago, we had similar experience with an
Emulex-controller emulating MASSBUS-adapter. Support engineer told us
that there are two bad sector files. DEC-MASSBUS-formatters write a
so-called factory bad sector file. Users can add later more bad
sectors into the user bad sector file. Emulex diagnostics seems to put
bad sectors only into the user bad sector file. BSD (and apparently
Ultrix, too) read only the factory bad sector file. I would be very
surprised if VMS doesn't read both of them. Could someone with
VMS-microfiches check this, please. I remember the user bad sector
file was at the start of the next track or cylinder or something like
that. I hope this helps.