From owner-freebsd-hackers Wed Dec 4 14:20: 9 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92AA937B401; Wed, 4 Dec 2002 14:20:05 -0800 (PST) Received: from herbelot.dyndns.org (herbelot.net1.nerim.net [62.212.117.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id F019B43EB2; Wed, 4 Dec 2002 14:20:03 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.12.6/8.12.6) with ESMTP id gB4ML40f007531; Wed, 4 Dec 2002 23:21:05 +0100 (CET) Content-Type: text/plain; charset="us-ascii" From: Thierry Herbelot To: "freebsd-hackers@FreeBSD.ORG" , hardware@FreeBSD.ORG Subject: problems with a firewire external hard disk [long] Date: Wed, 4 Dec 2002 23:19:56 +0100 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200212042319.56065.thierry@herbelot.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I can't seem to use my new external firewire hard disk : (this is with 5.0-DP2, there are the same kinds of symptoms under 4.7-Stable) My main question is to know where the problems are : is the hard disk dead ? is the firewire/ATA bridge fried ? are all problems due to the driver ? Any help very much appreciated (or hints to get debugging / trace info) TfH Here follows a list of problems encountered : 1/ error messages at startup ============================================ when booting, the disk is detected as : (for 5.0-DP2) firewire0:Discover new S400 device ID:00a0b800370000aa bus_explore done Device SBP-II sbp_post_explore: EUI:00a0b800370000aa spec=1 key=1. sbp0:0:0 LOGIN sbp0:0:0 ordered:0 type:0 EUI:00a0b800370000aa node:0 speed:2 maxrec:5 new! sbp0:0:0 'LSI Logic' 'SYM13FW500-DISK DRIVE' 'a0b835' sbp0:0:0 login: len 16, ID 0, cmd 0000fffff0010000, recon_hold 1 sbp0:0:0 sbp_busy_timeout sbp0:0:0 sbp_agent_reset sbp0:0:0 sbp_do_attach sbp0:0:0 sbp_cam_scan_lun sbp0:0:0 ORB status src:1 resp:0 dead:1 len:3 stat:c orb:0008c83a4 sbp0:0:0 Request aborted sbp0:0:0 sbp_agent_reset sbp0:0:0 XPT_SCSI_IO: cmd: 12 01 80 00 ff 00 00 00 00 00, flags: 0x40, 6b cmd/255b data/18b sense sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 24 qlfr 0 len 3 sbp0:0:0 ORB status src:1 resp:0 dead:1 len:3 stat:c orb:0008c84d8 sbp0:0:0 Request aborted sbp0:0:0 sbp_agent_reset sbp0:0:0 XPT_SCSI_IO: cmd: 00 00 00 00 00 00 00 00 00 00, flags: 0xc0, 6b cmd/0b data/32b sense sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 6 code 29 qlfr 0 len 3 sbp0:0:0 ORB status src:1 resp:0 dead:1 len:3 stat:c orb:0008c89a8 sbp0:0:0 Request aborted sbp0:0:0 sbp_agent_reset sbp0:0:0 XPT_SCSI_IO: cmd: 12 01 80 00 ff 00 00 00 00 00, flags: 0x40, 6b cmd/255b data/18b sense sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 24 qlfr 0 len 3 da0 at sbp0 bus 0 target 0 lun 0 da0: Fixed Simplified Direct Access SCSI-0 device da0: 50.000MB/s transfers da0: 28615MB (58605120 512 byte sectors: 255H 63S/T 3648C) I'm a bit disturbed by the "Request aborted" messages 2/ Geometry problems ============================================ furthermore, I can't use more than the first 1024 cylinders of the disk : I cannot create a BIOS partition above cylinder 1024 (all partitions seem cut at 1024, when seen from the 4.7-Stable of 5.0 fdisk, even when forcing 3648 cylinders for the size) for now, I've tried to just use 4 1G partitions : portable-cur# fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=3648 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=3648 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 2040192 (996 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 126/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 2040255, size 2040255 (996 Meg), flag 80 (active) beg: cyl 127/ head 0/ sector 1; end: cyl 253/ head 254/ sector 63 The data for partition 3 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 4080510, size 2040255 (996 Meg), flag 80 (active) beg: cyl 254/ head 0/ sector 1; end: cyl 380/ head 254/ sector 63 The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 6120765, size 2040255 (996 Meg), flag 80 (active) beg: cyl 381/ head 0/ sector 1; end: cyl 507/ head 254/ sector 63 portable-cur# (why are all partitions active ?) 3/ Write errors ============================================ when I try to write to any partitions, one write operations ends "as stuck", with an error message such as : Dec 4 21:41:09 portable-cur kernel: sbp_scsi_status: unknown scsi status Dec 4 21:41:09 portable-cur kernel: sbp0:0:0 sbp_abort_ocb 0x1b Dec 4 21:41:09 portable-cur kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 2a 00 00 00 00 9f 00 00 20 00, flags: 0x80, 10b cmd/16384b data/32b sense Dec 4 21:41:09 portable-cur kernel: sbp0:0:0 ORB status src:0 resp:1 dead:1 len:3 stat:4 orb:0008c8fac Dec 4 21:41:09 portable-cur kernel: sbp0:0:0 Object: Operation request block (ORB), Serial Bus Error: Busy retry limit exceeded(X) Dec 4 21:41:09 portable-cur kernel: sbp0:0:0 unordered execution order:1 Dec 4 21:41:09 portable-cur kernel: sbp0:0:0 sbp_agent_reset Dec 4 21:41:09 portable-cur kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 2a 00 00 00 00 9f 00 00 20 00, flags: 0x80, 10b cmd/16384b data/32b sense Dec 4 21:41:09 portable-cur kernel: sbp0:0:0 SCSI status 8 sfmt 0 valid 0 key b code 8 qlfr 0 len 3 Dec 4 21:41:09 portable-cur kernel: sbp_scsi_status: unknown scsi status Dec 4 21:41:09 portable-cur kernel: sbp0:0:0 sbp_abort_ocb 0x1b Dec 4 21:41:09 portable-cur kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 2a 00 00 00 00 7f 00 00 20 00, flags: 0x80, 10b cmd/16384b data/32b sense Dec 4 21:41:10 portable-cur kernel: sbp0:0:0 ORB status src:0 resp:1 dead:1 len:3 stat:4 orb:0008c9214 Dec 4 21:41:10 portable-cur kernel: sbp0:0:0 Object: Operation request block (ORB), Serial Bus Error: Busy retry limit exceeded(X) Dec 4 21:41:10 portable-cur kernel: sbp0:0:0 unordered execution order:1 Dec 4 21:41:10 portable-cur kernel: sbp0:0:0 sbp_agent_reset Dec 4 21:41:10 portable-cur kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 2a 00 00 00 00 7f 00 00 20 00, flags: 0x80, 10b cmd/16384b data/32b sense Dec 4 21:41:10 portable-cur kernel: sbp0:0:0 SCSI status 8 sfmt 0 valid 0 key b code 8 qlfr 0 len 3 Dec 4 21:41:10 portable-cur kernel: sbp_scsi_status: unknown scsi status Dec 4 21:41:10 portable-cur kernel: sbp0:0:0 sbp_abort_ocb 0x1b Dec 4 21:41:10 portable-cur kernel: sbp0:0:0 XPT_SCSI_IO: cmd: 2a 00 00 00 00 9f 00 00 20 00, flags: 0x80, 10b cmd/16384b data/32b sense Dec 4 21:41:11 portable-cur kernel: sbp0:0:0 ORB status src:0 resp:1 dead:1 len:3 stat:4 orb:0008c947c Dec 4 21:41:11 portable-cur kernel: sbp0:0:0 Object: Operation request block (ORB), Serial Bus Error: Busy retry limit exceeded(X) ============================================ PS : I recently tried to read from the firewire disk of a colleague, which was formatted as HFS+, so these attempts did not go very far To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message