MyBook connected through FireWire gets offline or has problems immediately after connecting:
[31061.790094] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
[31069.392433] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
[31071.343528] scsi16 : SBP-2 IEEE-1394
[31071.355051] scsi17 : SBP-2 IEEE-1394
[31071.355192] firewire_core: created device fw1: GUID 0090a938358b939f, S400, 3 config ROM retries
[31072.281325] firewire_sbp2: fw1.0: logged in to LUN 0000 (0 retries)
[31072.298622] scsi 16:0:0:0: Direct-Access WD My Book 1028 PQ: 0 ANSI: 4
[31072.304849] sd 16:0:0:0: [sdb] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
[31072.308829] sd 16:0:0:0: [sdb] Write Protect is off
[31072.308837] sd 16:0:0:0: [sdb] Mode Sense: 10 00 00 00
[31072.312188] sd 16:0:0:0: [sdb] Cache data unavailable
[31072.312194] sd 16:0:0:0: [sdb] Assuming drive cache: write through
[31072.318472] sd 16:0:0:0: [sdb] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB)
[31072.322446] sd 16:0:0:0: [sdb] Write Protect is off
[31072.322454] sd 16:0:0:0: [sdb] Mode Sense: 10 00 00 00
[31072.325780] sd 16:0:0:0: [sdb] Cache data unavailable
[31072.325787] sd 16:0:0:0: [sdb] Assuming drive cache: write through
[31072.325793] sdb: sdb1 sdb2 < sdb5 sdb6 sdb7 >
[31072.413205] sd 16:0:0:0: [sdb] Attached SCSI disk
[31072.413267] sd 16:0:0:0: Attached scsi generic sg2 type 0
[31073.708088] sd 16:0:0:0: [sdb] Unhandled error code
[31073.708098] sd 16:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
[31073.708109] end_request: I/O error, dev sdb, sector 40981815
[31073.708118] Buffer I/O error on device sdb2, logical block 0
[31073.818302] firewire_core: Unsolicited response (source ffc0, tlabel 1)
[31073.818312] firewire_core: Unsolicited response (source ffc0, tlabel 2)
[31073.818333] firewire_core: Unsolicited response (source ffc0, tlabel 3)
[31073.818341] firewire_core: Unsolicited response (source ffc0, tlabel 4)
[31073.818347] firewire_core: Unsolicited response (source ffc0, tlabel 5)
[31073.818367] firewire_core: Unsolicited response (source ffc0, tlabel 6)
[31073.818373] firewire_core: Unsolicited response (source ffc0, tlabel 7)
[31073.880623] firewire_sbp2: status write for unknown orb
[31075.752536] firewire_sbp2: fw1.1: logged in to LUN 0001 (0 retries)
[31075.893091] scsi 17:0:0:1: Enclosure WD My Book Device PQ: 0 ANSI: 4
[31075.896242] ses 17:0:0:1: Attached Enclosure device
[31075.896409] ses 17:0:0:1: Attached scsi generic sg3 type 13
[31103.989061] firewire_sbp2: fw1.0: sbp2_scsi_abort
[31113.992609] firewire_sbp2: fw1.0: sbp2_scsi_abort
[31114.000059] sd 16:0:0:0: Device offlined - not ready after error recovery
[31114.000086] sd 16:0:0:0: [sdb] Unhandled error code
[31114.000092] sd 16:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK
[31114.000101] end_request: I/O error, dev sdb, sector 40981878
[31114.000111] Buffer I/O error on device sdb5, logical block 0
[31114.000121] Buffer I/O error on device sdb5, logical block 1
[31114.000127] Buffer I/O error on device sdb5, logical block 2
[31114.000133] Buffer I/O error on device sdb5, logical block 3
[31114.000144] Buffer I/O error on device sdb5, logical block 4
[31114.000150] Buffer I/O error on device sdb5, logical block 5
[31114.000156] Buffer I/O error on device sdb5, logical block 6
[31114.000163] Buffer I/O error on device sdb5, logical block 7
[31114.000169] Buffer I/O error on device sdb5, logical block 8
[31114.000200] sd 16:0:0:0: rejecting I/O to offline device
This
Add
KERNEL=="fw[0-9]*", NAME="%k", OWNER="root", GROUP="root", MODE="0600"
to the file
/etc/udev/rules.d/50-udev.rules
I have to plug in the adapter, power on the MyBook with a button, then wait for a few minutes and then plug in the firewire cable.
Posts
Hello,
ReplyDeleteI'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.
But now I have the almost same problem that you have :
----------8<----------
Apr 22 19:11:17 nas kernel: [2650125.709952] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
Apr 22 19:11:19 nas kernel: [2650128.360672] sd 4:0:0:0: [sdb] Stopping disk
Apr 22 19:11:47 nas kernel: [2650156.000552] firewire_sbp2: fw1.0: sbp2_scsi_abort
Apr 22 19:11:47 nas kernel: [2650156.002518] sd 4:0:0:0: Device offlined - not ready after error recovery
Apr 22 19:11:47 nas kernel: [2650156.007270] sd 4:0:0:0: [sdb] Unhandled error code
Apr 22 19:11:47 nas kernel: [2650156.008973] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK
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
Apr 22 19:11:47 nas kernel: [2650156.012787] end_request: I/O error, dev sdb, sector 441920243
Apr 22 19:11:47 nas kernel: [2650156.018861] sd 4:0:0:0: [sdb] START_STOP FAILED
Apr 22 19:11:47 nas kernel: [2650156.021062] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK
Apr 22 19:11:47 nas kernel: [2650156.030707] firewire_sbp2: released fw1.0, target 4:0:0
Apr 22 19:11:47 nas kernel: [2650156.050134] EXT3-fs error (device sdb8): ext3_find_entry: reading directory #43917430 offset 0
Apr 22 19:11:47 nas kernel: [2650156.054863] EXT3-fs error (device sdb8): ext3_find_entry: reading directory #43917430 offset 0
[...]
----------8<----------
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.
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.
Anyway, I wanted you to know that you are not the only one experiencing such issue with external FireWire drive.
Thank you.
ReplyDeleteI use Lenny, but with lenny-backports repository. It still happens to me sometimes.
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.
I wonder about other OSes...