![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
![Zarathustra[H]](https://cdn.hardforum.com/data/avatars/m/9/9298.jpg?1707758471){kind=avatar}
Zarathustra[H]
Extremely [H]
- Joined
- Oct 29, 2000
- Messages
- 38,862
Hey all,
This is really frustrating. I recently bought one of those cute little Dell Zino HD boxes to use as a Linux NAS server. I was going to build my own box, but my fiance is very eco conscious, so the 22W TDP of the little unit seemed like a good idea for a computer thats going to be running 24/7. (That and the fact that it's diminuative size takes up less of our almost non-existant closet space was also a bonus). Either way, the problem is I can't just get a cheap eSATA board to replace the on board ports, as there are no PCIe ports...
So anyway, this little computer has two eSATA ports. They appear to work OK in Windows (it came with Vista) but for some reason they simply do not work with my "Drobo S" under linux. (the Drobo works fine on my Desktop Linux box, an Intel X58 express based box.)
So my NAS box is currently hosting storage over USB, giving me about a third of the transfer speeds I would have had with eSATA... It's really frustrating, as I replaced all my wires with Cat6 and upgraded my switches to gigabit to prepare for this install only to be limited by USB transfer speeds...
Here are what I think are the appropriate parts from dmesg
So it looks like the drobo is properly detected, but then it tries 3 times to connect to it, and when it fails it gives up.
It says to manually issue scan to resume this link. Does anyone know how to do this?
Any other suggestions?
Hopefully you [H] guys will be more knowledgable than the Ubuntu forums, as they just seem to be a bunch of noobs these days. It's remarkable how fast such a good support forum can become useless.
This is really frustrating. I recently bought one of those cute little Dell Zino HD boxes to use as a Linux NAS server. I was going to build my own box, but my fiance is very eco conscious, so the 22W TDP of the little unit seemed like a good idea for a computer thats going to be running 24/7. (That and the fact that it's diminuative size takes up less of our almost non-existant closet space was also a bonus). Either way, the problem is I can't just get a cheap eSATA board to replace the on board ports, as there are no PCIe ports...
So anyway, this little computer has two eSATA ports. They appear to work OK in Windows (it came with Vista) but for some reason they simply do not work with my "Drobo S" under linux. (the Drobo works fine on my Desktop Linux box, an Intel X58 express based box.)
So my NAS box is currently hosting storage over USB, giving me about a third of the transfer speeds I would have had with eSATA... It's really frustrating, as I replaced all my wires with Cat6 and upgraded my switches to gigabit to prepare for this install only to be limited by USB transfer speeds...
Here are what I think are the appropriate parts from dmesg
Code:
dmesg| grep ata3
[ 0.956381] ata3: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 22
[ 1.880037] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.880430] ata3.15: Port Multiplier 1.1, 0x1a62:0x0003 r23, 14 ports, feat 0x0/0x0
[ 1.880434] ata3.15: Asynchronous notification not supported, hotplug won't
[ 1.881194] ata3.00: hard resetting link
[ 2.410350] ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 2.410399] ata3.01: hard resetting link
[ 2.760497] ata3.01: SATA link down (SStatus 0 SControl 320)
[ 2.760581] ata3.02: hard resetting link
[ 3.110580] ata3.02: SATA link down (SStatus 0 SControl 320)
[ 3.110677] ata3.03: hard resetting link
[ 3.460581] ata3.03: SATA link down (SStatus 0 SControl 320)
[ 3.460677] ata3.04: hard resetting link
[ 3.810588] ata3.04: SATA link down (SStatus 0 SControl 320)
[ 3.810685] ata3.05: hard resetting link
[ 4.160584] ata3.05: SATA link down (SStatus 0 SControl 320)
[ 4.160681] ata3.06: hard resetting link
[ 4.510543] ata3.06: SATA link down (SStatus 0 SControl 320)
[ 4.510631] ata3.07: hard resetting link
[ 4.860586] ata3.07: SATA link down (SStatus 0 SControl 320)
[ 4.860684] ata3.08: hard resetting link
[ 5.210580] ata3.08: SATA link down (SStatus 0 SControl 320)
[ 5.210676] ata3.09: hard resetting link
[ 5.560584] ata3.09: SATA link down (SStatus 0 SControl 320)
[ 5.560681] ata3.10: hard resetting link
[ 5.910579] ata3.10: SATA link down (SStatus 0 SControl 320)
[ 5.910675] ata3.11: hard resetting link
[ 6.260585] ata3.11: SATA link down (SStatus 0 SControl 320)
[ 6.260682] ata3.12: hard resetting link
[ 6.610599] ata3.12: SATA link down (SStatus 0 SControl 320)
[ 6.610689] ata3.13: hard resetting link
[ 6.960590] ata3.13: SATA link down (SStatus 0 SControl 320)
[ 6.960972] ata3.00: ATA-6: Drobo 3rd Gen DRDR3-A, v1.0.0, max UDMA/133
[ 6.960976] ata3.00: 17179869184 sectors, multi 0: LBA48
[ 6.961352] ata3.00: configured for UDMA/133
[ 6.961407] ata3: PMP SError.N set for some ports, repeating recovery
[ 6.961465] ata3.00: hard resetting link
[ 7.890351] ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 7.891063] ata3.00: configured for UDMA/133
[ 7.891114] ata3: PMP SError.N set for some ports, repeating recovery
[ 7.891167] ata3.00: hard resetting link
[ 8.820354] ata3.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 8.821063] ata3.00: configured for UDMA/133
[ 8.821121] ata3.00: failed to recover link after 3 tries, disabling
[ 8.821124] ata3.00: disabled
[ 8.821128] ata3.00: PHY status changed but maxed out on retries, giving up
[ 8.821131] ata3.00: Manully issue scan to resume this link
[ 8.821137] ata3: EH completeSo it looks like the drobo is properly detected, but then it tries 3 times to connect to it, and when it fails it gives up.
It says to manually issue scan to resume this link. Does anyone know how to do this?
Any other suggestions?
Hopefully you [H] guys will be more knowledgable than the Ubuntu forums, as they just seem to be a bunch of noobs these days. It's remarkable how fast such a good support forum can become useless.
