tag:blogger.com,1999:blog-4708820857427100257.post1618222258631747912..comments2023-05-02T15:47:32.269+02:00Comments on GNU/Linux every day use: Solved issues: Fwd: firewire_core: Unsolicited response (external HDD drive & firewire)Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4708820857427100257.post-51604272934126333762011-04-28T09:49:21.823+02:002011-04-28T09:49:21.823+02:00Thank you.
I use Lenny, but with lenny-backports ...Thank you.<br /><br />I use Lenny, but with lenny-backports repository. It still happens to me sometimes.<br /><br />I wondered if the other distributions have this problem. But I googled for "Device offlined - not ready after error recovery firewire" and, yes, they have. Maybe they all have imported this issue from one source.<br /><br />I wonder about other OSes...Martin Žemberhttps://www.blogger.com/profile/01418937094087300606noreply@blogger.comtag:blogger.com,1999:blog-4708820857427100257.post-3814508782548191102011-04-25T01:14:08.316+02:002011-04-25T01:14:08.316+02:00Hello,
I've been running a Macally FireWire e...Hello,<br /><br />I've been running a Macally FireWire external enclosure (the G-S350SUA : http://www.macally.com/en/product/ArticleShow.asp?ArticleID=215) on a Apple Mac Mini PPC running Debian 5 (Lenny) for several months, then a I updated Debian to version 6 (Squeeze) in February.<br /><br />But now I have the almost same problem that you have :<br />----------8<----------<br />Apr 22 19:11:17 nas kernel: [2650125.709952] firewire_core: phy config: card 0, new root=ffc1, gap_count=5<br />Apr 22 19:11:19 nas kernel: [2650128.360672] sd 4:0:0:0: [sdb] Stopping disk<br />Apr 22 19:11:47 nas kernel: [2650156.000552] firewire_sbp2: fw1.0: sbp2_scsi_abort<br />Apr 22 19:11:47 nas kernel: [2650156.002518] sd 4:0:0:0: Device offlined - not ready after error recovery<br />Apr 22 19:11:47 nas kernel: [2650156.007270] sd 4:0:0:0: [sdb] Unhandled error code<br />Apr 22 19:11:47 nas kernel: [2650156.008973] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK<br />Apr 22 19:11:47 nas kernel: [2650156.010822] sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 1a 57 2a f3 00 00 20 00<br />Apr 22 19:11:47 nas kernel: [2650156.012787] end_request: I/O error, dev sdb, sector 441920243<br />Apr 22 19:11:47 nas kernel: [2650156.018861] sd 4:0:0:0: [sdb] START_STOP FAILED<br />Apr 22 19:11:47 nas kernel: [2650156.021062] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK<br />Apr 22 19:11:47 nas kernel: [2650156.030707] firewire_sbp2: released fw1.0, target 4:0:0<br />Apr 22 19:11:47 nas kernel: [2650156.050134] EXT3-fs error (device sdb8): ext3_find_entry: reading directory #43917430 offset 0<br />Apr 22 19:11:47 nas kernel: [2650156.054863] EXT3-fs error (device sdb8): ext3_find_entry: reading directory #43917430 offset 0<br />[...]<br />----------8<----------<br /><br />As the problem only happened a month and an half after the Debian 6 upgrade, I'm not sure I can blame Squeeze, but I'm wondering if they didn't changed their FireWire drivers from Lenny to Squeeze.<br /><br />As my enclosure has both FireWire and USB connectivity I switched to USB but this can only be temporary given the limited bandwidth USB can offers.<br /><br />Anyway, I wanted you to know that you are not the only one experiencing such issue with external FireWire drive.CDuvhttp://claude.duvergier.frnoreply@blogger.com