From owner-freebsd-scsi Fri Jan 1 02:21:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25588 for freebsd-scsi-outgoing; Fri, 1 Jan 1999 02:21:05 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25583 for ; Fri, 1 Jan 1999 02:21:03 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id LAA00530 for scsi@FreeBSD.ORG; Fri, 1 Jan 1999 11:20:40 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id LAA09065; Fri, 1 Jan 1999 11:19:53 +0100 (MET) (envelope-from j) Message-ID: <19990101111952.22869@uriah.heep.sax.de> Date: Fri, 1 Jan 1999 11:19:52 +0100 From: J Wunsch To: scsi@FreeBSD.ORG Subject: Re: DDS alternative Reply-To: Joerg Wunsch References: <199812311825.NAA38381@whizzo.transsys.com> <199812311924.UAA18718@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199812311924.UAA18718@yedi.iaf.nl>; from Wilko Bulte on Thu, Dec 31, 1998 at 08:24:11PM +0100 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 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Wilko Bulte wrote: > > The media is pretty cost-effective, which you should be sure to take > > into account when comparing the alternatives. > > Ever tried to read a tape written a year ago? I've heared to much horror > stories about unreadable DAT tapes to trust them... DDS media interchangeability between different devices (of different vintage and vendor) has also proven to be a problem for us. We've been using DDS until recently in the company for daily backups (with rotating tapes, in case a single one fails), and are using DLT now. We're happy about the switch, it gives us a much warmer feeling. -- 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. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 1 03:43:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01205 for freebsd-scsi-outgoing; Fri, 1 Jan 1999 03:43:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01200 for ; Fri, 1 Jan 1999 03:43:52 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id MAA12492; Fri, 1 Jan 1999 12:30:14 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA03485 (5.67b/IDA-1.5); Fri, 1 Jan 1999 12:12:57 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id MAA27219; Fri, 1 Jan 1999 12:03:13 +0100 (CET) From: Wilko Bulte Message-Id: <199901011103.MAA27219@yedi.iaf.nl> Subject: Re: DDS alternative In-Reply-To: <19990101113324.Z39598@freebie.lemis.com> from Greg Lehey at "Jan 1, 99 11:33:24 am" To: grog@lemis.com (Greg Lehey) Date: Fri, 1 Jan 1999 12:03:13 +0100 (CET) Cc: louie@TransSys.COM, joerg_wunsch@uriah.heep.sax.de, scsi@FreeBSD.ORG, skynyrd@opus.cts.cwu.edu X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Greg Lehey wrote... > On Thursday, 31 December 1998 at 20:24:11 +0100, Wilko Bulte wrote: > > As Louis A. Mamakos wrote... > >>> As Chris Timmons wrote: > >>> > >>>> What sort of FreeBSD compatible HW do you recommend in lieue of DDS > >>>> tape? [snip] > >> The media is pretty cost-effective, which you should be sure to take > >> into account when comparing the alternatives. > > > > Ever tried to read a tape written a year ago? > > Frequently. I read tapes written 5 years ago. That's the part that > works :-) Then you should not complain.. > > I've heared to much horror stories about unreadable DAT tapes to > > trust them... > > The trouble I have (and continue to have) is that the things have > such a short life. I used to do a complete backup (4 hours tape > motion) every night. Under those circumstances, the old DDS-1 drives > lasted about 6 months, and the DDS-2 last about 18 months. That is the 'glorified consumer product' side of DAT drives. They are not really designed for heavy duty use. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 1 20:51:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08780 for freebsd-scsi-outgoing; Fri, 1 Jan 1999 20:51:38 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08775 for ; Fri, 1 Jan 1999 20:51:36 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA45144; Fri, 1 Jan 1999 21:51:06 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901020451.VAA45144@panzer.plutotech.com> Subject: Re: cdrecord - write failures / 2.2.8-stable / cdrecord 1.6.1 In-Reply-To: <19981230153949.A65181@paert.tse-online.de> from Andreas Braukmann at "Dec 30, 98 03:39:49 pm" To: braukmann@tse-online.de (Andreas Braukmann) Date: Fri, 1 Jan 1999 21:51:06 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andreas Braukmann wrote... > Hi, > > during the last months I've used cdrecord 1.6 without any problems > on my 2.2-stable (from a few days before 2.2.8-release) system > (no-cam, Plextor-Writer). > Yesterday I brought it to the latest 2.2.8-stable (cvsup). > Afterwards I've tried to write some CDRs (media: Kodak CD-R) > with no success: > Each time I got the following: > > [...] [ various errors from cdrecord ] > I suppose that these are some kind of real errors on the media? > The CDRs were all from the same bunch of 100. > Happily I found some left over CDRs (same brand) from our last > burning session and tried a few of them. Interestingly enough I was > able to burn them without a hitch. > Aftwerwards I gave another few from the fresh bunch a try, to no success. > (exactly the same error, again) > > Any hints? > Should I just "slap the just bought media into the distributor's face" ? ;) I'm not sure which Plextor CD-R you have, but if you've got the 4/12 Max, (burns CD-R's at 4X speed), make sure you have at least firmware revision 1.04. I've heard (from folks on the 'net, and Plextor tech support) that there are problems with the 1.03 firmware. I upgraded mine to version 1.04 of the firmware, and haven't had any trouble with it. That said, it does sound like you might have a media problem. I would suggest talking to Joerg Schilling , the author of cdrecord. Make sure you include the full output from your cdrecord session, and the brand/type information on the CD-R blanks that did and didn't work. Maybe you got a bad batch or something. It'll probably take someone more knowledgeable about CD-R's (e.g. Joerg) to figure it out. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 1 21:20:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10920 for freebsd-scsi-outgoing; Fri, 1 Jan 1999 21:20:17 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10915 for ; Fri, 1 Jan 1999 21:20:15 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id AAA19127; Sat, 2 Jan 1999 00:18:30 -0500 (EST) Date: Sat, 2 Jan 1999 00:18:30 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Greg Lehey cc: Wilko Bulte , "Louis A. Mamakos" , joerg_wunsch@uriah.heep.sax.de, scsi@FreeBSD.ORG, skynyrd@opus.cts.cwu.edu Subject: Re: DDS alternative In-Reply-To: <19990101113324.Z39598@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We just switched to AIT drives. So far so good, has anyone run into problems with those? The lifespan is supposed to be very comparable to DLT, and the seek time is excellent... Charles On Fri, 1 Jan 1999, Greg Lehey wrote: > Frequently. I read tapes written 5 years ago. That's the part that > works :-) > > > I've heared to much horror stories about unreadable DAT tapes to > > trust them... > > The trouble I have (and continue to have) is that the things have > such a short life. I used to do a complete backup (4 hours tape > motion) every night. Under those circumstances, the old DDS-1 drives > lasted about 6 months, and the DDS-2 last about 18 months. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 1 22:54:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17677 for freebsd-scsi-outgoing; Fri, 1 Jan 1999 22:54:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from amerasu.brel.com (amerasu.brel.com [203.127.231.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17658; Fri, 1 Jan 1999 22:54:42 -0800 (PST) (envelope-from calvinng@brel.com) Received: from localhost (calvinng@localhost) by amerasu.brel.com (8.8.8/8.8.8) with ESMTP id PAA24667; Sat, 2 Jan 1999 15:03:28 +0800 (SGT) (envelope-from calvinng@brel.com) Date: Sat, 2 Jan 1999 15:03:28 +0800 (SGT) From: Calvin NG To: scsi@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: NetFinity 5500-41U, cannot detect SCSI controller Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, Hi there. What a way to start a new year. If it is a sin to cross-post, I beg your forgiveness, but feeling a bit desperate here. problem: Just got the above mentioned hardware, been trying to install 3.0 on it. Tried with the normal floppy boot-image, and then the CAM boot-floppy, but both was not able to detect the on-board SCSI controller. background: According to the hardware specs, the SCSI controller is a IBM PCI ServRAID-3H/3L wide fast SCSI2, whatever that means. I opened up the cover to take a peek inside, saw two Adaptec AIC7880P chips in there. I tried fiddling with the BIOS setup, and the SCSI controller has been assigned interupt 11, but it does not help. BTW, the PCI bus are mostly Plug-and-Play, does it matter??? my take: The way I look at it, IBM probably uses its own BIOS, causing the Adaptec not to respond to the hardware probe. What do you think. Or I shouldn't assume that a adaptec chipset means it will defintely work. Or am I missing something entirely, such as the APM (power mgmt), or USB controller, both of which are detected. greetings: Seasons Greetings to you, Wishing You a Peaceful and Merry X'Mas and a Rewarding and Happy New Year! Regards, /calvin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 1 23:04:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18535 for freebsd-scsi-outgoing; Fri, 1 Jan 1999 23:04:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles354.castles.com [208.214.167.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18490; Fri, 1 Jan 1999 23:03:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA57322; Fri, 1 Jan 1999 23:00:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901020700.XAA57322@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Calvin NG cc: scsi@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: NetFinity 5500-41U, cannot detect SCSI controller In-reply-to: Your message of "Sat, 02 Jan 1999 15:03:28 +0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Jan 1999 23:00:41 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Greetings, > > Hi there. What a way to start a new year. > If it is a sin to cross-post, I beg your forgiveness, but feeling > a bit desperate here. > > problem: > Just got the above mentioned hardware, been trying to install 3.0 > on it. Tried with the normal floppy boot-image, and then the CAM > boot-floppy, but both was not able to detect the on-board > SCSI controller. > > background: > According to the hardware specs, the SCSI controller is a IBM > PCI ServRAID-3H/3L wide fast SCSI2, whatever that means. > I opened up the cover to take a peek inside, saw two Adaptec > AIC7880P chips in there. The ServeRAID controller is not supported, as explicitly noted in the FreeBSD-3.0 release notes. The controller uses the Adaptec chips internally, but these are not (AFAIK) available directly to the host system. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 2 00:12:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24253 for freebsd-scsi-outgoing; Sat, 2 Jan 1999 00:12:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24248 for ; Sat, 2 Jan 1999 00:12:52 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.89]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA4061; Sat, 2 Jan 1999 09:11:39 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 02 Jan 1999 09:18:38 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: mjacob@feral.com Subject: RE: AIC microcode problem? Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30-Dec-98 Matthew Jacob wrote: > > > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x151 > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x151 Last time I had this problem, one of my drive's SCSI interfaces was dying (yes Kenneth, it died on the 31st and I am replacing it today, and hopefully with a Seagate). Ye might also want to verify yer termination. --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 2 01:52:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00820 for freebsd-scsi-outgoing; Sat, 2 Jan 1999 01:52:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00814 for ; Sat, 2 Jan 1999 01:52:19 -0800 (PST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id KAA21626; Sat, 2 Jan 1999 10:51:49 +0100 (MET) Received: (from ticso@localhost) by cicely7.cicely.de (8.9.0/8.9.0) id KAA00515; Sat, 2 Jan 1999 10:51:38 +0100 (CET) Message-ID: <19990102105138.35033@cicely.de> Date: Sat, 2 Jan 1999 10:51:38 +0100 From: Bernd Walter To: freebsd-scsi@FreeBSD.ORG, grog@lemis.com Subject: new Quirk candidate and vinum behavour Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have had one of my hosts crashed sometime. Today I got a crash after setting logs to another volume: Jan 2 03:30:16 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 Jan 2 03:30:18 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 Jan 2 03:30:32 cicely7 syslogd: /var/log/messages: Input/output error Jan 2 03:30:32 cicely7 syslogd: /var/log/all.log: Input/output error Jan 2 03:30:32 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET Jan 2 03:30:32 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x0 Jan 2 03:30:32 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 1 SCBs aborted Jan 2 03:30:32 cicely7 /kernel: vinum: subdisk var.p0.s0 is crashed Jan 2 03:30:32 cicely7 /kernel: vinum: plex var.p0 is degraded Jan 2 03:30:32 cicely7 /kernel: vinum: subdisk var.p0.s0 is stale Jan 2 03:30:32 cicely7 /kernel: vinum: plex var.p0 is down Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET Jan 2 03:30:48 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 Jan 2 03:30:48 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 31 SCBs aborted Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET Jan 2 03:30:48 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 Jan 2 03:30:48 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 31 SCBs aborted Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET Jan 2 03:30:48 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 Jan 2 03:30:48 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 31 SCBs aborted Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET Jan 2 03:30:49 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x0, SEQ_FLAGS == 0x40 Jan 2 03:30:49 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 16 SCBs aborted Jan 2 03:31:04 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 Jan 2 03:31:04 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET Jan 2 03:31:04 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 Jan 2 03:31:04 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 32 SCBs aborted Jan 2 03:31:04 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 Jan 2 03:31:33 cicely7 sendmail[810]: DAA00810: SYSERR(root): collect: Cannot write tfDAA00810: Input/output error Jan 2 03:31:33 cicely7 syslogd: /var/log/maillog: Input/output error Jan 2 03:31:33 cicely7 sendmail[810]: DAA00810: SYSERR(root): Error writing control file tfDAA00810: Input/output error Jan 2 03:31:33 cicely7 sendmail[2798]: NOQUEUE: SYSERR(root): queuename: Cannot create "qfDAA02798" in "/var/spool/mqueue" (euid=0) : Input/output error Jan 2 03:31:33 cicely7 syslogd: /var/cron/log: Input/output error Jan 2 03:42:41 cicely7 /kernel: spec_getpages: I/O read failure: (error code=5) Jan 2 03:42:41 cicely7 /kernel: size: 36864, resid: 36864, a_count: 36864, valid: 0x0 Jan 2 03:42:41 cicely7 /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 9 Jan 2 03:42:41 cicely7 /kernel: vm_fault: pager read error, pid 250 (sshd1) Jan 2 03:42:41 cicely7 last message repeated 23 times Jan 2 03:42:41 cicely7 /kernel: vm_fault: p and so on ... As you can see the host was not realy crashed but unuseable after it happened. The Problem with da0:ahc0:0:1:0 happens every time the tagged openings are increased The side effect is that I'm now running /var on a vinum volume on da1 and da2 which are drives on the same channel and it looks like the bdr or anything between the tag increase and the bdr is the reason for the subdisk crash. root@cicely7# dmesg Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sun Dec 20 13:55:04 CET 1998 root@cicely5.cicely.de:/usr/src/sys/compile/CICELY7 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 90205005 Hz CPU: Pentium/P54C (90.21-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 67108864 (65536K bytes) config> quit avail memory = 62066688 (60612K bytes) Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ahc0: rev 0x00 int a irq 5 on pci0.8.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 5 on pci0.9.0 ahc1: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs vga0: rev 0x00 on pci0.10.0 de0: rev 0x20 int a irq 5 on pci0.11.0 de0: Cogent 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:92:9b:31:51 Probing for devices on the ISA bus: video#0: WARNING: video mode switching is not fully supported on this adapter sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 7 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 11 on isa sio2: type 16550A sio3: configured irq 12 not in bitmap of probed irqs 0 sio3 at 0x2e8-0x2ef irq 12 on isa sio3: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): , removable atapi0.0: unknown phase wdc0: unit 1 (atapi): , removable, intr, iordis wcd1: 689KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray wcd1: 120mm data disc loaded, unlocked wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 1536MB (3145968 sectors), 3121 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround Waiting 15 seconds for SCSI devices to settle (probe15:ahc1:0:0:0): Sending SDTR!! (probe19:ahc1:0:4:0): Sending SDTR!! da3 at ahc1 bus 0 target 0 lun 0 da3: Fixed Direct Access SCSI2 device da3: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da3: 1665MB (3409965 512 byte sectors: 64H 32S/T 1665C) da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 1030MB (2110812 512 byte sectors: 64H 32S/T 1030C) cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 4.237MB/s transfers (4.237MHz, offset 15) cd0: cd present [270169 x 2048 byte records] da2 at ahc0 bus 0 target 4 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da2: 2006MB (4110000 512 byte sectors: 64H 32S/T 2006C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2006MB (4110000 512 byte sectors: 64H 32S/T 2006C) da4 at ahc1 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI2 device da4: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da4: 1665MB (3409965 512 byte sectors: 64H 32S/T 1665C) changing root device to da0s1a de0: autosense failed: cable problem? vinum: loaded vinum: drive cuda1 is up vinum: drive cuda2 is up vinum: drive fujitsu1 is up vinum: drive fujitsu2 is up vinum: subdisk var.p0.s0 is up vinum: subdisk var.p0.s1 is up vinum: subdisk news.p0.s0 is up vinum: subdisk news.p0.s1 is up vinum: plex var.p0 is up vinum: plex news.p0 is up vinum: volume var is up vinum: volume news is up WARNING: R/W mount of /var denied. Filesystem is not clean - run fsck de0: enabling 100baseTX port de0: enabling Full Duplex 100baseTX port root@cicely7# cat /etc/vinum.conf drive cuda1 device /dev/da1e drive cuda2 device /dev/da2e drive fujitsu1 device /dev/da3e drive fujitsu2 device /dev/da4e volume var setupstate plex org striped 128b sd length 4108000b drive cuda1 sd length 4108000b drive cuda2 volume news setupstate plex org striped 128b sd length 3402065b drive fujitsu1 sd length 3402065b drive fujitsu2 -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 2 02:26:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02939 for freebsd-scsi-outgoing; Sat, 2 Jan 1999 02:26:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02929 for ; Sat, 2 Jan 1999 02:26:44 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id UAA22976; Sat, 2 Jan 1999 20:55:50 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id UAA66483; Sat, 2 Jan 1999 20:55:53 +1030 (CST) Message-ID: <19990102205553.G66110@freebie.lemis.com> Date: Sat, 2 Jan 1999 20:55:53 +1030 From: Greg Lehey To: Bernd Walter , freebsd-scsi@FreeBSD.ORG Subject: Re: new Quirk candidate and vinum behavour References: <19990102105138.35033@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19990102105138.35033@cicely.de>; from Bernd Walter on Sat, Jan 02, 1999 at 10:51:38AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Saturday, 2 January 1999 at 10:51:38 +0100, Bernd Walter wrote: > > I have had one of my hosts crashed sometime. > Today I got a crash after setting logs to another volume: > > Jan 2 03:30:16 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > Jan 2 03:30:18 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 > Jan 2 03:30:32 cicely7 syslogd: /var/log/messages: Input/output error > Jan 2 03:30:32 cicely7 syslogd: /var/log/all.log: Input/output error > Jan 2 03:30:32 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > Jan 2 03:30:32 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x0 > Jan 2 03:30:32 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 1 SCBs aborted > Jan 2 03:30:32 cicely7 /kernel: vinum: subdisk var.p0.s0 is crashed > Jan 2 03:30:32 cicely7 /kernel: vinum: plex var.p0 is degraded > Jan 2 03:30:32 cicely7 /kernel: vinum: subdisk var.p0.s0 is stale > Jan 2 03:30:32 cicely7 /kernel: vinum: plex var.p0 is down > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 > Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > Jan 2 03:30:48 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 > Jan 2 03:30:48 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 31 SCBs aborted > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 > Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > Jan 2 03:30:48 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 > Jan 2 03:30:48 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 31 SCBs aborted > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 > Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > Jan 2 03:30:48 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 > Jan 2 03:30:48 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 31 SCBs aborted > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 > Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > Jan 2 03:30:49 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x0, SEQ_FLAGS == 0x40 > Jan 2 03:30:49 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 16 SCBs aborted > Jan 2 03:31:04 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > Jan 2 03:31:04 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > Jan 2 03:31:04 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 > and so on ... > > As you can see the host was not realy crashed but unuseable after it > happened. The Problem with da0:ahc0:0:1:0 happens every time the > tagged openings are increased The side effect is that I'm now > running /var on a vinum volume on da1 and da2 which are drives on > the same channel and it looks like the bdr or anything between the > tag increase and the bdr is the reason for the subdisk crash. On the face of it, of course, this is a SCSI problem, not a Vinum problem. Vinum reacted correctly to the error (this time :-). But we've seen a surprising number of this kind of problem in connection with Vinum, and I think the reason is that Vinum tickles otherwise unseen hardware problems in SCSI chains. It's quite common for Vinum to issue a series of I/O commands on a number of devices on a chain (for example, with striped or RAID-5 volumes which require accessing several drives at a time for a single user request). You might like to set debug flag 1: vinum -> debug 1 This will log to syslogd details of all transfers; in combination with the log you show, it might help the SCSI guys figure out where things are happening. But I have a suspicion that the real problem is hardware (less than perfect SCSI chain, for whatever reason) rather than software. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 2 07:09:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24379 for freebsd-scsi-outgoing; Sat, 2 Jan 1999 07:09:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24369 for ; Sat, 2 Jan 1999 07:09:22 -0800 (PST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id QAA06973; Sat, 2 Jan 1999 16:05:55 +0100 (MET) Received: (from ticso@localhost) by cicely7.cicely.de (8.9.0/8.9.0) id QAA01396; Sat, 2 Jan 1999 16:08:29 +0100 (CET) Message-ID: <19990102160829.32955@cicely.de> Date: Sat, 2 Jan 1999 16:08:29 +0100 From: Bernd Walter To: Greg Lehey , freebsd-scsi@FreeBSD.ORG Subject: Re: new Quirk candidate and vinum behavour References: <19990102105138.35033@cicely.de> <19990102205553.G66110@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19990102205553.G66110@freebie.lemis.com>; from Greg Lehey on Sat, Jan 02, 1999 at 08:55:53PM +1030 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jan 02, 1999 at 08:55:53PM +1030, Greg Lehey wrote: > On Saturday, 2 January 1999 at 10:51:38 +0100, Bernd Walter wrote: > > > > I have had one of my hosts crashed sometime. > > Today I got a crash after setting logs to another volume: > > > > Jan 2 03:30:16 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > > Jan 2 03:30:18 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 > > Jan 2 03:30:32 cicely7 syslogd: /var/log/messages: Input/output error > > Jan 2 03:30:32 cicely7 syslogd: /var/log/all.log: Input/output error > > Jan 2 03:30:32 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > > Jan 2 03:30:32 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x0 > > Jan 2 03:30:32 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 1 SCBs aborted > > Jan 2 03:30:32 cicely7 /kernel: vinum: subdisk var.p0.s0 is crashed > > Jan 2 03:30:32 cicely7 /kernel: vinum: plex var.p0 is degraded > > Jan 2 03:30:32 cicely7 /kernel: vinum: subdisk var.p0.s0 is stale > > Jan 2 03:30:32 cicely7 /kernel: vinum: plex var.p0 is down > > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 > > Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > > Jan 2 03:30:48 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 > > Jan 2 03:30:48 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 31 SCBs aborted > > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 > > Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > > Jan 2 03:30:48 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 > > Jan 2 03:30:48 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 31 SCBs aborted > > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 > > Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > > Jan 2 03:30:48 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 > > Jan 2 03:30:48 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 31 SCBs aborted > > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > > Jan 2 03:30:48 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 31 > > Jan 2 03:30:48 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > > Jan 2 03:30:49 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x0, SEQ_FLAGS == 0x40 > > Jan 2 03:30:49 cicely7 /kernel: ahc0: Bus Device Reset on A:1. 16 SCBs aborted > > Jan 2 03:31:04 cicely7 /kernel: (da0:ahc0:0:1:0): tagged openings now 32 > > Jan 2 03:31:04 cicely7 /kernel: ahc0:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > > Jan 2 03:31:04 cicely7 /kernel: SAVED_TCL == 0x10, ARG_1 == 0x20, SEQ_FLAGS == 0x40 > > and so on ... > > > > As you can see the host was not realy crashed but unuseable after it > > happened. The Problem with da0:ahc0:0:1:0 happens every time the > > tagged openings are increased The side effect is that I'm now > > running /var on a vinum volume on da1 and da2 which are drives on > > the same channel and it looks like the bdr or anything between the > > tag increase and the bdr is the reason for the subdisk crash. > > On the face of it, of course, this is a SCSI problem, not a Vinum > problem. Vinum reacted correctly to the error (this time :-). But Which error? > we've seen a surprising number of this kind of problem in connection > with Vinum, and I think the reason is that Vinum tickles otherwise > unseen hardware problems in SCSI chains. It's quite common for Vinum The SCSI-Chain is OK and even the power suply :) > to issue a series of I/O commands on a number of devices on a chain > (for example, with striped or RAID-5 volumes which require accessing What I mean is that da0 has problems with the tag increasing - they are directly after it each time - looks much like often discussed Firmware problems. No problems without increasing and no problems after. That's point one and there's no doubt about the reason. da1 and da2 are on the same chain and hold /var so they are accesed to write logs. No reason for errors on da1 and da2 since only a BDR happend. No errors on da1 and da2 are logged. vinum marks var.p0.s0 as crashed without any logged error from one of the drives. > several drives at a time for a single user request). You might like > to set debug flag 1: Not good on this host - logfiles are writen to a vinum drive, because the da0 don't write very well in the error condition and all other disks a striped > > vinum -> debug 1 > > This will log to syslogd details of all transfers; in combination with > the log you show, it might help the SCSI guys figure out where things > are happening. But I have a suspicion that the real problem is > hardware (less than perfect SCSI chain, for whatever reason) rather > than software. > -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 2 07:39:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26072 for freebsd-scsi-outgoing; Sat, 2 Jan 1999 07:39:40 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26060 for ; Sat, 2 Jan 1999 07:39:37 -0800 (PST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id QAA07669; Sat, 2 Jan 1999 16:36:12 +0100 (MET) Received: (from ticso@localhost) by cicely7.cicely.de (8.9.0/8.9.0) id QAA01452; Sat, 2 Jan 1999 16:38:45 +0100 (CET) Message-ID: <19990102163844.38818@cicely.de> Date: Sat, 2 Jan 1999 16:38:44 +0100 From: Bernd Walter To: Greg Lehey , freebsd-scsi@FreeBSD.ORG Subject: Re: new Quirk candidate and vinum behavour References: <19990102105138.35033@cicely.de> <19990102205553.G66110@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19990102205553.G66110@freebie.lemis.com>; from Greg Lehey on Sat, Jan 02, 1999 at 08:55:53PM +1030 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jan 02, 1999 at 08:55:53PM +1030, Greg Lehey wrote: > On Saturday, 2 January 1999 at 10:51:38 +0100, Bernd Walter wrote: > > > > I have had one of my hosts crashed sometime. > > Today I got a crash after setting logs to another volume: > > > > vinum -> debug 1 > I forgot that damned IDE-Drive. It's turned on now - let's wait for next failure. -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 2 09:42:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06181 for freebsd-scsi-outgoing; Sat, 2 Jan 1999 09:42:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hyper.activeisp.com (hyper.activeisp.com [195.139.101.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06170 for ; Sat, 2 Jan 1999 09:42:45 -0800 (PST) (envelope-from erik@habatech.no) Received: from smtp.activeisp.com (inter.activeisp.com [195.139.101.100]) by hyper.activeisp.com (2.5 Build 2639 (Berkeley 8.8.6)/8.8.4) with ESMTP id SAA03486; Sat, 02 Jan 1999 18:44:48 +0100 Received: from erik ([130.67.197.193]) by smtp.activeisp.com with Microsoft SMTPSVC(5.5.1877.977.9); Sat, 2 Jan 1999 18:39:32 +0100 Message-ID: <017201be3676$cfdd72f0$1b08a8c0@erik.habatech.no> From: "Erik Haugen Bakke" To: , " - (052)scsi(a)FreeBSD.ORG" Subject: SV: Can FreeBSD boot from a 18 GB SCSI harddisk ? Date: Sat, 2 Jan 1999 18:31:28 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA06177 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >an ASUS P2B-S ( or LS) board which contains an >AIC 7890 chip on board, could I install FreeBSD on >BTW, I just heard this board has 2 SCSI connectors (one 50 and one 68). >Does this system have one or two SCSI channels ? The Adaptec 7890 Chip has only one channel, the 7895 (I believe) have two. The reason for this connector configuration is to allow you to connect both 8-bit and 16-bit devices at the same time. The two bus segments are electrically separate, so addition of 8-bit devices on the 50-pin connector will not reduce the speed of the 18-bit connector. >Is it then possible, to install an Ultra 2 Wide SCSI Harddisk like the Seagate >Cheetah or Barracuda on the wide connector and normal Narrow SCSI >Devices like CD-Rom and Tape on the other connector ??? Yes, I am using this configuration on some of my systems, a stack of U2W drives on the 68-pin connector, and a CD tower on the 50-pin. >So to say, can I mix 20 MHZ with 80 MHz SCSI devices ??? I guess you mean 80Mb/s :) And, yes you can. As the two bus segments are electrically separate, you can mix different clock frequencies, all the way up to the 40Mhz clock allowed by Ultra2. Note, however, that all devices on a bus segment will run on the highest clock that is supported by ALL devices, so be careful where you put your slow devices. Try to group them together on the 8-bit segment if you can. Hope this helps you --- Erik H. Bakke Habatech AS erik@habatech.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 2 10:43:59 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12902 for freebsd-scsi-outgoing; Sat, 2 Jan 1999 10:43:59 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12893 for ; Sat, 2 Jan 1999 10:43:56 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id TAA27131; Sat, 2 Jan 1999 19:30:17 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA05827 (5.67b/IDA-1.5); Sat, 2 Jan 1999 19:01:03 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id KAA10768; Sat, 2 Jan 1999 10:44:57 +0100 (CET) From: Wilko Bulte Message-Id: <199901020944.KAA10768@yedi.iaf.nl> Subject: Re: DDS alternative In-Reply-To: from spork at "Jan 2, 99 00:18:30 am" To: spork@super-g.com (spork) Date: Sat, 2 Jan 1999 10:44:57 +0100 (CET) Cc: grog@lemis.com, louie@TransSys.COM, joerg_wunsch@uriah.heep.sax.de, scsi@FreeBSD.ORG, skynyrd@opus.cts.cwu.edu X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As spork wrote... > We just switched to AIT drives. So far so good, has anyone run into > problems with those? The lifespan is supposed to be very comparable to > DLT, and the seek time is excellent... I've played with one once and it appears to work well. And it was very fast too. I can't comment on durability, but from looking at them I'd guess they are a whole lot better than DAT drives. Also the cartridges are more robust, as is the tape media. > Charles > > On Fri, 1 Jan 1999, Greg Lehey wrote: > > > Frequently. I read tapes written 5 years ago. That's the part that > > works :-) > > > > > I've heared to much horror stories about unreadable DAT tapes to > > > trust them... > > > > The trouble I have (and continue to have) is that the things have > > such a short life. I used to do a complete backup (4 hours tape > > motion) every night. Under those circumstances, the old DDS-1 drives > > lasted about 6 months, and the DDS-2 last about 18 months. > > > > Greg Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 2 15:39:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15077 for freebsd-scsi-outgoing; Sat, 2 Jan 1999 15:39:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15065 for ; Sat, 2 Jan 1999 15:39:02 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA25104; Sun, 3 Jan 1999 10:07:59 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA67835; Sun, 3 Jan 1999 10:08:03 +1030 (CST) Message-ID: <19990103100802.H66110@freebie.lemis.com> Date: Sun, 3 Jan 1999 10:08:02 +1030 From: Greg Lehey To: Wilko Bulte , spork Cc: louie@TransSys.COM, joerg_wunsch@uriah.heep.sax.de, scsi@FreeBSD.ORG, skynyrd@opus.cts.cwu.edu Subject: Re: DDS alternative References: <199901020944.KAA10768@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199901020944.KAA10768@yedi.iaf.nl>; from Wilko Bulte on Sat, Jan 02, 1999 at 10:44:57AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Saturday, 2 January 1999 at 10:44:57 +0100, Wilko Bulte wrote: > As spork wrote... >> On Fri, 1 Jan 1999, Greg Lehey wrote: >> >>> Frequently. I read tapes written 5 years ago. That's the part that >>> works :-) >>> >>>> I've heared to much horror stories about unreadable DAT tapes to >>>> trust them... >>> >>> The trouble I have (and continue to have) is that the things have >>> such a short life. I used to do a complete backup (4 hours tape >>> motion) every night. Under those circumstances, the old DDS-1 drives >>> lasted about 6 months, and the DDS-2 last about 18 months. >> >> We just switched to AIT drives. So far so good, has anyone run into >> problems with those? The lifespan is supposed to be very comparable to >> DLT, and the seek time is excellent... > > I've played with one once and it appears to work well. And it was very fast > too. I can't comment on durability, but from looking at them I'd guess they > are a whole lot better than DAT drives. Also the cartridges are more robust, > as is the tape media. Who makes these drives? I haven't heard of them, so I suspect they have some other name as well. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 2 15:53:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16334 for freebsd-scsi-outgoing; Sat, 2 Jan 1999 15:53:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles335.castles.com [208.214.167.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16314 for ; Sat, 2 Jan 1999 15:53:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01614; Sat, 2 Jan 1999 15:49:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901022349.PAA01614@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Wilko Bulte , spork , louie@TransSys.COM, joerg_wunsch@uriah.heep.sax.de, scsi@FreeBSD.ORG, skynyrd@opus.cts.cwu.edu Subject: Re: DDS alternative In-reply-to: Your message of "Sun, 03 Jan 1999 10:08:02 +1030." <19990103100802.H66110@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 Jan 1999 15:49:19 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> We just switched to AIT drives. So far so good, has anyone run into > >> problems with those? The lifespan is supposed to be very comparable to > >> DLT, and the seek time is excellent... > > > > I've played with one once and it appears to work well. And it was very fast > > too. I can't comment on durability, but from looking at them I'd guess they > > are a whole lot better than DAT drives. Also the cartridges are more robust, > > as is the tape media. > > Who makes these drives? I haven't heard of them, so I suspect they > have some other name as well. No, AIT drives are called just that. Sony are making them, Seagate are selling what looks like an OEM Sony mechanism (could be wrong there), and I *think* Exabyte are doing an AIT-compatible drive. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message