From owner-freebsd-hardware@FreeBSD.ORG Tue Jul 6 07:29:38 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39A79106564A for ; Tue, 6 Jul 2010 07:29:38 +0000 (UTC) (envelope-from kwcheong@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id E00178FC0A for ; Tue, 6 Jul 2010 07:29:37 +0000 (UTC) Received: by vws6 with SMTP id 6so7372336vws.13 for ; Tue, 06 Jul 2010 00:29:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=xvkjarz6FWLFQkEgtku51VrMxHGRjUlaW50jdBTBEdo=; b=vshJk5jcVdPwF1iJbW7ziZq55Gh3H/pa3mDlIZuy8xw0nm7q64X4iaLmTeIGPhqrjZ UJt0zTbHuKI3+eY3NauB2EKepYJz0v4e+vvK3Nb63anGRIWKy6S1Z7+o40XE6nq2sWD+ fzBi++/zoKZsArEScg88ftWC+APCScNVq2J9Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=aZymHcjcEzrYmbqD0ICb4TQqao8YSTaT8Mn6YcT5HvUmCyVnHxf2/oWRuMppH32w6W aBqCdoOzuWFCSKs+myTGN4IspcyHwyvLVBoXhRxYeXWeI0HYTiIHiAldF8y/ySVEtTtl hfVrGnMGQvhcjT+fPL09JbhV5A043WtJPOOZ4= Received: by 10.229.181.3 with SMTP id bw3mr2307207qcb.155.1278399994059; Tue, 06 Jul 2010 00:06:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.211.20 with HTTP; Tue, 6 Jul 2010 00:06:12 -0700 (PDT) From: frank cheong Date: Tue, 6 Jul 2010 15:06:12 +0800 Message-ID: To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: /dev/ch0 not recognized/found X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 07:29:38 -0000 Riding on http://www.experts-exchange.com/OS/Unix/BSD/FreeBSD/Q_26283427.html as well as http://www.pubbs.net/200911/freebsd/20344-ciss4-not-seeing-multiple-luns.html I would like to know if there is any way to manually create/link the /dev/ch0 driver for this case. Actually, I have my msl 2024 1760 SAS tape library attaching to my HP DL 180 G6 thru Smart Array P212. I can successfully use this tape library with my window 2008 ad backup exec 2010. While from my freeBSD 8.0, 8.0 p3 or even 8.1 RC2, I don't even see the /dev/ch0 device link whereby I can see this device using the camcontrol devlist -v. My question is: - 1. Is there any way I can manually create/link the /dev/ch0 device driver ? 2. How can I achieve 1 if it is possible. 3. Having learnt that exposing disk mirror controller should be considered as danger, may I have more information and background information about that ? What specific problem will I encounter for that ? Pls find below the configuration details which is related to the tape library:- 1: 2: 3: 4: 5: 6: 7: 8: 9: server# dmesg | grep ciss ciss0: port 0xd800-0xd8ff mem 0xfb800000-0xfbbfffff,0xfbdff000-0xfbdfffff irq 24 at device 0.0 on pci6 ciss0: PERFORMANT Transport ciss0: [ITHREAD] ciss1: port 0xc800-0xc8ff mem 0xfb400000-0xfb7fffff,0xfb3ff000-0xfb3fffff irq 32 at device 0.0 on pci4 ciss1: PERFORMANT Transport ciss1: [ITHREAD] sa0 at ciss0 bus 32 scbus1 target 6 lun 0 da0 at ciss1 bus 0 scbus2 target 0 lun 0 1: 2: 3: 4: 5: 6: 7: 8: 9: server# camcontrol devlist -v scbus0 on ciss0 bus 0: scbus1 on ciss0 bus 32: at scbus1 target 6 lun 0 (sa0,pass0) scbus2 on ciss1 bus 0: at scbus2 target 0 lun 0 (da0,pass1) scbus3 on ciss1 bus 32: scbus-1 on xpt0 bus 0: <> at scbus-1 target -1 lun -1 (xpt0) 1: 2: 3: 4: server# camcontrol reportluns 1:6 2 LUNs found 0 1 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: server# ls /dev/ acd0 da0s1e led sa0.2 ttyvb acpi da0s1f log sa0.3 ttyvc ata dcons mdctl sa0.ctl ttyvd atkbd0 devctl mem stderr ttyve audit devstat nfslock stdin ttyvf bpf dgdb nsa0 stdout ufsid bpf0 esa0 nsa0.0 sysmouse ugen0.1 bpsm0 esa0.0 nsa0.1 ttyu0 ugen1.1 ciss0 esa0.1 nsa0.2 ttyu0.init ugen2.1 ciss1 esa0.2 nsa0.3 ttyu0.lock ugen3.1 console esa0.3 null ttyv0 ugen3.2 consolectl fd pass0 ttyv1 ugen4.1 ctty fido pass1 ttyv2 ugen5.1 cuau0 geom.ctl pci ttyv3 ukbd0 cuau0.init io psm0 ttyv4 ums0 cuau0.lock kbd0 ptmx ttyv5 urandom da0 kbd1 pts ttyv6 usb da0s1 kbd2 random ttyv7 usbctl da0s1a kbdmux0 sa0 ttyv8 xpt0 da0s1b klog sa0.0 ttyv9 zero da0s1d kmem sa0.1 ttyva From owner-freebsd-hardware@FreeBSD.ORG Tue Jul 6 14:19:40 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 722E3106566B for ; Tue, 6 Jul 2010 14:19:40 +0000 (UTC) (envelope-from kwcheong@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 29B468FC12 for ; Tue, 6 Jul 2010 14:19:39 +0000 (UTC) Received: by qwg5 with SMTP id 5so2475921qwg.13 for ; Tue, 06 Jul 2010 07:19:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=UFRg6aDgfKjZ82L+Je5KANrIofcw/tpCBu5dIaVx7Uc=; b=fDmLUU6kyg85ME1Q90EeRHf6T0sL2qInUS+Z/qERUB1JvrB7Hwb1zoQhvk1qCxqSlY ttdP4QIiMKIzgR9smG5OJLN/oDQ7vZ3fdTwCx6EJs8uQ3phI8J5J5CJBZh4z/Y7zW0aj 4s+wpK6cNsn8SmZFhQzKibailipPuKdOZGzTw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=a2TYTAcF4jm1czHw3mSTQBZZE5a/Jwakmbr5ijyM1Z2BfgYDW1oxf+KBfzopmaKF7s W/3vRsmzRsftpdfo9Amg3Nf4MTzZ6zOo6Zhq/I9QMeKAetSXFHg4Lcoklv29pywvNYhv zfyRdqWKfw83349DMubnHOXZvEKmh2p9c/ETg= Received: by 10.224.100.142 with SMTP id y14mr2464147qan.282.1278425970513; Tue, 06 Jul 2010 07:19:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.211.20 with HTTP; Tue, 6 Jul 2010 07:19:10 -0700 (PDT) In-Reply-To: References: From: frank cheong Date: Tue, 6 Jul 2010 22:19:10 +0800 Message-ID: To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: /dev/ch0 not recognized/found X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 14:19:40 -0000 After installation the same setup with redhat linux and drivers downloaded from hp website, I found that the problem lies on the ciss driver in freeBSD which didn't handle lun>0. Coz rehat works nicely with the changer only when using the drivers provided by HP (that means redhat also can't recognize this tape library using the default ciss driver/setup). Sad news is I will have to stick with redhat linux when everything works in order to save some money from grabbing another controller which suppose to work with freeBSD. I keep this post here hopes other will not fall into the same HP P212 related media changer problem or best if someone will enhance the ciss driver in order to handle device with lun > 0. Frank On Tue, Jul 6, 2010 at 3:06 PM, frank cheong wrote: > Riding on > http://www.experts-exchange.com/OS/Unix/BSD/FreeBSD/Q_26283427.html as > well as > http://www.pubbs.net/200911/freebsd/20344-ciss4-not-seeing-multiple-luns.html > I would like to know if there is any way to manually create/link the > /dev/ch0 driver for this case. > > Actually, I have my msl 2024 1760 SAS tape library attaching to my HP DL > 180 G6 thru Smart Array P212. I can successfully use this tape library with > my window 2008 ad backup exec 2010. While from my freeBSD 8.0, 8.0 p3 or > even 8.1 RC2, I don't even see the /dev/ch0 device link whereby I can see > this device using the camcontrol devlist -v. My question is: - > > 1. Is there any way I can manually create/link the /dev/ch0 device driver ? > 2. How can I achieve 1 if it is possible. > 3. Having learnt that exposing disk mirror controller should be considered > as danger, may I have more information and background information about that > ? What specific problem will I encounter for that ? > > Pls find below the configuration details which is related to the tape > library:- > > 1: > 2: > 3: > 4: > 5: > 6: > 7: > > > 8: > 9: > > server# dmesg | grep ciss > ciss0: port 0xd800-0xd8ff mem 0xfb800000-0xfbbfffff,0xfbdff000-0xfbdfffff irq 24 at device 0.0 on pci6 > > ciss0: PERFORMANT Transport > ciss0: [ITHREAD] > ciss1: port 0xc800-0xc8ff mem 0xfb400000-0xfb7fffff,0xfb3ff000-0xfb3fffff irq 32 at device 0.0 on pci4 > ciss1: PERFORMANT Transport > ciss1: [ITHREAD] > > > > sa0 at ciss0 bus 32 scbus1 target 6 lun 0 > da0 at ciss1 bus 0 scbus2 target 0 lun 0 > > > > 1: > 2: > 3: > > 4: > 5: > 6: > 7: > 8: > 9: > > server# camcontrol devlist -v > scbus0 on ciss0 bus 0: > scbus1 on ciss0 bus 32: > at scbus1 target 6 lun 0 (sa0,pass0) > > > > scbus2 on ciss1 bus 0: > at scbus2 target 0 lun 0 (da0,pass1) > scbus3 on ciss1 bus 32: > scbus-1 on xpt0 bus 0: > <> at scbus-1 target -1 lun -1 (xpt0) > > > > 1: > 2: > 3: > 4: > > server# camcontrol reportluns 1:6 > > 2 LUNs found > 0 > 1 > > > > 1: > 2: > 3: > 4: > 5: > 6: > 7: > 8: > 9: > 10: > 11: > 12: > 13: > 14: > 15: > 16: > 17: > > 18: > 19: > 20: > 21: > 22: > > server# ls /dev/ > acd0 da0s1e led sa0.2 ttyvb > acpi da0s1f log sa0.3 ttyvc > > > > ata dcons mdctl sa0.ctl ttyvd > atkbd0 devctl mem stderr ttyve > audit devstat nfslock stdin ttyvf > bpf dgdb nsa0 stdout ufsid > > > > bpf0 esa0 nsa0.0 sysmouse ugen0.1 > bpsm0 esa0.0 nsa0.1 ttyu0 ugen1.1 > ciss0 esa0.1 nsa0.2 ttyu0.init ugen2.1 > > > > ciss1 esa0.2 nsa0.3 ttyu0.lock ugen3.1 > console esa0.3 null ttyv0 ugen3.2 > consolectl fd pass0 ttyv1 ugen4.1 > > > > ctty fido pass1 ttyv2 ugen5.1 > cuau0 geom.ctl pci ttyv3 ukbd0 > cuau0.init io psm0 ttyv4 ums0 > > > cuau0.lock kbd0 ptmx ttyv5 urandom > > da0 kbd1 pts ttyv6 usb > da0s1 kbd2 random ttyv7 usbctl > da0s1a kbdmux0 sa0 ttyv8 xpt0 > da0s1b klog sa0.0 ttyv9 zero > > > > da0s1d kmem sa0.1 ttyva > > From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 8 17:55:56 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FBB9106566C for ; Thu, 8 Jul 2010 17:55:56 +0000 (UTC) (envelope-from rob@rsee.net) Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.121]) by mx1.freebsd.org (Postfix) with ESMTP id 287E38FC0C for ; Thu, 8 Jul 2010 17:55:55 +0000 (UTC) Received: from cdptpa-omtalb.mail.rr.com ([10.127.143.53]) by cdptpa-qmta04.mail.rr.com with ESMTP id <20100708172308380.RYSQ6102@cdptpa-qmta04.mail.rr.com> for ; Thu, 8 Jul 2010 17:23:08 +0000 X-Authority-Analysis: v=1.1 cv=mPFsO0+iuMofjwDMsQIP+3gv/0Z8gJtEDRMUNi8ZZGQ= c=1 sm=0 a=zoFJPBr0ZCkA:10 a=FKkrIqjQGGEA:10 a=zNANCjgXmV0A:10 a=ORa4HqFjfvEA:10 a=IkcTkHD0fZMA:10 a=w0F5w/LA3ptD8MaKEJjQzg==:17 a=i-ucG1bMgQ4nTWOgStYA:9 a=0R_Sa9xDzEV3u8ISVBUA:7 a=GXoYJ4B9QK9uYwkjq4ef3O_dK5AA:4 a=QEXdDO2ut3YA:10 a=w0F5w/LA3ptD8MaKEJjQzg==:117 X-Cloudmark-Score: 0 X-Originating-IP: 24.25.135.60 Received: from [24.25.135.60] ([24.25.135.60:59801] helo=zimbra.rsee.net) by cdptpa-oedge03.mail.rr.com (envelope-from ) (ecelerity 2.2.2.39 r()) with ESMTP id 89/94-18593-C39063C4; Thu, 08 Jul 2010 17:22:04 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.rsee.net (Postfix) with ESMTP id 5CEBC27C03C for ; Thu, 8 Jul 2010 13:14:15 -0400 (EDT) X-Virus-Scanned: amavisd-new at zimbra.rsee.net Received: from zimbra.rsee.net ([127.0.0.1]) by localhost (zimbra.rsee.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZ3VYGoCscTk for ; Thu, 8 Jul 2010 13:14:03 -0400 (EDT) Received: from zimbra.rsee.net (zimbra.rsee.net [192.168.10.240]) by zimbra.rsee.net (Postfix) with ESMTP id C804B27C03A for ; Thu, 8 Jul 2010 13:14:03 -0400 (EDT) Date: Thu, 8 Jul 2010 13:14:03 -0400 (EDT) From: Rob See To: freebsd-hardware@freebsd.org Message-ID: <906629297.36878.1278609243142.JavaMail.root@zimbra.rsee.net> In-Reply-To: <268684233.36870.1278608957965.JavaMail.root@zimbra.rsee.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 6.0.4_GA_2038.RHEL5_64 (ZimbraWebClient - FF3.0 (Mac)/6.0.4_GA_2038.RHEL5_64) Subject: Port Multiplier Problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 17:55:56 -0000 Hi, I've got 3 silicon image based esata port multipliers hanging off of a server running FreeBSD 8.1b1, a five bay, and an 8 bay that is divided into 2 4 bays (2 different esata cables going into it.) Recently I've started experiencing problems with one half of the 8 bay. I've started getting messages like: siisch2: Error while READ LOG EXT siisch2: port is not ready (timeout 10000ms) status = 001f2000 siisch2: device ready timeout siisch2: trying full port reset ... siisch2: Error while READ LOG EXT siisch2: port is not ready (timeout 1000ms) status = 001f2000 siisch2: Error while READ LOG EXT siisch2: Timeout on slot 30 siisch2: siis_timeout is 00040000 ss 78000000 rs 78000000 es 00000000 sts 801e2040 serr 00000000 siisch2: ... waiting for slots 38000000 siisch2: Timeout on slot 29 siisch2: siis_timeout is 00040000 ss 78000000 rs 78000000 es 00000000 sts 801e2040 serr 00000000 siisch2: ... waiting for slots 18000000 siisch2: Timeout on slot 28 siisch2: siis_timeout is 00040000 ss 78000000 rs 78000000 es 00000000 sts 801e2040 serr 00000000 siisch2: ... waiting for slots 08000000 siisch2: Timeout on slot 27 siisch2: siis_timeout is 00040000 ss 78000000 rs 78000000 es 00000000 sts 801e2040 serr 00000000 siisch2: Error while READ LOG EXT siisch2: port is not ready (timeout 10000ms) status = 001f2000 siisch2: device ready timeout siisch2: trying full port reset ... siisch2: Error while READ LOG EXT I've tried switching the controller card that the "bad" half is plugged into, and that didn't fix the issue. Its always the same multiplier that gives me issues, and it has gotten worse over the last couple days. Am I looking at bad backplane here, or is it possible that it might be one of the 4 drives causing issues. Thanks, -Rob