Newsgroups: u3b.tech,comp.sys.att
Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!lsuc!robohack!woods
From: woods@robohack.uucp (Greg A. Woods)
Subject: 3B2 SCSI Soft Power fun...
Organization: Elegant Communications Inc.
Date: Thu, 27 Jun 91 02:16:18 GMT
Message-ID: <1991Jun27.021618.664@robohack.UUCP>
Summary: don't let it get you down!
Sender: woods@robohack.UUCP (Greg A. Woods)
Lines: 34


I just went through an episode that gave me a good scare.

I came home this evening to find my DM/135e with its power light out
and tons of messages spewing out on the console about a bad block 0 on
that device.  Oh-oh!  I tried an emergency power down, but it
"failed", so I logged in and tried 'telinit 0' which eventually worked.

When I tried to power back up, only the DCM/4e came on, and not even
the TM/60S!  After much goofing around and searching through the
maintenance manual, I finally looked at the SCSI Operations Manual.
A very short paragraph suggested shutting everything off *and*
disconnecting all of the power cables, and starting up from scratch.

It almost worked, but I was getting funny clicks from my new line
conditioner (TrippLite LS-600 b).  I also noticed noise on my AM radio
when I removed the power cords from units that were supposedly off.

Ah yes!  That wee paragraph said problems might occur if either
someone accidentally powered off a module, *or* if there were
un-expected power transients.

So, I removed the "line conditioner" from the power bar and went
through the disconnect procedure again before everything was stable.

I think I'll leave the line conditioner for some other application,
after I check it's output under load with a scope!  Meanwhile, I think
that I'll let those "intelligent" SCSI module power supplies fend for
themselves.
-- 
						Greg A. Woods

woods@{robohack,gate,eci386,tmsoft,ontmoh}.UUCP
+1 416 443-1734 [h]   +1 416 595-5425 [w]   VE3-TCP   Toronto, Ontario; CANADA