From owner-freebsd-scsi Sun Feb 16 13:43:43 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA29109 for freebsd-scsi-outgoing; Sun, 16 Feb 1997 13:43:43 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA29103 for ; Sun, 16 Feb 1997 13:43:36 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id WAA11487 for scsi@freebsd.org; Sun, 16 Feb 1997 22:32:00 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.5/8.8.2) id WAA01275; Sun, 16 Feb 1997 22:11:40 +0100 (MET) Message-ID: <19970216221140.YQ26603@klemm.gtn.com> Date: Sun, 16 Feb 1997 22:11:40 +0100 From: andreas@klemm.gtn.com (Andreas Klemm) To: scsi@freebsd.org Subject: 2.2-gamma: new problems with scsi subsystem X-Mailer: Mutt 0.60-PL0 Mime-Version: 1.0 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When trying to make dumps using dump(8), the system still hangs, if tagged command queueing is enabled. Bad news is, that removing every AHC_xxx option doesn't result in a stable system as well. My machine sometimes hangs, but unfortunately doesn't panic. All I can do is write down some of the error messages in the X console. sd0(ahc0:0:0) timed out while idle LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x10 ahc0: Issued channel A Bus Reset, 2 SCB's aborted clearing bus reset clearing 'in-reset' flag ahc0:4:0 synchronous at 4.4 MHz offset == 0x8 spe_getpages: I/O read error vmfault: pager input (probably hardware) error,... BTW, this is an unmodified 2.2-GAMMA kernel of today. Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-GAMMA #0: Sun Feb 16 21:31:45 MET 1997 root@klemm.gtn.com:/usr/sys.bisdn/compile/BISDN Calibrating clock(s) relative to mc146818A clock ... i586 clock: 99468279 Hz, i8254 clock: 1193118 Hz CPU: Pentium (99.47-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 63692800 (62200K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 chip2 rev 2 on pci0:7:1 vga0 rev 0 int a irq 12 on pci0:10 ahc0 rev 3 int a irq 11 on pci0:12 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "IBM DORS-32160 WA6A" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2063MB (4226725 512 byte sectors) sd0(ahc0:0:0): with 6703 cyls, 5 heads, and an average 126 sectors/track (ahc0:1:0): "IBM DORS-32160 WA6A" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2063MB (4226725 512 byte sectors) sd1(ahc0:1:0): with 6703 cyls, 5 heads, and an average 126 sectors/track (ahc0:4:0): "TANDBERG TDC 4222 =07:" type 1 removable SCSI 2 st0(ahc0:4:0): Sequential-Access density code 0x0, 512-byte blocks, write-enabled (ahc0:6:0): "TOSHIBA CD-ROM XM-3601TA 0725" type 5 removable SCSI 2 cd0(ahc0:6:0): CD-ROM can't get the size Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <4 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa ed0: address 00:00:c0:25:fd:2d, type WD8013EPC (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in tel0 at 0xd80 irq 9 on isa tel0: card type Teles S0/16.3 npx0 on motherboard npx0: INT 16 interface joy0 at 0x201 on isa joy0: joystick sb0 at 0x220 irq 5 drq 1 on isa sb0: sbxvi0 at 0x0 drq 5 on isa sbxvi0: sbmidi0 at 0x330 on isa opl0 at 0x388 on isa opl0: IP packet filtering initialized, divert disabled, logging limited to 100 packets/entry machine "i386" cpu "I586_CPU" ident BISDN maxusers 64 options INET #Internet communications protocols options FFS #Fast filesystem options PROCFS #Process filesystem options "COMPAT_43" options SCSI_DELAY=8 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow ordinary users to take the # console - this is useful for X. options "MAXCONS=4" # Number of virtual SCO compat consoles options "MD5" options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity options TELES_HAS_MEMCPYB # bisdn 0.97 options SYSVSHM,SYSVSEM,SYSVMSG # System V shared memory ###options "IBCS2" # COFF binary compatibility options COMPAT_LINUX # Linux Binary compatibility options SHOW_BUSYBUFS # busy buffers on shutdown ? #options AHC_TAGENABLE #options AHC_SCBPAGING_ENABLE #options AHC_ALLOW_MEMIO options SCSI_REPORT_GEOMETRY options DDB options KTRACE #kernel tracing options MFS #Memory File System config kernel root on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # my hardwired scsi devices, they have always the same SCSI ID ! controller ahc0 controller scbus0 at ahc0 disk sd0 at scbus0 target 0 disk sd1 at scbus0 target 1 disk sd2 at scbus0 target 2 tape st0 at scbus0 target 4 device cd0 at scbus0 target 6 # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr # Joystick device joy0 at isa? port "IO_GAME" pseudo-device loop pseudo-device ether pseudo-device log pseudo-device tun 1 pseudo-device pty 16 pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device gzip pseudo-device vn #Vnode driver (turns a file into a device) #pseudo-device speaker # SB = SoundBlaster; PAS = ProAudioSpectrum; GUS = Gravis UltraSound # Controls all sound devices controller snd0 # SoundBlaster DSP driver - for SB, SB Pro, SB16, PAS(emulating SB) device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr # SoundBlaster 16 DSP driver - for SB16 - requires sb0 device device sbxvi0 at isa? drq 5 # SoundBlaster 16 MIDI - for SB16 - requires sb0 device device sbmidi0 at isa? port 0x330 # Yamaha OPL-2/OPL-3 FM - for SB, SB Pro, SB16, PAS device opl0 at isa? port 0x388 #--------------------------------------------------------------------------- # # ISDN - parts of an example config file for bisdn # ------------------------------------------------ # # last edit-date: [Sun May 26 10:35:22 1996] # #--------------------------------------------------------------------------- options IPI_VJ # Van Jacobsen header compression support #options "IPI_DIPA=3" # send ip accounting packets every 3 seconds # Teles S0/16.3 ###################################################### IRQ 9 ## controller tel0 at isa? port 0xd80 net irq 9 vector telintr pseudo-device disdn pseudo-device isdn pseudo-device ipi 4 pseudo-device itel 2 pseudo-device ispy 1 From owner-freebsd-scsi Tue Feb 18 09:29:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA16942 for freebsd-scsi-outgoing; Tue, 18 Feb 1997 09:29:37 -0800 (PST) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA16937 for ; Tue, 18 Feb 1997 09:29:32 -0800 (PST) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.3/8.8.3) with SMTP id MAA15911 for ; Tue, 18 Feb 1997 12:38:19 -0500 (EST) Message-Id: <3.0.1.32.19970218121828.00a42af0@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 18 Feb 1997 12:18:28 -0500 To: scsi@freebsd.org From: Mike Tancsa Subject: ASUS SC-200 vs SC-875 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, In our news machine we currently have 6 drives and one 2940 controller... I was thinking of adding another PCI scsi controller to speed it up a bit and allow us to add more drives.... Since I already have a controller I can boot from, would this matter with that card ? Or should I pay a little extra for the Ultra version ? We dont have any ultra drives just yet... Would it matter for now? Also, how are the drivers for the NCR based SCSI controllers ? Are they as stable as the Adaptec ones ? Thanks, ---Mike ---Mike From owner-freebsd-scsi Tue Feb 18 10:11:20 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA19351 for freebsd-scsi-outgoing; Tue, 18 Feb 1997 10:11:20 -0800 (PST) Received: from m1.cs.man.ac.uk (0@m1.cs.man.ac.uk [130.88.13.4]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA19345 for ; Tue, 18 Feb 1997 10:11:15 -0800 (PST) Received: from amu7.cs.man.ac.uk by m1.cs.man.ac.uk (4.1/SMI-4.1:AL6) id AA27758; Tue, 18 Feb 97 18:11:07 GMT Date: Tue, 18 Feb 97 18:11:11 GMT From: David Alan Gilbert Message-Id: <9702181811.AA22259@amu7.cs.man.ac.uk> To: scsi@freebsd.org Subject: About to go SCSI - advice? Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi , I've used SCSI under many other OSs and am about to put a 4GB drive on our FreeBSD 2.2 server with an adaptec 2940UW - the drive is A Seagate Barracuda NT15150. Anything I'd better be careful of? Dave P.S. We're having the controller replaced first...I think it was doing very nasty things to drive termination power fuses..... From owner-freebsd-scsi Tue Feb 18 22:21:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA06570 for freebsd-scsi-outgoing; Tue, 18 Feb 1997 22:21:58 -0800 (PST) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA06565 for ; Tue, 18 Feb 1997 22:21:53 -0800 (PST) Received: from seabass.progroup.com (seabass.progroup.com [206.24.122.1]) by seabass.progroup.com (8.7.5/8.7.3) with SMTP id WAA13412; Tue, 18 Feb 1997 22:20:49 -0800 (PST) Message-ID: <330A9BC1.59E2B600@ProGroup.com> Date: Tue, 18 Feb 1997 22:20:49 -0800 From: Craig Shaver Organization: Productivity Group, Inc. X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: Mike Tancsa CC: scsi@freebsd.org Subject: Re: ASUS SC-200 vs SC-875 References: <3.0.1.32.19970218121828.00a42af0@sentex.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike Tancsa wrote: > > Hello, > In our news machine we currently have 6 drives and one 2940 controller... > I was thinking of adding another PCI scsi controller to speed it up a bit > and allow us to add more drives.... Since I already have a controller I > can boot from, would this matter with that card ? Or should I pay a little > extra for the Ultra version ? We dont have any ultra drives just yet... > Would it matter for now? Also, how are the drivers for the NCR based SCSI > controllers ? Are they as stable as the Adaptec ones ? > > Thanks, > > ---Mike I have only run NCR controllers on my FreeBSD computer. I like them. And most of the people say the 810 NCR fast scsi-II controllers (ASUS SC-200) are almost equal to the performance of the 2940. The fast and wide NCR 825 based controllers are supported in all version of FreeBSD, and the Ultra Wide NCR 875 controllers are supported in version 2.2 and later. By all means use the ASUS 200 for a second controller. I recommend it. :) -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088 From owner-freebsd-scsi Tue Feb 18 22:54:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA08002 for freebsd-scsi-outgoing; Tue, 18 Feb 1997 22:54:56 -0800 (PST) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA07997 for ; Tue, 18 Feb 1997 22:54:53 -0800 (PST) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.3/8.8.3) with SMTP id CAA18879; Wed, 19 Feb 1997 02:03:50 -0500 (EST) Message-Id: <3.0.1.32.19970219014358.00aa2140@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Wed, 19 Feb 1997 01:43:58 -0500 To: Craig Shaver From: Mike Tancsa Subject: Re: ASUS SC-200 vs SC-875 Cc: scsi@FreeBSD.ORG In-Reply-To: <330A9BC1.59E2B600@ProGroup.com> References: <3.0.1.32.19970218121828.00a42af0@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 10:20 PM 2/18/97 -0800, Craig Shaver wrote: >Mike Tancsa wrote: >> > >I have only run NCR controllers on my FreeBSD computer. I like them. >And most of the people say the 810 NCR fast scsi-II controllers (ASUS >SC-200) are almost equal to the performance of the 2940. The fast and >wide NCR 825 based controllers are supported in all version of FreeBSD, >and the Ultra Wide NCR 875 controllers are supported in version 2.2 and >later. By all means use the ASUS 200 for a second controller. I >recommend it. :) Super, Thanks for the response... Right now we are running 2.1.5 as the news server and will do an upgrade to 2.2 after the bugs are ironed out... One thing I dont get is why the FAQ (http://www.freebsd.org/FAQ/FAQ45.html#45) lists the Ultra Wide as being supported, when I find no mention of it in LINT in either 2.1.6 or 2.1.5... PCI Generic NCR 53C81x based controllers NCR 53C82x based controllers NCR 53C860/75 based controllers I am leaning toward getting the higher end controller since we might actually be able to afford higher class drives one day :-)... However, if it will only work with 2.2, then I am not sure if I should take a chance on it just yet. ---Mike From owner-freebsd-scsi Tue Feb 18 23:09:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA08651 for freebsd-scsi-outgoing; Tue, 18 Feb 1997 23:09:44 -0800 (PST) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA08628 for ; Tue, 18 Feb 1997 23:09:37 -0800 (PST) Received: from seabass.progroup.com (seabass.progroup.com [206.24.122.1]) by seabass.progroup.com (8.7.5/8.7.3) with SMTP id XAA14684; Tue, 18 Feb 1997 23:08:39 -0800 (PST) Message-ID: <330AA6F7.1CFBAE39@ProGroup.com> Date: Tue, 18 Feb 1997 23:08:39 -0800 From: Craig Shaver Organization: Productivity Group, Inc. X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: Mike Tancsa CC: scsi@FreeBSD.ORG Subject: Re: ASUS SC-200 vs SC-875 References: <3.0.1.32.19970218121828.00a42af0@sentex.net> <3.0.1.32.19970219014358.00aa2140@sentex.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Tancsa wrote: del ... > > Super, > Thanks for the response... Right now we are running 2.1.5 as the news > server and will do an upgrade to 2.2 after the bugs are ironed out... One > thing I dont get is why the FAQ (http://www.freebsd.org/FAQ/FAQ45.html#45) > lists the Ultra Wide as being supported, when I find no mention of it in > LINT in either 2.1.6 or 2.1.5... They are all in the ncr controller device driver. Actually you should be able to use an 875 on 2.1.5 or 2.1.6/7. I have a Tekram 390F based on the 875 chip, and I got the boot disks and patch for the driver from the Tekram web site (actually ftp area). http://www.tekram.com/ see the technical support area. I also got a small patch from Stefan Esser for the driver. This allowed me to use Ultra Wide drives and get the 40MB/s speed enabled. It works great for me -- on this machine, which is used for news, mail, and www. I have also used a second NCR card on this machine to support some legacy scsi-II drives. You can use it as an 810/825 if you don't want to jump through the hoops to use the Tekram driver stuff. If you want to, and have trouble getting it installed, just drop me an email and I'll help you. You may have to move the cards around to get the boot sequence right. > > PCI Generic > > NCR 53C81x based controllers > NCR 53C82x based controllers > NCR 53C860/75 based controllers > > I am leaning toward getting the higher end controller since we might > actually be able to afford higher class drives one day :-)... However, if > it will only work with 2.2, then I am not sure if I should take a chance on > it just yet. Go ahead and use it on 2.1.x as a non-wide controller, and then use it as a Ultra Wide when you make the jump to 2.2 and UW disks. > > ---Mike -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088 From owner-freebsd-scsi Wed Feb 19 00:51:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA12824 for freebsd-scsi-outgoing; Wed, 19 Feb 1997 00:51:24 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA12819 for ; Wed, 19 Feb 1997 00:51:20 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA29517; Wed, 19 Feb 1997 09:50:41 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id JAA21852; Wed, 19 Feb 1997 09:29:03 +0100 (MET) Message-ID: Date: Wed, 19 Feb 1997 09:29:03 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: gilbertd@cs.man.ac.uk (David Alan Gilbert) Cc: scsi@freebsd.org Subject: Re: About to go SCSI - advice? References: <9702181811.AA22259@amu7.cs.man.ac.uk> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9702181811.AA22259@amu7.cs.man.ac.uk>; from David Alan Gilbert on Feb 18, 1997 18:11:11 +0000 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As David Alan Gilbert wrote: > P.S. We're having the controller replaced first...I think it was doing > very nasty things to drive termination power fuses..... Huh? No. *You* were doing very nasty things to drive termpower fuses! Rule #1: Turn off termpower! On any drive you're going to connect... let them take termpower from bus, and let the controller provide this to the bus, nobody else. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Feb 19 00:51:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA12866 for freebsd-scsi-outgoing; Wed, 19 Feb 1997 00:51:42 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA12851 for ; Wed, 19 Feb 1997 00:51:37 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA29524; Wed, 19 Feb 1997 09:51:26 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id JAA21828; Wed, 19 Feb 1997 09:22:09 +0100 (MET) Message-ID: Date: Wed, 19 Feb 1997 09:22:09 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: mike@sentex.net (Mike Tancsa) Cc: scsi@freebsd.org Subject: Re: ASUS SC-200 vs SC-875 References: <3.0.1.32.19970218121828.00a42af0@sentex.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3.0.1.32.19970218121828.00a42af0@sentex.net>; from Mike Tancsa on Feb 18, 1997 12:18:28 -0500 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Mike Tancsa wrote: > Or should I pay a little > extra for the Ultra version ? We dont have any ultra drives just yet... > Would it matter for now? Obviously, the Ultra version wouldn't get you anything then, but it doesn't harm either. If you plan to buy Ultra drives in the future, well then it's ``already there''. > Also, how are the drivers for the NCR based SCSI > controllers ? Are they as stable as the Adaptec ones ? At least as stable. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Feb 19 04:50:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA20937 for freebsd-scsi-outgoing; Wed, 19 Feb 1997 04:50:42 -0800 (PST) Received: from hda.hda.com (ip78-max1-fitch.ziplink.net [199.232.245.78]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA20931 for ; Wed, 19 Feb 1997 04:50:38 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.6.12/8.6.12) id HAA01017; Wed, 19 Feb 1997 07:44:25 -0500 From: Peter Dufault Message-Id: <199702191244.HAA01017@hda.hda.com> Subject: Re: About to go SCSI - advice? In-Reply-To: from J Wunsch at "Feb 19, 97 09:29:03 am" To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 19 Feb 1997 07:44:25 -0500 (EST) Cc: gilbertd@cs.man.ac.uk, scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As David Alan Gilbert wrote: > > > P.S. We're having the controller replaced first...I think it was doing > > very nasty things to drive termination power fuses..... > > Huh? No. *You* were doing very nasty things to drive termpower fuses! > > Rule #1: Turn off termpower! On any drive you're going to connect... > let them take termpower from bus, and let the controller provide this > to the bus, nobody else. No, Joerg. Any device that can become an initiator must supply terminator power (so Simon must have more than one device with TERMPWR to meet the letter of the spec). Other devices can as long as they don't exceed the total maximum current (which is huge - I think it is something like 5 amps and is driven by regulatory issues). The discussion is somewhere near the beginning of the spec. My intuitive opinion is that the host adapter and the devices at either end of the chain should provide TERMPWR. Peter -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-scsi Wed Feb 19 04:56:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA21223 for freebsd-scsi-outgoing; Wed, 19 Feb 1997 04:56:22 -0800 (PST) Received: from m1.cs.man.ac.uk (0@m1.cs.man.ac.uk [130.88.13.4]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id EAA21211 for ; Wed, 19 Feb 1997 04:56:10 -0800 (PST) Received: from amu7.cs.man.ac.uk by m1.cs.man.ac.uk (4.1/SMI-4.1:AL6) id AA17558; Wed, 19 Feb 97 12:55:54 GMT Date: Wed, 19 Feb 97 12:55:58 GMT From: David Alan Gilbert Message-Id: <9702191255.AA22930@amu7.cs.man.ac.uk> To: dufault@hda.com, scsi@freebsd.org Subject: Re: About to go SCSI - advice? Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter spoke thus: > No, Joerg. Any device that can become an initiator must supply > terminator power (so Simon must have more than one device with > TERMPWR to meet the letter of the spec). Other devices can as long > as they don't exceed the total maximum current (which is huge - I > think it is something like 5 amps and is driven by regulatory > issues). The discussion is somewhere near the beginning of the > spec. > > My intuitive opinion is that the host adapter and the devices at > either end of the chain should provide TERMPWR. Our problem originally started when we found a device which wouldn't work (at all - wouldn't even respond to identify) unless it had termpwr when it was switched on; so you had to switch the source of termpwr on first and then the drive. 50% of the SCSI users in the world say you should have 1 term power device, 50% of the SCSI users say that you can have as many as you like, and the other 80% say termpwr - what? To make life bareable we turned termpwr on on that drive enabling it to be switched on; but the docs with our Adaptec don't say >ANYTHING< about termpower - they don't say where the fuse is, how to turn it on/off, whether it should be on/off etc. Dave From owner-freebsd-scsi Wed Feb 19 07:40:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA28262 for freebsd-scsi-outgoing; Wed, 19 Feb 1997 07:40:19 -0800 (PST) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA28257 for ; Wed, 19 Feb 1997 07:40:16 -0800 (PST) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.3/8.8.3) with SMTP id KAA19445; Wed, 19 Feb 1997 10:49:10 -0500 (EST) Message-Id: <3.0.1.32.19970219102901.00b30b00@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Wed, 19 Feb 1997 10:29:01 -0500 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) From: Mike Tancsa Subject: Re: ASUS SC-200 vs SC-875 Cc: scsi@freebsd.org In-Reply-To: References: <3.0.1.32.19970218121828.00a42af0@sentex.net> <3.0.1.32.19970218121828.00a42af0@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 09:22 AM 2/19/97 +0100, J Wunsch wrote: >As Mike Tancsa wrote: > >> Or should I pay a little >> extra for the Ultra version ? We dont have any ultra drives just yet... >> Would it matter for now? > >Obviously, the Ultra version wouldn't get you anything then, but it >doesn't harm either. If you plan to buy Ultra drives in the future, >well then it's ``already there''. > >> Also, how are the drivers for the NCR based SCSI >> controllers ? Are they as stable as the Adaptec ones ? > >At least as stable. Thanks for the response.... As Craig Shaver reccomended, I think I will end up getting the Ultra card for now and use it as a standard SCSI controller in the 2.1.5 news box... When 2.2 release comes out, I will upgrade the O/S and perhaps wangle an ULTRA drive out of the boss and use the card more to its potential... ---Mike From owner-freebsd-scsi Wed Feb 19 09:47:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA06262 for freebsd-scsi-outgoing; Wed, 19 Feb 1997 09:47:25 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA06254 for ; Wed, 19 Feb 1997 09:47:21 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id JAA13489; Wed, 19 Feb 1997 09:47:15 -0800 (PST) Date: Wed, 19 Feb 1997 09:47:14 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: David Walter cc: freebsd-scsi@freebsd.org Subject: Re: your mail In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm moving this over to freebsd-scsi, I don't know the status at current. On Wed, 19 Feb 1997, David Walter wrote: > Are there any plans to support the Buslogic Flashpoint series of SCSI > cards? Thank You. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-scsi Wed Feb 19 11:51:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA14642 for freebsd-scsi-outgoing; Wed, 19 Feb 1997 11:51:48 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA14628 for ; Wed, 19 Feb 1997 11:51:24 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA14428 for scsi@freebsd.org; Wed, 19 Feb 1997 20:50:40 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id UAA23294; Wed, 19 Feb 1997 20:21:27 +0100 (MET) Message-ID: Date: Wed, 19 Feb 1997 20:21:27 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@freebsd.org Subject: Re: About to go SCSI - advice? References: <199702191244.HAA01017@hda.hda.com> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199702191244.HAA01017@hda.hda.com>; from Peter Dufault on Feb 19, 1997 07:44:25 -0500 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Peter Dufault wrote: > > Rule #1: Turn off termpower! On any drive you're going to connect... > > let them take termpower from bus, and let the controller provide this > > to the bus, nobody else. > > No, Joerg. Any device that can become an initiator must supply > terminator power (so Simon must have more than one device with > TERMPWR to meet the letter of the spec). Other devices can as long > as they don't exceed the total maximum current (which is huge - I > think it is something like 5 amps and is driven by regulatory > issues). The discussion is somewhere near the beginning of the > spec. I've got nothing but problems in the past by having disk supplying termpower, and since switched to leave this solely to the host adapter. Maybe these drives were faulty wrt. standard, i don't know. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Feb 19 12:10:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA15488 for freebsd-scsi-outgoing; Wed, 19 Feb 1997 12:10:25 -0800 (PST) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA15477 for ; Wed, 19 Feb 1997 12:10:16 -0800 (PST) Received: by iafnl.es.iaf.nl with UUCP id AA31778 (5.67b/IDA-1.5 for scsi@freebsd.org); Wed, 19 Feb 1997 21:09:23 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id TAA00702; Wed, 19 Feb 1997 19:40:09 +0100 (MET) From: Wilko Bulte Message-Id: <199702191840.TAA00702@yedi.iaf.nl> Subject: Re: About to go SCSI - advice? To: gilbertd@cs.man.ac.uk (David Alan Gilbert) Date: Wed, 19 Feb 1997 19:40:09 +0100 (MET) Cc: dufault@hda.com, scsi@freebsd.org In-Reply-To: <9702191255.AA22930@amu7.cs.man.ac.uk> from "David Alan Gilbert" at Feb 19, 97 12:55:58 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As David Alan Gilbert wrote... > > Peter spoke thus: > > > No, Joerg. Any device that can become an initiator must supply > > terminator power (so Simon must have more than one device with > > TERMPWR to meet the letter of the spec). Other devices can as long > > as they don't exceed the total maximum current (which is huge - I > > think it is something like 5 amps and is driven by regulatory This highly depends on what you use for the SCSI bus. I've seen eh hum interesting things happen with 6 SCSI devices all feeding TERMPWR to a single printed circuit backplane that got shorted. All devices are fused with 1 or 1.5 Amps. Printed wiring does not like that (and most likely ribbon cable also has problems). > > My intuitive opinion is that the host adapter and the devices at > > either end of the chain should provide TERMPWR. > > Our problem originally started when we found a device which wouldn't > work (at all - wouldn't even respond to identify) unless it had Some harddrives need termpower to start spinning. > termpwr when it was switched on; so you had to switch the source of > termpwr on first and then the drive. > > 50% of the SCSI users in the world say you should have 1 term power device, At least one, being the initiator as per SCSI-2 standard. > 50% of the SCSI users say that you can have as many as you like, > and the other 80% say termpwr - what? See the shorting issue. > To make life bareable we turned termpwr on on that drive enabling it to > be switched on; but the docs with our Adaptec don't say >ANYTHING< > about termpower - they don't say where the fuse is, how to turn it on/off, > whether it should be on/off etc. Newer cards tend to have self-restoring fuses. Look for small obscure metal thingy (approx 0.4" square). That might be it. Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-scsi Fri Feb 21 09:29:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA06901 for freebsd-scsi-outgoing; Fri, 21 Feb 1997 09:29:32 -0800 (PST) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA06893; Fri, 21 Feb 1997 09:29:29 -0800 (PST) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.3/8.8.3) with SMTP id MAA12188; Fri, 21 Feb 1997 12:39:03 -0500 (EST) Message-Id: <3.0.1.32.19970221121819.00a5f1c0@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Fri, 21 Feb 1997 12:18:19 -0500 To: questions@freebsd.org From: Mike Tancsa Subject: New SCSI card... Old HD.. Cc: scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am going to be adding a NCR based SCSI controller to our news machine to take some of the load off the 2940 thats in there and also to allow us to add another disk. My question is, will I have to low level format the drive that is currently being used on the Adaptec ? If so, what are the procedures for it... The new SCSI card is just a ASUS 200 (NCR 810), so I doubt it has too many smarts in it in terms of disk formatting etc... ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatre (http://www.sentex.net/~mdtancsa) * From owner-freebsd-scsi Fri Feb 21 09:59:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA09473 for freebsd-scsi-outgoing; Fri, 21 Feb 1997 09:59:04 -0800 (PST) Received: from m1.cs.man.ac.uk (0@m1.cs.man.ac.uk [130.88.13.4]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA09468 for ; Fri, 21 Feb 1997 09:59:00 -0800 (PST) Received: from amu7.cs.man.ac.uk by m1.cs.man.ac.uk (4.1/SMI-4.1:AL6) id AA25160; Fri, 21 Feb 97 17:58:51 GMT Date: Fri, 21 Feb 97 17:58:57 GMT From: David Alan Gilbert Message-Id: <9702211758.AA25679@amu7.cs.man.ac.uk> To: scsi@freebsd.org Subject: SCSI error Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Well our nice new 4GB disc is humming along on our FreeBSD box. When I first mounted it I got: Feb 20 20:07:09 uriah /kernel: sd0(ahc0:0:0): Unexpected busfree. LASTPHASE == 0 xa0 Feb 20 20:07:19 uriah /kernel: sd0(ahc0:0:0): timed out in message out phase, SCS ISIGI == 0x0 Feb 20 20:07:19 uriah /kernel: SEQADDR == 0x0 Feb 20 20:07:19 uriah /kernel: sd0(ahc0:0:0): abort message in message buffer it sat there for a few seconds and its been fine ever since. I get the feeling its running a bit slowly 3.5MB a second ish writing - which I reckon is slow for a Barracuda (15150N). Why did that happen? On a separate note we gave up using the fdisk and disklabel commands and used the nice programs on the installation disc. We kept getting write: read only file system and never figured out how to get rid of it. The fdisk and disklabel programs are individually arcane; when used together they are just stupid. Is the partitioning utility from the installation disc available for use on a running system? Dave From owner-freebsd-scsi Fri Feb 21 10:29:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA11022 for freebsd-scsi-outgoing; Fri, 21 Feb 1997 10:29:03 -0800 (PST) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA11017; Fri, 21 Feb 1997 10:28:56 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-47.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA08212 (5.67b/IDA-1.5); Fri, 21 Feb 1997 19:28:52 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id TAA16338; Fri, 21 Feb 1997 19:28:50 +0100 (CET) Message-Id: <19970221192849.EM46969@x14.mi.uni-koeln.de> Date: Fri, 21 Feb 1997 19:28:49 +0100 From: se@freebsd.org (Stefan Esser) To: mike@sentex.net (Mike Tancsa) Cc: questions@freebsd.org, scsi@freebsd.org Subject: Re: New SCSI card... Old HD.. References: <3.0.1.32.19970221121819.00a5f1c0@sentex.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 In-Reply-To: <3.0.1.32.19970221121819.00a5f1c0@sentex.net>; from Mike Tancsa on Feb 21, 1997 12:18:19 -0500 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Feb 21, mike@sentex.net (Mike Tancsa) wrote: > > I am going to be adding a NCR based SCSI controller to our news machine to > take some of the load off the 2940 thats in there and also to allow us to > add another disk. My question is, will I have to low level format the > drive that is currently being used on the Adaptec ? If so, what are the > procedures for it... The new SCSI card is just a ASUS 200 (NCR 810), so I > doubt it has too many smarts in it in terms of disk formatting etc... The NCR will accept your drives as they are. Just mount the file systems ... Regards, STefan From owner-freebsd-scsi Fri Feb 21 10:54:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA12915 for freebsd-scsi-outgoing; Fri, 21 Feb 1997 10:54:59 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA12909; Fri, 21 Feb 1997 10:54:58 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id KAA00717 ; Fri, 21 Feb 1997 10:54:43 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA03098; Fri, 21 Feb 1997 19:53:05 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id TAA03197; Fri, 21 Feb 1997 19:47:49 +0100 (MET) Message-ID: Date: Fri, 21 Feb 1997 19:47:48 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: mike@sentex.net (Mike Tancsa) Cc: questions@freebsd.org, scsi@freebsd.org Subject: Re: New SCSI card... Old HD.. References: <3.0.1.32.19970221121819.00a5f1c0@sentex.net> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3.0.1.32.19970221121819.00a5f1c0@sentex.net>; from Mike Tancsa on Feb 21, 1997 12:18:19 -0500 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Mike Tancsa wrote: > I am going to be adding a NCR based SCSI controller to our news machine to > take some of the load off the 2940 thats in there and also to allow us to > add another disk. My question is, will I have to low level format the > drive that is currently being used on the Adaptec ? If so, what are the > procedures for it... The new SCSI card is just a ASUS 200 (NCR 810), so I > doubt it has too many smarts in it in terms of disk formatting etc... . You never need to low-level format a SCSI drive because of another controller. Almost the only reason that might you considering a low-level formatting is too many bad blocks (in order to restructure the drive). . You can always use /sbin/scsiformat to low-level format a drive, no need for stinkin' BIOS functions. :) . The worst that could happen is that you gotta revamp your fdisk table on the drive (if you're using one). However, i think the NCR BIOS does a good job in detecting the previously used geometry, and adapting its own geometry translation values to it. . Even in this case, you could get away without any restructuring in two cases: you've been using ``dangerously dedicated'' mode, or you are willing to fiddle with the C/H/S values in your fdisk table. For the latter, you basically gotta pick the offset and total number of sectors of your fdisk slice, and recalculate the beginning C/H/S values according to the geometry translation method of you controller. This will usually leave you with `odd' figures (the slice seems to start ``inmidst a track''), but i know that it works. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sat Feb 22 05:50:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA17180 for freebsd-scsi-outgoing; Sat, 22 Feb 1997 05:50:53 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id FAA17175 for ; Sat, 22 Feb 1997 05:50:49 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA24634; Sat, 22 Feb 1997 14:50:35 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.6.9) id OAA07104; Sat, 22 Feb 1997 14:45:54 +0100 (MET) Message-ID: Date: Sat, 22 Feb 1997 14:45:53 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: gilbertd@cs.man.ac.uk (David Alan Gilbert) Cc: scsi@FreeBSD.ORG Subject: Re: SCSI error References: <9702211758.AA25679@amu7.cs.man.ac.uk> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9702211758.AA25679@amu7.cs.man.ac.uk>; from David Alan Gilbert on Feb 21, 1997 17:58:57 +0000 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As David Alan Gilbert wrote: > On a separate note we gave up using the fdisk and disklabel commands and > used the nice programs on the installation disc. We kept getting > > write: read only file system > > and never figured out how to get rid of it. Do you have old junk in your fdisk table? The slice code can sometimes return EROFS if it means to protect you from clobbering non-FreeBSD slices. > The fdisk and disklabel programs are individually arcane; when used together > they are just stupid. Is the partitioning utility from the installation > disc available for use on a running system? /stand/sysinstall However, it's been reported to not always do a good job when using it standalone. Btw., fdisk is only needed for disks that are about to be shared with other systems (or if you need more than 7 partitions). You can safely skip this step, and infact, i never use it myself. If your disk contains old junk at the beginning, you can wipe it first with something like dd if=/dev/zero of=/dev/rsdX count=100 (The 100 is overkill.) For a plain BSD disk, i prefer: disklabel -Brw sdX auto disklabel -e sdX That's about all there is to be for a BSD-only disk. You might think of it being arcane, but i wouldn't bother to fire off sysinstall for these three command lines. :-) (Sure, i have to calculate some partition offsets manually, but since i usually use multiples of 100000 blocks, that's no big deal.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)