lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061207221015.GA342@DervishD>
Date:	Thu, 7 Dec 2006 23:10:15 +0100
From:	DervishD <lkml@...vishd.net>
To:	Matthias Schniedermeyer <ms@...d.de>
Cc:	linux-kernel@...r.kernel.org, usb-storage@...ts.one-eyed-alien.net
Subject: Re: single bit errors on files stored on USB-HDDs via USB2/usb_storage

    Hi Matthias :)

 * Matthias Schniedermeyer <ms@...d.de> dixit:
> My averate file size is about 1GB with files from about 400MB to
> 5000MB I estimate the average error-rate at about one damaged file in
> about 10GB of data.
> 
> I'm not sure and haven't checked if the files are wrongly written or
> "only" wrongly read back as i delete the defective files and copy them
> again.
> 
> Today i copied a few files back and checked them against the stored MD5
> sums and 5 files of 86 (each about 700 MB) had errors. So i copied the 5
> files again. 4 of the files were OK after that and coping the last file
> the third time also resulted in the correct MD5.

    I had more or less the same issue a week or two ago. I performed
lots of tests and only by replacing the USB2.0 PCI card, the USB cable
and the power supply of the usb-hdd adapter got the problem solved.

    I'm not sure if the problem is really gone, but the system works now
reliably. I don't know if sooner or later I'll get the issue again,
because I didn't really identify a culprit: looks like the
card+adapter+cable combination was just "ugly", and errors from the
adapter were not reported correctly.

> NEVER did i see any messages in syslog regarding erros or an aborting
> program due to errors passed down from the kernel or something like
> that.

    The same here! Looks like USB-HDD adapters don't report any errors
to the kernel :?????

    The best advice I can give you, from my limited experience with the
problem, is: replace the cable. This minimizes the chance of corrupted
data getting into the adapter. If that doesn't solve the problem, try
removing any unconnected cable that is plugged into the USB card.
Believe it or not, a long but unconnected cable (put there just to be
able to plug my USB card-reader without having to look for the cable in
a drawer) was causing errors *even in a Kingston USB key that worked
flawlessly otherwise*!!!

    If you have any other question, feel free to drop me a note. I'm
sorry I cannot give a much more technical or scientific answer, but
unfortunately I have none :((

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ