Desktops: Need Help, Data Corruption issue
Need Help, Data Corruption issue
by Tokimemofan - 1/24/09 5:28 PMTo start with I have already cleaned up the 3GB worth of damage caused by this.
I have 2 computers that I share files between.
Computer 1: Compaq Presario SR1950NX, Default Hardware/OS
Computer 2: HP Pavillion 9795c, Network/Modem removed, Graphics upgraded, Sil3512 based SATA card, 2 permanent HDDs, Quantum Bigfoot 3.2GB (NTLDR, NT4, MSDOS 7.10, Pagefile), Quantum Fireball 20GB (Windows 2000) 2 Semi-Permanent HDD, Western Digital 80GB, Western Digital 500GB SATA, DVD-RW Dual Layer drive.
I use 18 HDDs, so far I've found several things.
All 3 SCSI Drives have been corruption free.
All 4 of 5 SATA Drives have been corruption free, 1 Western Digital 320GB SATA had several corrupt files, It is probable that these became corrupt durring transfer from another drive.
All 6 of 7 PATA Drives 40GB or smaller and have been corruption free, 1 20GB drive was cleared off before I caught this issue.
A 80GB PATA Western Digital Drive has been corruption free
The corruption seems to originate from following 2 drives:
A 160GB PATA Western Digital in a Ximeta Netdisk had 2GB worth of Crosslinked files and 100MB of Minor damage.
A 60GB PATA Drive had minor damage.
These 2 Drives are used through USB on Computer 1 and PATA or USB Computer 2 (USB 1.1=Slow). These drives are still going strong with no signs of failure. When connected through PATA these drives work fine, USB however often corrupts the data. I moved a .zip file on the 60GB PATA and it became corrupt, specifically a single file in the .zip could not be extracted due to corruption. I verified this by using a data recovery tool on the 60GB to undelete the file, the recovered .zip extracted properly. I use these drives to move data from Computer 1 to Computer 2 and corruption is happening on both sets of hardware. So it seems the problems are USB related. Any ideas where to start troubleshooting?
The moment I hit the word Ximeta
by R. Proffitt
- 1/24/09 7:00 PM
In reply to: Need Help, Data Corruption issue by Tokimemofan
I knew it was trouble. Is there any chance you can eject Ximeta from your systems?
More Information
by Tokimemofan - 1/26/09 8:02 AM In reply to: The moment I hit the word Ximeta by R. Proffitt
It's currently disconnected and disassembled. It contains a Western Digital PATA 160GB drive.
I forgot to mention the USB<->ATA Cable I used on the 60GB. You can find everything about the cable here:
http://www.powmax.com/pics/accessory/en2535a.htm
Except my power cable sucks more so I use a different one.
Unfortunately it seems I have 1 problem with at least 2 different causes.
And that was not an answer my question.
by R. Proffitt - 1/26/09 8:10 AM
In reply to: More Information by Tokimemofan
Let me share that my encounters with Ximeta left nothing good to be said. Maybe it was the hardware they used, maybe a software issue. Just like you added there could be two sources.
At least I was able to eject the software. Since the hardware didn't function without Ximeta we also gifted that hardware out. Good riddance to bad rubbish.
Bob
About the Netdisk
by Tokimemofan - 1/27/09 8:00 PM In reply to: And that was not an answer my question. by R. Proffitt
I always used my Netdisk via usb so I never had to use the proprietary software. However it seems that my problem is either multi sourced or resource conflict related.
When faced with a pile of drives.
by R. Proffitt - 1/27/09 8:45 PM
In reply to: About the Netdisk by Tokimemofan
And you see corruption, be sure all the formats are error resistant.
Its odd you noted XIMETA and yet don't use the driver from them. What XIMETA gear I encountered was poorly designed and the hard drive temperatures was killing drives in just a few years.
Bob
Like I said
by Tokimemofan - 1/28/09 2:53 PM In reply to: When faced with a pile of drives. by R. Proffitt
The Ximeta isn't the only corrupt drive, any drive connected to the USB-P/SATA cable also had some corruption. The only common link seems to be USB, however I have yet to see corruption on any Flash drives. I do agree however that the Ximeta drives run too hot.
"any drive connected to the USB-P/SATA cable also had some
by R. Proffitt - 1/28/09 5:16 PM
In reply to: Like I said by Tokimemofan
"any drive connected to the USB-P/SATA cable also had some corruption"
That's a fine clue. Gift, trash or remove that from your collection. Corruption can be caused by the chip in the cable or the power supplied by that cable's bundled power supply.
Worth repeating. No FAT.
Bob
Updated info...
by Tokimemofan - 1/29/09 4:20 PM In reply to: "any drive connected to the USB-P/SATA cable also had some by R. Proffitt
All but one of my partitions are NTFS except for 1, and that 1 is clean. I'm now looking at the USB controller on Computer 2 as well as a suspected resource conflict involving the same system's SATA card. In case it helps the SATA problem has the following symptoms:
When copying data TO a SATA drive there is no failure.
When copying data FROM a SATA drive the computer randomly freezes.
When copying data FROM a SATA drive TO a SATA drive the computer freezes immediately.
Copying Data through USB increases the chances of a SATA freeze at least 3X
Pulling the SATA cable unfreezes the computer.
The computer unfreezes after several minutes with an error, "Device is not Ready".
After recovering via the 2nd method attempting to recopy usualy refreezes the computer.
In some cases the computer will freeze at a certain point in a file on repeated attempts to copy the file, these files are large (300MB-7GB) indicating a bad sector however these drives are working fine, showing that it may be a data pattern that is cause these (Less 5% of freezes show this behavior but it is noteworthy.)
Removing all other cards except for Graphics and Sound reduced the frequency of the freezes to less than 1% of the previous numbers.
The SATA Card is a PNY brand PCI card with a Sil3512 Revision A chipset. I have checked and there is no file corruption resulting from this SATA error.
There is another minor issue where the Graphics output abruptly color shifts to a strong bluish tint, this problem seems consistant with intermittant Red and Green signal line issues. This can be triggered by tapping the graphics card. The Graphics card is a Nvidia GeForce4 MX 4000 64MB.
"the computer freezes immediately."
by R. Proffitt - 1/29/09 5:20 PM
In reply to: Updated info... by Tokimemofan
Every time that happens there is a chance of corruption. While NTFS is what it is (no need to document that here), FAT usually shows up as damaged and progressively gets worse.
-> Focus on that lockup issue. Talk to your machine's builder and the person who designed the OS install plan. Consider that SATA showed up after XP and drivers may be buggy for that.
Bob
Tip:
by R. Proffitt - 1/29/09 5:22 PM
In reply to: Need Help, Data Corruption issue by Tokimemofan
Don't mix SATA on old operating systems. You find even XP to be somewhat troublesome at times. Try to stick to XP SP2 and better. (Linux is...)
Ok I talked to myself for a while, now what?
by Tokimemofan - 1/30/09 12:46 PM In reply to: Tip: by R. Proffitt
To make a long story short I bought a HP Pavillion 9795c that was missing some parts, I replaced the parts I needed, tested it, and installed Windows 2000. The SATA bug is worse on Windows XP and worse on a Dell Optiplex GX110 when I used the card there.
Look at the number of drives at play.
by R. Proffitt - 1/30/09 1:16 PM
In reply to: Ok I talked to myself for a while, now what? by Tokimemofan
I wonder if you are dealing with old drive issues. These drives are only 5 year designs. Example at http://en.wikipedia.org/wiki/Flat_Flex_Cable
What if you remove the parts over 5 years old?
Only one problem
by Tokimemofan - 1/30/09 3:22 PM In reply to: Look at the number of drives at play. by R. Proffitt
The corruption patterns are don't support the theory as the oldest corrupt drive is barely 5 years old and the 4 sata drives were made in 2008. There is a range of model numbers that I'll list.
Again, All 18 drives work fine except for a few bad sectors on some of the older ones that I have retired. I know that bad sectors are not the issue here because the this hardware has a nasty way of crashing when it hits one, even CHKDSK takes down the whole system.
The SATA issue seems to be a common problem with the Sil3x12 chipset (Google Sil3512 crash).
The following is the list of non retired drives
20.5AT Quantum Fireball Plus AS PATA (OS)
3240AT Quantum Bigfoot CY PATA (Boot)
MHV2060AT PL Fujitsu PATA (Known corruption)
ST3500320AS Seagate Barracuda 7200.11 SATA
WD800JB Western Digital Caviar PATA
WD1600 Western Digital Caviar PATA (Ximeta)(Known corruption)
WD3200AAJS Western Digital Caviar SE SATA
WD3200AAKS Western Digital Caviar SE16 SATA
WD5000AAKS Western Digital Caviar SE16 SATA
Then what's common to all the failures?
by R. Proffitt - 1/30/09 6:13 PM
In reply to: Only one problem by Tokimemofan
Let's flip that around and look at what's common. Change that and what happens?
| Forum legend: | |
 |
Locked thread |
 |
Moderator |
 |
CNET staff |
 |
Samsung staff |
 |
Norton Authorized Support team |
 |
AVG staff |
 |
Windows Outreach team |
 |
Dell staff |
 |
Intel staff |
