Date: Wed, 4 Dec 2002 16:31:45 -0700 From: "Kenneth D. Merry" <ken@kdm.org> To: Thierry Herbelot <thierry@herbelot.com> Cc: "freebsd-hackers@FreeBSD.ORG" <freebsd-hackers@FreeBSD.ORG>, hardware@FreeBSD.ORG Subject: Re: problems with a firewire external hard disk [long] Message-ID: <20021204163145.A12325@panzer.kdm.org> In-Reply-To: <200212042319.56065.thierry@herbelot.com>; from thierry@herbelot.com on Wed, Dec 04, 2002 at 11:19:56PM %2B0100 References: <200212042319.56065.thierry@herbelot.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 04, 2002 at 23:19:56 +0100, Thierry Herbelot wrote: > 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 It's complaining there about the serial number inquiry. That's normal, and you'll notice there are no CAM errors showing up from it. The firewire code is just being chatty. > 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 Now it's reporting unit attention, which is normal after power on. Again, we retry the command so it isn't a problem. > 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 It's complaining about the serial number inquiry again, doesn't like it. That's not a problem. > da0 at sbp0 bus 0 target 0 lun 0 > da0: <LSI Logi SYM13FW500-DISK b835> 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) [ someone else will have to address the fdisk issues ] > > 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 Looks like some sort of firewire error (i.e. not a SCSI error coming back from the drive). > 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 Now the drive says it's busy. Note that no CAM error has been printed for this one -- it probably got retried. > 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 This is a firewire-level problem. > 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 It says it's busy again. > 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) And that's a firewire error of some sort. > ============================================ > > 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 You can use dd to read from the drive and see at least whether reads work correctly. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021204163145.A12325>