Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Netware SCSI Errors - (SDMSNET3) SCSI Check Condition - HELP!!!!!

0 views
Skip to first unread message

Micah Nerren

unread,
Oct 3, 1996, 3:00:00 AM10/3/96
to

Hiya. I am having some strange errors that nobody seems to know how to
fix.

It all started when one of our SCSI drives failed and had to be
replaced. After this occurance I moved the SCSI tape drive from a
workstation to the SCSI Tower on the server and installed ARCSERVE 6
from Cheyenne on the server.

Now when I load ARCSERVE I get periodic SCSI error messages at the
server console. The following message pops up every 13 minutes when
ARCSERVE is loaded:

10/3/96 9:56:25 am Severity = 5.
0.0.0 (SDMSNET3) SCSI Check Condition: SenseKey=MEDIUM_ERROR
(8D000003)

Tech support for every part of this system wasn't able to help, from
Cheyenne to the SCSI card manufacturer to the PC manufacturer.

I am using a DFI SHA-1500P PCI SCSI card in the server with the latest
drivers (NCRSDMS3.DSK and ASPICAM3.NLM)

The server is a Netware 3.11 P90 system with the entire SCSI system in
an external tower.

I also received the following error messages this morning which are
probably a symptom of the same problem:

10/3/96 8:22:47 am Severity = 5.
0.0.0 (SDMSNET3) CAM Error: CMD_TIMEOUT (8D000003)

10/3/96 8:22:47 am Severity = 4.
1.1.10 Device #3 (8D030) MICROP :2105-08MQ1068605:2401 deactivated
due to drive failure.

At this point the server had to be downed and rebooted. After I
unloaded ARCSERVE however none of these messages has appeared.

Any help resolving these issues will be greatly appreciated, I have
gotten no help from anyone responsible for this hardware and am
getting desperate, I really need to know what is causing this. I
believe it has something to do with the power on the SCSI bus, but am
just guessing. All my SCSI drives have many options for SCSI Term
power, etc. but I cannot find *anywhere* information on how an
external SCSI tower should be setup with many drives.

Thanks in advance for any suggestions you may have,

Micah Nerren

Edwin Cleton - LESi Ts&S Engineering

unread,
Oct 4, 1996, 3:00:00 AM10/4/96
to

Quoting from: hydr...@earthlink.net (Micah Nerren)

> Hiya. I am having some strange errors that nobody seems to know how to
> fix.

> It all started when one of our SCSI drives failed and had to be
> replaced. After this occurance I moved the SCSI tape drive from a
> workstation to the SCSI Tower on the server and installed ARCSERVE 6
> from Cheyenne on the server.

> Now when I load ARCSERVE I get periodic SCSI error messages at the
> server console. The following message pops up every 13 minutes when
> ARCSERVE is loaded:

> 10/3/96 9:56:25 am Severity = 5.
> 0.0.0 (SDMSNET3) SCSI Check Condition: SenseKey=MEDIUM_ERROR
> (8D000003)

Install a second scsi controller and move the tape to its own controller.
(ie. don't share cdroms&tapedrives with harddrives on 1 ctrlr)

--
Ec...@xs4all.nl CLinks at http://www.xs4all.nl/~ecl2 +31-6-54632921
LESi Ts&S Engineering; PoBox 9179, 3007 AD Rotterdam The Netherlands
A.I. & Expert Technology, System Security Expertise/ICSE, ACE, NetWare
# Non-standard-disclaimer, I only speak for those who pay me enough. #

John Matrow

unread,
Oct 7, 1996, 3:00:00 AM10/7/96
to

NCR SCSI chips are supported by Symbios Logic (former NCR
Microelectronics):

(1) BBS: 719-573-3562 (719-533-7235 after Oct 1) (Europe:
001 719 573 3562)
(2) FAX: 719-533-7240 (Europe: 49 8231 9644 66)
(3) FTP: ftp.symbios.com
(4) EMAIL: sup...@symbios.com
(5) VOICE: 719-573-3016 (719-533-7230 after Oct 1)
(Germany: 49 89 547470 0; Hong Kong: 852 859 6044)
(6) LITERATURE: 800-334-5454 (U.S. only),
liter...@symbios.com
but *NOT* CompuServe, USENET newsgroups or any other
channel.

Micah Nerren

unread,
Oct 7, 1996, 3:00:00 AM10/7/96
to

Ec...@xs4all.nl (Edwin Cleton - LESi Ts&S Engineering) wrote:

>> It all started when one of our SCSI drives failed and had to be
>> replaced. After this occurance I moved the SCSI tape drive from a
>> workstation to the SCSI Tower on the server and installed ARCSERVE 6
>> from Cheyenne on the server.
>
>

>Install a second scsi controller and move the tape to its own controller.
>(ie. don't share cdroms&tapedrives with harddrives on 1 ctrlr)
>

Thanks, thats what I think I will do, as thats what I keep being told
by various people as the best solution.

BTW, where do you get information on SCSI and how to set it up
properly? I've not found any documentation on setting up towers and
how to do the termination properly (ie. Term power from bus, to bus,
etc.)

Thanks,

Micah


Hansang Bae

unread,
Oct 7, 1996, 3:00:00 AM10/7/96
to

hydr...@earthlink.net (Micah Nerren) writes:
snip

>BTW, where do you get information on SCSI and how to set it up
>properly? I've not found any documentation on setting up towers and
>how to do the termination properly (ie. Term power from bus, to bus,
>etc.)

comp.periphs.scsi goto rtfm.mit.edu, follow the usenet hierachy and
grab the faq.

There is also a pretty good book written by the Sound Blaster people
about scsi. Can't remember the title, but it's pretty sophmoric
looking. The info in is is *very* good.


-----------------------------------------------------------------
| Hansang Bae, CNE | Network Analyst, Richey Systems |
| hb...@primenet.com | Voice: (408) 235-3775 Fax: (408) 235-3850 |
-----------------------------------------------------------------

Edwin Cleton - LESi Ts&S Engineering

unread,
Oct 9, 1996, 3:00:00 AM10/9/96
to

Quoting from: hydr...@earthlink.net (Micah Nerren)

> >> It all started when one of our SCSI drives failed and had to be


> >> replaced. After this occurance I moved the SCSI tape drive from a
> >> workstation to the SCSI Tower on the server and installed ARCSERVE 6
> >> from Cheyenne on the server.
> >
> >Install a second scsi controller and move the tape to its own controller.
> >(ie. don't share cdroms&tapedrives with harddrives on 1 ctrlr)

> Thanks, thats what I think I will do, as thats what I keep being told
> by various people as the best solution.

> BTW, where do you get information on SCSI and how to set it up


> properly? I've not found any documentation on setting up towers and
> how to do the termination properly (ie. Term power from bus, to bus,
> etc.)

I never really read or look at specifics, coming from electro and
following electronics as engineer complemented by the software and
hardware industry over some years, you more or less figure these
things out by common sense and logic. Termpower is still somewhat
of a mistic issue, everyone conficts with each other about how to
set it, explain to me how you have your bus set and whats on it like
disks and controller type, it usually comes down to having 2 points
supplying termpower to the chain, 1 end by the controller and the
other end by an (external) active terminator, all other devices,
including the end chains device, take termpower from the bus. The
exception here is when you have more then 5 devices it may help to
let the middle device supply termpower to the bus as well.

0 new messages