From owner-freebsd-firewire Mon Sep 23 4:18:45 2002 Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6842237B401 for ; Mon, 23 Sep 2002 04:18:44 -0700 (PDT) Received: from vault.chamber.ee (vault.chamber.ee [195.50.209.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B45B43E6A for ; Mon, 23 Sep 2002 04:18:43 -0700 (PDT) (envelope-from exile@chamber.ee) Received: from chamber.ee (nobody@localhost [127.0.0.1]) by vault.chamber.ee (8.12.5/8.12.5) with SMTP id g8NCJob0008546 for ; Mon, 23 Sep 2002 14:19:50 +0200 (EET) (envelope-from exile@chamber.ee) Date: Mon, 23 Sep 2002 12:19:50 -0000 To: freebsd-firewire@freebsd.org Subject: 28bit address limitation on HD From: Sten Poldma X-Mailer: twiggi 1.10.3 Reply-To: exile@chamber.ee Message-ID: <20020923141950.re5k5m1g9s00o@.chamber.ee> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-firewire@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'm Sorry if the following is not firewire related but depends on other system components instead. I'm using the newest firewire driver (http://people.freebsd.org/~simokawa/firewire-20020918.tar.gz) To test a 160GB IDE drive (in a box), through the CAM and passthrough drivers I have no problem locating the device (da0) but the geometry of the drive found makes me believe that there is a 28bit addressing mode bottleneck somewhere as the log reports that 268435455 512 byte sectors found. (~131GB) (I believe 268435456 being the 28bit limit?) Although using it is OK I'm still wondering if it would be possible to locate the missing 20GB before the disk actually goes into active use. I'd like to know what is causing this limitation? From the hardware I have: FreeBSD 4.4 -> make buildworld to 4.6.2, latest kernel: 4.7-RC FreeBSD 4.7-RC #0: Sun Sep 22 01:39:47 EET 2002 Firewire PCI card: fwohci0: and a Western Digital 160GB drive in a standard firewire box. Again, accept my apologies if this is the wrong place to request help\clarification on the matter but any help or hint is appreciated. Have a nice day, Sten To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-firewire" in the body of the message From owner-freebsd-firewire Mon Sep 23 6:34:31 2002 Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2CB437B401 for ; Mon, 23 Sep 2002 06:34:29 -0700 (PDT) Received: from ns.koganei.wide.ad.jp (koganei.wide.ad.jp [202.249.37.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59BE943E6A for ; Mon, 23 Sep 2002 06:34:29 -0700 (PDT) (envelope-from ikob@koganei.wide.ad.jp) Received: from koganei.wide.ad.jp (168.pool2.ftthtokyo.att.ne.jp [165.76.218.168]) (authenticated bits=0) by ns.koganei.wide.ad.jp (8.12.3/8.12.3) with ESMTP id g8NDbgXk015691; Mon, 23 Sep 2002 22:37:42 +0900 (JST) (envelope-from ikob@koganei.wide.ad.jp) X-Authentication-Warning: ns.koganei.wide.ad.jp: Host 168.pool2.ftthtokyo.att.ne.jp [165.76.218.168] claimed to be koganei.wide.ad.jp Date: Mon, 23 Sep 2002 22:35:23 +0900 Subject: Re: 28bit address limitation on HD Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v546) Cc: freebsd-firewire@FreeBSD.ORG To: exile@chamber.ee From: Katsushi Kobayashi In-Reply-To: <20020923141950.re5k5m1g9s00o@.chamber.ee> Message-Id: <4FADD69D-CEF9-11D6-8E6A-000393D603A4@koganei.wide.ad.jp> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.546) Sender: owner-freebsd-firewire@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have not had any experience on the such disk size of IEEE1394 disk. If you are using IEEE1394/IDE bridge or similar one, let me know the product information. Or if you have an experience on other OS, let me know whether to success to detect size in correct. On 2002.Sep.23, at 09:19 PM, Sten Poldma wrote: > > Hi, > > I'm Sorry if the following is not firewire related but depends on > other system > components instead. > > I'm using the newest firewire driver > (http://people.freebsd.org/~simokawa/firewire-20020918.tar.gz) > > To test a 160GB IDE drive (in a box), through the CAM and passthrough > drivers I > have no problem locating the device (da0) but the geometry of the > drive found > makes me believe that there is a 28bit addressing mode bottleneck > somewhere as > the log reports that 268435455 512 byte sectors found. (~131GB) (I > believe > 268435456 being the 28bit limit?) > > Although using it is OK I'm still wondering if it would be possible to > locate > the missing 20GB before the disk actually goes into active use. > > I'd like to know what is causing this limitation? > >> From the hardware I have: > > FreeBSD 4.4 -> make buildworld to 4.6.2, latest > kernel: 4.7-RC FreeBSD 4.7-RC #0: Sun Sep 22 01:39:47 EET 2002 > Firewire PCI card: fwohci0: > and a Western Digital 160GB drive in a standard firewire box. > > Again, accept my apologies if this is the wrong place to request > help\clarification on the matter but any help or hint is appreciated. > > Have a nice day, > > Sten > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-firewire" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-firewire" in the body of the message From owner-freebsd-firewire Mon Sep 23 7:17:58 2002 Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 441E937B401 for ; Mon, 23 Sep 2002 07:17:55 -0700 (PDT) Received: from vault.chamber.ee (vault.chamber.ee [195.50.209.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AB3743E4A for ; Mon, 23 Sep 2002 07:17:54 -0700 (PDT) (envelope-from exile@chamber.ee) Received: from chamber.ee (nobody@localhost [127.0.0.1]) by vault.chamber.ee (8.12.5/8.12.5) with SMTP id g8NFIvb0019610; Mon, 23 Sep 2002 17:18:57 +0200 (EET) (envelope-from exile@chamber.ee) Date: Mon, 23 Sep 2002 15:18:57 -0000 To: Katsushi Kobayashi , exile@chamber.ee Subject: Re: 28bit address limitation on HD From: Sten Poldma X-Mailer: twiggi 1.10.3 Cc: freebsd-firewire@FreeBSD.ORG Reply-To: exile@chamber.ee Message-ID: <20020923171857.re4bt81isgg8k@.chamber.ee> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-firewire@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Thanks for the response, that's probably it, The bridge uses the Oxford chipset, which probably does not support the 48 bit mode. I'm sure a new box will remedy the problem. Thanks again, Sten Katsushi Kobayashi said: > > I have not had any experience on the such disk size of IEEE1394 disk. > > If you are using IEEE1394/IDE bridge or similar one, let me know > the product information. Or if you have an experience on other OS, > let me know whether to success to detect size in correct. > > > On 2002.Sep.23, at 09:19 PM, Sten Poldma wrote: > > > > > Hi, > > > > I'm Sorry if the following is not firewire related but depends on > > other system > > components instead. > > > > I'm using the newest firewire driver > > (http://people.freebsd.org/~simokawa/firewire-20020918.tar.gz) > > > > To test a 160GB IDE drive (in a box), through the CAM and passthrough > > drivers I > > have no problem locating the device (da0) but the geometry of the > > drive found > > makes me believe that there is a 28bit addressing mode bottleneck > > somewhere as > > the log reports that 268435455 512 byte sectors found. (~131GB) (I > > believe > > 268435456 being the 28bit limit?) > > > > Although using it is OK I'm still wondering if it would be possible to > > locate > > the missing 20GB before the disk actually goes into active use. > > > > I'd like to know what is causing this limitation? > > > >> From the hardware I have: > > > > FreeBSD 4.4 -> make buildworld to 4.6.2, latest > > kernel: 4.7-RC FreeBSD 4.7-RC #0: Sun Sep 22 01:39:47 EET 2002 > > Firewire PCI card: fwohci0: > > and a Western Digital 160GB drive in a standard firewire box. > > > > Again, accept my apologies if this is the wrong place to request > > help\clarification on the matter but any help or hint is appreciated. > > > > Have a nice day, > > > > Sten > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-firewire" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-firewire" in the body of the message From owner-freebsd-firewire Thu Sep 26 0:56:59 2002 Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D98437B401 for ; Thu, 26 Sep 2002 00:56:56 -0700 (PDT) Received: from vault.chamber.ee (vault.chamber.ee [195.50.209.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7555043E75 for ; Thu, 26 Sep 2002 00:56:55 -0700 (PDT) (envelope-from exile@chamber.ee) Received: from chamber.ee (nobody@localhost [127.0.0.1]) by vault.chamber.ee (8.12.5/8.12.5) with SMTP id g8Q8wBb0059703; Thu, 26 Sep 2002 10:58:12 +0200 (EET) (envelope-from exile@chamber.ee) Date: Thu, 26 Sep 2002 08:58:11 -0000 To: Katsushi Kobayashi Subject: Re: 28bit address limitation on HD From: Sten Poldma X-Mailer: twiggi 1.10.3 Cc: freebsd-firewire@FreeBSD.ORG Reply-To: exile@chamber.ee Message-ID: <20020926105811.envmzsns5m0ogk@.chamber.ee> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-firewire@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, A follow-up om the case previously reported.. [excuse me for the rant] A new box: MAPOWER (MAP-35F), Unfortunately it does not appear on the manufacturer homepage anymore: http://www.mapower.com.tw/ieee_1394.htm But is similar to the MAP-J51F although not much details are offered there. The box works fine Under MacOS X, when plugging into the FreeBSD and loading the firewire drivers, I see the Hd fine.. /kernel: da1: Fixed Simplified Direct Access SCSI-4 device /kernel: da1: 50.000MB/s transfers /kernel: da1: 156334MB (320173056 512 byte sectors: 255H 63S/T 19929C) As you can see, it is the same Hd, and the geometry looks fine.. The HD was formatted to UFS in Mac before plugging it in, still, I did not find the partition there when I plugged it to the BSD machine. Anyhow, I partitioned, Labeled it and newfs'it through the /stand/sysinstall with no freaky settings. So far so good, and created the da1s1e partition. When trying to mount it, I get device busy. I try to switch the ports of the firewire etc, Still unable to mount it with the same error. I check the partition and label, they look to be OK. So what seems to be the problem now ? The sytem can see the box and the disk, I can fdisk,label,newfs it. But I can't mount it. Also, why is the device recognized as da1 ? It is the only device on the chain. Anyway, I seemed to solve the problem with rebooting the entire box (firewire driver unload\load cycle did not seem to help). The reboot phase gave me a Page Fault 12 error as well, but after the system came up, the device was recognized as da0 and mounting the disk was fine. I find it peculiar behaviour, do you happen to have any idea of what might have caused this ? Anyway, I hope this little experience might come in handy to someone in the future. Regards, Sten Sten Poldma said: > > Hi, > > Thanks for the response, that's probably it, The bridge uses the Oxford chipset, > which probably does not support the 48 bit mode. > > I'm sure a new box will remedy the problem. > > Thanks again, > > Sten > > Katsushi Kobayashi said: > > > > > I have not had any experience on the such disk size of IEEE1394 disk. > > > > If you are using IEEE1394/IDE bridge or similar one, let me know > > the product information. Or if you have an experience on other OS, > > let me know whether to success to detect size in correct. > > > > > > On 2002.Sep.23, at 09:19 PM, Sten Poldma wrote: > > > > > > > > Hi, > > > > > > I'm Sorry if the following is not firewire related but depends on > > > other system > > > components instead. > > > > > > I'm using the newest firewire driver > > > (http://people.freebsd.org/~simokawa/firewire-20020918.tar.gz) > > > > > > To test a 160GB IDE drive (in a box), through the CAM and passthrough > > > drivers I > > > have no problem locating the device (da0) but the geometry of the > > > drive found > > > makes me believe that there is a 28bit addressing mode bottleneck > > > somewhere as > > > the log reports that 268435455 512 byte sectors found. (~131GB) (I > > > believe > > > 268435456 being the 28bit limit?) > > > > > > Although using it is OK I'm still wondering if it would be possible to > > > locate > > > the missing 20GB before the disk actually goes into active use. > > > > > > I'd like to know what is causing this limitation? > > > > > >> From the hardware I have: > > > > > > FreeBSD 4.4 -> make buildworld to 4.6.2, latest > > > kernel: 4.7-RC FreeBSD 4.7-RC #0: Sun Sep 22 01:39:47 EET 2002 > > > Firewire PCI card: fwohci0: > > > and a Western Digital 160GB drive in a standard firewire box. > > > > > > Again, accept my apologies if this is the wrong place to request > > > help\clarification on the matter but any help or hint is appreciated. > > > > > > Have a nice day, > > > > > > Sten > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-firewire" in the body of the message > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-firewire" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-firewire" in the body of the message From owner-freebsd-firewire Thu Sep 26 5: 8:40 2002 Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E391C37B401 for ; Thu, 26 Sep 2002 05:08:36 -0700 (PDT) Received: from ns.koganei.wide.ad.jp (koganei.wide.ad.jp [202.249.37.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDA4D43E6E for ; Thu, 26 Sep 2002 05:08:35 -0700 (PDT) (envelope-from ikob@koganei.wide.ad.jp) Received: from koganei.wide.ad.jp (tweedledee.koganei.wide.ad.jp [202.249.37.72]) (authenticated bits=0) by ns.koganei.wide.ad.jp (8.12.3/8.12.3) with ESMTP id g8QCBmXk026368; Thu, 26 Sep 2002 21:11:48 +0900 (JST) (envelope-from ikob@koganei.wide.ad.jp) X-Authentication-Warning: ns.koganei.wide.ad.jp: Host tweedledee.koganei.wide.ad.jp [202.249.37.72] claimed to be koganei.wide.ad.jp Date: Thu, 26 Sep 2002 21:10:23 +0900 Subject: Re: 28bit address limitation on HD Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v546) Cc: freebsd-firewire@FreeBSD.ORG To: exile@chamber.ee From: Katsushi Kobayashi In-Reply-To: <20020926105811.envmzsns5m0ogk@.chamber.ee> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.546) Sender: owner-freebsd-firewire@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, By the basic policy of current SBP-II driver, the different device No. is assigned if the device has different EUI-64 ID. If you had once attached other SBP-II SCSI disk or IDE/Firewire bridges, the device No. is not zero. Even if the first device has been removed already. In the case of dynamic attached disk system, it is difficult to manipulate legacy UNIX way. This issue is not only SBP-II. I thought some mechanism or policy is needed which disk should bind which ids. Also, I am not sure, why happen busy device messages. On 2002.Sep.26, at 05:58 PM, Sten Poldma wrote: > > Hi, > > A follow-up om the case previously reported.. > > [excuse me for the rant] > > A new box: MAPOWER (MAP-35F), Unfortunately it does not appear on the > manufacturer homepage anymore: http://www.mapower.com.tw/ieee_1394.htm > But is similar to the MAP-J51F although not much details are offered > there. > > The box works fine Under MacOS X, when plugging into the FreeBSD and > loading the > firewire drivers, I see the Hd fine.. > > /kernel: da1: Fixed Simplified Direct Access SCSI-4 > device > /kernel: da1: 50.000MB/s transfers > /kernel: da1: 156334MB (320173056 512 byte sectors: 255H 63S/T 19929C) > > As you can see, it is the same Hd, and the geometry looks fine.. > The HD was formatted to UFS in Mac before plugging it in, still, I did > not find > the partition there when I plugged it to the BSD machine. > > Anyhow, I partitioned, Labeled it and newfs'it through the > /stand/sysinstall > with no freaky settings. So far so good, and created the da1s1e > partition. > > When trying to mount it, I get device busy. I try to switch the ports > of the > firewire etc, Still unable to mount it with the same error. I check the > partition and label, they look to be OK. > > So what seems to be the problem now ? The sytem can see the box and > the disk, I > can fdisk,label,newfs it. But I can't mount it. > > Also, why is the device recognized as da1 ? It is the only device on > the chain. > > Anyway, I seemed to solve the problem with rebooting the entire box > (firewire > driver unload\load cycle did not seem to help). The reboot phase gave > me a Page > Fault 12 error as well, but after the system came up, the device was > recognized > as da0 and mounting the disk was fine. > > I find it peculiar behaviour, do you happen to have any idea of what > might have > caused this ? > > Anyway, I hope this little experience might come in handy to someone > in the > future. > > Regards, > > Sten > > Sten Poldma said: > >> >> Hi, >> >> Thanks for the response, that's probably it, The bridge uses the >> Oxford chipset, >> which probably does not support the 48 bit mode. >> >> I'm sure a new box will remedy the problem. >> >> Thanks again, >> >> Sten >> >> Katsushi Kobayashi said: >> >>> >>> I have not had any experience on the such disk size of IEEE1394 disk. >>> >>> If you are using IEEE1394/IDE bridge or similar one, let me know >>> the product information. Or if you have an experience on other OS, >>> let me know whether to success to detect size in correct. >>> >>> >>> On 2002.Sep.23, at 09:19 PM, Sten Poldma wrote: >>> >>>> >>>> Hi, >>>> >>>> I'm Sorry if the following is not firewire related but depends on >>>> other system >>>> components instead. >>>> >>>> I'm using the newest firewire driver >>>> (http://people.freebsd.org/~simokawa/firewire-20020918.tar.gz) >>>> >>>> To test a 160GB IDE drive (in a box), through the CAM and >>>> passthrough >>>> drivers I >>>> have no problem locating the device (da0) but the geometry of the >>>> drive found >>>> makes me believe that there is a 28bit addressing mode bottleneck >>>> somewhere as >>>> the log reports that 268435455 512 byte sectors found. (~131GB) (I >>>> believe >>>> 268435456 being the 28bit limit?) >>>> >>>> Although using it is OK I'm still wondering if it would be possible >>>> to >>>> locate >>>> the missing 20GB before the disk actually goes into active use. >>>> >>>> I'd like to know what is causing this limitation? >>>> >>>>> From the hardware I have: >>>> >>>> FreeBSD 4.4 -> make buildworld to 4.6.2, latest >>>> kernel: 4.7-RC FreeBSD 4.7-RC #0: Sun Sep 22 01:39:47 EET 2002 >>>> Firewire PCI card: fwohci0: >>>> and a Western Digital 160GB drive in a standard firewire box. >>>> >>>> Again, accept my apologies if this is the wrong place to request >>>> help\clarification on the matter but any help or hint is >>>> appreciated. >>>> >>>> Have a nice day, >>>> >>>> Sten >>>> >>>> To Unsubscribe: send mail to majordomo@FreeBSD.org >>>> with "unsubscribe freebsd-firewire" in the body of the message >>> >> >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-firewire" in the body of the message >> > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-firewire" in the body of the message From owner-freebsd-firewire Thu Sep 26 14:30: 0 2002 Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CBF137B401 for ; Thu, 26 Sep 2002 14:29:59 -0700 (PDT) Received: from rotini.customfilmeffects.com (rotini.customfilmeffects.com [66.134.82.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EE9F43E6A for ; Thu, 26 Sep 2002 14:29:59 -0700 (PDT) (envelope-from david@customfilmeffects.com) Received: from ethel (lan08.customfilmeffects.com [192.168.1.8]) by rotini.customfilmeffects.com (8.11.6/8.11.6) with SMTP id g8QLI1A11306 for ; Thu, 26 Sep 2002 14:18:01 -0700 Message-ID: <00ec01c265a3$de400f50$0801a8c0@customfilmeffects.com> From: "David Smithson" To: Subject: RAID Host Adapter Date: Thu, 26 Sep 2002 14:30:00 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-firewire@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi. I've been looking at Indigita Corp's products. They will soon have a host adapter that supports RAID configurations (iDT800PCI). I was just wondering if there is any reason to think this adapter will not work with the current FreeBSD firewire module? -- David Smithson - Systems Administrator Custom Film Effects To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-firewire" in the body of the message