On Tue, Sep 4, 2012 at 5:32 PM, Alon Bar-Lev alon.bar...@gmail.com wrote:
Going to try out this one[1][2], but now I go to the store and test it
on site before buying.
Alon
[1] http://a.slickdeals.net/attachment.php?attachmentid=84784d=...
[2]
On Sun, 2 Sep 2012, Alon Bar-Lev wrote:
I modified the patch to the following to make sure my main disk is unaffected:
---
--- drivers/scsi/sd.c 2012-07-21 23:58:29.0 +0300
+++ drivers/scsi/sd.c.new 2012-08-31 19:47:15.822632952 +0300
@@ -1899,13 +1899,17 @@ static int
On Tue, Sep 4, 2012 at 5:25 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Sun, 2 Sep 2012, Alon Bar-Lev wrote:
I modified the patch to the following to make sure my main disk is
unaffected:
---
--- drivers/scsi/sd.c 2012-07-21 23:58:29.0 +0300
+++ drivers/scsi/sd.c.new
On Sun, Sep 2, 2012 at 11:57 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Sun, 2 Sep 2012, Alon Bar-Lev wrote:
This shows the computer asking the drive to read 8 blocks starting at
block 0. The drive (actually the JMicron USB interface, not the drive
itself) returns an error code
On Fri, Aug 31, 2012 at 12:08 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
I was trying to figure out if there can be automatic workaround based
on USB vendor:product... If these exposed at this point then a patch
can be written to effect only
On Sun, 2 Sep 2012, Alon Bar-Lev wrote:
I modified the patch to the following to make sure my main disk is unaffected:
This is what I get now, I guess detection is good now, but something
in the IO is wrong, when plugged to computer's sata it works
correctly.
---
Sep 2 11:42:55
On Sun, Sep 2, 2012 at 4:59 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Sun, 2 Sep 2012, Alon Bar-Lev wrote:
I modified the patch to the following to make sure my main disk is
unaffected:
This is what I get now, I guess detection is good now, but something
in the IO is wrong, when
On Sun, 2 Sep 2012, Alon Bar-Lev wrote:
Attached usbmon, I hope I've done this OK.
The errors start here:
880112a12d80 3034504955 S Bo:2:009:2 -115 31 = 55534243 0a00 0010
8a28 0008 00
880112a12d80 3034505013 C Bo:2:009:2 0 31
On Sun, Sep 2, 2012 at 8:57 PM, Alon Bar-Lev alon.bar...@gmail.com wrote:
On Sun, Sep 2, 2012 at 6:47 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Sun, 2 Sep 2012, Alon Bar-Lev wrote:
Attached usbmon, I hope I've done this OK.
The errors start here:
880112a12d80 3034504955 S
On Sun, 2 Sep 2012, Alon Bar-Lev wrote:
This shows the computer asking the drive to read 8 blocks starting at
block 0. The drive (actually the JMicron USB interface, not the drive
itself) returns an error code indicating that it thinks the command
was not sent properly -- even though it
On Sun, 2 Sep 2012, Matthew Hall wrote:
I can't see any reasonable way of fixing this problem. Even if Linux
did settle for the READ CAPACITY(10) value, it would then think that
the drive was only 2 TB.
blasphemous_hack
What about a quirk which gets the blocksize from the smaller
On Sun, Sep 02, 2012 at 10:43:25PM -0400, Alan Stern wrote:
On Sun, 2 Sep 2012, Matthew Hall wrote:
I can't see any reasonable way of fixing this problem. Even if Linux
did settle for the READ CAPACITY(10) value, it would then think that
the drive was only 2 TB.
Robert Hancock wrote:
On 05/08/2012 06:12 PM, Norman Diamond wrote:
On Wed, 2012/5/9, Alan Stern wrote:
On Tue, 8 May 2012, Norman Diamond wrote:
Alan Stern wrote:
On Tue, 8 May 2012, Norman Diamond wrote:
Sometimes I guess a USB-to-[S]ATA bridge might obey ATA passthru of
an ATA Identify
Hello,
Is there anything new in this regard?
I have the same issue with 3T drive.
Thanks!
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
Hello,
Is there anything new in this regard?
I have the same issue with 3T drive.
What are you referring to? What issue?
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to
On Thu, Aug 30, 2012 at 5:29 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
Hello,
Is there anything new in this regard?
I have the same issue with 3T drive.
What are you referring to? What issue?
Alan Stern
Thanks for replying!
This[1]
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
On Thu, Aug 30, 2012 at 5:29 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
Hello,
Is there anything new in this regard?
I have the same issue with 3T drive.
What are you referring to? What
On Thu, Aug 30, 2012 at 9:49 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
On Thu, Aug 30, 2012 at 5:29 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
Hello,
Is there anything new in this
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
On Thu, Aug 30, 2012 at 9:49 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
On Thu, Aug 30, 2012 at 5:29 PM, Alan Stern st...@rowland.harvard.edu
wrote:
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
Thank you!
I will test this and report back.
As this is in scsi layer, I guess it does not get the USB
vendor:product to automatically apply this workaround... :(
I don't entirely understand this comment. But it is true that the
patch will affect
On Thu, Aug 30, 2012 at 11:47 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
Thank you!
I will test this and report back.
As this is in scsi layer, I guess it does not get the USB
vendor:product to automatically apply this workaround... :(
I
On Thu, 30 Aug 2012, Alon Bar-Lev wrote:
I was trying to figure out if there can be automatic workaround based
on USB vendor:product... If these exposed at this point then a patch
can be written to effect only this device.
I never traced the scsi module, but scsi_device does contain vendor,
On 05/08/2012 06:12 PM, Norman Diamond wrote:
On Wed, 2012/5/9, Alan Stern wrote:
On Tue, 8 May 2012, Norman Diamond wrote:
Alan Stern wrote:
On Tue, 8 May 2012, Norman Diamond wrote:
In my case there is no other way that a host (PC or other, any OS or
driver) could obtain a reported
23 matches
Mail list logo
