Thread: Freecom Hard Drive Quattro USB 3.0 TB Firewire problems
Brought to you by:
aeb,
bencollins
From: <pho...@ya...> - 2014-01-10 09:56:30
|
Hello List, I have run into problems with an external firewire disk. It is a new "Freecom Hard Drive Quattro USB 3.0 TB", P/N: 056068-71, Model Code SACCAA. The drive works fine over usb 2.0 and usb 3.0 on another laptop. I don't have an esata port, so I could not test esata. I spoke with Freecom's tech support on the phone, they did send me a firmware upgrader for windows my email, which I ran. However my drive already had that current fireware version. Freecom does not offer support for linux, so I did not get any further help. The firewire port on my linux laptop is a 4pin firewire 400 port. The port on the freecom is a 9pin firewire 800 port. The cables work fine with another freecom 1TB and another freecom 2TB "Freecom Hard Drive Quattro 2.0" drives over firewire. I also tested another different 4pin to 8pin firewire 400 cable and another two 4pin to 9pin firewire 800 cable. They all work with the other two older drives, but not with the new drive. When I connect the new drive, I can then create some small files, i.e. in the lower megabyte range, browse directories, write some text files, etc. The problem/errors start once I start a backup to save my data onto the external freecom disk. Is there something I can do to make this new freecom drive work ? fsck -pf of the filesystem returns no errors. Filesystem is ext4 inside a truecrypt container which uses all of the drive's first partition /dev/sdb1 The firewire controller inside the laptop is this one: 03:01.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02) (prog-if 10 [OHCI]) Subsystem: Dell Device 01f9 Flags: bus master, medium devsel, latency 64, IRQ 19 Memory at f1dff000 (32-bit, non-prefetchable) [size=4K] Memory at f1dfe800 (32-bit, non-prefetchable) [size=2K] Capabilities: [60] Power Management version 2 Kernel driver in use: firewire_ohci Kernel modules: firewire-ohci This is the dmesg output when I connect the drive: [38407.928194] scsi15 : SBP-2 IEEE-1394 [38407.928365] firewire_core 0000:03:01.4: created device fw1: GUID 0001db9200188188, S400 [38407.928378] firewire_core 0000:03:01.4: phy config: new root=ffc0, gap_count=5 [38408.146794] firewire_sbp2 fw1.0: logged in to LUN 0000 (0 retries) [38408.147879] scsi 15:0:0:0: Direct-Access ST3000DM 001-1CH166 PQ: 0 ANSI: 5 [38408.152234] sd 15:0:0:0: Attached scsi generic sg2 type 0 [38408.165642] sd 15:0:0:0: [sdb] 5860533152 512-byte logical blocks: (3.00 TB/2.72 TiB) [38408.180978] sd 15:0:0:0: [sdb] Write Protect is off [38408.180991] sd 15:0:0:0: [sdb] Mode Sense: 10 00 00 00 [38408.210982] sd 15:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [38408.293556] Alternate GPT is invalid, using primary GPT. [38408.293570] sdb: sdb1 [38408.357721] sd 15:0:0:0: [sdb] Attached SCSI disk This is the dmesg output when I mount the truecrypt partition on the freecom [38408.357721] sd 15:0:0:0: [sdb] Attached SCSI disk [38479.499458] bio: create slab <bio-1> at 1 [38479.897130] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null) This is the dmesg output after I start rsync to do the backup. [38835.735813] firewire_sbp2 fw1.0: status write for unknown ORB [38854.379707] firewire_sbp2 fw1.0: status write for unknown ORB [38864.309201] firewire_sbp2 fw1.0: status write for unknown ORB [38874.273059] firewire_sbp2 fw1.0: status write for unknown ORB [38883.707197] firewire_sbp2 fw1.0: status write for unknown ORB [38892.932137] sd 15:0:0:0: [sdb] Unhandled error code [38892.932149] sd 15:0:0:0: [sdb] [38892.932152] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK [38892.932156] sd 15:0:0:0: [sdb] CDB: [38892.932158] Write(16): 8a 00 00 00 00 00 10 60 89 00 00 00 04 00 00 00 [38892.932174] end_request: I/O error, dev sdb, sector 274761984 [38892.932220] EXT4-fs warning (device dm-0): ext4_end_bio:332: I/O error writing to inode 115343986 (offset 8388608 size 8388608 starting block 34344960) [38892.932225] buffer_io_error: 99624 callbacks suppressed [38892.932227] Buffer I/O error on device dm-0, logical block 34344960 [38892.932233] Buffer I/O error on device dm-0, logical block 34344961 [38892.932237] Buffer I/O error on device dm-0, logical block 34344962 [38892.932240] Buffer I/O error on device dm-0, logical block 34344963 [38892.932243] Buffer I/O error on device dm-0, logical block 34344964 [38892.932246] Buffer I/O error on device dm-0, logical block 34344965 [38892.932249] Buffer I/O error on device dm-0, logical block 34344966 [38892.932252] Buffer I/O error on device dm-0, logical block 34344967 [38892.932256] Buffer I/O error on device dm-0, logical block 34344968 [38892.932259] Buffer I/O error on device dm-0, logical block 34344969 [38893.116359] firewire_core 0000:03:01.4: phy config: new root=ffc1, gap_count=5 [38894.016023] firewire_ohci 0000:03:01.4: failed to read phy reg 5 [38894.016031] CPU: 0 PID: 22770 Comm: kworker/0:2 Tainted: GF O 3.11.0-031100-generic #201309021735 [38894.016033] Hardware name: Dell Inc. Latitude D630 / , BIOS A18 12/06/2011 [38894.016058] Workqueue: events bm_work [firewire_core] [38894.016060] 0000000000000067 ffff88018d695cb8 ffffffff81720fca 0000000000000000 [38894.016064] ffff88020f858000 ffff88018d695ce8 ffffffffa0084cbc ffffffffa0075420 [38894.016067] 0000000000000005 ffff88020f858000 0000000000000000 ffff88018d695d18 [38894.016070] Call Trace: [38894.016076] [<ffffffff81720fca>] dump_stack+0x46/0x58 [38894.016083] [<ffffffffa0084cbc>] read_phy_reg+0x8c/0xd0 [firewire_ohci] [38894.016089] [<ffffffffa0084d2d>] update_phy_reg+0x2d/0x70 [firewire_ohci] [38894.016094] [<ffffffffa0084dbd>] ohci_update_phy_reg+0x4d/0x80 [firewire_ohci] [38894.016100] [<ffffffffa006b054>] bm_work+0x464/0x500 [firewire_core] [38894.016106] [<ffffffffa006e700>] ? fw_device_update+0x40/0x40 [firewire_core] [38894.016111] [<ffffffff81081060>] process_one_work+0x170/0x4a0 [38894.016114] [<ffffffff81082121>] worker_thread+0x121/0x390 [38894.016118] [<ffffffff81082000>] ? manage_workers.isra.20+0x170/0x170 [38894.016121] [<ffffffff81088fe0>] kthread+0xc0/0xd0 [38894.016124] [<ffffffff81088f20>] ? flush_kthread_worker+0xb0/0xb0 [38894.016127] [<ffffffff81735a2c>] ret_from_fork+0x7c/0xb0 [38894.016130] [<ffffffff81088f20>] ? flush_kthread_worker+0xb0/0xb0 [38895.116039] firewire_sbp2 fw1.0: ORB reply timed out, rcode 0x00 [38895.116046] firewire_sbp2 fw1.0: failed to reconnect [38897.316035] firewire_sbp2 fw1.0: ORB reply timed out, rcode 0x00 [38902.334389] firewire_sbp2 fw1.0: status write for unknown ORB [38902.535616] firewire_sbp2 fw1.0: status write for unknown ORB [38903.359639] firewire_sbp2 fw1.0: status write for unknown ORB [38903.378997] firewire_sbp2 fw1.0: logged in to LUN 0000 (0 retries) Best regards P. |
From: <pho...@ya...> - 2014-01-10 13:20:23
|
Hello, I forgot to add my kernel version: uname -a Linux tuxtux 3.11.0-031100-generic #201309021735 SMP Mon Sep 2 21:36:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux This is a linux mint 13 maya 64 bit with a kernel from the kernel ppa repository. BR P. > > Hello List, > > I have run into problems with an external firewire disk. It is a new > "Freecom Hard Drive Quattro USB 3.0 TB", P/N: 056068-71, Model Code > SACCAA. The drive works fine over usb 2.0 and usb 3.0 on another laptop. > I don't have an esata port, so I could not test esata. > > I spoke with Freecom's tech support on the phone, they did send me a > firmware upgrader for windows my email, which I ran. However my drive > already had that current fireware version. Freecom does not offer > support for linux, so I did not get any further help. > > The firewire port on my linux laptop is a 4pin firewire 400 port. The > port on the freecom is a 9pin firewire 800 port. The cables work fine > with another freecom 1TB and another freecom 2TB "Freecom Hard Drive > Quattro 2.0" drives over firewire. I also tested another different 4pin > to 8pin firewire 400 cable and another two 4pin to 9pin firewire 800 > cable. They all work with the other two older drives, but not with the > new drive. > > When I connect the new drive, I can then create some small files, i.e. > in the lower megabyte range, browse directories, write some text files, > etc. The problem/errors start once I start a backup to save my data onto > the external freecom disk. > > Is there something I can do to make this new freecom drive work ? > > fsck -pf of the filesystem returns no errors. > > Filesystem is ext4 inside a truecrypt container which uses all of the > drive's first partition /dev/sdb1 > > The firewire controller inside the laptop is this one: > 03:01.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev > 02) (prog-if 10 [OHCI]) > Subsystem: Dell Device 01f9 > Flags: bus master, medium devsel, latency 64, IRQ 19 > Memory at f1dff000 (32-bit, non-prefetchable) [size=4K] > Memory at f1dfe800 (32-bit, non-prefetchable) [size=2K] > Capabilities: [60] Power Management version 2 > Kernel driver in use: firewire_ohci > Kernel modules: firewire-ohci > > This is the dmesg output when I connect the drive: > [38407.928194] scsi15 : SBP-2 IEEE-1394 > [38407.928365] firewire_core 0000:03:01.4: created device fw1: GUID > 0001db9200188188, S400 > [38407.928378] firewire_core 0000:03:01.4: phy config: new root=ffc0, > gap_count=5 > [38408.146794] firewire_sbp2 fw1.0: logged in to LUN 0000 (0 retries) > [38408.147879] scsi 15:0:0:0: Direct-Access ST3000DM 001-1CH166 > PQ: 0 ANSI: 5 > [38408.152234] sd 15:0:0:0: Attached scsi generic sg2 type 0 > [38408.165642] sd 15:0:0:0: [sdb] 5860533152 512-byte logical blocks: > (3.00 TB/2.72 TiB) > [38408.180978] sd 15:0:0:0: [sdb] Write Protect is off > [38408.180991] sd 15:0:0:0: [sdb] Mode Sense: 10 00 00 00 > [38408.210982] sd 15:0:0:0: [sdb] Write cache: enabled, read cache: > enabled, doesn't support DPO or FUA > [38408.293556] Alternate GPT is invalid, using primary GPT. > [38408.293570] sdb: sdb1 > [38408.357721] sd 15:0:0:0: [sdb] Attached SCSI disk > > This is the dmesg output when I mount the truecrypt partition on the freecom > [38408.357721] sd 15:0:0:0: [sdb] Attached SCSI disk > [38479.499458] bio: create slab <bio-1> at 1 > [38479.897130] EXT4-fs (dm-0): mounted filesystem with ordered data > mode. Opts: (null) > > This is the dmesg output after I start rsync to do the backup. > [38835.735813] firewire_sbp2 fw1.0: status write for unknown ORB > [38854.379707] firewire_sbp2 fw1.0: status write for unknown ORB > [38864.309201] firewire_sbp2 fw1.0: status write for unknown ORB > [38874.273059] firewire_sbp2 fw1.0: status write for unknown ORB > [38883.707197] firewire_sbp2 fw1.0: status write for unknown ORB > [38892.932137] sd 15:0:0:0: [sdb] Unhandled error code > [38892.932149] sd 15:0:0:0: [sdb] > [38892.932152] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK > [38892.932156] sd 15:0:0:0: [sdb] CDB: > [38892.932158] Write(16): 8a 00 00 00 00 00 10 60 89 00 00 00 04 00 00 00 > [38892.932174] end_request: I/O error, dev sdb, sector 274761984 > [38892.932220] EXT4-fs warning (device dm-0): ext4_end_bio:332: I/O > error writing to inode 115343986 (offset 8388608 size 8388608 starting > block 34344960) > [38892.932225] buffer_io_error: 99624 callbacks suppressed > [38892.932227] Buffer I/O error on device dm-0, logical block 34344960 > [38892.932233] Buffer I/O error on device dm-0, logical block 34344961 > [38892.932237] Buffer I/O error on device dm-0, logical block 34344962 > [38892.932240] Buffer I/O error on device dm-0, logical block 34344963 > [38892.932243] Buffer I/O error on device dm-0, logical block 34344964 > [38892.932246] Buffer I/O error on device dm-0, logical block 34344965 > [38892.932249] Buffer I/O error on device dm-0, logical block 34344966 > [38892.932252] Buffer I/O error on device dm-0, logical block 34344967 > [38892.932256] Buffer I/O error on device dm-0, logical block 34344968 > [38892.932259] Buffer I/O error on device dm-0, logical block 34344969 > [38893.116359] firewire_core 0000:03:01.4: phy config: new root=ffc1, > gap_count=5 > [38894.016023] firewire_ohci 0000:03:01.4: failed to read phy reg 5 > [38894.016031] CPU: 0 PID: 22770 Comm: kworker/0:2 Tainted: GF > O 3.11.0-031100-generic #201309021735 > [38894.016033] Hardware name: Dell Inc. Latitude D630 > / , BIOS A18 12/06/2011 > [38894.016058] Workqueue: events bm_work [firewire_core] > [38894.016060] 0000000000000067 ffff88018d695cb8 ffffffff81720fca > 0000000000000000 > [38894.016064] ffff88020f858000 ffff88018d695ce8 ffffffffa0084cbc > ffffffffa0075420 > [38894.016067] 0000000000000005 ffff88020f858000 0000000000000000 > ffff88018d695d18 > [38894.016070] Call Trace: > [38894.016076] [<ffffffff81720fca>] dump_stack+0x46/0x58 > [38894.016083] [<ffffffffa0084cbc>] read_phy_reg+0x8c/0xd0 [firewire_ohci] > [38894.016089] [<ffffffffa0084d2d>] update_phy_reg+0x2d/0x70 > [firewire_ohci] > [38894.016094] [<ffffffffa0084dbd>] ohci_update_phy_reg+0x4d/0x80 > [firewire_ohci] > [38894.016100] [<ffffffffa006b054>] bm_work+0x464/0x500 [firewire_core] > [38894.016106] [<ffffffffa006e700>] ? fw_device_update+0x40/0x40 > [firewire_core] > [38894.016111] [<ffffffff81081060>] process_one_work+0x170/0x4a0 > [38894.016114] [<ffffffff81082121>] worker_thread+0x121/0x390 > [38894.016118] [<ffffffff81082000>] ? manage_workers.isra.20+0x170/0x170 > [38894.016121] [<ffffffff81088fe0>] kthread+0xc0/0xd0 > [38894.016124] [<ffffffff81088f20>] ? flush_kthread_worker+0xb0/0xb0 > [38894.016127] [<ffffffff81735a2c>] ret_from_fork+0x7c/0xb0 > [38894.016130] [<ffffffff81088f20>] ? flush_kthread_worker+0xb0/0xb0 > [38895.116039] firewire_sbp2 fw1.0: ORB reply timed out, rcode 0x00 > [38895.116046] firewire_sbp2 fw1.0: failed to reconnect > [38897.316035] firewire_sbp2 fw1.0: ORB reply timed out, rcode 0x00 > [38902.334389] firewire_sbp2 fw1.0: status write for unknown ORB > [38902.535616] firewire_sbp2 fw1.0: status write for unknown ORB > [38903.359639] firewire_sbp2 fw1.0: status write for unknown ORB > [38903.378997] firewire_sbp2 fw1.0: logged in to LUN 0000 (0 retries) > > Best regards > P. > |