From owner-freebsd-questions Fri Aug 11 12:51:29 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id MAA05291 for questions-outgoing; Fri, 11 Aug 1995 12:51:29 -0700 Received: from jd-unix.wpafb.af.mil (jd-unix.wpafb.af.mil [129.52.114.42]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id MAA05285 for ; Fri, 11 Aug 1995 12:51:28 -0700 Received: (from news@localhost) by jd-unix.wpafb.af.mil (8.6.11/8.6.9) id PAA00891; Fri, 11 Aug 1995 15:58:38 GMT Date: Fri, 11 Aug 1995 15:58:38 +0000 () From: Berkeley NEWS! To: Alan Char cc: questions@freebsd.org Subject: Re: Free BSD problems and questions In-Reply-To: <9508111201.ZM1700@topic> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: questions-owner@freebsd.org Precedence: bulk Alan, I've found weird problems such as that when working with Unix or Windows NT with scsi drives. Make sure your terminating resistors on the drives are set up properly. If they are off in any way, they may work with simple OS's like dos, but not UNIX. The resistor problem often causes the machine to appear to write to the hard drive correctly, but the info actually never physically gets placed on the drive, the controller just returns a code of 0 for success. Some of these controllers do not recognize these problems correctly. The appearance that some of the data may be recorded and some may not can be the ghosty workings of scsi drives terminated improperly. Sometimes the cache will keep enough information in memory not sync'ed to appear fine everytime you look. But after a couple of megs have been saved, the os starts syncing the disks (but no data is saved) it goes to scsispace. Jeff -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= - Jeffrey D. Dean SrA - - Computer Technician / Programmer - - Wright Patterson AFB, Ohio - - root@jd-unix.wpafb.af.mil - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=