WD data lifeguard tools on a HDD with data on it

  • Thread starter Thread starter Greg
  • Start date Start date
G

Greg

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
 
Greg said:
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.
Click to expand...

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
Click to expand...

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.
 
..../000:10/LOG> ### LOG START ###
..../000:10/LOG> DISKPATCH 2.1.100
..../000:10/LOG> (C) 2000-2005, DIY DataRecovery
..../000:10/LOG> Contact info: HTTP://www.DIYDataRecovery.nl
..../000:10/LOG> DPRunType: 0
..../000:10/LOG> DPUsrName: DEMO
..../000:10/LOG> MemFree: 107Kb
..../000:10/LOG> LogDate: 10-10-2005
..../000:10/CFG> Dump Options requested
..../000:10/CFG> FilePath="1/.\DP_FILES\"
..../000:10/CFG> LogFilename="DP.LOG"
..../000:10/CFG> ReadRetries="32"
..../000:10/CFG> MaxReadErrors="32"
..../000:10/CFG> ReadDelay="1"
..../000:10/CFG> AutoSaveState="1"
..../000:10/CFG> DumpFoundSectors="0"
..../000:10/CFG> LogLevel="2"
..../000:10/CFG> DebugLevel="0"
..../000:10/CFG> MaxFatScan="51200"
..../000:10/CFG> MaxDataColEntries="512"
..../000:10/CFG> ScanType="0"
..../000:10/CFG> IgnoreF8FF="0"
..../000:10/CFG> ScanSignature="55AA"
..../000:10/13H> Ext13H installed test requested
..../000:10/13H> Disk found at 128
..../000:10/13H> Ext13H version: 2.1 / EDD-1.1
..../000:10/13H> Ext13H Support: Extended disk access functions
..../000:10/13H> Ext13H Support: Enhanced disk drive functions
..../000:10/13H> Disk 128 X13H data : 0/0/0 12594960/512
..../000:10/13H> Disk found at 129
..../000:10/13H> Ext13H version: 2.1 / EDD-1.1
..../000:10/13H> Ext13H Support: Extended disk access functions
..../000:10/13H> Ext13H Support: Enhanced disk drive functions
..../000:10/13H> Disk 129 X13H data : 0/0/0 390721968/512
..../000:10/13H> Ext13H tested ok
..../000:10/FDL> DiskList requested
..../000:10/FDL> Disk found at 128
..../000:10/FDL> Disk found at 129
..../000:10/LOG> Dump DiskList requested
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB
128 | ..12594960 | 255 | 63 | ..6
129 | .390721968 | 255 | 63 | 186
...0 | .........0 | ..0 | .0 | ..0
...0 | .........0 | ..0 | .0 | ..0

..../000:10/IAS> Admi Sector found on disk 0 (128)
..../000:10/IAS> Admi Sector found on disk 1 (129)
..../000:10/EXE> FingerPrint found
..../000:10/PFC> PQstuff signature detected on disk 0 (128)
..../000:10/PFC> PQstuff signature not detected on disk 1 (129)
..../000:11/PFC> Partition State Backup not found on disk 0 (128)
..../000:11/PFC> Partition State Backup not found on disk 1 (129)
..../000:15/MNU> - Main, Select Disk
..../000:18/USD> Disk 1 (129) selected
..../000:18/USD> Read/WriteErrors reset to 0
..../000:18/USD> DataCollection / PartList cleared
..../000:18/GSC> No Geo change detected for Disk 1 (129)
..../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 |
é}.ú3ÀŽÐŽÀŽØ¼.|
016 8B F4 FB BF 00 06 B9 00 01 F3 A5 BB 20 06 FF E3 |
‹ôû¿..¹..ó¥» ..ã
032 90 90 BE 7D 07 81 3C AA 55 75 11 E8 58 00 73 0C |
¾}.<ªUu.èX.s.
048 E8 65 00 72 07 E8 B1 00 72 3B EB 2C BE 7D 07 C7 |
èe.r.è±.r;ë,¾}.Ç
064 04 00 00 BA 80 00 BE BE 07 B9 04 00 F6 04 80 75 |
....º€.¾¾.¹..ö.€u
080 07 83 C6 10 E2 F6 EB 1D 8A 74 01 8B 4C 02 BB 00 |
..ƒÆ.âöë.Št.‹L.».
096 7C B8 01 02 CD 13 72 0D 81 3E FE 7D 55 AA 75 05 |
|¸..Í.r.>þ}Uªu.
112 EA 00 7C 00 00 BE 6A 07 AC 0A C0 74 FE BB 07 00 |
ê.|..¾j.¬.Àtþ»..
128 B4 0E CD 10 EB F2 BB 00 7E C6 07 13 C6 47 01 00 |
´.Í.ëò».~Æ..ÆG..
144 B2 80 B8 00 E0 CD 13 C3 BF 00 7E BA F0 01 B3 A0 |
²€¸.àÍ.ÿ.~ºð.³
160 E8 84 00 72 0C B1 01 E8 48 00 72 05 E8 19 00 73 |
è,,.r.±.èH.r.è..s
176 16 F6 C3 10 75 05 80 CB 10 EB E5 81 FA 70 01 74 |
..öÃ.u.€Ë.ëåúp.t
192 05 BA 70 01 EB D8 F9 C3 81 BD FE 01 55 AA 75 17 |
..ºp.ëØùýþ.Uªu.
208 8B 75 02 81 FE BE 01 77 0E 03 F7 81 3C AA 55 75 |
‹u.þ¾.w..÷<ªUu
224 06 F6 44 02 01 75 01 F9 C3 BF 00 7C B1 0A E8 01 |
..öD..u.ùÿ.|±.è.
240 00 C3 52 57 83 C2 02 B0 01 EE 42 8A C1 EE 42 32 |
..ÃRWƒÂ.°.îBŠÁîB2
256 C0 EE 42 EE 42 8A C3 EE 42 B0 20 EE E8 33 00 EC |
ÀîBîBŠÃîB° îè3.ì
272 24 FD 3C 58 75 0D 83 EA 07 B9 00 01 FA F3 6D FB |
$ý<Xu.ƒê.¹..úómû
288 F8 EB 01 F9 5F 5A C3 52 83 C2 07 EC A8 80 75 0F |
øë.ù_ZÃRƒÂ.쨀u.
304 4A 8A C3 EE 42 EC 24 D0 3C 50 75 03 F8 EB 01 F9 |
JŠÃîBì$Ð<Pu.øë.ù
320 5A C3 51 8B 0E 6C 04 83 C1 12 81 C2 FF 01 EC 8A |
ZÃQ‹.l.ƒÁ.Â..ìŠ
336 E0 80 E4 D8 80 FC 58 74 06 3B 0E 6C 04 75 EF 81 |
à€äØ€üXt.;.l.uï
352 EA FF 01 B9 00 20 E2 FE 59 C3 0D 0A 45 72 72 6F | ê..¹.
âþYÃ..Erro
368 72 20 4C 6F 61 64 69 6E 67 20 4F 53 00 55 AA 00 | r Loading
OS.Uª.
384 00 E9 80 FE 00 00 00 00 68 00 00 00 00 00 00 00 |
..é€þ....h.......
400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |
.................
416 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |
.................
432 00 00 00 00 00 00 00 00 9E A0 D9 DB 00 00 80 01 |
.........ž ÙÛ..€.
448 01 00 07 FE FF FF 3F 00 00 00 82 DD 49 17 00 00 |
....þ..?...,ÝI...
464 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |
.................
480 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |
.................
496 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA |
...............Uª
### Interpreted Partition Table Information
###
_ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
...1 .128 | ..07 | ....0...1...1 | .1023.254..63 | ........63 |
..390716802
...2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 |
..........0
...3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 |
..........0
...4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 |
..........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_|______START_|_____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_|______START_|_____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_|________END_|__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
...1 .128 | ..07 | ....0...1...1 | .1023.254..63 | ........63 |
..390716802
...2 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 |
..........0
...3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 |
..........0
...4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 |
..........0

129/027:02/LOG> BootSectorDump requested at 63 (0 1 1)
### BootSectorDump for BStype NTFS
............Jump Code (hex): EB5290
.............OEM Name (txt): NTFS
.....Bytes per Sector (dec): 512
..Sectors per Cluster (dec): 8
.....Reserved Sectors (dec): 0
...............Unused (hex): 0000000000
.....Media Descriptor (hex): F8
...............Unused (hex): 0000
....Sectors per Track (dec): 63
......Heads per Track (dec): 255
.......Hidden Sectors (dec): 63
...............Unused (hex): 00000000
..............Unknown (hex): 00800080
........Total Sectors (dec): 390716801
.........MFT Location (dec): 4
..MFT Mirror Location (dec): 24419800
.....Clusters per FRS (dec): 246
..Clusters/Indx Block (dec): 1
............Volume ID (hex): AEC48BBCC48B84F5
.........Volume Label (txt): DRV2_VOL1
.............Checksum (hex): 00000000
.....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 ###
 
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\Services\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 said:
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\Services\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.
Click to expand...

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.
 
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.
Click to expand...
Apparently it is possible to boot from the cd
and update the existing installation.
Click to expand...
I still cannot work out if the DDO software is installed on
the master (boot) drive, or the slave (Western Digital) drive.
Click to expand...
Also, would the DOS version of Data Lifeguard
be compatible with Windows 2000?
Click to expand...
I cannot figure out where to get the Data Lifeguard Tools 11 CD
without buying a new hard drive.
Click to expand...
 
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.
Click to expand...

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.
Click to expand...

You need a work out?
Also, would the DOS version of Data Lifeguard be compatible with
Windows 2000?
Click to expand...

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?
Click to expand...

Their website maybe?
Oh, and using tools like testdisk and ptedit may have destroyed my
data.
Click to expand...

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
Click to expand...

bullshit

? - in an incompatible way.

It appears you yourself are a bit incompatible.
 
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....
How?
Click to expand...

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.
update what existing installation and update with what?
Click to expand...

Update the existing (faulty) installation of DDO with a fresh
installation of DDO
You need a work out?
Click to expand...

I am guessing that DDO goes on the slave drive (have not been able to
find docs on that)
I suggest you look that up yourself.
Click to expand...

I have, could not find the answer, can you help? or are you just being
smart?

Their website maybe?
Click to expand...

They don't have it - I checked. Maybe you saw it and I didn't?

what did you do with those then?
Click to expand...

"fixed" the boot sector and "rebuilt" the partition table. I know it
was stupid to do that, but I was desperate.
? - in an incompatible way.
Click to expand...

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.
Click to expand...

Incompatible with who?
 
Greg said:
Notwithstanding your rather abusive response....


I have, could not find the answer, can you help? or are you just being
smart?
Click to expand...

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.
 
Peter

Unfortunately Data Lifeguard Tools 11 for Windows will only let me
install a new drive by partitioning and formatting which I don't want
to do.

Joep
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.
Click to expand...

I followed your instructions but Windows will still not see the data

I will try a Linux boot CD to recover data by copying it somewhere else
and report the results
 
Peter said:
How much do you value data on that drive?
Or is that just an exercise?
Click to expand...

I would like to get some of the files back if I can. Most are backed up
but there are some I would like.

I am not prepared to spend a lot of money to purchase software if I
don't know it will work. I have noticed a lot of the tools have a demo
version which allows the identification of files which may be
recoverable.

Any reccomendations?
 
How much do you value data on that drive?
I would like to get some of the files back if I can. Most are backed up
but there are some I would like.

I am not prepared to spend a lot of money to purchase software if I
don't know it will work. I have noticed a lot of the tools have a demo
version which allows the identification of files which may be
recoverable.

Any reccomendations?
Click to expand...

With information you have supplied I cannot recommend any tools.

Next time, make sure you backup ALL of the files you like to have back; not
just SOME.
 
How much do you value data on that drive?
With information you have supplied I cannot recommend any tools.
Click to expand...
Next time, make sure you backup ALL of the files you like to have back; not
just SOME.
Click to expand...

You are right, backing up is the best solution always. Data recovery
software is a last resort.

I will try some out and report the results
 
Greg said:
Rod Speed
Click to expand...
You posted a link to Data Lifeguard Diagnostic
for DOS (CD) NOT Data Lifeguard Tools 11
Click to expand...
"Diagnostic" and "Tools" are different programs, but thanks anyway
Click to expand...

All there is is listed on that same page.

What you claim is supplied with hard drives in some
situations is just what is listed on that web page.
 
Rod said:
All there is is listed on that same page.

What you claim is supplied with hard drives in some
situations is just what is listed on that web page.
Click to expand...

I saw listed:
Data Lifeguard Tools 11 for Windows
Data Lifeguard Tools 11 for DOS
Data Lifeguard Diagnostic for DOS (Floppy)
Data Lifeguard Diagnostic for DOS (CD)
Data Lifeguard Diagnostic for Windows

I could not see Data Lifeguard Tools 11 for DOS (CD).

I have tried the Data Lifeguard Tools 11 for DOS but my floppy drive is
not working properly, which I why I am looking for the CD version.
 
I asked for the logfile to be posted in our forum.
sorry - my mistake
I am hoping this is a good sign

Booting up windows said the disk needed to checked for consistency and
then started deleting "orphaned file segments"

In case that was bad, I re-started and next time skipped disk checking.

Should I boot up and allow the disk to be checked and all the "orphaned
file segments" to be deleted? I am worried that they are actually the
files I want.

Linux reports: mount: wrong fs type, bad option, bad superblock on
/dev/hdb1

missing codepage or other error
I have partially scanned the drive and the only files found so far are
in the last folder that I put on the drive.

Not sure what to do next
 
Back
Top