From owner-freebsd-firewire@FreeBSD.ORG Mon Mar 6 11:02:59 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org 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 16C5816A420 for ; Mon, 6 Mar 2006 11:02:59 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C06AD43D45 for ; Mon, 6 Mar 2006 11:02:58 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k26B2wu0097981 for ; Mon, 6 Mar 2006 11:02:58 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k26B2u6Z097699 for freebsd-firewire@freebsd.org; Mon, 6 Mar 2006 11:02:56 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 6 Mar 2006 11:02:56 GMT Message-Id: <200603061102.k26B2u6Z097699@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-firewire@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Mar 2006 11:02:59 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/11/22] kern/74238 firewire [firewire] fw_rcv: unknown response; fire o [2005/08/29] kern/85434 firewire [fwip] fwip (IP over firewire) doesn't wo 2 problems total. Non-critical problems From owner-freebsd-firewire@FreeBSD.ORG Thu Mar 9 15:32:01 2006 Return-Path: X-Original-To: freebsd-firewire@freebsd.org 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 B7D6116A420 for ; Thu, 9 Mar 2006 15:32:01 +0000 (GMT) (envelope-from mkucenski@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73AE643D49 for ; Thu, 9 Mar 2006 15:32:01 +0000 (GMT) (envelope-from mkucenski@mac.com) Received: from mac.com (webmail09-en1 [10.13.10.98]) by smtpout.mac.com (Xserve/8.12.11/smtpout11/MantshX 4.0) with ESMTP id k29FW1QV017331 for ; Thu, 9 Mar 2006 07:32:01 -0800 (PST) Received: from webmail09 (localhost [127.0.0.1]) by mac.com (Xserve/webmail09/MantshX 4.0) with ESMTP id k29FVxPR006889 for ; Thu, 9 Mar 2006 07:32:01 -0800 (PST) Message-ID: <3135653.1141918319959.JavaMail.mkucenski@mac.com> Date: Thu, 09 Mar 2006 10:31:59 -0500 From: Matt Kucenski To: freebsd-firewire@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 214.3.138.234/instID=134 Subject: Access Mac in Target Disk Mode X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Mar 2006 15:32:01 -0000 I am attempting to access a Macintosh computer in Target Disk Mode (i.e. as an external hard drive) over firewire with no success. I am wondering if there is anyone out there who has tried this or if someone with more firewire experience can help me figure out what is going on. When I make the firewire connection: Mar 2 17:24:47 Matt kernel: fwohci0: BUS reset Mar 2 17:24:47 Matt kernel: fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode Mar 2 17:24:47 Matt kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) Mar 2 17:24:47 Matt kernel: firewire0: bus manager 1 (me) Mar 2 17:24:47 Matt kernel: firewire0: New S800 device ID:001124fffee4b4cc Mar 2 17:24:48 Matt kernel: da5 at sbp0 bus 0 target 0 lun 0 Mar 2 17:24:48 Matt kernel: da5: Removable Simplified Direct Access SCSI-3 device Mar 2 17:24:48 Matt kernel: da5: 50.000MB/s transfers Mar 2 17:24:48 Matt kernel: da5: Attempt to query device size failed: NOT READY, Medium not present Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): CAM Status: SCSI Status Error Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): SCSI Status: Check Condition Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): NOT READY asc:3a,0 Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): Medium not present Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): Unretryable error Mar 2 17:24:48 Matt kernel: Opened disk da5 -> 6 Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): CAM Status: SCSI Status Error Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): SCSI Status: Check Condition Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): NOT READY asc:3a,0 Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): Medium not present Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): Unretryable error Mar 2 17:24:48 Matt kernel: Opened disk da5 -> 6 Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): CAM Status: SCSI Status Error Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): SCSI Status: Check Condition Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): NOT READY asc:3a,0 Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): Medium not present Mar 2 17:24:48 Matt kernel: (da5:sbp0:0:0:0): Unretryable error Mar 2 17:24:48 Matt kernel: Opened disk da5 -> 6 When I try to access da5 with something like 'dd if=/dev/da5 of=./test.img bs=8192': dd: /dev/da5: Device not configured and I get more of the "medium not present" and "unretryable error" messages. 'camcontrol devlist' shows: at scbus1 target 0 lun 0 (pass6,da5) at scbus5 target 0 lun 0 (pass0,da0) at scbus5 target 0 lun 1 (pass1,da1) at scbus5 target 0 lun 2 (pass2,da2) at scbus5 target 0 lun 3 (pass3,da3) at scbus7 target 0 lun 0 (cd0,pass4) at scbus13 target 0 lun 0 (pass5,da4) 'fwcontrol -c 0' shows: first quad: 0x0404e1b1 info_len=4 crc_len=4 crc=0xe1b1(OK) bus_name: 0x31333934 irmc:0 cmc:0 isc:0 bmc:0 pmc:0 cyc_clk_acc:0 max_rec:11 max_rom:0 generation:12 link_spd:3 EUI64: 00-11-24-ff-fe-e4-b4-cc root_directory: len=0x0008(8) crc=0xe36d(OK) 03(I:03) 000a27 module_vendor_ID: 81(L:01) 00000d text_leaf: len=3 crc=0xb542(OK) AAPL 0c(I:0c) 0083c0 node_capabilities: 04(I:04) 020000 hardware_version: 17(I:17) 54444d model_ID: 81(L:01) 00000d text_leaf: len=6 crc=0xa7ba(OK) Target Disk Mode d1(D:11) 000013 unit_directory: len=7 crc=0xeb0f(OK) 12(I:12) 00609e unit_spec_ID: 13(I:13) 010483 unit_sw_version: SBP-2 38(I:38) 00609e command_set_spec_ID: 39(I:39) 0104d8 command_set: 3a(I:3a) 401e08 unit_characteristics: 14(I:14) 0e0000 logical_unit_number: 54(C:14) 004000 management_agent: offset=0x4000(16384) d1(D:11) 00001a unit_directory: len=7 crc=0xcf6d(OK) 12(I:12) 00609e unit_spec_ID: 13(I:13) 010483 unit_sw_version: SBP-2 38(I:38) 00609e command_set_spec_ID: 39(I:39) 0104d8 command_set: 3a(I:3a) 401e08 unit_characteristics: 14(I:14) 0e0000 logical_unit_number: 54(C:14) 004020 management_agent: offset=0x4020(16416) Linux does not have any problems accessing the drive (the same dd command works fine): Scanning for device 7 0 0 0 ... OLD: Host: scsi7 Channel: 00 Id: 00 Lun: 00 Vendor: AAPL Model: FireWire Target Rev: 0000 Type: Direct-Access ANSI SCSI revision: 03 Scanning for device 7 0 1 0 ... OLD: Host: scsi7 Channel: 00 Id: 01 Lun: 00 Vendor: AAPL Model: FireWire Target Rev: 0000 Type: Direct-Access ANSI SCSI revision: 03 Linux appears to be recognizing two targets on the Mac, but FreeBSD is only showing one. My guess is that for some reason FreeBSD is not making both targets accessible and the second one is the one I need to access the hard drive data. In fact when in Linux I had /dev/sde and /dev/sdf (I believe). I wasn't able to use dd on sde, but was sdf. I'm not sure why the Mac is showing two targets. I am using 6-STABLE from about a month ago. Does anyone have any thoughts on this problem? I am interested in making this work because I use FreeBSD for computer forensics work and occasionally need to make images of Macintosh computers. Many of Apple's newer systems are a pain to disassemble to remove the hard drive. I would prefer to stay with FreeBSD and not have to switch to Linux to create the disk images. Thanks, -Matt