I am one of the victims of the bug described above.
In fact, my neigbour is the victim: Ubuntu destroyed her Windows partition.
I was trying to help her.
That is more than a reason to turn people away from Linux.
But what is written here above is another reason.
It is perfectly incomprehensible.
Like in comment #31 I have the same issues with Raring Ringtail Final
release Kernel 3.9.0-19-generic.
The same device works fine in Ubuntu 12.04.2 with Kernel
3.5.0-28-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Correction to comment #34:
The correct Raring-Kernel is 3.8.0-19-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
Writing on a certain USB HDD causes corruption
To manage
Hi
Working fine on raring with 3.8.0-19 kernel
idVendor 0x14cd Super Top
idProduct 0x6116 M6116 SATA Bridge
bcdDevice 2.20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
Hi,
After the latest official kernel patch(3.2.0.40) for my xubuntu 12.04 ,
my external HDD now works. Lsusb -v reports, that the bcdDevice = 2.20
for my HDD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
Writing on a certain USB HDD causes corruption
To manage
lsusb -vd 14cd:6116
...
idVendor 0x14cd Super Top
idProduct 0x6116 M6116 SATA Bridge
bcdDevice 1.60
...
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1161985
Working fine in 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Device 14cd:6116 with bcdDevice 1.60 doesn't work in Preceise.
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1161985
Working fine in 12.04 with stock kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can test on both systems, but I don't want to corrupt the data! I have
no spare disk at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
Writing on a certain USB HDD causes
Sorry, mistyped again. Fixed version:
Device 14cd:6116 with bcdDeice 1.60 doesn't work in Raring.
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1161985
Working fine in 12.04 (Preceise) with stock kernel.
I can test it on both systems, but I don't want to corrupt the data! I
have no
Sorry,
I no longer have that specific HDD enclosure.
Tal
--- On Sat, 4/13/13, Julian Wiedmann 1082...@bugs.launchpad.net wrote:
From: Julian Wiedmann 1082...@bugs.launchpad.net
Subject: [Bug 1082215] Re: Writing on a certain USB HDD causes corruption
To: taln...@yahoo.com
Date: Saturday
Can anyone else test?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
Writing on a certain USB HDD causes corruption
To manage notifications about this bug go to:
Tal Nevo,
could you please test the latest kernel from -updates (3.2.0-40.64) and see if
it fixes this bug?. Thank you.
** Changed in: linux (Ubuntu)
Status: Fix Committed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The abovementioned fix is now available in the upstream 3.2.40 kernel. A
PPA of this kernel is available at http://kernel.ubuntu.com/~kernel-
ppa/mainline/ and instructions on how to install and uninstall it are
available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds#Installing_Mainline_Kernels
This is fixed upstream in kernel 3.8.1 by the following patch:
commit c8f96b36a83763b2cdedaec489eb39d3394a2366
Author: Josh Boyer
Date: Thu Feb 14 09:39:09 2013 -0500
USB: usb-storage: unusual_devs update for Super TOP SATA bridge
commit 18e03310b5caa6d11c1a8c61b982c37047693fba
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
Writing on a certain USB HDD causes corruption
To manage
@Tal Nevo have you opened an upstream bug? I am curios what is the
status of this bug as I am affected as well. I don't know if I should
wait for a bug fix or I should look for another HDD enclosure. I can buy
another usb drive, that's not an issue, but I don't know what vendor to
choose (the
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
Writing on a certain USB HDD causes corruption
To manage notifications
Hi,
I'm suffering from the same problem.
Is there a dummys quide somewhere, that would describe compiling a driver
module? I managed to compile the usb-storage.ko file again, but it ended
about 10% different in size compared to the original, and not surprising, it
does not work. I would
@Janne
The v3.8-rc3 kernel is not available. Can you test that kernel to see
if it also exhibits this bug?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc3-raring/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello again,
I installed the 3.8-rc3 kernel, but all usb devices connected (apart
from touchpad and fingerprint reader) refused to work, so no way to test
if this hdd adapter would work.
Maybe someone else with the offending adapter can try this out and
report here?
--
You received this bug
Ok I installed the 3.8-rc3 kernel, and after installing also the extras-package
I got the usb devices to work.
But the same problem persists, trying to partition the hdd just fails.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the
issue, and may provide a quicker resolution to the bug.
Please follow the instructions on
Same here, same numbers, almost same output for the dd test. (Just
slightly different, not writing 0's only anyway).
I'm not sure this would be of any help but the problem appears on
raspbian as well.
I'm keen to test that new kernel but I don't have any free machines. I
could probably try to
Do you happen to know if there was a prior Ubuntu release that did not
exhibit this bug?
Also, the v3.8-rc2 mainline kernel is now available. Can you test that kernel
as well? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc2-raring/
Thanks in advance!
--
You
Same problem here
my device is same as yours
idVendor 0x14cd Super Top
idProduct 0x6116 M6116 SATA Bridge
bcdDevice 2.20
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
Writing
maybe helpful
quota from https://bbs.archlinux.org/viewtopic.php?pid=1204327
Hello,
If you are still interested, I may have found the cause of the HDD enclosure
corrupting your drive.
http://code.metager.de/source/history/linux/stable/drivers/usb/storage/unusual_cypress.h
the patch submitted
Hi,
I got the same numbers as mentioned above:
idVendor 0x14cd Super Top
idProduct 0x6116 M6116 SATA Bridge
bcdDevice 2.20
Must be the same problem...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The following tar file (usb-debug.tgz) contains debugging obtained using
the instructions in the link provided above.
I used two USB enclosures with the SATA hard drive, one that works and the
one that exhibits the bug.
Testing was done with the last kernel installed (3.7.0-030700rc7).
I zeroed
If possible, can you take a look at the following wiki page:
https://wiki.ubuntu.com/Kernel/Debugging/USB
It would be helpful if you could gather some USB tracing data.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lsusb-v.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082215/+attachment/3447451/+files/lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
** Attachment added: sys-kernel-debug-usb-devices.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082215/+attachment/3447452/+files/sys-kernel-debug-usb-devices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: bus2data.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082215/+attachment/3447453/+files/bus2data.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1082215
Title:
Writing on a certain USB HDD causes corruption
To manage notifications about this bug go to:
The laptop on which I reported the bug is not one I can modify. Therefore I
used a different one that is running Ubuntu 10.04 32-bit.
First I verified that the problem I reported above can be recreated on this
other system. I quickly managed to confirm that it can.
I then installed the kernel
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.7 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
Have you tried partitioning the driver and using dd to write to the
partition? For example:
dd if=/dev/zero of=/dev/sdb1 bs=1M count=100
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Importance: High = Medium
**
As far as my tests went, it does not matter where in the drive I write to with
dd - it gets corrupted.
The example I gave was in order to simplify the description of what I was
seeing.
Originally, The drive had a formatted partition and when I moved it to this
USB/SATA enclosure I began
38 matches
Mail list logo
