On Tue, 19 Oct 2004, Andre Steinert wrote: > Hello Alan, > > I don't think that it's a harddisk-fault because > - each run of full md5sum-procedure returns different "faulty" sectors > - the same error occurs on two different drives. The drive with the > error shown below is new. > > Do you need more of these errors in debug-mode, for example errors of > different drives? > > Do you only need x-lines around the error (because these logfiles are > very big)? > > I can't check the drive with this special error under windows because > I'm not able to mount ext3 there. Harddisk-errorchecking-tools don't > work with USB? > > What else can I do to help you and me locating the error? > > Oh, just now md5sum-calculating showed an error with my third > harddisk-drive. I'm sure, it's not a harddisk-hardware-failure: > > Oct 19 17:49:59 titanic kernel: SCSI error : <2 0 0 0> return code = > 0x8000002 > Oct 19 17:49:59 titanic kernel: Current sdc: sense key Hardware Error > Oct 19 17:49:59 titanic kernel: Additional sense: Data phase error > Oct 19 17:49:59 titanic kernel: end_request: I/O error, dev sdc, sector > 103423551 > > The problem: These errors are very important to be solved because > linux-filechecking-tools could think of a real failure and mark these > sectors bad although being error-free. > > Andre.
I believe you that it's not a disk error. It's probably some subtle issue involving the Genesys Logic interface chip and the disk drive. But I don't have any idea what the actual cause is or how to fix it. Unfortunately, your log indicates that everything on the host computer appears to be working correctly. The error message is genuine, and it comes from the device (not the driver). Maybe some other reader will have a good idea on how to solve SK=x04 ASC=x4b (hardware phase error) problems. Or maybe you can get some help from the technical support people at Genesys Logic. Alan Stern > Alan Stern wrote: > > On Mon, 18 Oct 2004, Andre Steinert wrote: > > > > > >>The attached logfile contains only the relevant period. To help you > >>finding the right section where the error occured (the file contains > >>3922341 lines, 290 MB decompressed): > >> > >>[...] > >>Oct 18 21:24:01 titanic kernel: usb-storage: -- transfer complete > >>Oct 18 21:24:01 titanic kernel: usb-storage: Bulk status result = 0 > >>Oct 18 21:24:01 titanic kernel: usb-storage: Bulk Status S 0x53425355 T > >>0x8006d1 > >>4f R 0 Stat 0x0 > >>Oct 18 21:24:01 titanic kernel: usb-storage: -- Result from auto-sense is 0 > >>Oct 18 21:24:01 titanic kernel: usb-storage: -- code: 0x70, key: 0x4, > >>ASC: 0x4b, > >> ASCQ: 0x0 > >>Oct 18 21:24:01 titanic kernel: usb-storage: queuecommand called > >>Oct 18 21:24:01 titanic kernel: usb-storage: Hardware Error: Data phase > >>error > > > > > > Well, like the logfile says, this particular error is a hardware fault of > > some kind. It may be that you need to replace the drive. Does everything > > work okay under a different version of the OS? ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
