Need help on my maxtor harddrives

[arthurleung]

I bought 2 new 6L300S0 300G SATA drives, but I got tons of problem with them

The first disk came with 2.3% bad sectors which render the drive unusable.
The second disk appear to have no bad sectors, but my partition keep getting corrupted (I could copy the file out by R-studio NTFS with no error at all), but my folders just corrupting.

I'm wondering what happened to my disks?

I'm copying the remaining 100GB data out of the drive now, going to replace the SATA cable and see will it help.

CHKDSK is verifying files (stage 1 of 3)...
Truncating corrupt attribute list for file 464.
Deleted corrupt attribute list for file 464.
Truncating corrupt attribute list for file 494.
Deleted corrupt attribute list for file 494.
Truncating corrupt attribute list for file 607.
Deleted corrupt attribute list for file 607.
Truncating corrupt attribute list for file 803.
Deleted corrupt attribute list for file 803.
Deleting corrupt attribute record (128, "")
from file record segment 1036.
File verification completed.
Deleting orphan file record segment 465.
Deleting orphan file record segment 466.
Deleting orphan file record segment 467.
Deleting orphan file record segment 492.
Deleting orphan file record segment 493.
Deleting orphan file record segment 495.
Deleting orphan file record segment 496.
Deleting orphan file record segment 497.
Deleting orphan file record segment 498.
Deleting orphan file record segment 499.
Deleting orphan file record segment 500.
Deleting orphan file record segment 501.
Deleting orphan file record segment 502.
Deleting orphan file record segment 503.
Deleting orphan file record segment 504.
Deleting orphan file record segment 505.
Deleting orphan file record segment 506.
Deleting orphan file record segment 507.
Deleting orphan file record segment 508.
Deleting orphan file record segment 509.
Deleting orphan file record segment 510.
Deleting orphan file record segment 511.
Deleting orphan file record segment 512.
Deleting orphan file record segment 513.
Deleting orphan file record segment 514.
Deleting orphan file record segment 515.
Deleting orphan file record segment 516.
Deleting orphan file record segment 517.
Deleting orphan file record segment 518.
Deleting orphan file record segment 519.
Deleting orphan file record segment 520.
Deleting orphan file record segment 521.
Deleting orphan file record segment 522.
Deleting orphan file record segment 608.
Deleting orphan file record segment 609.
Deleting orphan file record segment 610.
Deleting orphan file record segment 611.
Deleting orphan file record segment 612.
Deleting orphan file record segment 613.
Deleting orphan file record segment 614.
Deleting orphan file record segment 615.
Deleting orphan file record segment 616.
Deleting orphan file record segment 617.
Deleting orphan file record segment 618.
Deleting orphan file record segment 619.
Deleting orphan file record segment 620.
Deleting orphan file record segment 621.
Deleting orphan file record segment 622.
Deleting orphan file record segment 623.
Deleting orphan file record segment 624.
Deleting orphan file record segment 625.
Deleting orphan file record segment 804.
Deleting orphan file record segment 805.
Deleting orphan file record segment 806.
Deleting orphan file record segment 807.
Deleting orphan file record segment 808.
Deleting orphan file record segment 809.
Deleting orphan file record segment 810.
Deleting orphan file record segment 811.
Deleting orphan file record segment 812.
Deleting orphan file record segment 813.
Deleting orphan file record segment 814.
Deleting orphan file record segment 815.
Deleting orphan file record segment 816.
Deleting orphan file record segment 817.
Deleting orphan file record segment 818.
Deleting orphan file record segment 819.
Deleting orphan file record segment 820.
Deleting orphan file record segment 821.
Deleting orphan file record segment 822.
Deleting orphan file record segment 823.
Deleting orphan file record segment 824.
Deleting orphan file record segment 825.
Deleting orphan file record segment 826.
Deleting orphan file record segment 827.
Deleting orphan file record segment 828.
Deleting orphan file record segment 829.
Deleting orphan file record segment 830.
Deleting orphan file record segment 831.
Deleting orphan file record segment 832.
Deleting orphan file record segment 833.

Errors found. CHKDSK cannot continue in read-only mode.

The drive is new so may be it is kind of DoA
I already RMA-ed the first disk, may be I'll need to RMA this one as well....

[eldren]

I'm guessing it's not the drives, since you're getting the same issue (Data corruption) on both drives. When I've had data corruption issues similar to that (MBR corruption in my case) in the past, it was actually the controller that was to blame. Have you tried them in a different machine with different cables, etc.? That'd be the easiest way to test if it's the drive or the hardware it's connected to. Good luck.

[satkiss]

I recovered my slave drive and 90% of the files,
1. I got a drive caddy so i could access it via usb after windows had started. This stopped C.D. Trying to scan it and allowed me to view the files. 2. Though i could see the files i couldn't access them (C.D. Screwed that up) however i downloade a free file recovery program (pci_filerecovery.exe) and bit by bit managed to recover all the files that weren't on damaged secters of the disk.
...

[xAmritx]

:O are u using windows built in scandisk? U know that causes more hdd problems than solves!!!!

Reformat with maxtors own utility from their website and get another software that does the drive check(think a tool like that in maxtors utility)

[Supershanks]

Maxtor have a bad recent history especially with nvidia boards & series 10 drives:-
Maxtor Diamond Max 10 - Possible solutions
& solution for disappearing Maxtor drives?
I used to happily use maxtor series 9 drives but won'y touch the new drives, seeing the issues that occur.

[timtim86]

Has anyone realised yet that the original post is from 2005?

[Supershanks]

Has anyone realised yet that the original post is from 2005?

Hehe thought i'd not seen to many maxtor issues for a while.

welcome to the forum satkiss

[amjedm]

Has anyone realised yet that the original post is from 2005?

Thank you - I over looked it

[moogle]

Has anyone realised yet that the original post is from 2005?

nope, we all assume that the old threads dont get bumped alot
alot of that been happening lately.

[xAmritx]

DOH!

[satkiss]

Ooops