Date: Fri, 25 Apr 2003 19:26:43 +0100 From: David Haworth <dave@fyonn.net> To: freebsd-questions@FreeBSD.ORG Subject: firewire drive Message-ID: <20030425192643.1f4860e4.dave@fyonn.net>
next in thread | raw e-mail | index | archive | help
hiya folks I recently got a smartdisk firelite firewire HD enclusure off the 'bay and stuck an old 2.5" HD in it and I'm having trouble. here is the url for the enclosure itself for interest: http://www.smartdisk.com/Products/Storage%20Products/Hard%20Drives/FireLite.asp it's a rather neat looking bus powered firewire enclosure for 2.5" ata drives. I initially plugged it into my 5-current box (last rebuild on the 23rd april, ie 2 days ago) and got this: <dmesg entry for fw controller first for info) Apr 23 19:49:33 blink kernel: fwohci0: vendor=104c, dev=8026 Apr 23 19:49:33 blink kernel: fwohci0: <1394 Open Host Controller Interface> mem 0xce000000-0xce003fff,0xce800000 -0xce8007ff irq 10 at device 7.0 on pci0 Apr 23 19:49:33 blink kernel: fwohci0: OHCI version 1.10 (ROM=1) Apr 23 19:49:33 blink kernel: fwohci0: No. of Isochronous channel is 4. Apr 23 19:49:33 blink kernel: fwohci0: EUI64 00:e0:18:00:00:03:67:08 Apr 23 19:49:33 blink kernel: fwohci0: Phy 1394a available S400, 1 ports. Apr 23 19:49:33 blink kernel: fwohci0: Link S400, max_rec 2048 bytes. Apr 23 19:49:33 blink kernel: firewire0: <IEEE1394(FireWire) bus> on fwohci0 Apr 23 19:49:33 blink kernel: fwohci0: Initiate bus reset entry for the drive: Apr 24 17:23:23 blink kernel: sbp0: <SBP2/SCSI over firewire> on firewire0 Apr 24 17:23:32 blink kernel: fwohci0: BUS reset Apr 24 17:23:32 blink kernel: fwohci0: node_id=0x8800ffc0, gen=4, non CYCLEMASTER mode Apr 24 17:23:32 blink kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me) Apr 24 17:23:37 blink kernel: da1 at sbp0 bus 0 target 0 lun 0 Apr 24 17:23:37 blink kernel: da1: <SmartDis FireLite Drive 2801> Fixed Simplified Direct Access SCSI-0 device Apr 24 17:23:37 blink kernel: da1: 50.000MB/s transfers, Tagged Queueing Enabled Apr 24 17:23:37 blink kernel: da1: 3102MB (6354432 512 byte sectors: 255H 63S/T 395C) which looked good. it also spat stuff like this out at me: Apr 24 17:23:37 blink kernel: (da1:sbp0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 Apr 24 17:23:37 blink kernel: (da1:sbp0:0:0:0): UNIT ATTENTION asc:24,0 Apr 24 17:23:37 blink kernel: (da1:sbp0:0:0:0): Invalid field in CDB Apr 24 17:23:37 blink kernel: (da1:sbp0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 Apr 24 17:23:37 blink kernel: (da1:sbp0:0:0:0): UNIT ATTENTION csi:c4,b1,ea,20 asc:24,0 Apr 24 17:23:37 blink kernel: (da1:sbp0:0:0:0): Invalid field in CDB (lots of) but it produced da1 entries in /dev so I mounted the drive and saw all the contents of the HD on it (it was originally formatted for ntfs. I tarred all that stuff up, about a gig onto another drive and that worked fine. then I used sysinstall to repartion the drive into one big ffs volume so I could have a play. once I'd done the partitioning and labelling from sysinstall it left me with da1, da1s1 and da1s1c whcih seemed odd, I was expecting to be formatting da1s1a or somesuch. I ran newfs on da1s1 and it seemed to work. I then mounted it and that worked but I run into trouble when I try and copy stuff to it. if I copy small files one at a time, it works fine. but as soon as I try and copy a large file, or many large files it just locks up. the copy stops copying but I can;t break the copy. and other things start acting up. ie I started up iostat which hung too. or xterms might suddenly stop appearing when I start a new one from my wm's menu (fluxbox). I'd pull the drive and put it back in and then things would burst back into life a bit, but not always. sometimes the box has ended up hung completely and I had to hit the reset switch. I'd see stuff like this in the logs Apr 24 18:22:29 blink kernel: sbp0:0:0 request timeout ... agent reset Apr 24 18:23:29 blink kernel: sbp0:0:0 request timeout ... target reset Apr 24 18:24:29 blink kernel: sbp0:0:0 request timeout ... agent reset Apr 24 18:25:29 blink kernel: sbp0:0:0 request timeout ... target reset Apr 24 18:26:29 blink kernel: sbp0:0:0 request timeout ... agent reset any idea's folks? I've not tried this on a windows box yet as I don;t have one, but I'm intending to try one at the weekend when I visit a friend. thanks in advance for any help. dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030425192643.1f4860e4.dave>