From owner-freebsd-questions Mon May 8 12:38: 8 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from cortex.NSMA.Arizona.EDU (cortex.NSMA.Arizona.EDU [128.196.180.125])
by hub.freebsd.org (Postfix) with ESMTP
id 77CDB37BBA6; Mon, 8 May 2000 12:38:00 -0700 (PDT)
(envelope-from ddw@cortex.NSMA.Arizona.EDU)
Received: from cortex (localhost [127.0.0.1]) by cortex.NSMA.Arizona.EDU (8.7.5/8.7.5) with ESMTP id MAA16581; Mon, 8 May 2000 12:50:36 -0700 (MST)
Message-Id: <200005081950.MAA16581@cortex.NSMA.Arizona.EDU>
Reply-To: ddw@NSMA.Arizona.EDU
X-Mailer: nmh - The "True to Unix" mail handler
To: freebsd-scsi@freebsd.org
Cc: freebsd-questions@freebsd.org
Subject: Problems with 36GB SCSI drives...
Date: Mon, 08 May 2000 12:50:35 -0700
From: Doug Wellington
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
OK, I've been working on various incarnations of this problem for a week
now... I have another day or two and then I'm gonna have to go back to
NT... Sigh... [Help me, PLEASE...!]
I have a PC (550 MHZ P-III, Asus P3B-F, 256 MB) with two Adaptec 2940U2W
boards with six IBM DMVS36V 36GB drives. I also have a four gig internal
SCSI drive attached to the first 2940U2W to boot from. The goal is to use
vinum and create a RAID5 system...
OK, I have installed FreeBSD 4.0 from the CD that I was shipped. I then
try to use disklabel to put a label onto the first 36GB drive, like so:
disklabel -Brw da1 auto
but the SCSI bus times out and then I'm hosed.
I get the following messages:
(da1:ahc0:0:1:0) SCB 0x0c - timed out in Data-out phase, SSEQADDR == 0x5d
(da1:ahc0:0:1:0) BDR message in message buffer
(da1:ahc0:0:1:0) SCB 0x0c - timed out in Data-out phase, SSEQADDR == 0x5e
(da1:ahc0:0:1:0) BDR message in message buffer
(da1:ahc0:0:1:0) no longer in timeout, status = 34b
ahc0: Issued Channel A Bus Reset. 4 SCBs aborted
And a screen full of similar messages. (I have to copy them over by hand,
but I'll do it if it means solving this problem.) The internal disk seems
to go into a timeout as well. (da0:ahc0:0:0:0) After a few minutes, the
command prompt comes back, and I can type "disklabel da1" and get what looks
like a valid reply. I can also run disklabel -e and add another partition,
but if I try to use newfs, I get the same timeout problems. I've tried this
with disks attached to the other 2940 with the same results. (Except that
the internal drive doesn't time out in that case...)
If I try to reboot the computer at this (or any other) point, it freezes with
the following message:
int=00000000 err=00000000 efl=00030246 eip=00001b54
eax=00000000 ebx=00000386 ecx=00000000 edx=00000000
esi=00009ebd edi=00001a3e ebp=0000038e esp=00000382
cs=d000 ds=0040 es=9ebd fs=0000 gs=0000 ss=9ebd
cs:eip=f7 f1 33 d2 8a 4e f6 f7-f1 3d ff 03 76 03 b8 ff
ss:esp=00 00 3f 00 00 00 00 00-00 00 02 00 df 09 00 d0
system halted
I get this message whether I reboot immediately after the first disklabel
command, or if I reboot after using disklabel to add a partition, or after
using newfs. I get the same message whether I try to boot from the system
on the hard disk or from the 4.0 CD-ROM. I get a similar message when trying
to boot from a 3.4 CD. At this point, the only way I can do anything is to
reboot, hit ctrl-A to get into the Adaptec diagnostics and reformat the 36 GB
hard disk at that level. Then I can reboot and FreeBSD starts right up from
the internal hard disk where it was originally installed.
What gives? Anybody have any ideas?
-Doug
--
Doug Wellington System and Network Administrator
ddw@nsma.arizona.edu The University of Arizona, Tucson, AZ, USA
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message