11-Cable Test::Write sector error!

same problem here!!!

does your wd making too much noise ???

mine makes this noise

http://www.2shared.com/file/11277304/5c33b6bd/Memo.html

is it normal???

I’m getting the same message too. I downloaded the earlier version as posted in thins thread. I have 2 drives. The c drive is a WD Caviar and it works fine. The other is a Seagate which i thought was giving me problems because the system would lock up. I tried to run the quick test and extended on the WD and i got the same stupid message but i got it to run on the seagate! Why would it tell me the cables are bad on one drive and not the other and i can use the pc obviously. Both drives are quiet so i have no complaints it’s just the occasional lock up that started me to look into this.

Thought I would share that I worked around this problem by going into Device Manager drive properties, and disabling write caching on the policies tabs.

The test then ran fine, after which I re-enabled the setting.

no noise.

just it occasionally lock up for 4-5 sec.:angry:

disabling write cachin…

it doesn’t work for me…:cry:

i lowered AAM setting and the noise faded.

should this happen?

what is the default value ?

Hello everybody, I’ve ran into the same problem here even though when I run the LifeGuard Diagnostics it shows a “pass” for the S.M.A.R.T. status.  While I’m not fortunate enough to own more than one hdd to test this problem out, I did some quick research that might have revealed something very important in finding out what the heck is going on.

I found this website ( http://club.myce.com/f138/western-digital-cable-test-failed-265602/) where people were posting about the same exact problem we have all ran into.  After reading it, it has seemed like they all came to the conclusion that the hdd and their via chipsets don’t get along well.

I checked to see if my mobo has a via chipset, and sure enough it does.  I have the asus m4a785td-v evo with the via vt6308p chipset installed in it.  I would like to see if anybody else has a via chipset to determine if there’s an incompatibility issue going on here with these things.

I have a gigabyte ga-p35c mobo and an intel E6750 processor and i’m getting the msg. I think if things are working leave it alone. I added a 2nd internal Seagate HD which started me on this path. Everything is fine now but the WD tool still fails the tests so i’m thinking it’s the tool not the drives or the tool doesn’t coexist with win 7

I too have the same problem. It happens on both my external and internal drive. I suspected immediately that there was something wrong with dataLifegaurd. I am going to get the drive replaced anyways for the 2 days of trouble spent finding out what was wrong.

I apologize for not catching this earlier, but DLG Diagnostics does [deleted] work on Windows 7, yet.  We’re [deleted] working on the update for 7. 

Added: We’re working on an update that will fix the Cable Test error.  Thanks Carol_in_WV for catching my error.

1 Like

now we have march 2010 and still no updates… same problem (cable test::write error)  here on an Ati 770 chipset!

If someone does not get drives listed simply ‘run as administrator’ in Win7 and drives will list properly.

WD1001FALS 1TG Black Caviar drive replaced a Samsung 250GB dated 2006.12.  Samsung was 7200rpm and worked fine, replaced for capacity.

Running Windows 7 pro 64-bit.

Data Lifeguard 1.17 release notes (  http://support.wdc.com/download/notes/WinDLG_v1_17_Release_Notes.pdf) include the following:  

New Features:

• Supports all Windows 7 32/64 bit versions, all Vista 32/64 bit versions and all Windows XP

32/64 bit versions

Motherboard is ASUS A8M2N-LA  w/ Award BIOS, GeForce 6150 LE chipset.  Not a VIA chipset.

Right-clicked to run DL, can see drives and start test, but test returns error already described.  Installed this drive yesterday.  If it is faulty, I need to know right away and return.  I tried different SATA cable and also switched SATA connection on motherboard, just in case.  No change.

Since WD has specifically reported that this version of DL is compatible with my Windows version, it appears that this hard drive is faulty after one day.

If no further information is available here within a day or two, I will return this drive.  Please, if someone has better info, save me this nuisance!

Just an off-the-wall question here . . .

I used the Acronis disk cloning software available from WD when I set up this drive.  It was really impressive, and I appreciate that it was available.  I’d tried to start with a different one, Drive Pro, and it could not see either of my drives I probably failed to ‘run as admin’ or something, but too late now!)

Any difference in success rates on cloned drives versus drives with fresh software installs?

Mine is cloned, GeForce 6150 chipset, AMD Athlon 64 X2 4400+.  I pulled the old drive (glad I cloned and didn’t migrate, since WD may be going back!), so this WD is the only drive in the system.  Initial partitions were set in Acronis for primary and recovery.  Used Win 7 Disk Manager to partition the unassigned space.

I have the same problem when i ran the data lifeguard diagnostics on a  Windows 7 -32 bit OS.The quick and extended test gave the same message. I tried with another cable ,still the same. I tried it on a different PC with Windiows Vista -32 bit and the drive passed the tests. I think it is a software compatibility with windows 7.

If you have Windows 7 platform and facing the same problem .Lemme know.

Class Action!  Class Action!

Someone is lying:

Version 1.17:

New Features:

32/64 bit versions

Supports all Windows 7 32/64 bit versions, all Vista 32/64 bit versions and all Windows XP

.

I got the same eroor as you did.  With the WD software.  It passed their general quick test(green check mark).  But when I tried to load the other test I received an immediate error.  Now, I can read the release notse as well as you can for Version 1.17.

However, I spoke to a WD digital rep the other day.  Although he had an accent he told me in absolute terms their software does not work for win7.  He told me I needed to use the dos version: download it, burn it(use something like Alch 120 - was his quote) then test it.  If you receive the same error then the drive is bad.

Comeon WD Win 7 has been out long enough. . .

Anyhow, I know someone has lied to me(and you).  I am not sure if this was their intention.  I know the patch notes say it works. . .   But, I know for sure less that 20 hours ago a WD tech support rep told me their software does not support win 7 - he told me this without skipping a beat.  Has WD addressed this issue anywhere else?

Anyone having BSOD?

My drive is less than a few months old.  I have read some pretty horrible stuff about WD.  However, I have used WD a lot and not had any issues.  I mean come on less than a year, less than 6 months even.  Just pushing the 90 day mark… Isnt that a smidgen obscene for my drive to break?

I already noted this on page 3.  DLG Diagnostics does work, but has an issue that is being fixed now. 

1 Like

I am using a wd3200AAJS (320GB 8MB sata2).

os: win7 pro x64

mobo: asus m4a785td-v evo

north: amd785g

south: amd710

lifeguard 1.17

I am getting the same test error code while trying to perform a quick or extended test. But smart test is ok. I am also having this problem while trying to boot lifeguard from a cd:

“Starting Caldera DOS”…

then 2 minutes or so later:

“Unable to locate the license agrement file, DLGLICE.TXT!!
Please make sure the license agrement is located in the same path as DLGDIAG.EXE”

Few minutes later:

“Cannot load the file A:\COMMAND.com”
Insert correct Disk and stike any key"

files on the CD:
DLGDIAG.TXT
DLGDIAG5.EXE
DLGLICE.TXT

IBMDOS.COM

I have tried 3 diffent burning programs and 2 different cd/dvd writers. So i am sure that the iso image is burned ok. I haven´t tried the floppy version because my mobo does not include a floppy controller on board.

Please WD!!!  The hdd is 2 weeks new. My pc keeps rebooting any time and showing blue screens. I know ram is ok. Already tried 3 different ddr3 modules and I get the same result. how can i be sure that the problem is on the hdd if  lifeguard 1.17 seems not to work on win7? Can your company do something? Or perhaps you want all of us to run win vista/xp/98 so your tool will work. In this case i have an idea. When selling a new hdd please include the following message: “Dear user, please don´t install win7 because our dianostic tool will NOT work” That will save our time.

As said before: win 7 wasn´t born yesterday…

This is probably going to be a terribly stupid question, but when burning the DLG Diagnostics ISO image to a CD, are you burning the ISO image straight to the CD?  Or, are you creating the CD from the ISO image?  Because if you are just burning the ISO image to the CD, it won’t work.  You have to use a burning software that gives you the option to create the CD from the ISO image.  Then it will see the software correctly.

1 Like

in other words, the writer software has to be (iso) image file aware to burn it properly - only then it works as expected.

that is correct! :slight_smile:

Exactly.  Looks like we’re on the same page.