Welcome, Guest. Please login or register.
Did you miss your activation email?
June 19, 2019, 07:04:26 PM
Home Help Search Login Register
News:

+  DIY DataRecovery.nl Support forum
|-+  Support
| |-+  DiskPatch (Moderators: Tom, Joep)
| | |-+  Resized Vista partition w/gparted - now getting flashing cursor - log included
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Resized Vista partition w/gparted - now getting flashing cursor - log included  (Read 6962 times)
ymeaga1n
member

Posts: 3


« on: March 22, 2009, 07:08:10 AM »

Hello.

I have a dell laptop with a 160gb HD that is partitioned into dells various recovery, utility, os parts. I wanted to resize my c: to create a new partition I could install windows 7 on. Long story short, I couldn't use Vista's builtin resizing tool so I found an application called gparted. Without wasting too much time thinking how smart it was, I booted into gparted and resized the partition. After reboot I got a boring black screen with a flashing cursor.

While browsing around I found a fella's comment on (http://www.howtogeek.com/howto/windows-vista/using-gparted-to-resize-your-windows-vista-partition) that lead me to you guys. He's problem is a tad different but I believe solutions might be the same. His post is made on 3/18/09 at 2:19pm (pst). I've quoted it here and below that is my log. Unfortunately I can't get a health log because it's asking for an A: drive which I don't have.

I haven't purchased the software (yet) but if it's the solution to my problem then I will glady.

Quote
Hello, I'd like to share my experience with Vista partitioning. An attempt at this almost went wrong for me. I ended up with a black screen and a "Verifying dmi data pool" screen at bootup. But it got fixed eventually. Perhaps this information can help others.

I wanted to resize my 290 gig C-partition to a 150 gig one and add a few smaller partitions for data. I used Gparted 0.4.3 with the gui. I noticed it had the option "round to cylinders" ticked on as default. When you leave this on, it not only resizes the partition but also entirely -moves- it to align with a nearby cylinder. This could take hours, whereby just resizing could be done in seconds. Turn this option OFF.
When I rebooted, I was meeted with the "Verifying dmi data pool" message. I tried the Vista Recovery disc's repair function, and it found a new partition, but after rebooting it stayed at the black screen and blinking cursor. Another go at the repair function had it scanning the partition without finding any error at all. Still after rebooting it stayed at this black screen of death. Terror! I tried to open the command console and enter commands like bootrec /fixmbr and /fixboot and reset the BCD (Boot Configuration Data) with the bcdedit command, but there was something else going on. After alot of research, I used the excellent Diskpatch program to make a log of the harddisk properties. It showed that the bootsector of every partition had matching values for the startsector of the partition and for another value in the bootsector known as the "hidden sectors" (at offset 0?1C in every partition's bootsector, readable in decimal values with Diskpatch). Only the Vista partition had different values. The startsector read 16787925 but hidden sectors read 16789504. I edited this last value to match with the startsector value and rebooted and behold, Vista came back to life! I only had to assing some driveletters to the new partitions and Vista lived happily.

What happened, apparently, after resizing and moving the partition, this "hidden sectors" value was not updated to match the new startsector value. This made Vista unbootable. This could have been avoided if I had turned OFF the "round to cylinders" option in Gparted, because that is what made the partition slide to a new startsector. If you have just partitioned a drive in this manner an encountered this black screen, you could check if the "hidden sectors" value in your bootpartition is different than your bootpartition's startsector. This can be done with Diskpatch, and you can even e-mail the log to the author's service desk for analysis, but if you want to use the program to actually edit these values, you have to buy the program. But once you know the values are not matching, you could also use free software like "Roadkil's Boot Build" which is included on the UBCD4WIN livecd. This program shows you the values in the bootsector in -decimal- (a very important feature, otherwhise you would have to use a diskeditor to set the value in hex and in Little Endian (reversed byte order). So to sum up, it's definitely easier to just check Diskpatch' logfile to see if the "hidden sectors" differ from the startsector, and if so then use the UBCD4win livecd with Boot Build to set the "hidden sector" value to be the same as the startsector. Save (by using the "write to disk" - option), reboot and hopefully you will then have a deep breath of relief when Vista boots.
Regards,
G.R.
Sites: www.diydatarecovery.nl for Diskpatch, www.ubcd4win.com for Boot Build.

My Log
Code:
.../000:16/LOG> ### LOG START ###
.../000:16/LOG> DISKPATCH 3.5.200
.../000:16/LOG> (C) 2000-2008 DIY DataRecovery
.../000:16/LOG> Contact info: HTTP://www.DIYDataRecovery.nl
.../000:16/LOG> MemFree: 70Kb
.../000:16/LOG> CommandLineParms: /sup
.../000:16/LOG> LogDate: 03-21-2009
.../000:16/CFG> FilePath="1/C:\DPFILES\"
.../000:16/CFG> LogFilename="DP.LOG"
.../000:16/CFG> ReadRetries="32"
.../000:16/CFG> WriteRetries="32"
.../000:16/CFG> MaxReadErrors="32"
.../000:16/CFG> MaxWriteErrors="1"
.../000:16/CFG> LogEachReadError="1"
.../000:16/CFG> ReadDelay="0"
.../000:16/CFG> VfyFixedBadSect="1"
.../000:16/CFG> CleanAfterDOD="1"
.../000:16/CFG> DiskReset="1"
.../000:16/CFG> SectorSkip="1024"
.../000:16/CFG> AutoSaveState="1"
.../000:16/CFG> DumpFoundSectors="0"
.../000:16/CFG> FixFats="1"
.../000:16/CFG> MaxFatScan="51200"
.../000:16/CFG> MaxDataColEntries="256"
.../000:16/CFG> IgnoreF8FF="0"
.../000:16/CFG> DownSizeExt="1"
.../000:16/CFG> ScanSignature="55AA"
.../000:16/CFG> Rebuild="00"
.../000:16/13H> Ext13H installed test requested
.../000:16/13H> Disk found at 128
.../000:16/13H> Ext13H version: 2.1 / EDD-1.1
.../000:16/13H> Ext13H Support: Extended disk access functions
.../000:16/13H> Ext13H Support: Enhanced disk drive functions
.../000:16/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:16/13H> Drive Interface Info:
.../000:16/13H> Disk 128 X13H data : 16383/16/63 312581808/512
.../000:16/13H> Disk found at 129
.../000:16/13H> Ext13H version: 2.1 / EDD-1.1
.../000:16/13H> Ext13H Support: Extended disk access functions
.../000:16/13H> Ext13H Support: Enhanced disk drive functions
.../000:16/13H> Ext13H Flags: DMA boundary errors handled transparently
.../000:16/13H> Drive Interface Info:
.../000:16/13H> Disk 129 X13H data : 15308/16/32 7831552/512
.../000:16/13H> Ext13H tested ok
.../000:16/FDL> DiskList requested
.../000:16/FDL> Disk found at 128
.../000:16/FDL> Disk found at 129
### DISKLIST.ARRAY ###
__D_|________LBA_|___H_|__S_|__GB_|__GEO
128 | .312581808 | 255 | 63 | 149 | BIOS
129 | ...7831552 | 128 | 32 | ..3 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
..0 | .........0 | ..0 | .0 | ..0 | BIOS
.../000:17/IAS> AdmiSector found on disk 0 (128)
.../000:17/IAS> AdmiSector init complete for disk 1 (129)
.../000:17/EXE> Read/Write pattern test for disk 0 (128) successful
.../000:18/EXE> Read/Write pattern test for disk 1 (129) successful
.../000:18/WAS> AdmiSectors in use : 0+ 1+
.../000:18/KEY> DEMO/1
.../000:18/PFC> PQstuff signature not detected on disk 0 (128)
.../000:18/PFC> PQstuff signature not detected on disk 1 (129)
.../000:18/PFC> UDMA driver not loaded
.../000:18/PFC> Disk health 50-100
.../000:19/PFC> Partition State backup not found on disk 0 (128)
.../000:19/PFC> Partition State backup not found on disk 1 (129)
.../000:19/PFC> No Repair date found on disk 0 (128)
.../000:19/PFC> No Repair date found on disk 1 (129)
.../000:36/CSD> Start CheckDisk for disk 0 (128)
.../000:36/CSD> CheckDisk complete, ReadErrors 0
.../000:36/USD> Disk 0 (128) selected
.../000:36/GSC> No geo change detected for disk 0 (128)
.../000:36/WAS> AdmiSectors in use : 0+ 1+
128/000:36/USD> MBR for disk 0 (128)
128/000:36/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 00 00 00 F8 00 00 00 01  |  m....bz?...?....
448   01 00 DE FE 3F 05 3F 00 00 00 47 78 01 00 00 1E  |  ..???.?...Gx....
464   19 06 07 FE FF FF 00 80 01 00 00 00 40 01 80 FE  |  ...?...?....@.??
480   FF FF 07 FE FF FF 20 9D 41 01 AA C6 80 0E 00 FE  |  ...?.. ?A.??..?
496   FF FF 0F FE FF FF 00 90 51 12 00 00 50 00 55 AA  |  ...?...?Q...P.U?
###
128/000:37/VEC> Start Verify EPBR Chain for disk 0 (128)
128/000:37/VEC> Listing current partitions on disk:
128/000:37/VEC>  UNKNOWN (P)  DellUtility          63       96327       (0 Gb)
128/000:37/VEC>     NTFS (P)     RECOVERY       98304    20971520      (10 Gb)
128/000:37/VEC>     NTFS (P)           OS    21077280   243320490     (116 Gb)
128/000:37/VEC>  UNKNOWN (L)  DellMD3play   307337216     5240832       (2 Gb)
128/000:37/VEC> Extended starts at 307335168 (19130 186 1)
128/000:37/VEC> Partition Table info for sector 0 (0 0 1)
128/000:37/LOG> PartListDump requested at 0 (0 0 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..DE | ....0...1...1 | ....5.254..63 | ........63 | .....96327
..2 ...0 | ..07 | ....6..30..25 | .1023.254..63 | .....98304 | ..20971520
..3 .128 | ..07 | .1023.254..63 | .1023.254..63 | ..21077280 | .243320490
..4 ...0 | ..0F | .1023.254..63 | .1023.254..63 | .307335168 | ...5242880
128/000:37/VEC> 55AA sig Ok
128/000:37/VEC> Partition Table info for sector 307335168 (19130 186 1)
128/000:37/LOG> PartListDump requested at 307335168 (19130 186 1)
### _ACT_|_TYPE_|__START--C/H/S_|__END----C/H/S_|__LBA-start_|_LBA-length
..1 ...0 | ..DD | .1023.254..63 | .1023.254..63 | ......2048 | ...5240832
..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
128/000:37/VEC> 55AA sig Ok
128/000:37/LOG> Boot sector dump requested at 63 (0 1 1)
### BootSectorDump for BStype FAT16
...........Jump Code (hex): EB5490
............OEM Name (txt): Dell 8.0
....Bytes per Sector (dec): 512
.Sectors per Cluster (dec): 4
....Reserved Sectors (dec): 1
...........FAT count (dec): 2
....Root Entry Count (dec): 512
..Total Sectors (16) (dec): 0
....Media Descriptor (hex): F8
.......FAT Size (16) (dec): 94
...Sectors per Track (dec): 63
.....Heads per Track (dec): 255
......Hidden Sectors (dec): 63
..Total Sectors (32) (dec): 96327
........Drive Number (hex): 80
............Reserved (hex): 00
......Boot Signature (hex): 29
...........Volume ID (hex): 07D80605
........Volume Label (txt): DellUtility
..Filesystem Type ID (txt): FAT16
....Sector Signature (hex): AA55
..........1st FAT at      : 64 (0 1 2)
..........2nd FAT at      : 158 (0 2 33)
128/000:37/CF8> FAT sectors are equal
128/000:37/LOG> SectorDump requested at 252 (0 4 1)
###
     COMMAND COM DELLBIO BIN DELLRMK BIN AUTOEXECUP 
     CONFIG  UP  COPYUP  BAT DELLDIAGINI DIAGS       
     HIMEM   SYS AUTOEXECBAT CONFIG  SYS DELL       
     SETMD3  BAT SEAL    EXE OOBEDONEFLG ...........
###
128/000:37/LOG> Boot sector dump requested at 98304 (6 30 25)
### 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): 98304
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 20971519
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 1310719
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 6052BDF452BDCED2
........Volume Label (txt): RECOVERY
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/000:37/VEC> BS and BBS equal
128/000:37/LOG> Boot sector dump requested at 21077280 (1312 0 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): 21069824
..............Unused (hex): 00000000
.............Unknown (hex): 00800080
.......Total Sectors (dec): 243320480
........MFT Location (dec): 786432
.MFT Mirror Location (dec): 18219263
....Clusters per FRS (dec): 246
.Clusters/Indx Block (dec): 1
...........Volume ID (hex): 08CAC08CCAC07788
........Volume Label (txt): OS
............Checksum (hex): 00000000
....Sector Signature (hex): AA55
128/000:37/VEC> BS and BBS equal
128/000:37/VEC> Verify EPBR Chain completed
128/000:37/USD> Select disk completed
128/000:44/SCN> DiskScan requested, ScanType is 3
128/000:44/SCN> from 0 (0 0 1) to 312581807 (19457 80 63), 312581808 sectors
128/000:44/SCN> Starting QuickScan (vista) at 2048 (0 32 33)
128/000:44/CDC> No DataCollection entries, CleanDatacollection aborted
128/000:44/MPL> No DataCollection entries, MakePartList aborted
128/000:44/SCN> Next QuickScan location at 0 (0 0 1)
128/000:45/SCN> QuickScan finished
128/000:45/SCN> Starting SmartScan (vista) at 0 (0 0 1)
128/000:45/RDS> Read past EOD intercept for disk 128 at 4294967295 (267349 89 4)
128/021:14/SCN> SmartScan finished
128/021:14/SCN> DiskScan completed
128/021:14/SCN> ReadErrors for disk 0 (128): 0
128/023:15/LOG> DataCollection items found: 9 / 0
### DATACOLLECTION.ARRAY, FULL ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL_|_F
001 | 128 | .........0 | ...NTFS | PTE2 | .....98304 | ..20971520 | PRI | .
002 | 128 | .........0 | ...NTFS | PTE3 | ..21077280 | .243320490 | PRI | .
003 | 128 | .........0 | ....EXT | PTE4 | .307335168 | ...5242880 | PRI | .
004 | 128 | .....98304 | ...NTFS | ..BS | .....98304 | ..20971520 | PRI | .
005 | 128 | ..21069823 | ...NTFS | .BBS | .....98304 | ..20971520 | PRI | .
006 | 128 | ..21069824 | ...NTFS | ..BS | ..21069824 | .243320481 | PRI | .
007 | 128 | .257353727 | ...NTFS | .BBS | .225882456 | ..31471272 | PRI | .
008 | 128 | .307337216 | ..FAT32 | ..BS | .307337216 | ...5240832 | PRI | .
009 | 128 | .307337222 | ..FAT32 | .BBS | .307337216 | ...5240832 | LOG | .
128/023:15/LOG> DataCollection items found: 9 / 0
### DATACOLLECTION.ARRAY, CLEANED ###
SEQ_|___D_|________LOC_|____TYPE_|__COM_|______START_|_____LENGTH_|__PL
001 | 128 | .........0 | ...NTFS | PTE2 | .....98304 | ..20971520 | PRI
002 | 128 | .........0 | ...NTFS | PTE3 | ..21077280 | .243320490 | PRI
003 | 128 | .........0 | ....EXT | PTE4 | .307335168 | ...5242880 | PRI
004 | 128 | .....98304 | ...NTFS | ..BS | .....98304 | ..20971520 | PRI
005 | 128 | ..21069823 | ...NTFS | .BBS | .....98304 | ..20971520 | PRI
006 | 128 | ..21069824 | ...NTFS | ..BS | ..21069824 | .243320481 | PRI
007 | 128 | .257353727 | ...NTFS | .BBS | .225882456 | ..31471272 | PRI
008 | 128 | .307337216 | ..FAT32 | ..BS | .307337216 | ...5240832 | PRI
009 | 128 | .307337222 | ..FAT32 | .BBS | .307337216 | ...5240832 | LOG
128/023:15/LOG> PartList items created: 6
### PARTLIST.ARRAY ###
SEQ_|____TYPE_|_PTE_|__BS_|_BBS_|F8FF_|___S_|___L_|__PL_|_C_|___R
001 | ...NTFS | ..1 | ..4 | ..5 | ..0 | ..1 | ..1 | ..1 | 3 | ..A
002 | ...NTFS | ... | ..6 | ... | ..0 | ..6 | ..6 | ..6 | 1 | ..B
003 | ...NTFS | ..2 | ... | ... | ..0 | ..2 | ..2 | ..2 | 1 | ...
004 | ...NTFS | ... | ... | ..7 | ..0 | ..7 | ..7 | ..7 | 1 | ..B
005 | ..FAT32 | ... | ..8 | ... | ... | ..8 | ..8 | ..8 | 1 | ...
006 | ..FAT32 | ... | ... | ..9 | ... | ..9 | ..9 | ..9 | 1 | ...
### PARTLIST.ARRAY.INTERPRETED ###
SEQ_|____TYPE_|______START_|_____LENGTH_|________END_|__PL_|___R_|___A
001 | ...NTFS | .....98304 | ..20971520 | ..21069823 | PRI | ..A | ..V
002 | ...NTFS | ..21069824 | .243320481 | .264390304 | PRI | ..B | ..V
003 | ...NTFS | ..21077280 | .243320490 | .264397769 | PRI | ... | ..X
004 | ...NTFS | .225882456 | ..31471272 | .257353727 | PRI | ..B | ..?
005 | ..FAT32 | .307337216 | ...5240832 | .312578047 | PRI | ... | ..V
006 | ..FAT32 | .307337216 | ...5240832 | .312578047 | LOG | ... | ..V
128/023:15/SST> SaveState requested for disk 0 (128)
128/023:15/WAS> AdmiSectors in use : 0+ 1+
128/023:15/SST> SaveState completed for disk 0 (128)
128/023:15/EXE> Analysis complete
128/023:18/LOG> RunTime: 023:18
128/023:18/LOG> ### CLOSE LOG ###
Logged
Joep
Developer and Support Tech
Administrator
member
*****
Posts: 1476



WWW
« Reply #1 on: March 23, 2009, 08:46:56 AM »

Hello,

Current layout appears to be an original as shipped by Dell nowadays. Well, indeed 'his' and your story appear to be descibing the same issue. Hidden sectors in that 3rd partitions does not correspond with the actual amount of hidden sectors. It *is* 21077280 while the boot sector incorrectly says 21069824.

I can't give guarantees but it worked for that guy. So you can edit that with the registered version, and see if that resolves it. If not then please create and post a new log, and if we can't solve it using DiskPatch you can always request a refund.
Logged

--
Kind regards,
Joep - My blog @: www.disktuna.com - Try my JPEG Repair Tool: https://youtu.be/Ox2F8QRuU5Q
ymeaga1n
member

Posts: 3


« Reply #2 on: March 23, 2009, 07:27:00 PM »

Okay now the problem of adjust the hidden sector value problem. Can I do this using the "Perform repairs" function or do I do it using the hex/dec editor?

Could you point me in the right direction on how to use the hex editor, if that's what I must use.
Logged
ymeaga1n
member

Posts: 3


« Reply #3 on: March 23, 2009, 07:38:25 PM »

Nm I figured out how to fix it using these instructions.

http://www.diydatarecovery.nl/dp_manual/guide_ntfsbsrepair.htm

For those interested:

I selected Perform Repair > Rebuild Boot Sector > Display and Edit Boo sector, and then manually changed the value of the "hidden sector" by pressing F10.

Just rebooted computer and it is working fine! Thanks much for all your help.

My only complaint was that promo price for diskpatch that was running last week wasn't running this week Sad.
Logged
Tom
Developer and Support Tech
Administrator
member
*****
Posts: 1476


WWW
« Reply #4 on: March 24, 2009, 10:03:26 AM »

Ok, well done. Just so you know, DiskPatch would have also been able to fix that value automatically when running a boot sector repair. But yes, if you know what you're doing then your way is much quicker.

Quote
My only complaint was that promo price for diskpatch that was running last week wasn't running this week
Yes, i understand that may seem a tad unfair, that but these promo things change regularly. i'm sorry you missed the previous one.
Logged

Pages: [1] 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.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!