From owner-freebsd-scsi Fri Dec 28 2:15: 0 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from relay1.ntu-kpi.kiev.ua (www.ntu-kpi.kiev.ua [212.111.192.161]) by hub.freebsd.org (Postfix) with ESMTP id 1929F37B416 for ; Fri, 28 Dec 2001 02:14:55 -0800 (PST) Received: from comsys.ntu-kpi.kiev.ua (eth0.comsys.ntu-kpi.kiev.ua [10.0.1.184]) by relay1.ntu-kpi.kiev.ua (Postfix) with ESMTP id 73FD72EEC0 for ; Fri, 28 Dec 2001 12:14:51 +0200 (EET) Received: from pm5149 (pm514-9.comsys.ntu-kpi.kiev.ua [10.18.54.109]) by comsys.ntu-kpi.kiev.ua (8.11.6/8.11.6) with SMTP id fBSAGwF29435 for ; Fri, 28 Dec 2001 12:16:59 +0200 (EET) Message-ID: <005501c18f7f$62f61ec0$6d36120a@comsys.ntukpi.kiev.ua> From: "Andrey Simonenko" To: Subject: Error from SCSI hard disk, please explaine Date: Fri, 28 Dec 2001 12:09:41 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, My system (FreeBSD/i386 4.4-STABLE) begins to print following: Dec 26 02:05:33 lion /kernel: (da0:sym0:0:15:0): READ(06). CDB: 8 1b 60 7f 10 0 Dec 26 02:05:35 lion /kernel: (da0:sym0:0:15:0): MEDIUM ERROR info:1b607f asc:11,1 Dec 26 02:05:36 lion /kernel: (da0:sym0:0:15:0): Read retries exhausted sks:80,3f Dec 26 02:05:38 lion /kernel: (da0:sym0:0:15:0): READ(06). CDB: 8 1b 60 7f 10 0 Dec 26 02:05:38 lion /kernel: (da0:sym0:0:15:0): MEDIUM ERROR info:1b607f asc:11,1 Dec 26 02:05:38 lion /kernel: (da0:sym0:0:15:0): Read retries exhausted sks:80,3f Dec 26 02:05:42 lion /kernel: (da0:sym0:0:15:0): READ(06). CDB: 8 1d 60 8f 10 0 Dec 26 02:05:45 lion /kernel: (da0:sym0:0:15:0): MEDIUM ERROR info:1d608f asc:11,1 Can somebody explaine me what does it mean. This system was 18 days uptime and these messages first occurred two days ago. Here is some strings from /var/log/message: Dec 9 13:27:00 lion /kernel: sym0: <875> port 0x1400-0x14ff mem 0xfa200000-0xfa200fff,0xfa203000-0xfa2030ff irq 11 at device 13.0 on pci0 Dec 9 13:27:00 lion /kernel: sym0: No NVRAM, ID 7, Fast-20, SE, parity checking Dec 9 13:27:00 lion /kernel: sym1: <875> port 0x1800-0x18ff mem 0xfa201000-0xfa201fff,0xfa203400-0xfa2034ff irq 10 at device 13.1 on pci0 Dec 9 13:27:00 lion /kernel: sym1: No NVRAM, ID 7, Fast-20, SE, parity checking Dec 9 13:27:01 lion /kernel: da0 at sym0 bus 0 target 15 lun 0 Dec 9 13:27:01 lion /kernel: da0: Fixed Direct Access SCSI-4 device Dec 9 13:27:01 lion /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled Dec 9 13:27:01 lion /kernel: da0: 8715MB (17850264 512 byte sectors: 255H 63S/T 1111C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 4:25:48 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id D26A237B419 for ; Fri, 28 Dec 2001 04:25:44 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id fBSCNsE25994; Fri, 28 Dec 2001 13:23:54 +0100 (CET) (envelope-from wkb) Date: Fri, 28 Dec 2001 13:23:54 +0100 From: Wilko Bulte To: Andrey Simonenko Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Error from SCSI hard disk, please explaine Message-ID: <20011228132354.C25749@freebie.xs4all.nl> References: <005501c18f7f$62f61ec0$6d36120a@comsys.ntukpi.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <005501c18f7f$62f61ec0$6d36120a@comsys.ntukpi.kiev.ua>; from simon@comsys.ntu-kpi.kiev.ua on Fri, Dec 28, 2001 at 12:09:41PM +0300 X-OS: FreeBSD 4.5-PRERELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Dec 28, 2001 at 12:09:41PM +0300, Andrey Simonenko wrote: This means what is say: the disk has a bad block (medium error) which was discovered during a read. It has retried the read operation, but has failed to recover the data. > Hi all, > > My system (FreeBSD/i386 4.4-STABLE) begins to print following: > > Dec 26 02:05:33 lion /kernel: (da0:sym0:0:15:0): READ(06). CDB: 8 1b 60 7f 10 0 > Dec 26 02:05:35 lion /kernel: (da0:sym0:0:15:0): MEDIUM ERROR info:1b607f > asc:11,1 > Dec 26 02:05:36 lion /kernel: (da0:sym0:0:15:0): Read retries exhausted > sks:80,3f > Dec 26 02:05:38 lion /kernel: (da0:sym0:0:15:0): READ(06). CDB: 8 1b 60 7f 10 0 > Dec 26 02:05:38 lion /kernel: (da0:sym0:0:15:0): MEDIUM ERROR info:1b607f > asc:11,1 > Dec 26 02:05:38 lion /kernel: (da0:sym0:0:15:0): Read retries exhausted > sks:80,3f > Dec 26 02:05:42 lion /kernel: (da0:sym0:0:15:0): READ(06). CDB: 8 1d 60 8f 10 0 > Dec 26 02:05:45 lion /kernel: (da0:sym0:0:15:0): MEDIUM ERROR info:1d608f > asc:11,1 -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 5: 3:56 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mailout09.sul.t-online.com (mailout09.sul.t-online.com [194.25.134.84]) by hub.freebsd.org (Postfix) with ESMTP id 9748E37B429 for ; Fri, 28 Dec 2001 05:03:53 -0800 (PST) Received: from fwd00.sul.t-online.de by mailout09.sul.t-online.de with smtp id 16Jwfw-0001cp-05; Fri, 28 Dec 2001 14:03:52 +0100 Received: from twoflower.liebende.de (320072111332-0001@[217.80.127.86]) by fwd00.sul.t-online.com with esmtp id 16Jwfk-24Eq6iC; Fri, 28 Dec 2001 14:03:40 +0100 Subject: Allow users to write cds From: Jan.Stocker@t-online.de (Jan Stocker) To: scsi@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0 (Preview Release) Date: 28 Dec 2001 14:03:14 +0100 Message-Id: <1009544598.385.0.camel@twoflower> Mime-Version: 1.0 X-Sender: 320072111332-0001@t-dialin.net Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, under FreeBSD cdrecord cant use devices to write cds, you have to give it bus, target and lun id. So you have to enable access for the general scsi bus, havent you? But if you do, everything (including all hds) are accessable? Jan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 6:20:19 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 3E55737B41E for ; Fri, 28 Dec 2001 06:20:14 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id PAA14766; Fri, 28 Dec 2001 15:20:12 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id fBSE6Eo49620; Fri, 28 Dec 2001 15:06:14 +0100 (MET) (envelope-from j) Date: Fri, 28 Dec 2001 15:06:14 +0100 (MET) Message-Id: <200112281406.fBSE6Eo49620@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden 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 References: <1009544598.385.0.camel@twoflower> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: Allow users to write cds X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: Jan.Stocker@t-online.de Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Jan.Stocker@t-online.de (Jan Stocker) wrote: > But if you do, everything (including all hds) are > accessable? Yes, it is. The bad news: circumventing this would require writing a low-level device driver for CD-R devices (so you could use regular device permissions to maintain access rights). We used to have one (for very ancient CD-R drives, years ago when there wasn't an established standard for those devices). Unfortunately, the author of cdrecord has the opinion that his way of doing things is the best one on earth, so he certainly won't ever write us a device driver for CD-Rs. Thus it needs a person with good motivation and enough time to do it. And well, while cdrecord claims in its man page that it were safe to run setuid root, people have seen it dumping core, too... /I/ wouldn't trust it for setuid. You have to decide for yourself. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL 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 Dec 28 7:27:14 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from vortex.wa4phy.net (cc449817-a.mrtnz1.ga.home.com [24.12.79.51]) by hub.freebsd.org (Postfix) with ESMTP id CCBED37B423 for ; Fri, 28 Dec 2001 07:27:10 -0800 (PST) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.11.6/8.11.6) with ESMTP id fBSFR9104764 for ; Fri, 28 Dec 2001 10:27:09 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3C2C8F4D.E8A9A296@vortex.wa4phy.net> Date: Fri, 28 Dec 2001 10:27:09 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.5-PRERELEASE i386) X-Accept-Language: en, ja MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Second request for help. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Can someone tell me what's happening here? Is it hardware or maybe just a bad tape? The situation: All attempts to read/write/erase or even get status of any tape results in the error message below. The drive was working prior to my upgrade to 4.3-R, and now to 4.5-Pre. Have tried the card (2940 adaptec) in a windows machine with no luck either. Also have tried identical drive, new cable, same configuration, etc.. terminators are in place. At this time, I'm doing an erase, but the green led on the drive is not lit up. The amber led is, but not flashing. Any ideas/help appreciated. Sam sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) Mounting root from ufs:/dev/ad0s1a (sa0:ahc0:0:6:0): SCB 0x2 - timed out ahc0: Dumping Card State while idle, at SEQADDR 0x8 ACCUM = 0x28, SINDEX = 0x67, DINDEX = 0x27, ARG_2 = 0x0 HCNT = 0x0 SCSISEQ = 0x12, SBLKCTL = 0x0 DFCNTRL = 0x0, DFSTATUS = 0x2d LASTPHASE = 0x1, SCSISIGI = 0x0, SXFRCTL0 = 0x80 SSTAT0 = 0x5, SSTAT1 = 0xa STACK == 0x3, 0x186, 0x156, 0x0 SCB count = 10 Kernel NEXTQSCB = 3 Card NEXTQSCB = 3 QINFIFO entries: Waiting Queue entries: Disconnected Queue entries: 0:2 QOUTFIFO entries: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Pending list: 2 Kernel Free SCB list: 4 5 6 7 8 9 1 0 Untagged Q(6): 2 sg[0] - Addr 0x460e000 : Length 4096 sg[1] - Addr 0x4eaf000 : Length 4096 (sa0:ahc0:0:6:0): Queuing a BDR SCB (sa0:ahc0:0:6:0): Bus Device Reset Message Sent (sa0:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:6. 1 SCBs aborted (sa0:ahc0:0:6:0): unable to rewind after test read (sa0:ahc0:0:6:0): SCB 0x2 - timed out ahc0: Dumping Card State while idle, at SEQADDR 0x7 ACCUM = 0x4d, SINDEX = 0x67, DINDEX = 0x27, ARG_2 = 0x0 HCNT = 0x0 SCSISEQ = 0x12, SBLKCTL = 0x0 DFCNTRL = 0x0, DFSTATUS = 0x2d LASTPHASE = 0x1, SCSISIGI = 0x0, SXFRCTL0 = 0x80 SSTAT0 = 0x5, SSTAT1 = 0xa STACK == 0x3, 0x186, 0x156, 0xe1 SCB count = 10 Kernel NEXTQSCB = 3 Card NEXTQSCB = 3 QINFIFO entries: Waiting Queue entries: Disconnected Queue entries: 0:2 QOUTFIFO entries: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Pending list: 2 Kernel Free SCB list: 4 5 6 7 8 9 1 0 Untagged Q(6): 2 sg[0] - Addr 0x460e000 : Length 4096 sg[1] - Addr 0x4eaf000 : Length 4096 (sa0:ahc0:0:6:0): Queuing a BDR SCB (sa0:ahc0:0:6:0): Bus Device Reset Message Sent (sa0:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:6. 1 SCBs aborted (sa0:ahc0:0:6:0): unable to rewind after test read To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 12:49:14 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp017.mail.yahoo.com (smtp017.mail.yahoo.com [216.136.174.114]) by hub.freebsd.org (Postfix) with SMTP id E34E337B417 for ; Fri, 28 Dec 2001 12:48:55 -0800 (PST) Received: from mkc-65-30-96-67.kc.rr.com (HELO yahoo.com) (65.30.96.67) by smtp.mail.vip.sc5.yahoo.com with SMTP; 28 Dec 2001 20:48:55 -0000 Message-ID: <3C2CDAB6.1090408@yahoo.com> Date: Fri, 28 Dec 2001 14:48:54 -0600 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-current@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: Vinum issue with USB CompactFlash reader. Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I know this is probably a minor issue, as it is only an annoyance, and doesn't impact operation or performance, but still.. Ever since I concatenated some old drives to make a more reasonable capacity out of them, I have been noticing the following whenever vinum is loaded at startup [Note: The dmesg output doesn't show it, but before the check condition errors, vinum is loaded. Also this occurs when no CF card is present in the reader, seems to do well when booted with a card in place.]: Could vinum not be detecting that this is a removable media device? Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) da1 at ahc1 bus 0 target 15 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) Mounting root from ufs:/dev/ad0s1a cd1 at ahc0 bus 0 target 3 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 target 0 lun 0 da3: Removable Direct Access SCSI-2 device da3: 150KB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present cd2 at ahc0 bus 0 target 4 lun 0 cd2: Removable CD-ROM SCSI-2 device cd2: 3.300MB/s transfers cd2: Attempt to query device size failed: NOT READY, Medium not present da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da3:umass-sim0:0:0:0): SCSI Status: Check Condition (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 (da3:umass-sim0:0:0:0): Medium not present (da3:umass-sim0:0:0:0): Unretryable error jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! ----------------------------------------------------- POWER TO THE PEOPLE! ----------------------------------------------------- "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 12:51:26 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp017.mail.yahoo.com (smtp017.mail.yahoo.com [216.136.174.114]) by hub.freebsd.org (Postfix) with SMTP id 0883137B41B for ; Fri, 28 Dec 2001 12:51:24 -0800 (PST) Received: from mkc-65-30-96-67.kc.rr.com (HELO yahoo.com) (65.30.96.67) by smtp.mail.vip.sc5.yahoo.com with SMTP; 28 Dec 2001 20:51:23 -0000 Message-ID: <3C2CDB49.7050601@yahoo.com> Date: Fri, 28 Dec 2001 14:51:21 -0600 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Jan Stocker Cc: scsi@freebsd.org Subject: Re: Allow users to write cds References: <1009544598.385.0.camel@twoflower> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Well, FreeBSD-CURRENT now has ACL capability... Something to think about. Jan Stocker wrote: > Hi, > under FreeBSD cdrecord cant use devices to write cds, you have to give > it bus, target and lun id. So you have to enable access for the general > scsi bus, havent you? But if you do, everything (including all hds) are > accessable? > > Jan jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! ----------------------------------------------------- POWER TO THE PEOPLE! ----------------------------------------------------- "Religious fundamentalism is the biggest threat to international security that exists today." United Nations Secretary General B.B.Ghali, 1995 _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 15:39:22 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 3E7A937B425; Fri, 28 Dec 2001 15:39:13 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 58C97786E3; Sat, 29 Dec 2001 10:09:11 +1030 (CST) Date: Sat, 29 Dec 2001 10:09:11 +1030 From: Greg Lehey To: Jim Bryant Cc: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Vinum issue with USB CompactFlash reader. Message-ID: <20011229100911.D48518@monorchid.lemis.com> References: <3C2CDAB6.1090408@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C2CDAB6.1090408@yahoo.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Friday, 28 December 2001 at 14:48:54 -0600, Jim Bryant wrote: > I know this is probably a minor issue, as it is only an annoyance, and > doesn't impact operation or performance, but still.. > > Ever since I concatenated some old drives to make a more reasonable capacity > out of them, I have been noticing the following whenever vinum is loaded at > startup [Note: The dmesg output doesn't show it, but before the check > condition errors, vinum is loaded. Also this occurs when no CF card is > present in the reader, seems to do well when booted with a card in place.]: > > Could vinum not be detecting that this is a removable media device? This has nothing to do with Vinum. The errors are at the device driver level, and they appear to relate only to the compact flash adaptor. Does it work when Vinum is not loaded? Was there in fact a CF card in the adaptor? Greg > Waiting 15 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 5 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 10.000MB/s transfers (10.000MHz, offset 8) > da0 at ahc1 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing > Enabled > da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) > da1 at ahc1 bus 0 target 15 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing > Enabled > da1: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) > Mounting root from ufs:/dev/ad0s1a > cd1 at ahc0 bus 0 target 3 lun 0 > cd1: Removable CD-ROM SCSI-2 device > cd1: 20.000MB/s transfers (20.000MHz, offset 15) > cd1: Attempt to query device size failed: NOT READY, Medium not present > da3 at umass-sim0 bus 0 target 0 lun 0 > da3: Removable Direct Access SCSI-2 device > da3: 150KB/s transfers > da3: Attempt to query device size failed: NOT READY, Medium not present > cd2 at ahc0 bus 0 target 4 lun 0 > cd2: Removable CD-ROM SCSI-2 device > cd2: 3.300MB/s transfers > cd2: Attempt to query device size failed: NOT READY, Medium not present > da2 at ahc0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da2: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > cd0 at ahc0 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 20.000MB/s transfers (20.000MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present > (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (da3:umass-sim0:0:0:0): SCSI Status: Check Condition > (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 > (da3:umass-sim0:0:0:0): Medium not present > (da3:umass-sim0:0:0:0): Unretryable error -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 21:21:37 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 039ED37B417; Fri, 28 Dec 2001 21:21:29 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id fBT5LRg33027; Sat, 29 Dec 2001 06:21:27 +0100 (CET) (envelope-from ticso@cicely9.cicely.de) Received: from mail.cicely.de (cicely20.cicely.de [10.1.1.22]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id fBT5LWtx004405; Sat, 29 Dec 2001 06:21:32 +0100 (CET)?g (envelope-from ticso@cicely9.cicely.de) Received: from cicely9.cicely.de (cicely9.cicely.de [10.1.7.11]) by mail.cicely.de (8.11.0/8.11.0) with ESMTP id fBT5LUW05859; Sat, 29 Dec 2001 06:21:30 +0100 (CET) Received: (from ticso@localhost) by cicely9.cicely.de (8.11.6/8.11.6) id fBT5LTH23281; Sat, 29 Dec 2001 06:21:29 +0100 (CET) (envelope-from ticso) Date: Sat, 29 Dec 2001 06:21:29 +0100 From: Bernd Walter To: Greg Lehey Cc: Jim Bryant , freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Vinum issue with USB CompactFlash reader. Message-ID: <20011229052129.GB23224@cicely9.cicely.de> References: <3C2CDAB6.1090408@yahoo.com> <20011229100911.D48518@monorchid.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011229100911.D48518@monorchid.lemis.com> User-Agent: Mutt/1.3.24i X-Operating-System: FreeBSD cicely9.cicely.de 5.0-CURRENT alpha Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Dec 29, 2001 at 10:09:11AM +1030, Greg Lehey wrote: > On Friday, 28 December 2001 at 14:48:54 -0600, Jim Bryant wrote: > > I know this is probably a minor issue, as it is only an annoyance, and > > doesn't impact operation or performance, but still.. > > > > Ever since I concatenated some old drives to make a more reasonable capacity > > out of them, I have been noticing the following whenever vinum is loaded at > > startup [Note: The dmesg output doesn't show it, but before the check > > condition errors, vinum is loaded. Also this occurs when no CF card is > > present in the reader, seems to do well when booted with a card in place.]: > > > > Could vinum not be detecting that this is a removable media device? There are valid reasons to run vinum on removeable media so it should not exclude them. > This has nothing to do with Vinum. The errors are at the device > driver level, and they appear to relate only to the compact flash > adaptor. Does it work when Vinum is not loaded? Was there in fact a > CF card in the adaptor? vinums read_drive_label triggers this. It tries to read the label and produces the given errors if the drive is not ready - nothing wrong IMHO. I see the same messages for an MO drive if there is no media inserted. And I see these errors for a fixed drive with media errors. It is just unavoidable to have a single error for each drive and I don't know for shure why it happens several times - maybe vinum probes for multiple partitions. > > Greg > > > Waiting 15 seconds for SCSI devices to settle > > sa0 at ahc0 bus 0 target 5 lun 0 > > sa0: Removable Sequential Access SCSI-2 device > > sa0: 10.000MB/s transfers (10.000MHz, offset 8) > > da0 at ahc1 bus 0 target 0 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing > > Enabled > > da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) > > da1 at ahc1 bus 0 target 15 lun 0 > > da1: Fixed Direct Access SCSI-2 device > > da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing > > Enabled > > da1: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) > > Mounting root from ufs:/dev/ad0s1a > > cd1 at ahc0 bus 0 target 3 lun 0 > > cd1: Removable CD-ROM SCSI-2 device > > cd1: 20.000MB/s transfers (20.000MHz, offset 15) > > cd1: Attempt to query device size failed: NOT READY, Medium not present > > da3 at umass-sim0 bus 0 target 0 lun 0 > > da3: Removable Direct Access SCSI-2 device > > da3: 150KB/s transfers > > da3: Attempt to query device size failed: NOT READY, Medium not present > > cd2 at ahc0 bus 0 target 4 lun 0 > > cd2: Removable CD-ROM SCSI-2 device > > cd2: 3.300MB/s transfers > > cd2: Attempt to query device size failed: NOT READY, Medium not present > > da2 at ahc0 bus 0 target 2 lun 0 > > da2: Fixed Direct Access SCSI-2 device > > da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > > da2: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > > cd0 at ahc0 bus 0 target 6 lun 0 > > cd0: Removable CD-ROM SCSI-2 device > > cd0: 20.000MB/s transfers (20.000MHz, offset 15) > > cd0: Attempt to query device size failed: NOT READY, Medium not present > > (da3:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > > (da3:umass-sim0:0:0:0): CAM Status: SCSI Status Error > > (da3:umass-sim0:0:0:0): SCSI Status: Check Condition > > (da3:umass-sim0:0:0:0): NOT READY asc:3a,0 > > (da3:umass-sim0:0:0:0): Medium not present > > (da3:umass-sim0:0:0:0): Unretryable error > > -- > See complete headers for address and phone numbers > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 21:33:48 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from monorchid.lemis.com (monorchid.lemis.com [192.109.197.75]) by hub.freebsd.org (Postfix) with ESMTP id 5E02D37B422; Fri, 28 Dec 2001 21:33:44 -0800 (PST) Received: by monorchid.lemis.com (Postfix, from userid 1004) id 79D5C786E3; Sat, 29 Dec 2001 16:03:40 +1030 (CST) Date: Sat, 29 Dec 2001 16:03:40 +1030 From: Greg Lehey To: Bernd Walter Cc: Jim Bryant , freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Vinum issue with USB CompactFlash reader. Message-ID: <20011229160340.G90696@monorchid.lemis.com> References: <3C2CDAB6.1090408@yahoo.com> <20011229100911.D48518@monorchid.lemis.com> <20011229052129.GB23224@cicely9.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011229052129.GB23224@cicely9.cicely.de> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Saturday, 29 December 2001 at 6:21:29 +0100, Bernd Walter wrote: > On Sat, Dec 29, 2001 at 10:09:11AM +1030, Greg Lehey wrote: >> This has nothing to do with Vinum. The errors are at the device >> driver level, and they appear to relate only to the compact flash >> adaptor. Does it work when Vinum is not loaded? Was there in fact a >> CF card in the adaptor? > > vinums read_drive_label triggers this. > It tries to read the label and produces the given errors if the drive is > not ready - nothing wrong IMHO. This would assume that Vinum was started after the adaptor was inserted. > I see the same messages for an MO drive if there is no media inserted. > And I see these errors for a fixed drive with media errors. > It is just unavoidable to have a single error for each drive and I don't > know for shure why it happens several times - maybe vinum probes for > multiple partitions. Yes, Vinum probes for up to 35 partitions. First it tries each partition in each slice. If that doesn't work, it tries the compatibility slice. In each case, it ignores partition c. I suppose it would be possible to recognize conditions like "medium not present" and stop after the first attempt. But I can't see how to handle this without at least one error message. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 22:42:24 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 63C7E37B41F; Fri, 28 Dec 2001 22:42:11 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id fBT6g9634770; Sat, 29 Dec 2001 07:42:10 +0100 (CET) (envelope-from ticso@cicely9.cicely.de) Received: from mail.cicely.de (cicely20.cicely.de [10.1.1.22]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id fBT6g3tx004830; Sat, 29 Dec 2001 07:42:04 +0100 (CET)?g (envelope-from ticso@cicely9.cicely.de) Received: from cicely9.cicely.de (cicely9.cicely.de [10.1.7.11]) by mail.cicely.de (8.11.0/8.11.0) with ESMTP id fBT6g2W05900; Sat, 29 Dec 2001 07:42:02 +0100 (CET) Received: (from ticso@localhost) by cicely9.cicely.de (8.11.6/8.11.6) id fBT6g1r23462; Sat, 29 Dec 2001 07:42:01 +0100 (CET) (envelope-from ticso) Date: Sat, 29 Dec 2001 07:42:01 +0100 From: Bernd Walter To: Greg Lehey Cc: Jim Bryant , freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Vinum issue with USB CompactFlash reader. Message-ID: <20011229064201.GE23224@cicely9.cicely.de> References: <3C2CDAB6.1090408@yahoo.com> <20011229100911.D48518@monorchid.lemis.com> <20011229052129.GB23224@cicely9.cicely.de> <20011229160340.G90696@monorchid.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011229160340.G90696@monorchid.lemis.com> User-Agent: Mutt/1.3.24i X-Operating-System: FreeBSD cicely9.cicely.de 5.0-CURRENT alpha Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Dec 29, 2001 at 04:03:40PM +1030, Greg Lehey wrote: > On Saturday, 29 December 2001 at 6:21:29 +0100, Bernd Walter wrote: > > On Sat, Dec 29, 2001 at 10:09:11AM +1030, Greg Lehey wrote: > >> This has nothing to do with Vinum. The errors are at the device > >> driver level, and they appear to relate only to the compact flash > >> adaptor. Does it work when Vinum is not loaded? Was there in fact a > >> CF card in the adaptor? > > > > vinums read_drive_label triggers this. > > It tries to read the label and produces the given errors if the drive is > > not ready - nothing wrong IMHO. > > This would assume that Vinum was started after the adaptor was > inserted. You can see from the bootlog that the adapter was probed and detected during booting - it was even printed before some scsi harddisks. > > I see the same messages for an MO drive if there is no media inserted. > > And I see these errors for a fixed drive with media errors. > > It is just unavoidable to have a single error for each drive and I don't > > know for shure why it happens several times - maybe vinum probes for > > multiple partitions. > > Yes, Vinum probes for up to 35 partitions. First it tries each > partition in each slice. If that doesn't work, it tries the > compatibility slice. In each case, it ignores partition c. > > I suppose it would be possible to recognize conditions like "medium > not present" and stop after the first attempt. But I can't see how to > handle this without at least one error message. I'm not shure that you see this error inside vinum. From what I understood it's that reading the disklabel failed and vinum might only get ENXIO. I don't know the disklabel code but maybe there is something possible to have one call and get all available partitions. Nevertheless the errors are just telling why this drive was not succesfully scanned and have a valid reason to be there. You can alway tell vinum which partitions to probe. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 23:42:25 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f45.law9.hotmail.com [64.4.9.45]) by hub.freebsd.org (Postfix) with ESMTP id A2A0437B425 for ; Fri, 28 Dec 2001 23:42:19 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 28 Dec 2001 23:42:19 -0800 Received: from 65.30.229.190 by lw9fd.law9.hotmail.msn.com with HTTP; Sat, 29 Dec 2001 07:42:19 GMT X-Originating-IP: [65.30.229.190] From: "Joe Parks" To: freebsd-scsi@freebsd.org Subject: error in 4.4 release notes regarding PERC 2/QC ? Date: Sat, 29 Dec 2001 00:42:19 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 29 Dec 2001 07:42:19.0521 (UTC) FILETIME=[58323F10:01C1903C] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I was looking through the FreeBSD release notes for 4.4-RELEASE and saw: Dell PERC 2/QC However, on this page, http://people.freebsd.org/~msmith/RAID/ I see that, although the PERC 3/QC is listed, the '2/QC' is not. Further, I noticed that in the current notes for 5.0 there is no '2/QC' either. Therefore, I am curious as to whether the 4.4-RELEASE notes contain a typo, or if there really is support for the PERC 2/QC. My experience today leads me to believe that there is not. kern/MFSroot floppy set boots the kernel _up to_ the point that it identifies aac0 as a PERC 2/QC, and then hard locks the machine. Problem is reproducible. Dell PowerEdge 6300. POST tells me that I have a PERC 2 Bios v1.1-3[build 1963] thanks. _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 28 23:48:43 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 00E0037B41E for ; Fri, 28 Dec 2001 23:48:40 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBT7ubF20404; Fri, 28 Dec 2001 23:56:37 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112290756.fBT7ubF20404@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Joe Parks" Cc: freebsd-scsi@freebsd.org Subject: Re: error in 4.4 release notes regarding PERC 2/QC ? In-reply-to: Your message of "Sat, 29 Dec 2001 00:42:19 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Dec 2001 23:56:37 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Hello, > > I was looking through the FreeBSD release notes for 4.4-RELEASE and saw: > > Dell PERC 2/QC > > However, on this page, http://people.freebsd.org/~msmith/RAID/ > > I see that, although the PERC 3/QC is listed, the '2/QC' is not. Further, > I noticed that in the current notes for 5.0 there is no '2/QC' either. You need to read more closely. 8) > Therefore, I am curious as to whether the 4.4-RELEASE notes contain a > typo, or if there really is support for the PERC 2/QC. My experience > today leads me to believe that there is not. kern/MFSroot floppy set > boots the kernel _up to_ the point that it identifies aac0 as a PERC 2/QC, > and then hard locks the machine. Problem is reproducible. You'll need to talk to Scott Long , who now maintains the aac driver. It ought to work; it certainly did before I handed the driver over to Scott, and we regularly hear from people running them. Make very sure that you are running the most recent firmware; older firmware on these cards was... touchy. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 29 7:14:48 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by hub.freebsd.org (Postfix) with ESMTP id 4D8AB37B41B; Sat, 29 Dec 2001 07:14:44 -0800 (PST) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id HAA21351; Sat, 29 Dec 2001 07:14:43 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [162.62.64.10]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id GAA04162; Sat, 29 Dec 2001 06:58:52 -0800 (PST) Received: from btcexc01.btc.adaptec.com (btcexc01 [162.62.147.10]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id IAA17437; Sat, 29 Dec 2001 08:14:41 -0700 (MST) Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2653.19) id ; Sat, 29 Dec 2001 08:14:41 -0700 Message-ID: From: "Long, Scott" To: "'Mike Smith'" , Joe Parks Cc: freebsd-scsi@freebsd.org Subject: RE: error in 4.4 release notes regarding PERC 2/QC ? Date: Sat, 29 Dec 2001 08:14:40 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'll review the documentation today to make sure that it is accurate. Yes, the PERC2/QC is supported under the aac driver, and the aac driver is part of GENERIC and exists on the boot floppies. Mike probably guessed right about your problem; the driver does not work with version 1.x of the firmware. You can find out what version you have by checking the card's BIOS banner at boot time. In any case, I would recommend upgrading to the latest firmware from Dell and trying again. Scott > -----Original Message----- > From: Mike Smith [mailto:msmith@freebsd.org] > Sent: Saturday, December 29, 2001 12:57 AM > To: Joe Parks > Cc: freebsd-scsi@freebsd.org > Subject: Re: error in 4.4 release notes regarding PERC 2/QC ? > > > > Hello, > > > > I was looking through the FreeBSD release notes for > 4.4-RELEASE and saw: > > > > Dell PERC 2/QC > > > > However, on this page, http://people.freebsd.org/~msmith/RAID/ > > > > I see that, although the PERC 3/QC is listed, the '2/QC' is > not. Further, > > I noticed that in the current notes for 5.0 there is no > '2/QC' either. > > You need to read more closely. 8) > > > Therefore, I am curious as to whether the 4.4-RELEASE notes > contain a > > typo, or if there really is support for the PERC 2/QC. My > experience > > today leads me to believe that there is not. kern/MFSroot > floppy set > > boots the kernel _up to_ the point that it identifies aac0 > as a PERC 2/QC, > > and then hard locks the machine. Problem is reproducible. > > You'll need to talk to Scott Long , who > now maintains > the aac driver. It ought to work; it certainly did before I > handed the > driver over to Scott, and we regularly hear from people running them. > > Make very sure that you are running the most recent firmware; older > firmware on these cards was... touchy. > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > > > 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