Addonics AE51DECSUF (OXFW900 based enclosure) does not work with linux 2.6.10

Vendor claims support in Linux 2.4 and later of the enclosure, but I cannot get
it working with Linux 2.6.10. Btw, this just a SATA to IDE bridge + IDE to
Firewire + USB2 enclosure.

Device appears to be recognized during boot with either of the following two
sequence of log events:

Jan 10 11:45:35 kmsg_source@pawan kernel: ohci1394: fw-host0: SelfID received,
         but NodeID invalid (probably new bus reset occurred): 0800FFC0
Jan 10 11:45:35 kmsg_source@pawan kernel: ieee1394: Error parsing configrom for node 0-00:1023
Jan 10 11:45:35 kmsg_source@pawan kernel: ieee1394: Node changed: 0-00:1023 -> 0-01:1023
Jan 10 11:45:44 kmsg_source@pawan kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[0030e0f3e0101660]
Jan 10 11:45:44 log_source@pawan udevsend[29781]: udevd daemon started
Jan 10 11:45:44 log_source@pawan udevsend[29782]: udevd daemon started
Jan 10 11:45:45 kmsg_source@pawan kernel: sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
Jan 10 11:45:45 kmsg_source@pawan kernel: scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices
Jan 10 11:45:46 kmsg_source@pawan kernel: ieee1394: sbp2: Logged into SBP-2 device
Jan 10 11:45:46 kmsg_source@pawan kernel: ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Jan 10 11:45:46 kmsg_source@pawan kernel: Vendor: ST340083 Model: 2AS Rev:
Jan 10 11:45:46 kmsg_source@pawan kernel: Type: Direct-Access ANSI SCSI revision: 06
Jan 10 11:45:46 kmsg_source@pawan kernel: SCSI device sdd: 781422768 512-byte hdwr sectors (400088 MB)
Jan 10 11:45:46 kmsg_source@pawan kernel: sdd: asking for cache data failed
Jan 10 11:45:46 kmsg_source@pawan kernel: sdd: assuming drive cache: write through
Jan 10 11:45:46 kmsg_source@pawan kernel: SCSI device sdd: 781422768 512-byte hdwr sectors (400088 MB)
Jan 10 11:45:46 kmsg_source@pawan kernel: sdd: asking for cache data failed
Jan 10 11:45:46 kmsg_source@pawan kernel: sdd: assuming drive cache: write through
Jan 10 11:45:46 kmsg_source@pawan kernel: sdd: unknown partition table
Jan 10 11:45:46 kmsg_source@pawan kernel: Attached scsi disk sdd at scsi1, channel 0, id 0, lun 0
Jan 10 11:45:46 kmsg_source@pawan kernel: Attached scsi generic sg4 at scsi1, channel 0, id 0, lun 0, type 0
Jan 10 11:45:46 log_source@pawan ieee1394.agent[29790]: sbp2: loaded successfully
Jan 10 11:45:46 log_source@pawan scsi.agent[29879]: disk at
        /devices/pci0000:00/0000:00:0d.0/fw-host0/0030e0f3e0101660/0030e0f3e0101660-0/host1/target1:0:0/1:0:0:0
Jan 10 11:45:54 log_source@pawan udev[29901]: creating device node '/dev/sg4'
Jan 10 11:45:54 log_source@pawan udev[29899]: creating device node '/dev/sdd'

or:

Jan 11 01:00:35 kmsg_source@pawan kernel: ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
Jan 11 01:00:35 kmsg_source@pawan kernel: PCI: Found IRQ 12 for device 0000:00:0d.0
Jan 11 01:00:35 kmsg_source@pawan kernel: PCI: Sharing IRQ 12 with 0000:00:04.2
Jan 11 01:00:35 kmsg_source@pawan kernel: PCI: Sharing IRQ 12 with 0000:00:04.3
Jan 11 01:00:35 kmsg_source@pawan kernel: ohci1394: fw-host0: OHCI-1394 1.0 (PCI):
        IRQ=[12] MMIO=[de800000-de8007ff] Max Packet=[2048]
Jan 11 01:00:35 kmsg_source@pawan kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[0030e0f3e0101660]
Jan 11 01:00:35 kmsg_source@pawan kernel: ieee1394: Host added: ID:BUS[0-01:1023] GUID[230050c50000ba2d]
Jan 11 01:00:35 kmsg_source@pawan kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 11 01:00:35 kmsg_source@pawan kernel: sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
Jan 11 01:00:35 kmsg_source@pawan kernel: scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices
Jan 11 01:00:35 kmsg_source@pawan kernel: ip_conntrack version 2.1
        (6143 buckets, 49144 max) - 300 bytes per conntrack
Jan 11 01:00:35 kmsg_source@pawan kernel: ieee1394: sbp2: Logged into SBP-2 device
Jan 11 01:00:35 kmsg_source@pawan kernel: ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Jan 11 01:00:35 kmsg_source@pawan kernel: Vendor: ST340083 Model: 2AS Rev:
Jan 11 01:00:35 kmsg_source@pawan kernel: Type: Direct-Access ANSI SCSI revision: 0 6
Jan 11 01:00:35 kmsg_source@pawan kernel: SCSI device sdd: 781422768 512-byte hdwr sectors (400088 MB)
Jan 11 01:00:35 kmsg_source@pawan kernel: sdd: asking for cache data failed
Jan 11 01:00:35 kmsg_source@pawan kernel: sdd: assuming drive cache: write through
Jan 11 01:00:35 kmsg_source@pawan kernel: SCSI device sdd: 781422768 512-byte hdwr sectors (400088 MB)
Jan 11 01:00:35 kmsg_source@pawan kernel: sdd: asking for cache data failed
Jan 11 01:00:35 kmsg_source@pawan kernel: sdd: assuming drive cache: write through
Jan 11 01:00:35 kmsg_source@pawan kernel: sdd: sdd1
Jan 11 01:00:35 kmsg_source@pawan kernel: Attached scsi disk sdd at scsi1, channel 0, id 0, lun 0
Jan 11 01:00:35 kmsg_source@pawan kernel: Attached scsi generic sg4 at scsi1, channel 0, id 0, lun 0, type 0

The two events "sdd: asking for cache data failed" and "sdd: assuming drive
cache: write through" does not sound good.

I (obviously) managed to fdisk the device, and `mkfs -text3 -m0` seem to
working for between 105 and 499 of the 2981 inode tables before I get:

Jan 11 01:04:17 kmsg_source@pawan kernel: ieee1394: sbp2: aborting sbp2 command
Jan 11 01:04:17 kmsg_source@pawan kernel: Write (10) 00 2e 93 7c 3f 00 00 80 00
Jan 11 01:04:27 kmsg_source@pawan kernel: ieee1394: sbp2: aborting sbp2 command
Jan 11 01:04:27 kmsg_source@pawan kernel: Test Unit Ready 00 00 00 00 00
Jan 11 01:04:27 kmsg_source@pawan kernel: ieee1394: sbp2: aborting sbp2 command
Jan 11 01:04:27 kmsg_source@pawan kernel: Write (10) 00 04 ec 0c 4f 00 00 fe 00
Jan 11 01:04:37 kmsg_source@pawan kernel: ieee1394: sbp2: aborting sbp2 command
Jan 11 01:04:37 kmsg_source@pawan kernel: Test Unit Ready 00 00 00 00 00
Jan 11 01:04:37 kmsg_source@pawan kernel: ieee1394: sbp2: aborting sbp2 command
Jan 11 01:04:37 kmsg_source@pawan kernel: Write (10) 00 04 ec 0d 4d 00 00 fe 00
Jan 11 01:04:47 kmsg_source@pawan kernel: ieee1394: sbp2: aborting sbp2 command
Jan 11 01:04:47 kmsg_source@pawan kernel: Test Unit Ready 00 00 00 00 00
Jan 11 01:04:47 kmsg_source@pawan kernel: ieee1394: sbp2: aborting sbp2 command
Jan 11 01:04:47 kmsg_source@pawan kernel: Write (10) 00 04 ec 0e 4b 00 00 fe 00
Jan 11 01:08:47 kmsg_source@pawan kernel: - not ready after error recovery: host 1 channel 0 id 0 lun 0
Jan 11 01:08:47 kmsg_source@pawan kernel:
        scsi: Device offlined - not ready after error recovery: host 1 channel 0 id 0 lun 0
Jan 11 01:08:47 kmsg_source@pawan kernel:
        scsi: Device offlined - not ready after error recovery: host 1 channel 0 id 0 lun 0
Jan 11 01:08:47 kmsg_source@pawan kernel:
        scsi: Device offlined - not ready after error recovery: host 1 channel 0 id 0 lun 0
Jan 11 01:08:47 kmsg_source@pawan kernel:
        scsi: Device offlined - not ready after error recovery: host 1 channel 0 id 0 lun 0
Jan 11 01:08:47 kmsg_source@pawan kernel:
        scsi: Device offlined - not ready after error recovery: host 1 channel 0 id 0 lun 0
Jan 11 01:08:48 kmsg_source@pawan kernel:
        scsi: Device offlined - not ready after error recovery: host 1 channel 0 id 0 lun 0
Jan 11 01:08:48 kmsg_source@pawan kernel:
        scsi: Device offlined - not ready after error recovery: host 1 channel 0 id 0 lun 0
Jan 11 01:08:48 kmsg_source@pawan kernel: SCSI error : <1 0 0 0> return code = 0x50000
Jan 11 01:08:48 kmsg_source@pawan kernel: end_request: I/O error, dev sdd, sector 781417535
Jan 11 01:08:48 kmsg_source@pawan kernel: Buffer I/O error on device sdd1, logical block 390708736
Jan 11 01:08:48 kmsg_source@pawan kernel: lost page write due to I/O error on sdd1
Jan 11 01:08:48 kmsg_source@pawan kernel: scsi1 (0:0): rejecting I/O to offline device
[...]

Once mkfs completes, I can revive things thanks to the information provided
in http://marc.theaimsgroup.com/?m=110108595130929 with:

# rmmod ohci1394 sbp2 ieee1394
power cycle enclosure
# modprobe ohci1394

Neither max_speed=2 or serialize_io=1 makes any difference.

# gscanbus
couldn't get handle: No such file or directory
This probably means that you don't have raw1394 support in the kernel or that
you haven't loaded the raw1394 module.
# mknod /dev/raw1394 c 171 0
# gscanbus

and the output for the two nodes are:

SelfID Info
-----------
Physical ID: 1
Link active: Yes
Gap Count: 63
PHY Speed: S400
PHY Delay: <=144ns
IRM Capable: Yes
Power Class: -1W
Port 0: Not connected
Port 1: Not connected
Port 2: Connected to child node
Init. reset: No

CSR ROM Info
------------
GUID: 0x230050C50000BA2D
Node Capabilities: 0x000083C0
Vendor ID: 0x00230050
Unit Spec ID: 0x00000000
Unit SW Version: 0x00000000
Model ID: 0x00000000
Nr. Textual Leafes: 1

Vendor: Unknown
Textual Leafes:
Linux - ohci1394

AV/C Subunits
-------------
N/A

SelfID Info
-----------
Physical ID: 0
Link active: Yes
Gap Count: 63
PHY Speed: S400
PHY Delay: <=144ns
IRM Capable: No
Power Class: -1W
Port 0: Connected to parent node
Port 1: Not connected
Init. reset: Yes

CSR ROM Info
------------
GUID: 0x0030E0F3E0101660
Node Capabilities: 0x000083C0
Vendor ID: 0x000030E0
Unit Spec ID: 0x0000609E
Unit SW Version: 0x00010483
Model ID: 0x00000001
Nr. Textual Leafes: 2

Vendor: OXFORD SEMICONDUCTOR LTD.
Textual Leafes:
Oxford Semiconductor Ltd.
OXFW900

AV/C Subunits
-------------
N/A

I gather from the archives that there are no resolution to this yet
(http://sourceforge.net/mailarchive/forum.php?thread_id=6052359&forum_id=5387).
LVM is required for the rest of my disks, so I cannot try the minimal
suggestion.

Any suggestions (other than trying 2.6.6 or 2.4.x)? Is there anything I can
help with to advance a resolution in current (2.6.10+) kernels?

/Allan

-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user