Date: Mon, 08 May 2000 14:15:36 -0700 From: Doug Wellington <ddw@NSMA.Arizona.EDU> To: Mitch Collinsworth <mkc@graphics.cornell.edu> Cc: freebsd-scsi@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Problems with 36GB SCSI drives... Message-ID: <200005082115.OAA17706@cortex.NSMA.Arizona.EDU> In-Reply-To: Your message of "Mon, 08 May 2000 16:14:17 -0400." <200005082014.QAA70043@larryboy.graphics.cornell.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Previously: >[NT] >NO, anything but that! Yeah... That's what *I* said... >I hope you won't feel insulted if I ask if you've made extra certain >that you don't have 2 devices using the same scsi address. Not just >by looking at the switch or jumper settings, but reading through the >boot messages to make sure they're all registering differently. No insult at all. I'm actually hoping it's something really stupid that I'm doing wrong! As for the scsi addresses, I set the jumpers myself, watched as each Adaptec board probed its address range and listed the drives it found during boot and then checked the logs. I even scribbled a little matrix out with the adapters and scsi id numbers and checked each one off... I originally had the scsi cards in different slots, but I thought there was an IRQ problem, (you know, the AGP slot shares an IRQ with PCI slot #1 kinda thAng) so I swapped cards around and I don't think that's an issue... Hmmmm, funny thing is that when I had the 2940 in slot #1, I was able to get all the way to using vinum and trying the "init" command before it failed... >Maybe >even try disconnecting power from the ones not currently being used to >see if that gets you through disklabel. Yeah, I'm down to where I have one external case turned on (with three drives in it. The other drives are turned off. After lunch, I guess I'll just open that case up and pull the power off of the other two drives. After that, I guess I'll have to try putting one of the disks on the internal SCSI connector... [Drumming fingers] I'm wondering if it's the motherboard... Wish I had another one to test. (I have tried different 2940U2W boards already.) >And double-check termination and cabling distance rules. FWIW, the light on the active terminator is on. I only have a three foot cable going from the computer to the external box... >(Somehow this doesn't sound like the sort of thing NT is going to solve.) Well, the weird thing is that just for grins, I DID boot up NT once and I was able to see and format one of the external disks... That was one of my first attempts to get past that boot up error message, before I started using the built in (ctrl-A) adaptec formatting routines. (Since I couldn't boot from the FreeBSD CD or the internal hard disk, I had to try something to get rid of the partitions on the disk...) The problem is that since NT worked, that makes me wonder if it is the motherboard after all...? Is there a disk size limit with FreeBSD? Is 36 GB too big? SIGH... Thanks, -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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005082115.OAA17706>