On Tue, Aug 24, 2004 at 11:48:28AM -0400, Alan Stern wrote: > On Mon, 23 Aug 2004, J. Bruce Fields wrote: > > > > Can you post the debugging log for max_sectors = 16? If the behavior is > > > the same as before, then it's pretty clear that the device is defective. > > > > Here you are: > > > > http://fieldses.org/~bfields/usb_storage_log_ms16.txt.gz > > I took a look, and it appears to be the same failure mechanism as before. > Either the USB hardware on your computer doesn't work right (highly > unlikely) or your drive is defective.
I got the chance to fool around with it some more this weekend. I tried connecting it to my laptop instead. I ran e2fsck, a big "find", and a backup, and they all worked fine, despite the fact that all 3 of these produce the problem very quickly on the desktop. Besides hardware, the only other difference was a slightly newer kernel on the laptop (2.6.9-rc1 vs. 2.6.8.1). Would it be worth retrying with the same kernel on both? And is my further mucking around with this of any use to you, or are you to thoroughly convinced that it's a hardware bug at this point? --Bruce Fields ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
