Unmountable boot volume error resulted in lost data

[jimmie1978]

Hi people. I need some help in deciding what software to buy, or who to use.

I have a 2TB HDD which suffered an unmountable boot volume error, resulting in lots of non replacable data, such as my eldest 4th birthday party, and other precious photos. I thought I had a backup sorted through Norton, but it turns out that the backups stopped for some reason back in February.

I was experiencing blue screen deaths. It would load, crash, reboot and go around in circles, so I decided to reload Windows Vista from scratch, but making sure that I created a backup file, rather than get rid of everything.

The good news is that it no longer gives me the dreaded blue screen, the bad news, its forced in to a scndsk everytime, and gets stuck on step 3 of 3 and stalls on the message verifying USN journal.

I have tried connected this drive as a secondary to retreive the data, but connecting the HDD as a secondary only makes the PC hang, or slow considerably, and refuses to give me access blaming it on an I/O error.

I really need to get these pictures back, and documents come to think of it, but I don't know if A) its possible and B) what software or service I should use.

All help on this would be greatly appreciated. Thanks.

[Joep]

Hello,

If Windows stalls as soon as this disk is connected then that's a bit of a problem because iRecover runs in Windows. At the same time it says something about the condition of the hard disk. The symptoms described can be due to just one or two bad sectors in the 'right' place.

DiskPatch could be an option then, it depends a bit on how bad the disk is. If there are a few bad sectors, then these may cause Windows to stall. An option would be to run a DiskPatch read/write surface scan so that the bad sectors are 'swapped' for spare sectors. If possible create a DiskPatch disk health report (can be done with the demo):
http://www.diydatarecovery.nl/dp_manual/guide_smartcheck.htm.

[jimmie1978]

I have a log for you to analise. I thought I had 2 as I did the pre vista install, and the after install check, but I can only find one log file to send you, of which I do not know what one this log belongs too.

Just to fill you in on the latest. When I reboot now, it no longer forces a scndsk, but will not load vista. I see a blue screen of death for a breaf second, then it reboots. It will do the same on both safe mode and normal mode.

.../000:01/LOG> ### LOG START ###
.../000:01/LOG> DISKPATCH 3.5.300
.../000:01/LOG> (C) 2000-2009 DIY DataRecovery
.../000:01/LOG> Contact info: http://HTTP://www.DIYDataRecovery.nl
.../000:01/LOG> MemFree: 63Kb
.../000:01/LOG> CommandLineParms: /sup
.../000:01/LOG> LogDate: 11-10-2011
.../000:01/CFG> FilePath="C:DPFILES\"
.../000:01/CFG> ReadRetries="32"
.../000:01/CFG> WriteRetries="32"
.../000:01/CFG> MaxReadErrors="32"
.../000:01/CFG> MaxWriteErrors="1"
.../000:01/CFG> LogEachReadError="1"
.../000:01/CFG> ReadDelay="0"
.../000:01/CFG> VfyFixedBadSect="1"
.../000:01/CFG> CleanAfterDOD="1"
.../000:01/CFG> DiskReset="1"
.../000:01/CFG> SectorSkip="1024"
.../000:01/CFG> AutoSaveState="1"
.../000:01/CFG> DumpFoundSectors="0"
.../000:01/CFG> FixFats="1"
.../000:01/CFG> MaxFatScan="51200"
.../000:01/CFG> MaxDataColEntries="256"
.../000:01/CFG> IgnoreF8FF="0"
.../000:01/CFG> DownSizeExt="1"
.../000:01/CFG> ScanSignature="55AA"
.../000:01/CFG> Rebuild="00"
.../000:01/13H> Ext13H installed test requested
.../000:01/13H> Disk found at 128
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Ext13H Flags: Write with verify supported
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 128 X13H data : 973/255/63 15633408/512
.../000:01/13H> Disk found at 129
.../000:01/13H> Ext13H version: EDD-3.0
.../000:01/13H> Ext13H Support: Extended disk access functions
.../000:01/13H> Ext13H Support: Enhanced disk drive functions
.../000:01/13H> Drive Interface Info:
.../000:01/13H> Disk 129 X13H data : 16383/16/63 3907029168/512
.../000:01/13H> Ext13H tested ok
.../000:01/FDL> DiskList requested
.../000:01/FDL> Disk found at 128
.../000:01/FDL> Disk found at 129
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB_|__GEO
128 | ..15633408 | 255 | 63 | ..7 | BIOS
129 | 3907029168 | 255 | 63 | 863 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
.../000:02/IAS> AdmiSector found on disk 0 (128)
.../000:02/IAS> AdmiSector found on disk 1 (129)
.../000:02/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:03/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:03/WAS> AdmiSectors in use : 0+ 1+
.../000:03/KEY> DEMO/1
.../000:03/PFC> PQstuff signature not detected on disk 0 (128)
.../000:03/PFC> PQstuff signature not detected on disk 1 (129)
.../000:03/PFC> UDMA driver not loaded
.../000:03/PFC> Disk health not checked
.../000:04/PFC> Partition State backup not found on disk 0 (128)
.../000:04/PFC> Partition State backup not found on disk 1 (129)
.../000:04/PFC> No Repair date found on disk 0 (128)
.../000:04/PFC> No Repair date found on disk 1 (129)
.../000:18/CSD> Start CheckDisk for disk 1 (129)
.../000:19/CSD> CheckDisk complete, ReadErrors 0
.../000:19/USD> Disk 1 (129) selected
.../000:19/GSC> No geo change detected for disk 1 (129)
.../000:19/WAS> AdmiSectors in use : 0+ 1+
129/000:19/USD> MBR for disk 1 (129)
129/000:19/LOG> SectorDump requested at 0 (0 0 1)
###
000   33 C0 8E D0 BC 00 7C 8E C0 8E D8 BE 00 7C BF 00  |  3ÀŽÐ¼.|ŽÀŽØ¾.|¿.
016   06 B9 00 02 FC F3 A4 50 68 1C 06 CB FB B9 04 00  |  .¹..üó¤Ph..Ëû¹..
032   BD BE 07 80 7E 00 00 7C 0B 0F 85 10 01 83 C5 10  |  ½¾.€~..|..…..ƒÅ.
048   E2 F1 CD 18 88 56 00 55 C6 46 11 05 C6 46 10 00  |  âñÍ.ˆV.UÆF..ÆF..
064   B4 41 BB AA 55 CD 13 5D 72 0F 81 FB 55 AA 75 09  |  ´A»ªUÍ.]r.�ûUªu.
080   F7 C1 01 00 74 03 FE 46 10 66 60 80 7E 10 00 74  |  ÷Á..t.þF.f`€~..t
096   26 66 68 00 00 00 00 66 FF 76 08 68 00 00 68 00  |  &fh....f.v.h..h.
112   7C 68 01 00 68 10 00 B4 42 8A 56 00 8B F4 CD 13  |  |h..h..´BŠV.‹ôÍ.
128   9F 83 C4 10 9E EB 14 B8 01 02 BB 00 7C 8A 56 00  |  ŸƒÄ.žë.¸..».|ŠV.
144   8A 76 01 8A 4E 02 8A 6E 03 CD 13 66 61 73 1E FE  |  Šv.ŠN.Šn.Í.fas.þ
160   4E 11 0F 85 0C 00 80 7E 00 80 0F 84 8A 00 B2 80  |  N..…..€~.€.„Š.²€
176   EB 82 55 32 E4 8A 56 00 CD 13 5D EB 9C 81 3E FE  |  ë‚U2äŠV.Í.]ëœ�>þ
192   7D 55 AA 75 6E FF 76 00 E8 8A 00 0F 85 15 00 B0  |  }Uªun.v.èŠ..…..°
208   D1 E6 64 E8 7F 00 B0 DF E6 60 E8 78 00 B0 FF E6  |  Ñædè.°ßæ`èx.°.æ
224   64 E8 71 00 B8 00 BB CD 1A 66 23 C0 75 3B 66 81  |  dèq.¸.»Í.f#Àu;f�
240   FB 54 43 50 41 75 32 81 F9 02 01 72 2C 66 68 07  |  ûTCPAu2�ù..r,fh.
256   BB 00 00 66 68 00 02 00 00 66 68 08 00 00 00 66  |  »..fh....fh....f
272   53 66 53 66 55 66 68 00 00 00 00 66 68 00 7C 00  |  SfSfUfh....fh.|.
288   00 66 61 68 00 00 07 CD 1A 5A 32 F6 EA 00 7C 00  |  .fah...Í.Z2öê.|.
304   00 CD 18 A0 B7 07 EB 08 A0 B6 07 EB 03 A0 B5 07  |  .Í. ·.ë. ¶.ë. µ.
320   32 E4 05 00 07 8B F0 AC 3C 00 74 FC BB 07 00 B4  |  2ä...‹ð¬<.tü»..´
336   0E CD 10 EB F2 2B C9 E4 64 EB 00 24 02 E0 F8 24  |  .Í.ëò+Éädë.$.àø$
352   02 C3 49 6E 76 61 6C 69 64 20 70 61 72 74 69 74  |  .ÃInvalid partit
368   69 6F 6E 20 74 61 62 6C 65 00 45 72 72 6F 72 20  |  ion table.Error
384   6C 6F 61 64 69 6E 67 20 6F 70 65 72 61 74 69 6E  |  loading operatin
400   67 20 73 79 73 74 65 6D 00 4D 69 73 73 69 6E 67  |  g system.Missing
416   20 6F 70 65 72 61 74 69 6E 67 20 73 79 73 74 65  |   operating syste
432   6D 00 00 00 00 62 7A 99 B6 FC 6F B7 00 00 00 20  |  m....bz™¶üo·...
448   21 00 07 FE FF FF 00 08 00 00 00 00 80 01 80 FE  |  !..þ........€.€þ
464   FF FF 07 FE FF FF 00 08 80 01 00 78 60 E7 00 00  |  ...þ....€..x`ç..
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:19/VEC> Start Verify EPBR Chain for disk 1 (129)
129/000:19/VEC> Listing current partitions on disk:
129/000:19/VEC>     NTFS (P)       _OEMBP        2048    25165824      (12 Gb)
129/000:19/VEC>     NTFS (P)          HDD    25167872  3881859072    (1851 Gb)
129/000:19/VEC> Partition Table info for sector 0 (0 0 1)
129/000:19/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..07 | ....0..32..33 | .1023.254..63 | ......2048 | ..25165824
..2 .128 | ..07 | .1023.254..63 | .1023.254..63 | ..25167872 | 3881859072
..3 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
..4 ...0 | ..00 | ....0...0...0 | ....0...0...0 | .........0 | .........0
129/000:19/VEC> 55AA sig Ok
129/000:19/LOG> Boot sector dump requested at 2048 (0 32 33)
### 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): 2048
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 25165823
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 1572863
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 18BEA770BEA744DA
........Volume Label (txt): _OEMBP
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/000:19/VEC> BS and BBS equal
129/000:19/LOG> Boot sector dump requested at 25167872 (1566 160 3)
### 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): 25167872
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 3881859071
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 242616191
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 1AC89D98C89D732D
........Volume Label (txt): HDD
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
129/000:19/VEC> BS and BBS equal
129/000:19/VEC> Verify EPBR Chain completed
129/000:19/USD> Select disk completed
129/000:28/SCN> DiskScan requested, ScanType is 3
129/000:28/SCN> from 0 (0 0 1) to 3907029167 (243201 80 63), 3907029168 sectors
129/000:28/SCN> Starting QuickScan (vista) at 2048 (0 32 33)
129/000:28/SCN> Next QuickScan location at 25167872 (1566 160 3)
129/000:29/SCN> Next QuickScan location at 3907026944 (243201 45 45)
129/000:29/SCN> Next QuickScan location at 0 (0 0 1)
129/000:30/SCN> QuickScan finished
129/000:30/SCN> Starting SmartScan (vista) at 0 (0 0 1)
129/000:30/RDS> Read past EOD intercept for disk 129 at 4294967295 (267349 89 4)
129/354:44/SCN> SmartScan finished
129/354:44/SCN> DiskScan completed
129/354:44/SCN> ReadErrors for disk 1 (129): 0
129/364:38/LOG> DataCollection items found: 10 / 4
### DATACOLLECTION.ARRAY, FULL ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL_|_F
001 | 129 | ......2048 | ...NTFS | ..BS | ......2048 | ..25165824 | PRI | .
002 | 129 | ..25167871 | ...NTFS | .BBS | ......2048 | ..25165824 | PRI | .
003 | 129 | ..25167872 | ...NTFS | ..BS | ..25167872 | 3881859072 | PRI | .
004 | 129 | 3907026943 | ...NTFS | .BBS | ..25167872 | 3881859072 | PRI | .
005 | 129 | .........0 | ...NTFS | PTE1 | ......2048 | ..25165824 | PRI | .
006 | 129 | .........0 | ...NTFS | PTE2 | ..25167872 | 3881859072 | PRI | .
007 | 129 | ......2048 | ...NTFS | ..BS | ......2048 | ..25165824 | PRI | I
008 | 129 | ..25167871 | ...NTFS | .BBS | ......2048 | ..25165824 | PRI | I
009 | 129 | ..25167872 | ...NTFS | ..BS | ..25167872 | 3881859072 | PRI | I
010 | 129 | 3907026943 | ...NTFS | .BBS | ..25167872 | 3881859072 | PRI | I
129/364:38/LOG> DataCollection items found: 10 / 4
### DATACOLLECTION.ARRAY, CLEANED ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL
001 | 129 | ......2048 | ...NTFS | ..BS | ......2048 | ..25165824 | PRI
002 | 129 | ..25167871 | ...NTFS | .BBS | ......2048 | ..25165824 | PRI
003 | 129 | ..25167872 | ...NTFS | ..BS | ..25167872 | 3881859072 | PRI
004 | 129 | 3907026943 | ...NTFS | .BBS | ..25167872 | 3881859072 | PRI
005 | 129 | .........0 | ...NTFS | PTE1 | ......2048 | ..25165824 | PRI
006 | 129 | .........0 | ...NTFS | PTE2 | ..25167872 | 3881859072 | PRI
129/364:38/LOG> PartList items created: 2
### PARTLIST.ARRAY ###
SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_|__PL_|_C_|___R
001 | ...NTFS | ..5 | ..1 | ..2 | ..0 | ..5 | ..5 | ..5 | 3 | ..A
002 | ...NTFS | ..6 | ..3 | ..4 | ..0 | ..6 | ..6 | ..6 | 3 | ..A
### PARTLIST.ARRAY.INTERPRETED ###
SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R_|___A
001 | ...NTFS | ......2048 | ..25165824 | ..25167871 | PRI | ..A | ..V
002 | ...NTFS | ..25167872 | 3881859072 | 3907026943 | PRI | ..A | ..V
129/364:38/SST> SaveState requested for disk 1 (129)
129/364:38/WAS> AdmiSectors in use : 0+ 1+
129/364:39/SST> SaveState completed for disk 1 (129)
129/364:39/EXE> Analysis complete
129/364:42/LOG> RunTime: 364:42
129/364:42/LOG> ### CLOSE LOG ###
[/FONT]

Your help is much appreciated.

[Joep]

Hello,

Reboots, blue screens, it all has nothing to do with the MBR, partition tables or boot records, and in the log they al look fine. One thing that can sometimes explain these problems is the disk health, but I see you skipped that test. Only one thing we can help you determine: is the disk health ok, and for that you'd need to run the disk health report and you can run a read-only surface sacn and report your findings. If it ain't that then it's nothing we / DiskPatch can help you with, but my next step would be testing memory. For a memory tester you'd have to look somewhere else.

Chkdsk running may simply be explained by the PC being forcefully shut down each time.

[jimmie1978]

Thank you for responding quickly.

Regarding the disk health. When running the tests, I noticed that disk health automatically disabled itself. All other options were ticked apart from the disk health which gave me a coutionary sign. This happened in both tests that I ran.

This may seem like a stupid question, but is there a way of making sure that it runs?

[Tom]

Have you done this:
http://www.diydatarecovery.nl/dp_manual/guide_smartcheck.htm
And/or this:
http://www.diydatarecovery.nl/dp_manual/guide_surfacescan.htm