If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
WD data lifeguard tools on a HDD with data on it
I installed a new 200GB hard drive as a slave drive using western
digital data lifeguard tools. After uninstalling some software, Windows 2000 (SP4) now reports the drive as unformatted. I have used various utilities to confirm the drive is ok, and the data is still there (it is) If I use western digital data lifeguard tools to set up the drive again, I will lose my data as threre is no option other than partition and format the drive - losing all data. my master (boot) drive is a Quantum HDD I assume that data lifeguard installs some kind of dynamic drive overlay software on the boot disk. If so, how could I check for this? Also, is dynamic drive overlay software installed on the boot sector of the master (boot) drive, or the slave (non-bootable) drive? Note: I can't use data recovery software to recover the data because I do not have anywhere to put it Further note: yes, I have searched and searched for an answer, but could not find one. If there is a thread that I should read, please notify me and I will read it. Thanks |
#2
|
|||
|
|||
"Greg" wrote in message
oups.com... I installed a new 200GB hard drive as a slave drive using western digital data lifeguard tools. After uninstalling some software, Windows 2000 (SP4) now reports the drive as unformatted. Can be a relatively simple boot sector problem. Note: I can't use data recovery software to recover the data because I do not have anywhere to put it You can see if you can use data recovery tools that fix damage in-place. If the issue is a boot sector issue then this is often possible. I am the co-author of DiskPatch, and DiskPatch was designed to address partition table and boot sector issues If you grab the DiskPatch demo from the website in my signature and create a DiskPatch support analysis logfile I can determine if we can or can not fix this. Please use our online forum (support section) to post the logfile. How to create a Support Analysis Log file: - download the latest DiskPatch demo - create the DiskPatch bootdiskette and boot the PC from this diskette - start DiskPatch (select option 1 from the start menu) - select the problem disk (menu "select disk") - start the Analysis Scan (menu "Support", "create support analysis log") - let the scan finish, you will be notified when the scan has completed - exit DiskPatch DP.LOG in the folder DP_FILES on your DiskPatch diskette is the logfile we'd like to have a look at. -- Kind regards, Joep -- D I Y D a t a R e c o v e r y . N L - Data & Disaster Recovery Tools http://www.diydatarecovery.nl http://www.diydatarecovery.com |
#3
|
|||
|
|||
..=2E./000:10/LOG ### LOG START ###
..=2E./000:10/LOG DISKPATCH 2.1.100 ..=2E./000:10/LOG (C) 2000-2005, DIY DataRecovery ..=2E./000:10/LOG Contact info: HTTP://www.DIYDataRecovery.nl ..=2E./000:10/LOG DPRunType: 0 ..=2E./000:10/LOG DPUsrName: DEMO ..=2E./000:10/LOG MemFree: 107Kb ..=2E./000:10/LOG LogDate: 10-10-2005 ..=2E./000:10/CFG Dump Options requested ..=2E./000:10/CFG FilePath=3D"1/.\DP_FILES\" ..=2E./000:10/CFG LogFilename=3D"DP.LOG" ..=2E./000:10/CFG ReadRetries=3D"32" ..=2E./000:10/CFG MaxReadErrors=3D"32" ..=2E./000:10/CFG ReadDelay=3D"1" ..=2E./000:10/CFG AutoSaveState=3D"1" ..=2E./000:10/CFG DumpFoundSectors=3D"0" ..=2E./000:10/CFG LogLevel=3D"2" ..=2E./000:10/CFG DebugLevel=3D"0" ..=2E./000:10/CFG MaxFatScan=3D"51200" ..=2E./000:10/CFG MaxDataColEntries=3D"512" ..=2E./000:10/CFG ScanType=3D"0" ..=2E./000:10/CFG IgnoreF8FF=3D"0" ..=2E./000:10/CFG ScanSignature=3D"55AA" ..=2E./000:10/13H Ext13H installed test requested ..=2E./000:10/13H Disk found at 128 ..=2E./000:10/13H Ext13H version: 2.1 / EDD-1.1 ..=2E./000:10/13H Ext13H Support: Extended disk access functions ..=2E./000:10/13H Ext13H Support: Enhanced disk drive functions ..=2E./000:10/13H Disk 128 X13H data : 0/0/0 12594960/512 ..=2E./000:10/13H Disk found at 129 ..=2E./000:10/13H Ext13H version: 2.1 / EDD-1.1 ..=2E./000:10/13H Ext13H Support: Extended disk access functions ..=2E./000:10/13H Ext13H Support: Enhanced disk drive functions ..=2E./000:10/13H Disk 129 X13H data : 0/0/0 390721968/512 ..=2E./000:10/13H Ext13H tested ok ..=2E./000:10/FDL DiskList requested ..=2E./000:10/FDL Disk found at 128 ..=2E./000:10/FDL Disk found at 129 ..=2E./000:10/LOG Dump DiskList requested ### DISKLIST.ARRAY ### __D_|________LBA_|___H_|__S_|__GB 128 | ..12594960 | 255 | 63 | ..6 129 | .390721968 | 255 | 63 | 186 ..=2E0 | .........0 | ..0 | .0 | ..0 ..=2E0 | .........0 | ..0 | .0 | ..0 ..=2E./000:10/IAS Admi Sector found on disk 0 (128) ..=2E./000:10/IAS Admi Sector found on disk 1 (129) ..=2E./000:10/EXE FingerPrint found ..=2E./000:10/PFC PQstuff signature detected on disk 0 (128) ..=2E./000:10/PFC PQstuff signature not detected on disk 1 (129) ..=2E./000:11/PFC Partition State Backup not found on disk 0 (128) ..=2E./000:11/PFC Partition State Backup not found on disk 1 (129) ..=2E./000:15/MNU - Main, Select Disk ..=2E./000:18/USD Disk 1 (129) selected ..=2E./000:18/USD Read/WriteErrors reset to 0 ..=2E./000:18/USD DataCollection / PartList cleared ..=2E./000:18/GSC No Geo change detected for Disk 1 (129) ..=2E./000:18/GSC Geo for Disk 1 (129) saved as 0390721968255063 129/000:18/LOG Dump MBR requested ### MBR FOR DISK 129 000 90 E9 7D 01 FA 33 C0 8E D0 8E C0 8E D8 BC 00 7C | =90=E9}.=FA3=C0=8E=D0=8E=C0=8E=D8=BC.| 016 8B F4 FB BF 00 06 B9 00 01 F3 A5 BB 20 06 FF E3 | =8B=F4=FB=BF..=B9..=F3=A5=BB ..=E3 032 90 90 BE 7D 07 81 3C AA 55 75 11 E8 58 00 73 0C | =90=90=BE}.=81=AAUu.=E8X.s. 048 E8 65 00 72 07 E8 B1 00 72 3B EB 2C BE 7D 07 C7 | =E8e.r.=E8=B1.r;=EB,=BE}.=C7 064 04 00 00 BA 80 00 BE BE 07 B9 04 00 F6 04 80 75 | ..=2E.=BA=80.=BE=BE.=B9..=F6.=80u 080 07 83 C6 10 E2 F6 EB 1D 8A 74 01 8B 4C 02 BB 00 | ..=83=C6.=E2=F6=EB.=8At.=8BL.=BB. 096 7C B8 01 02 CD 13 72 0D 81 3E FE 7D 55 AA 75 05 | |=B8..=CD.r.=81=FE}U=AAu. 112 EA 00 7C 00 00 BE 6A 07 AC 0A C0 74 FE BB 07 00 | =EA.|..=BEj.=AC.=C0t=FE=BB.. 128 B4 0E CD 10 EB F2 BB 00 7E C6 07 13 C6 47 01 00 | =B4.=CD.=EB=F2=BB.~=C6..=C6G.. 144 B2 80 B8 00 E0 CD 13 C3 BF 00 7E BA F0 01 B3 A0 | =B2=80=B8.=E0=CD.=C3=BF.~=BA=F0.=B3=20 160 E8 84 00 72 0C B1 01 E8 48 00 72 05 E8 19 00 73 | =E8,,.r.=B1.=E8H.r.=E8..s 176 16 F6 C3 10 75 05 80 CB 10 EB E5 81 FA 70 01 74 | ..=F6=C3.u.=80=CB.=EB=E5=81=FAp.t 192 05 BA 70 01 EB D8 F9 C3 81 BD FE 01 55 AA 75 17 | ..=BAp.=EB=D8=F9=C3=81=BD=FE.U=AAu. 208 8B 75 02 81 FE BE 01 77 0E 03 F7 81 3C AA 55 75 | =8Bu.=81=FE=BE.w..=F7=81=AAUu 224 06 F6 44 02 01 75 01 F9 C3 BF 00 7C B1 0A E8 01 | ..=F6D..u.=F9=C3=BF.|=B1.=E8. 240 00 C3 52 57 83 C2 02 B0 01 EE 42 8A C1 EE 42 32 | ..=C3RW=83=C2.=B0.=EEB=8A=C1=EEB2 256 C0 EE 42 EE 42 8A C3 EE 42 B0 20 EE E8 33 00 EC | =C0=EEB=EEB=8A=C3=EEB=B0 =EE=E83.=EC 272 24 FD 3C 58 75 0D 83 EA 07 B9 00 01 FA F3 6D FB | $=FDXu.=83=EA.=B9..=FA=F3m=FB 288 F8 EB 01 F9 5F 5A C3 52 83 C2 07 EC A8 80 75 0F | =F8=EB.=F9_Z=C3R=83=C2.=EC=A8=80u. 304 4A 8A C3 EE 42 EC 24 D0 3C 50 75 03 F8 EB 01 F9 | J=8A=C3=EEB=EC$=D0Pu.=F8=EB.=F9 320 5A C3 51 8B 0E 6C 04 83 C1 12 81 C2 FF 01 EC 8A | Z=C3Q=8B.l.=83=C1.=81=C2..=EC=8A 336 E0 80 E4 D8 80 FC 58 74 06 3B 0E 6C 04 75 EF 81 | =E0=80=E4=D8=80=FCXt.;.l.u=EF=81 352 EA FF 01 B9 00 20 E2 FE 59 C3 0D 0A 45 72 72 6F | =EA..=B9. =E2=FEY=C3..Erro 368 72 20 4C 6F 61 64 69 6E 67 20 4F 53 00 55 AA 00 | r Loading OS.U=AA. 384 00 E9 80 FE 00 00 00 00 68 00 00 00 00 00 00 00 | ..=E9=80=FE....h....... 400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ..=2E.............. 416 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ..=2E.............. 432 00 00 00 00 00 00 00 00 9E A0 D9 DB 00 00 80 01 | ..=2E......=9E =D9=DB..=80. 448 01 00 07 FE FF FF 3F 00 00 00 82 DD 49 17 00 00 | ..=2E.=FE..?...,=DDI... 464 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ..=2E.............. 480 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ..=2E.............. 496 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA | ..=2E............U=AA ### Interpreted Partition Table Information ### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length ..=2E1 .128 | ..07 | ....0...1...1 | .1023.254..63 | ........63 | ..390716802 ..=2E2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | ..=2E.......0 ..=2E3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | ..=2E.......0 ..=2E4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | ..=2E.......0 129/000:30/MNU - Support, Analyze Disk / StateFile (no repair, create log) 129/000:30/SCN DiskScan requested, ScanType is 0 129/000:30/SCN DiskScan 0 (0 0 1) / 390721967 (24321 80 63) / 390721968 129/000:30/SCN First bunnyhop BS at 63 (0 1 1) 129/000:31/SCN Next bunnyhop BS at 390716865 (24321 0 1) 129/026:57/SCN Next bunnyhop BS at 390716865 (24321 0 1) 129/026:57/SCN DiskScan completed 129/026:57/SCN ReadErrors for disk 1 (129): 0 129/026:57/SST SaveState requested for disk 1 (129) 129/027:02/SST SaveState finished for disk 1 (129) 129/027:02/CDC CleanDatacollection requested 129/027:02/CDC DataCollection Items found: 6 129/027:02/CDC DataCollection Items flagged: 3 129/027:02/CDC CleanDatacollection finished 129/027:02/LOG Dump DataCollection requested 129/027:02/LOG DataCollection Items found: 6 / 3 ### DATACOLLECTION.ARRAY, FULL ### SEQ_|___D_|________LOC_|____TYPE_|__COM_|______STA RT_|_____LENGTH_|__PL_|_F 001 | 129 | .........0 | ...NTFS | PTE1 | ........63 | .390716802 | PRI | . 002 | 129 | .........3 | ...NTFS | PTE1 | ........66 | .390716802 | LOG | I 003 | 129 | ........63 | ...NTFS | ..BS | ........63 | .390716802 | PRI | . 004 | 129 | ........63 | ...NTFS | ..BS | ........63 | .390716802 | PRI | I 005 | 129 | .390716864 | ...NTFS | .BBS | ........63 | .390716802 | PRI | . 006 | 129 | .390716864 | ...NTFS | .BBS | ........63 | .390716802 | PRI | I 129/027:02/LOG Dump DataCollection requested 129/027:02/LOG DataCollection Items found: 6 / 3 ### DATACOLLECTION.ARRAY, CLEANED ### SEQ_|___D_|________LOC_|____TYPE_|__COM_|______STA RT_|_____LENGTH_|__PL 001 | 129 | .........0 | ...NTFS | PTE1 | ........63 | .390716802 | PRI 003 | 129 | ........63 | ...NTFS | ..BS | ........63 | .390716802 | PRI 005 | 129 | .390716864 | ...NTFS | .BBS | ........63 | .390716802 | PRI 129/027:02/MPL MakePartList requested 129/027:02/MPL MakePartList Items created: 1 129/027:02/MPL MakePartList finished 129/027:02/LOG Dump PartList requested 129/027:02/LOG PartList Items created: 1 ### PARTLIST.ARRAY ### SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_ |__PL_|_C_|___R 001 | ...NTFS | ..1 | ..3 | ..5 | --- | ..1 | ..1 | ..1 | 3 | .7# ### PARTLIST.ARRAY.INTERPRETED ### SEQ_|____TYPE_|______START_|_____LENGTH_|________E ND_|__PL_|___R 001 | ...NTFS | ........63 | .390716802 | .390716864 | PRI | .7# 129/027:02/VEC Start Verify EPBR Chain for disk 1 (129) 129/027:02/VEC MBR: 55AA found, Valid Type F/5 not found 129/027:02/VEC Partition Table info for sector 0 (0 0 1) 129/027:02/LOG PartListDump requested at 0 (0 0 1) ### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length ..=2E1 .128 | ..07 | ....0...1...1 | .1023.254..63 | ........63 | ..390716802 ..=2E2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | ..=2E.......0 ..=2E3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | ..=2E.......0 ..=2E4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | ..=2E.......0 129/027:02/LOG BootSectorDump requested at 63 (0 1 1) ### BootSectorDump for BStype NTFS ..=2E.........Jump Code (hex): EB5290 ..=2E..........OEM Name (txt): NTFS ..=2E..Bytes per Sector (dec): 512 ..Sectors per Cluster (dec): 8 ..=2E..Reserved Sectors (dec): 0 ..=2E............Unused (hex): 0000000000 ..=2E..Media Descriptor (hex): F8 ..=2E............Unused (hex): 0000 ..=2E.Sectors per Track (dec): 63 ..=2E...Heads per Track (dec): 255 ..=2E....Hidden Sectors (dec): 63 ..=2E............Unused (hex): 00000000 ..=2E...........Unknown (hex): 00800080 ..=2E.....Total Sectors (dec): 390716801 ..=2E......MFT Location (dec): 4 ..MFT Mirror Location (dec): 24419800 ..=2E..Clusters per FRS (dec): 246 ..Clusters/Indx Block (dec): 1 ..=2E.........Volume ID (hex): AEC48BBCC48B84F5 ..=2E......Volume Label (txt): DRV2_VOL1 ..=2E..........Checksum (hex): 00000000 ..=2E..Sector Signature (hex): AA55 129/027:02/VEC Verify EPBR Chain finished 129/027:02/EXE Analysis Complete 129/027:09/MNU - Main, Quit 129/027:09/LOG RunTime: 027:09 129/027:09/LOG ### CLOSE LOG ### |
#4
|
|||
|
|||
Hi,
I asked for the logfile to be posted in our forum. Anyway, at first glance the partition table and boot sector look fine. Make sure this is not a Windows problem that may result in behavior as you describe it: Windows may have trouble accessing the entire disk and can not reach the backup boot sector. SP4 is allright, you may need to edit the registry as well: To enable EnableBigLba in the Windows registry, perform the following steps: a.. Start a registry editor (e.g., regedit.exe). In Windows, click on Start-Run, enter "regedit". a.. Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\atapi\Parameters registry subkey. a.. From the Edit menu, select New, DWORD Value. a.. Enter the name EnableBigLba, then press Enter. a.. Double-click the new value, set it to 1, then click OK. a.. Close the registry editor. a.. Restart the machine for the change to take effect. Once this is taken care of and if this was the issue, Windows can now access the backup boot sector and the non formatted message disappears. If this did not resolve the issue you may need a Linux boot CD to recover data by copying it somewher else. If that does not work you need a file recovery tool. -- Joep "Greg" wrote in message oups.com... I installed a new 200GB hard drive as a slave drive using western digital data lifeguard tools. After uninstalling some software, Windows 2000 (SP4) now reports the drive as unformatted. I have used various utilities to confirm the drive is ok, and the data is still there (it is) If I use western digital data lifeguard tools to set up the drive again, I will lose my data as threre is no option other than partition and format the drive - losing all data. my master (boot) drive is a Quantum HDD I assume that data lifeguard installs some kind of dynamic drive overlay software on the boot disk. If so, how could I check for this? Also, is dynamic drive overlay software installed on the boot sector of the master (boot) drive, or the slave (non-bootable) drive? Note: I can't use data recovery software to recover the data because I do not have anywhere to put it Further note: yes, I have searched and searched for an answer, but could not find one. If there is a thread that I should read, please notify me and I will read it. Thanks |
#5
|
|||
|
|||
Joep wrote: Hi, I asked for the logfile to be posted in our forum. Anyway, at first glance the partition table and boot sector look fine. Make sure this is not a Windows problem that may result in behavior as you describe it: Windows may have trouble accessing the entire disk and can not reach the backup boot sector. SP4 is allright, you may need to edit the registry as well: To enable EnableBigLba in the Windows registry, perform the following steps: a.. Start a registry editor (e.g., regedit.exe). In Windows, click on Start-Run, enter "regedit". a.. Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\atapi\Parameters registry subkey. a.. From the Edit menu, select New, DWORD Value. a.. Enter the name EnableBigLba, then press Enter. a.. Double-click the new value, set it to 1, then click OK. a.. Close the registry editor. a.. Restart the machine for the change to take effect. Once this is taken care of and if this was the issue, Windows can now access the backup boot sector and the non formatted message disappears. If this did not resolve the issue you may need a Linux boot CD to recover data by copying it somewher else. If that does not work you need a file recovery tool. -- Joep "Greg" wrote in message oups.com... I installed a new 200GB hard drive as a slave drive using western digital data lifeguard tools. After uninstalling some software, Windows 2000 (SP4) now reports the drive as unformatted. I have used various utilities to confirm the drive is ok, and the data is still there (it is) If I use western digital data lifeguard tools to set up the drive again, I will lose my data as threre is no option other than partition and format the drive - losing all data. my master (boot) drive is a Quantum HDD I assume that data lifeguard installs some kind of dynamic drive overlay software on the boot disk. If so, how could I check for this? Also, is dynamic drive overlay software installed on the boot sector of the master (boot) drive, or the slave (non-bootable) drive? Note: I can't use data recovery software to recover the data because I do not have anywhere to put it Further note: yes, I have searched and searched for an answer, but could not find one. If there is a thread that I should read, please notify me and I will read it. Thanks I have figured out I need the Data Lifeguard Tools 11 CD to fix my problem - but I did not get one with my hard drive. Apparently it is possible to boot from the cd and update the existing installation. I still cannot work out if the DDO software is installed on the master (boot) drive, or the slave (Western Digital) drive. Also, would the DOS version of Data Lifeguard be compatible with Windows 2000? I cannot figure out where to get the Data Lifeguard Tools 11 CD without buying a new hard drive. Any ideas? Oh, and using tools like testdisk and ptedit may have destroyed my data. Also, disk recovery tools do not work where a drive had DDO installed and now windows is being used to access the data because DDO and windows see the data differently - in an incompatible way. |
#6
|
|||
|
|||
Greg wrote:
Joep wrote: Hi, I asked for the logfile to be posted in our forum. Anyway, at first glance the partition table and boot sector look fine. Make sure this is not a Windows problem that may result in behavior as you describe it: Windows may have trouble accessing the entire disk and can not reach the backup boot sector. SP4 is allright, you may need to edit the registry as well: To enable EnableBigLba in the Windows registry, perform the following steps: a.. Start a registry editor (e.g., regedit.exe). In Windows, click on Start-Run, enter "regedit". a.. Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\atapi\Parameters registry subkey. a.. From the Edit menu, select New, DWORD Value. a.. Enter the name EnableBigLba, then press Enter. a.. Double-click the new value, set it to 1, then click OK. a.. Close the registry editor. a.. Restart the machine for the change to take effect. Once this is taken care of and if this was the issue, Windows can now access the backup boot sector and the non formatted message disappears. If this did not resolve the issue you may need a Linux boot CD to recover data by copying it somewher else. If that does not work you need a file recovery tool. -- Joep "Greg" wrote in message oups.com... I installed a new 200GB hard drive as a slave drive using western digital data lifeguard tools. After uninstalling some software, Windows 2000 (SP4) now reports the drive as unformatted. I have used various utilities to confirm the drive is ok, and the data is still there (it is) If I use western digital data lifeguard tools to set up the drive again, I will lose my data as threre is no option other than partition and format the drive - losing all data. my master (boot) drive is a Quantum HDD I assume that data lifeguard installs some kind of dynamic drive overlay software on the boot disk. If so, how could I check for this? Also, is dynamic drive overlay software installed on the boot sector of the master (boot) drive, or the slave (non-bootable) drive? Note: I can't use data recovery software to recover the data because I do not have anywhere to put it Further note: yes, I have searched and searched for an answer, but could not find one. If there is a thread that I should read, please notify me and I will read it. I have figured out I need the Data Lifeguard Tools 11 CD to fix my problem - but I did not get one with my hard drive. Apparently it is possible to boot from the cd and update the existing installation. I still cannot work out if the DDO software is installed on the master (boot) drive, or the slave (Western Digital) drive. Also, would the DOS version of Data Lifeguard be compatible with Windows 2000? I cannot figure out where to get the Data Lifeguard Tools 11 CD without buying a new hard drive. Any ideas? http://support.wdc.com/download/inde...id=999&swid=30 Oh, and using tools like testdisk and ptedit may have destroyed my data. Also, disk recovery tools do not work where a drive had DDO installed and now windows is being used to access the data because DDO and windows see the data differently - in an incompatible way. |
#7
|
|||
|
|||
"Greg" wrote in message
oups.com... I have figured out I need the Data Lifeguard Tools 11 CD to fix my problem - How? Apparently it is possible to boot from the cd and update the existing installation. update what existing installation and update with what? I still cannot work out if the DDO software is installed on the master (boot) drive, or the slave (Western Digital) drive. You need a work out? Also, would the DOS version of Data Lifeguard be compatible with Windows 2000? I suggest you look that up yourself. I cannot figure out where to get the Data Lifeguard Tools 11 CD without buying a new hard drive. Any ideas? Their website maybe? Oh, and using tools like testdisk and ptedit may have destroyed my data. what did you do with those then? Also, disk recovery tools do not work where a drive had DDO installed and now windows is being used to access the data because DDO and windows see the data differently bull**** ? - in an incompatible way. It appears you yourself are a bit incompatible. -- Joep |
#8
|
|||
|
|||
Rod Speed
You posted a link to Data Lifeguard Diagnostic for DOS (CD) NOT Data Lifeguard Tools 11 "Diagnostic" and "Tools" are different programs, but thanks anyway Jeop Notwithstanding your rather abusive response.... I have figured out I need the Data Lifeguard Tools 11 CD to fix my problem - How? I used Data Lifeguard Tools to set up the drive in the first place (thus installing DDO on the drive) as DDO has now dissapeared according to WD the Data Lifeguard Tools 11 CD can be used to reinstall (update) the DDO software on the drive. Apparently it is possible to boot from the cd and update the existing installation. update what existing installation and update with what? Update the existing (faulty) installation of DDO with a fresh installation of DDO I still cannot work out if the DDO software is installed on the master (boot) drive, or the slave (Western Digital) drive. You need a work out? I am guessing that DDO goes on the slave drive (have not been able to find docs on that) Also, would the DOS version of Data Lifeguard be compatible with Windows 2000? I suggest you look that up yourself. I have, could not find the answer, can you help? or are you just being smart? I cannot figure out where to get the Data Lifeguard Tools 11 CD without buying a new hard drive. Any ideas? Their website maybe? They don't have it - I checked. Maybe you saw it and I didn't? Oh, and using tools like testdisk and ptedit may have destroyed my data. what did you do with those then? "fixed" the boot sector and "rebuilt" the partition table. I know it was stupid to do that, but I was desperate. Also, disk recovery tools do not work where a drive had DDO installed and now windows is being used to access the data because DDO and windows see the data differently bull**** ? - in an incompatible way. I had DDO with windows - the drive was fine. I have now enabled 48-bit addressing, so windows can see the whole drive (but reports it as unformatted). DDO is gone and windows is being used to access the drive. All the filerecovery tools I have looked at the drive with do no see the files, even though the data is there (I checked that with PTTD It appears you yourself are a bit incompatible. Incompatible with who? |
#9
|
|||
|
|||
Update: Windows 2000 saw my drive as unformatted after enabling BigLba
this is from the segate site fyi: http://www.seagate.com/support/kb/di...wse_maint.html both Segate and Western Digital use Ontrack disk tools to manage thier DDO |
#10
|
|||
|
|||
"Greg" wrote in message
oups.com... Notwithstanding your rather abusive response.... I suggest you look that up yourself. I have, could not find the answer, can you help? or are you just being smart? Greg, You are asking stupid questions and for info available on the WD website you must be blind to miss. You're dealing wih a dataloss issue with the wrong tools, you should avoid messing around with drive overlay software installation stuff until you have recovered the data. If you can not use data recovery tools because you have nowehere to copy to, then get another disk. You're asking questions and at the same time trying to outsmart those who answer those questions. -- Joep |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Problem with WD Lifeguard Tools | news.telenet.be | Storage (alternative) | 33 | September 15th 05 11:11 AM |
Pulling Out Hair: P4T-E & 250 Gig Drive | Bill Anderson | Asus Motherboards | 10 | January 29th 04 04:39 PM |
help with motherboard choice | S.Boardman | General | 30 | October 20th 03 10:23 PM |
help with motherboard choice | S.Boardman | Overclocking AMD Processors | 30 | October 20th 03 10:23 PM |
Athlon 4 XP-M 2400+ ? | A. J. Moss | General | 89 | August 28th 03 02:53 PM |