Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #1405 > unrolled thread
| Started by | Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> |
|---|---|
| First post | 2011-06-13 13:53 +0200 |
| Last post | 2011-07-10 22:22 +0000 |
| Articles | 4 — 2 participants |
Back to article view | Back to comp.os.linux.misc
Difficulties starting up eSATA JBOD Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> - 2011-06-13 13:53 +0200
Re: Difficulties starting up eSATA JBOD Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> - 2011-06-19 22:52 +0200
Re: Difficulties starting up eSATA JBOD Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> - 2011-06-26 16:29 +0200
Re: Difficulties starting up eSATA JBOD Arno <me@privacy.net> - 2011-07-10 22:22 +0000
| From | Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> |
|---|---|
| Date | 2011-06-13 13:53 +0200 |
| Subject | Difficulties starting up eSATA JBOD |
| Message-ID | <4p1it9.crv.19.1@news.alt.net> |
The Fantec QB-35US3 has an USB 3.0 and an eSATA port.
Mechanically, this product is great. Almost screw-less mounting
of drives, and the fan is surprisingly quiet for an external
drive bay (it is not silent though, and I might try to exchange
it for another fan later).
USB 3.0 does *not* work, at least not when connected to my
Sharkoon controller. Drives are found, but as soon as there is
traffic on the bus, connections break down. I'll try another
controller later and report back here.
Now for eSATA. It works, but it has problems starting up.
Attached below is a log. All that happens within a couple of
seconds. After the drives finally have been found, apparently
everything works. (I had *one* break down with I/O errors
yesterday, but could not reproduce it.)
So what do you make out of this log? Should I expect more trouble
down the road? Kernel is 2.6.39.1, Glibc 2.13, GCC 4.5.3.
kern.err: ata6: exception Emask 0x10 SAct 0x0 SErr 0x40d0000 action 0xe frozen
kern.err: ata6: irq_stat 0x00400040, connection status changed
kern.err: ata6: SError: { PHYRdyChg CommWake 10B8B DevExch }
kern.info: ata6: hard resetting link
kern.info: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kern.info: ata6.15: Port Multiplier 1.2, 0x197b:0x0325 r0, 15 ports, feat 0x5/0xf
kern.info: ata6.00: hard resetting link
kern.info: ata6.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
kern.info: ata6.01: hard resetting link
kern.info: ata6.01: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
kern.info: ata6.02: hard resetting link
kern.info: ata6.02: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
kern.info: ata6.03: hard resetting link
kern.info: ata6.03: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
kern.info: ata6.04: hard resetting link
kern.err: ata6.04: failed to resume link (SControl 0)
kern.info: ata6.04: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.05: hard resetting link
kern.err: ata6.05: failed to resume link (SControl 0)
kern.info: ata6.05: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.06: hard resetting link
kern.err: ata6.06: failed to resume link (SControl 0)
kern.info: ata6.06: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.07: hard resetting link
kern.err: ata6.07: failed to resume link (SControl 0)
kern.info: ata6.07: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.08: hard resetting link
kern.err: ata6.08: failed to resume link (SControl 0)
kern.info: ata6.08: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.09: hard resetting link
kern.err: ata6.09: failed to resume link (SControl 0)
kern.info: ata6.09: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.10: hard resetting link
kern.err: ata6.10: failed to resume link (SControl 0)
kern.info: ata6.10: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.11: hard resetting link
kern.err: ata6.11: failed to resume link (SControl 0)
kern.info: ata6.11: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.12: hard resetting link
kern.err: ata6.12: failed to resume link (SControl 0)
kern.info: ata6.12: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.13: hard resetting link
kern.err: ata6.13: failed to resume link (SControl 0)
kern.info: ata6.13: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.14: hard resetting link
kern.err: ata6.14: failed to resume link (SControl 0)
kern.info: ata6.14: SATA link down (SStatus 0 SControl 0)
kern.info: ata6.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
kern.info: ata6.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
kern.info: ata6.00: configured for UDMA/133
kern.info: ata6.01: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
kern.info: ata6.01: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
kern.info: ata6.01: configured for UDMA/133
kern.info: ata6.02: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
kern.info: ata6.02: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
kern.info: ata6.02: configured for UDMA/133
kern.info: ata6.03: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
kern.info: ata6.03: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
kern.info: ata6.03: configured for UDMA/133
kern.info: ata6: EH complete
kern.notice: scsi 5:0:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5
kern.notice: sd 5:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
kern.notice: sd 5:0:0:0: Attached scsi generic sg5 type 0
kern.notice: sd 5:0:0:0: [sde] Write Protect is off
kern.debug: sd 5:0:0:0: [sde] Mode Sense: 00 3a 00 00
kern.notice: sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
kern.notice: scsi 5:1:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5
kern.notice: sd 5:1:0:0: Attached scsi generic sg6 type 0
kern.notice: scsi 5:2:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5
kern.notice: sd 5:2:0:0: Attached scsi generic sg7 type 0
kern.notice: scsi 5:3:0:0: Direct-Access ATA WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5
kern.notice: sd 5:3:0:0: Attached scsi generic sg8 type 0
kern.notice: sd 5:1:0:0: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
kern.notice: sd 5:1:0:0: [sdf] Write Protect is off
kern.debug: sd 5:1:0:0: [sdf] Mode Sense: 00 3a 00 00
kern.notice: sd 5:1:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
kern.info: sde: unknown partition table
kern.notice: sd 5:2:0:0: [sdg] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
kern.notice: sd 5:2:0:0: [sdg] Write Protect is off
kern.debug: sd 5:2:0:0: [sdg] Mode Sense: 00 3a 00 00
kern.notice: sd 5:2:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
kern.notice: sd 5:3:0:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
kern.info: sdf: unknown partition table
kern.notice: sd 5:3:0:0: [sdh] Write Protect is off
kern.debug: sd 5:3:0:0: [sdh] Mode Sense: 00 3a 00 00
kern.notice: sd 5:0:0:0: [sde] Attached SCSI disk
kern.notice: sd 5:1:0:0: [sdf] Attached SCSI disk
kern.info: sdg: unknown partition table
kern.notice: sd 5:3:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
kern.notice: sd 5:2:0:0: [sdg] Attached SCSI disk
kern.info: sdh: unknown partition table
kern.notice: sd 5:3:0:0: [sdh] Attached SCSI disk
[toc] | [next] | [standalone]
| From | Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> |
|---|---|
| Date | 2011-06-19 22:52 +0200 |
| Message-ID | <4picnb.tlf.17.1@news.alt.net> |
| In reply to | #1405 |
Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> wrote: > The Fantec QB-35US3 has an USB 3.0 and an eSATA port. [...] > Now for eSATA. It works, but it has problems starting up. > Attached below is a log. All that happens within a couple of > seconds. After the drives finally have been found, apparently > everything works. (I had *one* break down with I/O errors > yesterday, but could not reproduce it.) After a week of testing, there were no more break downs. The drive bay works over eSATA, despite the warnings and errors during detection. Performance is not quite what I had expected, but this may be down to so many things. Drives are WD20EARS running in RAID-5 with LVM and encryption. Write speed is about 22 MiB/sec.
[toc] | [prev] | [next] | [standalone]
| From | Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> |
|---|---|
| Date | 2011-06-26 16:29 +0200 |
| Message-ID | <4q44sr.e5u.17.1@news.alt.net> |
| In reply to | #1405 |
Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> wrote: > The Fantec QB-35US3 has an USB 3.0 and an eSATA port. > USB 3.0 does *not* work, at least not when connected to my > Sharkoon controller. Drives are found, but as soon as there is > traffic on the bus, connections break down. I'll try another > controller later and report back here. USB 3.0 works with a "LogiLink PCI-Express Card, 2x USB 3.0". It also works with a "LogiLink Express Card, 34mm, 2x USB 3.0" in my notebook. This is great. It's giving me a xhci_hcd 0000:02:00.0: WARN: Stalled endpoint from time to time, but that doesn't seem to matter. Kernel is 2.6.37.6; I have not yet tested with newer ones. eSATA continued to work with the warnings I posted earlier. So in total, I can give a recommendation for the Fantec QB-35US3 under Linux. If USB 3.0 doesn't work for you, try another controller.
[toc] | [prev] | [next] | [standalone]
| From | Arno <me@privacy.net> |
|---|---|
| Date | 2011-07-10 22:22 +0000 |
| Message-ID | <97un0uF21rU2@mid.individual.net> |
| In reply to | #1469 |
Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> wrote: > Lasse Kliemann <lasse-usenet-2011@mail.plastictree.net> wrote: >> The Fantec QB-35US3 has an USB 3.0 and an eSATA port. > >> USB 3.0 does *not* work, at least not when connected to my >> Sharkoon controller. Drives are found, but as soon as there is >> traffic on the bus, connections break down. I'll try another >> controller later and report back here. > USB 3.0 works with a "LogiLink PCI-Express Card, 2x USB 3.0". > It also works with a "LogiLink Express Card, 34mm, 2x USB 3.0" in > my notebook. This is great. > It's giving me a > xhci_hcd 0000:02:00.0: WARN: Stalled endpoint > from time to time, but that doesn't seem to matter. > Kernel is 2.6.37.6; I have not yet tested with newer ones. > eSATA continued to work with the warnings I posted earlier. > So in total, I can give a recommendation for the Fantec QB-35US3 > under Linux. > If USB 3.0 doesn't work for you, try another controller. I have USB3.0 working on a Sharkoon controller with 2.6.38.8. What does not work yet is an USB 3.0 hub. Despite grand claims of "Linux USB 3.0 support" by some kernel dev's a whole ago, the truth is that it slowly becomes usable at this time, but is by no means complete yet. My guesstimate would be that it will take another 3-6 months for hub support and for the kinks in controller support to be ironed out. Not that I mind too much, I think this timeframe is reasonable. I do mind the overstated self-promotion though. Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
[toc] | [prev] | [standalone]
Back to top | Article view | comp.os.linux.misc
csiph-web