Archived from groups: comp.sys.ibm.pc.hardware.storage (
More info?)
name <dohduhdah@gmail.com> wrote
> Rod Speed wrote
>> name <dohduhdah@gmail.com> wrote
>>> Rod Speed wrote
>>>> name <dohduhdah@gmail.com> wrote
>>>>> Eric Gisin wrote
>>>>>> name <dohduhdah@gmail.com> wrote
>>>>>>> Eric Gisin wrote
>>>>>>>> You should look up error message in eventvwr.
>>>>>>> I'm not familiar with that utility.
>>>>>>> Where do I find this eventviewer?
>>>>>> You can Start | Run - eventvwr or use Computer Management.
>>>>> Ok, here is a screenshot of the info displayed by eventvwr
>>>>> regarding the error generated when attempting to copy a
>>>>> file from the USB drive to another drive:
>>>>>
http://www.ibbu.nl/~nsprakel/screen_shot.jpg
>>>> That is basically saying that the disk itself has a bad
>>>> block on it. That would explain why it only showed up
>>>> once it was pretty full, presumably the bad block(s)
>>>> are towards the end of the physical drive.
>>> But shouldn't such problems normally be detected by
>>> error checking in windows when it includes a surface scan?
>> The surface scan is read only, presumably the problem is with writes.
> The problem specifically occurs when I copy files FROM
> the usb drive TO another drive, never the other way around.
> I don't get error msgs when I put files on the usb drive or when
> I delete those files, only when I copy them to another drive.
Odder and odder.
Maybe the event log entry is misleading, did you
see what the detailled help on that actually says ?
>> Check the SMART stats on the drive, that should show the bad sectors.
> Where do I find those SMART stats?
I use Everest. Not sure if it will show the stats with a USB drive,
havent tried. If it wont get them with the drive internal to a PC.
That would settle the question of whether its really a bad block or not.
http://www.lavalys.com/products/overview.php?pid=1&lang=en
>>>>> I did change the USB cable to a different port (that still results
>>>>> in the same CRC data error), but trying out another cable is more
>>>>> difficult since I only have one and don't like the idea of buying
>>>>> another cable just to try out if the problem is a faulty cable
>>>>> (the cable came with the USB enclosure).
>>>> It doesnt look like a USB problem at all. Try running
>>>> the hard drive manufacturer's diagnostic on the drive.
>>> Yep, but I presume that means booting from
>>> a floppy and having the drive mounted internally
>> That would certainly simplify things. I wouldnt personally
>> boot from a floppy tho, I'd use one of the bootable CDs that
>> has the hard drive manufacturer's diagnostics on the CD.
>>> or would it also be possible to check USB drives
>>> with the bootable diagnostic utility from maxtor?
>> I havent checked what maxtor has done with diags for USB lately.
>> Certainly easiest to try that route initially.
> Hopefully maxtor has a diagnostic utility with usb support
> which can be burned to a bootable CD (though I doubt it
> from my last look at their support webpage).
Best way to use their web site for that is to select the drive and
see what diag tools they offer for the particular drive you have.
> Perhaps I'll see if there is some utility to extensively
> scan and check the usb disk in norton system works first.
I'd try a maxtor diag first.