Welcome, Guest. Please login or register.
Did you miss your activation email?
June 18, 2013, 06:33:03 AM
Home Help Search Login Register
News: Before posting, please read sticky topics!

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  General Data Recovery (Moderators: Tom, Joep)
| | |-+  Dynamic Disk Unreadable		 0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] 2 Go Down Print
Author Topic: Dynamic Disk Unreadable  (Read 2884 times)
Trevor
member

Posts: 12
« on: November 08, 2010, 10:03:59 AM »
Morning,

I am looking for helo in deciding which tool is the better to use for this problem.

We have a server that has a data set of disks (Raid 5).

Due to HDD faliure, this raid set rebuilt,
HP Array Utils show the logical disk set as available, however Windows disk manager shows

Dynamic
Unreadable

I have run irecover, and this shows many files, however a lot of them are listed as red.

Thanks


Trevor
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1168


WWW
« Reply #1 on: November 08, 2010, 10:58:02 AM »
Hello,

How large is the array?

How large is/are the dynamic volume(s), are there one or more volumes?

I assume you ran iRecover simple volume recovery?
Logged
--
Kind regards,
Joep
Trevor
member

Posts: 12
« Reply #2 on: November 08, 2010, 11:11:10 AM »
Hi Thanks for the reply,

The array is

4 * 36.4 Gb HP Hotplug Ultra SCSI drives set to raid 5, giving approx 101Gb usable .

Irecover was run in the

Recover Data from Simple VOlume or functional Raid     mode.

I have the saved file if that is of any help.

Thanks

Trevor.
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1168


WWW
« Reply #3 on: November 08, 2010, 11:17:02 AM »
Hello,

Could you:

Check if DiskPatch sees the array, and if so, create a support analysis logfile? Maybe we can make the volume accessible.
Logged
--
Kind regards,
Joep
Trevor
member

Posts: 12
« Reply #4 on: November 08, 2010, 11:20:18 AM »
WIll do, Im creating the boot cd now and will post the results when run.

Thanks
Logged
Trevor
member

Posts: 12
« Reply #5 on: November 08, 2010, 01:04:16 PM »
Having a few problems with this. The Array is found with Diskpatch, and it takes around 15 mins to run through the disk range, finding 0 read errors and 4 items.

Where I'm having the problem is exporting the report.

The server is too old to boot from USB, so has to boot from CD, it won't can't write to a memory stick once the analysis is done. The USB stick has been formated with the HP tool as advised.

Thanks

Trevor
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1157


WWW
« Reply #6 on: November 08, 2010, 02:18:17 PM »
No (external) floppy drive lying around somewhere? Old machine, does it have a floppy drive?
Most machines allow access to USB through DOS but indeed, older machines may not (how old?). In some cases tweaking BIOS settings for USB may help. Look for things like "legacy USB settings".
Depending on how important this all is; you could add an additional hard disk and format that as FAT. The log can be saved there.
Logged
Useful links:
Support index: www.diydatarecovery.nl/support.htm
Glossary of terms: http://www.diydatarecovery.nl/FAQ_general.htm#F11
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1168


WWW
« Reply #7 on: November 08, 2010, 02:20:11 PM »
Hello,

I see. Well, maybe, since 4 items is not a that long list, you can just describe those here, or take a photograph. What we are basically looking for is an NTFS volume that is about the 100 GB you expect the volume to be. So the value in the length column should be the equivalent of 100 GB (since value is in sectors: multiply by 512 then devide by 1024, and devide that by 1024 again). If the volume label for the volume is displayed by DiskPatch then this is an encouraging sign: it means the boot sector for the volume is intact, and that the boot sector is in fact pointing to a valid MFT.

Problem with this approach is, that as we can not write logfiles, we can not create undo-files either. But, any repairs with unwanted outcome do not reduce chances of success for file recovery with something like iRecover either.

uh oh: double post! Yes, good idea, if you happen to have a small hard disk, format it FAT and use it to save the logfiles.
Logged
--
Kind regards,
Joep
Trevor
member

Posts: 12
« Reply #8 on: November 08, 2010, 02:41:56 PM »
Hehehe Thanks guys...

After finally finding a floppy in the deepest darkest depths of an old filing cabinet, then finding a drive that would read it, I have the log


.../000:03/LOG> ### LOG START ###
.../000:03/LOG> DISKPATCH 3.5.300
.../000:03/LOG> (C) 2000-2009 DIY DataRecovery
.../000:03/LOG> Contact info: http://HTTP://www.DIYDataRecovery.nl
.../000:03/LOG> MemFree: 72Kb
.../000:03/LOG> CommandLineParms: /sup
.../000:03/LOG> LogDate: 11-08-2010
.../000:03/CFG> FilePath="A:DPFILES\"
.../000:03/CFG> ReadRetries="32"
.../000:03/CFG> WriteRetries="32"
.../000:03/CFG> MaxReadErrors="32"
.../000:03/CFG> MaxWriteErrors="1"
.../000:03/CFG> LogEachReadError="1"
.../000:03/CFG> ReadDelay="0"
.../000:03/CFG> VfyFixedBadSect="1"
.../000:03/CFG> CleanAfterDOD="1"
.../000:03/CFG> DiskReset="1"
.../000:03/CFG> SectorSkip="1024"
.../000:03/CFG> AutoSaveState="1"
.../000:03/CFG> DumpFoundSectors="0"
.../000:03/CFG> FixFats="1"
.../000:03/CFG> MaxFatScan="51200"
.../000:03/CFG> MaxDataColEntries="256"
.../000:03/CFG> IgnoreF8FF="0"
.../000:03/CFG> DownSizeExt="1"
.../000:03/CFG> ScanSignature="55AA"
.../000:03/CFG> Rebuild="00"
.../000:03/13H> Ext13H installed test requested
.../000:03/13H> Disk found at 128
.../000:03/13H> Ext13H version: EDD-3.0
.../000:03/13H> Ext13H Support: Extended disk access functions
.../000:03/13H> Ext13H Flags: Cylinder/head/sector info is valid
.../000:03/13H> Drive Interface Info: SCSI
.../000:03/13H> Disk 128 X13H data : 2176/255/32 17756160/512
.../000:03/13H> Disk found at 129
.../000:03/13H> Ext13H version: EDD-3.0
.../000:03/13H> Ext13H Support: Extended disk access functions
.../000:03/13H> Ext13H Flags: Cylinder/head/sector info is valid
.../000:03/13H> Drive Interface Info: SCSI
.../000:03/13H> Disk 129 X13H data : 26148/255/32 213367680/512
.../000:03/13H> Ext13H tested ok
.../000:03/FDL> DiskList requested
.../000:03/FDL> Disk found at 128
.../000:03/FDL> Disk found at 129
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB_|__GEO
128 | ..17756160 | 255 | 32 | ..8 | BIOS
129 | .213367680 | 255 | 32 | 101 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
.../000:03/IAS> AdmiSector found on disk 0 (128)
.../000:03/IAS> AdmiSector found on disk 1 (129)
.../000:04/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:04/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:04/WAS> AdmiSectors in use : 0+ 1+
.../000:04/KEY> DEMO/1
.../000:04/PFC> PQstuff signature not detected on disk 0 (128)
.../000:04/PFC> PQstuff signature not detected on disk 1 (129)
.../000:04/PFC> UDMA driver not loaded
.../000:05/PFC> Disk health not checked
.../000:06/PFC> Partition State backup not found on disk 0 (128)
.../000:06/PFC> Partition State backup not found on disk 1 (129)
.../000:06/PFC> No Repair date found on disk 0 (128)
.../000:06/PFC> No Repair date found on disk 1 (129)
.../000:18/CSD> Start CheckDisk for disk 1 (129)
.../000:18/CSD> CheckDisk complete, ReadErrors 0
.../000:18/USD> Disk 1 (129) selected
.../000:18/GSC> No geo change detected for disk 1 (129)
.../000:18/WAS> AdmiSectors in use : 0+ 1+
129/000:18/USD> MBR for disk 1 (129)
129/000:19/LOG> SectorDump requested at 0 (0 0 1)
###
000   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
016   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
032   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
048   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
064   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
080   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
096   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
112   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
128   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
144   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
160   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
176   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
192   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
208   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
224   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
240   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
256   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
272   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
288   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
304   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
320   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
336   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
352   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
368   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
384   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  |  ................
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 45 9D 45 9D 00 00 00 01  |  ........EE....
448   01 00 42 FE E0 FF 20 00 00 00 60 BB B7 0C 00 00  |  ..B. ...`...
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
###
129/000:20/VEC> Start Verify EPBR Chain for disk 1 (129)
129/000:20/VEC> Listing current partitions on disk:
129/000:20/VEC>      DYN (P)        (Err)          32   213367648     (102 Gb)
129/000:20/VEC> Partition Table info for sector 0 (0 0 1)
129/000:20/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..42 | ....0...1...1 | .1023.254..32 | ........32 | .213367648
..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:20/VEC> 55AA sig Ok
129/000:20/VEC> Verify EPBR Chain completed
129/000:21/USD> Select disk completed
129/000:24/SCN> DiskScan requested, ScanType is 3
129/000:24/SCN> from 0 (0 0 1) to 213367679 (26147 254 32), 213367680 sectors
129/000:24/SCN> Starting QuickScan (pre-vista) at 32 (0 1 1)
129/000:24/CDC> No DataCollection entries, CleanDatacollection aborted
129/000:24/MPL> No DataCollection entries, MakePartList aborted
129/000:25/SCN> Next QuickScan location at 0 (0 0 1)
129/000:25/SCN> QuickScan finished
129/000:25/SCN> Starting SmartScan (pre-vista) at 0 (0 0 1) (JMP=8160, RNG=32)
129/012:25/SCN> SmartScan finished
129/012:25/SCN> DiskScan completed
129/012:25/SCN> ReadErrors for disk 1 (129): 0
129/012:38/LOG> DataCollection items found: 5 / 2
### DATACOLLECTION.ARRAY, FULL ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL_|_F
001 | 129 | .........0 | ....DYN | PTE1 | ........32 | .213367648 | PRI | I
002 | 129 | .........6 | ....DYN | .LDM | ........32 | 4294967264 | PRI | I
003 | 129 | ..25165439 | ...NTFS | .BBS | ...8461920 | ..16703520 | PRI | .
004 | 129 | ..25165440 | ...NTFS | ..BS | ..25165440 | .125337600 | PRI | .
005 | 129 | .213171839 | ...NTFS | .BBS | ..87834240 | .125337600 | PRI | .
129/012:39/LOG> DataCollection items found: 5 / 2
### DATACOLLECTION.ARRAY, CLEANED ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL
003 | 129 | ..25165439 | ...NTFS | .BBS | ...8461920 | ..16703520 | PRI
004 | 129 | ..25165440 | ...NTFS | ..BS | ..25165440 | .125337600 | PRI
005 | 129 | .213171839 | ...NTFS | .BBS | ..87834240 | .125337600 | PRI
129/012:39/C4L> PTE found for DYN partition at LBA 0 / DC 1
129/012:39/LOG> PartList items created: 3
### PARTLIST.ARRAY ###
SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_|__PL_|_C_|___R
001 | ...NTFS | ... | ... | ..3 | ..0 | ..3 | ..3 | ..3 | 1 | ..B
002 | ...NTFS | ... | ..4 | ... | ..0 | ..4 | ..4 | ..4 | 1 | ..B
003 | ...NTFS | ... | ... | ..5 | ..0 | ..5 | ..5 | ..5 | 1 | ..B
### PARTLIST.ARRAY.INTERPRETED ###
SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R_|___A
001 | ...NTFS | ...8461920 | ..16703520 | ..25165439 | PRI | ..B | ..?
002 | ...NTFS | ..25165440 | .125337600 | .150503039 | PRI | ..B | ..?
003 | ...NTFS | ..87834240 | .125337600 | .213171839 | PRI | ..B | ..?
129/012:39/SST> SaveState requested for disk 1 (129)
129/012:44/WAS> AdmiSectors in use : 0+ 1+
129/012:45/SST> SaveState completed for disk 1 (129)
129/012:45/EXE> Analysis complete
129/012:50/LOG> RunTime: 012:50
129/012:50/LOG> ### CLOSE LOG ###
Logged
Trevor
member

Posts: 12
« Reply #9 on: November 08, 2010, 02:43:50 PM »
DP State.129 file contains

"3.5.300   255       32        213367680 A5A62E28B66B919A    5         3         0         "
"129","0","DYN","PTE1","32","213367648","PRI","I"
"129","6","DYN","LDM","32","4294967264","PRI","I"
"129","25165439","NTFS","BBS","8461920","16703520","PRI","I"
"129","25165440","NTFS","BS","25165440","125337600","PRI","I"
"129","213171839","NTFS","BBS","87834240","125337600","PRI","I"
"NTFS","","","3","0","3","3","3","1","B","","","","?"
"NTFS","","4","","0","4","4","4","1","B","","","","?"
"NTFS","","","5","0","5","5","5","1","B","","","","?"
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1168


WWW
« Reply #10 on: November 08, 2010, 03:30:07 PM »
Hello,

Weird. LDM entry suggests a partition starts at sector 32. But if we scan the disk, we do not find any additional hints for that. Normally you'd then see a NTFS boot sector at sector 32 and a backup bootsector further out on the disk also pointing towards start sector 32.

What OS was used to partition the disk? Maybe the volume was sector aligned rather than cylinder aligned and if so, for scanning you'd then need to select vista aligned. Could you try that?
Logged
--
Kind regards,
Joep
Trevor
member

Posts: 12
« Reply #11 on: November 08, 2010, 03:33:50 PM »
The Disk array is a HP / Compaq array set using a smart array 5i controler, the partitions were created using the HP Array COnfig Utility then the disks were formatted under windows 2000 server NTFS.

Ill post the other scan when its run
Logged
Trevor
member

Posts: 12
« Reply #12 on: November 08, 2010, 03:56:17 PM »
...
running again thistime after deleting the old logs
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1168


WWW
« Reply #13 on: November 08, 2010, 03:59:12 PM »
Hello,

That's a "pre-vista" scan again, we need the other one. Note that the most recent logfile is always called DP.LOG, LO(n) are the older ones (n is 1 upto 5).
Logged
--
Kind regards,
Joep
Trevor
member

Posts: 12
« Reply #14 on: November 08, 2010, 04:00:20 PM »
.log file was empty running again now.

Have deleted older files
Logged
Pages: [1] 2 Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!