Need findpart help

[Phoenix]

I need help with findpart, below is a listing of findpart results. I am
seeking to restore disk 1 to two partitions, and disk 2 to 1 partition with
correct usage of approx 9M. Had a power surge while loading operating
system. Any help greatly appreciated.

Thanks in advance,




Findpart, version 4.36.
Copyright Svend Olaf Mikkelsen, 2003.

Searches for partitions type 01, 04, 06, 07, 0B, 0C, 0E, 82, 83,
plus Fdisk F6 and Lilo sectors. Information based on bootsectors
is marked B. If the disk is larger than supported by BIOS, the
supported part of the disk is examined. Disks are numbered from 1.

OS: DOS 7.10 All

Disk: 1 Cylinders: 1247 Heads: 255 Sectors: 63 MB: 9782

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0B 63 10024497 4894 0 1 1 623 254 63 B OK
624 1 0B 63 10008432 4886 624 1 1 1246*254 63 OK OK
0 - 07 63 20032992 9781 0 1 1 1246 254 63 BU OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 35 9771 4 2 9771 0 0 0 030817 2096
624 1 33 9756 4 2 9756 0 0 0 030817 112

Partitions according to partition tables on first harddisk:

None.

Disk: 2 Cylinders: 2434 Heads: 255 Sectors: 63 MB: 19093

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0+- 01 1 20739 10 0 1 1 1 75 12 B OK
0 - 0C 63 39102147 19092 0 1 1 2433 254 63 BU OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 9542 16# 2# 9542 0 0 0 010921 9448

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0C 63 39102147 19092 0 1 1 2433*254 63 NB OK

 

[Phoenix]

Update: Disk 1 is now OK and all partitions are working fine. Disk 2 is also
visible, but the disk information under XP displays a single partition disk
that is 10.1MB. Disk 2 is actually 20G.

I do not know enough about partition tables to correct this problem. Any
help will greatly be appreciated.

Thanks

 

[Geert Vancompernolle]

There's actually (almost) one guy who can help you in this matter:
Svend himself.

I've experienced something similar last Saturday (having problems
during startup while PM was resizing and moving partitions) and the
way he helped me through to get back all my precious data is really
unbelievable! He was even willing to work on his Sunday to help me
out of this problem!

Trying to figure out yourself what it all means is almost not doable.
His analyzing programs are also very powerful. However, you have to
know how to use them!

If you want to play sure, don't mess it up yourself and ask if he's
willing to help you (which I don't doubt...).

In the Google newsgroups, search for his name and you will find lots
of triggers, meaning he's very willing to help people!

HTH.

 

[Phoenix]

Can anyone provide me with a solution that will restore my MBR to the "BU"
line below? I used findpart to generate the output below and I am convinced
that the second FAT is what I need to repair the hard disk and make my data
accessible. Any help will be appreciated.



Thanks in advance,



============================================================================
================



Findpart, version 4.36.
Copyright Svend Olaf Mikkelsen, 2003.

Searches for partitions type 01, 04, 06, 07, 0B, 0C, 0E, 82, 83,
plus Fdisk F6 and Lilo sectors. Information based on bootsectors
is marked B. If the disk is larger than supported by BIOS, the
supported part of the disk is examined. Disks are numbered from 1.

OS: DOS 7.10 All



Disk: 2 Cylinders: 2434 Heads: 255 Sectors: 63 MB: 19093



-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS

0+- 01 1 20739 10 0 1 1 1 75 12 B OK

0 - 0C 63 39102147 19092 0 1 1 2433 254 63 BU OK



-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB

0 1 33 9542 16# 2# 9542 0 0 0 010921 9448



Partitions according to partition tables on second harddisk:



-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS

0 1*0C 63 39102147 19092 0 1 1 2433*254 63 NB OK

 

[Folkert Rienstra]

There's actually (almost) one guy who can help you in this matter:

Findpart that is.
With PowerQuest's PartInfo other people may be able to help.

Svend himself.

So why not use his email address: (e-mail address removed)2.dk

I've experienced something similar last Saturday (having problems
during startup while PM was resizing and moving partitions) and the
way he helped me through to get back all my precious data is really
unbelievable! He was even willing to work on his Sunday to help me
out of this problem!

Trying to figure out yourself what it all means is almost not doable.

Well, there is a little help on the webpage:
http://inet.uni2.dk/~svolaf/partitionnotes.htm

 

[Phoenix]

Partition Information Program

Oct 09 2000 - DOS32 Version

Copyright (c) 1994-2000, PowerQuest Corporation

Permission is granted for this utility to be freely copied so long

as it is not modified in any way. All other rights are reserved.



PowerQuest, makers of PartitionMagic(r), Drive Image(tm) and DriveCopy(tm),
can be reached at

Voice: 801-226-6834 Web site: http://support.powerquest.com

Fax: 801-226-8941 Email: (e-mail address removed)





=====================================================================


Disk 1: 1247 Cylinders, 255 Heads, 63 Sectors/Track.


The BIOS supports INT 13h extensions for this drive.


========================== Partition Tables =========================


Partition -----Begin---- ------End----- Start Num


Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects


--------- - ---- ---- ---- ---- -- ---- ---- ---- --------- ---------


0 0 80 0 1 1 0B 623 254 63 63 10024497


0 1 00 624 0 1 0F 1022 254 63 10024560 10008495


Info: Begin C,H,S values were large drive placeholders.


Info: End C,H,S values were large drive placeholders.


Actual values are:


0 1 00 624 0 1 0F 1246 254 63 10024560 10008495


10024560 0 00 624 1 1 0B 1023 254 63 10024623 10008432


Info: End C,H,S values were large drive placeholders.


Actual values are:


10024560 0 00 624 1 1 0B 1246 254 63 10024623 10008432






=====================================================================


Disk 2: 2434 Cylinders, 255 Heads, 63 Sectors/Track.


The BIOS supports INT 13h extensions for this drive.


========================== Partition Tables =========================


Partition -----Begin---- ------End----- Start Num


Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects


--------- - ---- ---- ---- ---- -- ---- ---- ---- --------- ---------


0 0 80 0 1 1 0C 1023 254 63 63 39102147


Info: Begin C,H,S values were large drive placeholders.


Info: End C,H,S values were large drive placeholders.


Actual values are:


0 0 80 0 1 1 0C 2433 254 63 63 39102147




============================================================================
==

Disk 1: 9781.8 Megabytes

============================ Partition Information
===========================

Volume Partition Partition Start
Total

Letter:Label Type Status Size MB Sector # Sector
Sectors

------------- --------------- -------- ------- --------- - --------- -------
--

C:NO NAME FAT32 Pri,Boot 4894.8 0 0 63
10024497


ExtendedX Pri 4886.10 0 1 10024560
10008495


EPBR Log 4886.10 None - 10024560
10008495


E:NHO_C_2 FAT32 Log 4886.9 10024560 0 10024623
10008432




============================================================================
==

Disk 2: 19092.9 Megabytes

============================ Partition Information
===========================

Volume Partition Partition Start
Total

Letter:Label Type Status Size MB Sector # Sector
Sectors

------------- --------------- -------- ------- --------- - --------- -------
--

D?¸ FAT32X Pri,Boot 19092.8 0 0 63
39102147






========================================================================


Boot Sector for drive C: (Drive 1, Starting Sector: 63, Type: FAT32


========================================================================


1. Jump: EB 58 90


2. OEM Name: MSDOS5.0


3. Bytes Per Sector: 512


4. Sectors Per Cluster: 8


5. Reserved Sectors: 34


6. Number of FAT's: 2


7. Reserved: 0x0000


8. Reserved: 0x0000


9. Media Descriptor: 0xF8


10. Sectors Per FAT: 0


11. Sectors Per Track: 63 (0x3F)


12. Number of Heads: 255 (0xFF)


13. Hidden Sectors: 63 (0x3F)


14. Big Total Sectors: 10024497 (0x98F631)


15. Big Sectors Per FAT: 9771


16. Extended Flags: 0x0000


17. FS Version: 0


18. First Cluster of Root: 2 (0x2)


19. FS Info Sector: 1


20. Backup Boot Sector: 6


21. Reserved: 000000000000000000000000


22. Drive ID: 0x80


23. Reserved for NT: 0x00


24. Extended Boot Sig: 0x29


25. Serial Number: 0xB0B7498A


26. Volume Name: NO NAME


27. File System Type: FAT32


28. Boot Signature: 0xAA55










========================================================================


Boot Sector for drive E: (Drive 1, Starting Sector: 10024623, Type: FAT32


========================================================================


1. Jump: EB 3C 90


2. OEM Name: MSWIN4.1


3. Bytes Per Sector: 512


4. Sectors Per Cluster: 8


5. Reserved Sectors: 32


6. Number of FAT's: 2


7. Reserved: 0x0000


8. Reserved: 0x0000


9. Media Descriptor: 0xF8


10. Sectors Per FAT: 0


11. Sectors Per Track: 63 (0x3F)


12. Number of Heads: 255 (0xFF)


13. Hidden Sectors: 63 (0x3F)


14. Big Total Sectors: 10008432 (0x98B770)


15. Big Sectors Per FAT: 9756


16. Extended Flags: 0x0000


17. FS Version: 0


18. First Cluster of Root: 2 (0x2)


19. FS Info Sector: 1


20. Backup Boot Sector: 6


21. Reserved: F6F6F6F6F6F6F6F6F6F6F6F6


22. Drive ID: 0x80


23. Reserved for NT: 0x00


24. Extended Boot Sig: 0x29


25. Serial Number: 0x7E7E99A2


26. Volume Name: NHO_C_2


27. File System Type: FAT32


28. Boot Signature: 0xAA55










========================================================================


Boot Sector for drive D: (Drive 2, Starting Sector: 63, Type: FAT32


========================================================================


1. Jump: EB 3C 90


2. OEM Name: MSDOS5.0


3. Bytes Per Sector: 512


4. Sectors Per Cluster: 8


5. Reserved Sectors: 1


6. Number of FAT's: 2


7. Reserved: 0x0200


8. Reserved: 0x5103


9. Media Descriptor: 0xF8


10. Sectors Per FAT: 8


11. Sectors Per Track: 17 (0x11)


12. Number of Heads: 4 (0x4)


13. Hidden Sectors: 1 (0x1)


14. Big Total Sectors: 0 (0x0)


15. Big Sectors Per FAT: 2687104


16. Extended Flags: 0x0000


17. FS Version: 19968


18. First Cluster of Root: 1095639119 (0x414E204F)


19. FS Info Sector: 17741


20. Backup Boot Sector: 8224


21. Reserved: 2020464154313220202033C9


22. Drive ID: 0x8E


23. Reserved for NT: 0xD1


24. Extended Boot Sig: 0xBC


25. Serial Number: 0xD98E7BF0


26. Volume Name: ¸ ?Àü½|8N


27. File System Type: $}$<


28. Boot Signature: 0xAA55

 

[Phoenix]

I hope the news message did not doublespace, it appeared textual correct
when I posted. Here it is again with only Disk 2 info. It is clear to me
that the end cyl info must be "2433" before I can see the entire disk. I do
not understand why item 11 reports "17", perhaps its the corruption of the
MBR.

If the MBR is set to zeros what restores it?

Thanks,

=====================================================================
Disk 2: 2434 Cylinders, 255 Heads, 63 Sectors/Track.
The BIOS supports INT 13h extensions for this drive.
========================== Partition Tables =========================
Partition -----Begin---- ------End----- Start Num
Sector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects
--------- - ---- ---- ---- ---- -- ---- ---- ---- --------- ---------
0 0 80 0 1 1 0C 1023 254 63 63 39102147
Info: Begin C,H,S values were large drive placeholders.
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 0 80 0 1 1 0C 2433 254 63 63 39102147

======================================================================
Disk 2: 19092.9 Megabytes
============================ Partition Information
===========================
Volume Partition Partition Start
Total
Letter:Label Type Status Size MB Sector # Sector
Sectors
------------- --------------- -------- ------- --------- - --------- -------
--
D?¸ FAT32X Pri,Boot 19092.8 0 0 63
39102147

========================================================================
Boot Sector for drive D: (Drive 2, Starting Sector: 63, Type: FAT32
========================================================================
1. Jump: EB 3C 90
2. OEM Name: MSDOS5.0
3. Bytes Per Sector: 512
4. Sectors Per Cluster: 8
5. Reserved Sectors: 1
6. Number of FAT's: 2
7. Reserved: 0x0200
8. Reserved: 0x5103
9. Media Descriptor: 0xF8
10. Sectors Per FAT: 8
11. Sectors Per Track: 17 (0x11)
12. Number of Heads: 4 (0x4)
13. Hidden Sectors: 1 (0x1)
14. Big Total Sectors: 0 (0x0)
15. Big Sectors Per FAT: 2687104
16. Extended Flags: 0x0000
17. FS Version: 19968
18. First Cluster of Root: 1095639119 (0x414E204F)
19. FS Info Sector: 17741
20. Backup Boot Sector: 8224
21. Reserved: 2020464154313220202033C9
22. Drive ID: 0x8E
23. Reserved for NT: 0xD1
24. Extended Boot Sig: 0xBC
25. Serial Number: 0xD98E7BF0
26. Volume Name: ¸ ŽÀü½|8N
27. File System Type: $}$<

28. Boot Signature: 0xAA55

 

[Folkert Rienstra]

Can anyone provide me with a solution that will restore my MBR to the
"BU" line below?

The 'BU' says your bootsector is missing or bad, probably by something
that caused Findpart to also find the false partition with ID 01.

The # after Root size/Cluster number in FAT output indicate that
your backup boot sector may not be correct either but that could
also be a flaw in Findpart because of that missing original bootsector.

That appears to be your problem, not the FAT(s), that appear to be correct.

 

[Phoenix]

How do I recover/repair the MBR?

Thanks for your response

 

[Svend Olaf Mikkelsen]

Findpart, version 4.36.
Copyright Svend Olaf Mikkelsen, 2003.

OS: DOS 7.10 All

Disk: 1 Cylinders: 1247 Heads: 255 Sectors: 63 MB: 9782

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0B 63 10024497 4894 0 1 1 623 254 63 B OK
624 1 0B 63 10008432 4886 624 1 1 1246*254 63 OK OK
0 - 07 63 20032992 9781 0 1 1 1246 254 63 BU OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 35 9771 4 2 9771 0 0 0 030817 2096
624 1 33 9756 4 2 9756 0 0 0 030817 112

Partitions according to partition tables on first harddisk:

None.

Disk: 2 Cylinders: 2434 Heads: 255 Sectors: 63 MB: 19093

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0+- 01 1 20739 10 0 1 1 1 75 12 B OK
0 - 0C 63 39102147 19092 0 1 1 2433 254 63 BU OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 9542 16# 2# 9542 0 0 0 010921 9448

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0C 63 39102147 19092 0 1 1 2433*254 63 NB OK

The commands to make partition table entries for the primary and
extended partition on disk 1, and to copy the backup boot sector of
the primary partition on disk 2 to the boot sector are:

findpart getsect 2 0 1 1 1 fp2-8a.bin noheader
findpart getsect 2 0 1 7 1 fp2-8b.bin noheader
set findpart=edit
findpart 1 0 1 * 0B 0 1 1 623 254 63 0 1247 255 63 26
findpart 1 0 2 - 0F 624 0 1 1246 254 63 0 1247 255 63 26
findpart putsect 2 0 1 1 fp2-8b.bin 2434 00000000 checkfile fp2-8a.bin
set findpart=
findpart all fp1-8.txt


The commands are available as phoenix8.bat in

http://inet.uni2.dk/~svolaf/phoenix8.zip

Do not attempt to boot the system from harddisk until it is verified
from pure DOS that the partitions are OK.

You have the option to insert the content from fp1-8.txt here for
confirmation.

It is assumed that nothing was changed since Findpart was run.

 

[Phoenix]

Findpart, version 4.36.
Copyright Svend Olaf Mikkelsen, 2003.

Searches for partitions type 01, 04, 06, 07, 0B, 0C, 0E, 82, 83,
plus Fdisk F6 and Lilo sectors. Information based on bootsectors
is marked B. If the disk is larger than supported by BIOS, the
supported part of the disk is examined. Disks are numbered from 1.

OS: DOS 7.10 All

Disk: 1 Cylinders: 1247 Heads: 255 Sectors: 63 MB: 9782

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0B 63 10024497 4894 0 1 1 623 254 63 B OK
624 1 0B 63 10008432 4886 624 1 1 1246*254 63 OK OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 35 9771 4 2 9771 0 0 0 030817 2192
624 1 33 9756 4 2 9756 0 0 0 030817 2382

Partitions according to partition tables on first harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0B 63 10024497 4894 0 1 1 623 254 63 OK OK
0 2 0F 10024560 10008495 4886 624 0 1 1246*254 63 OK

624 1 0B 63 10008432 4886 624 1 1 1246*254 63 OK OK

Disk: 2 Cylinders: 2434 Heads: 255 Sectors: 63 MB: 19093

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63 39102147 19092 0 1 1 2433 254 63 B OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 9542 16 2 9509 0 5 28 010921 9448

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0B 63 39102147 19092 0 1 1 2433*254 63 NB OK

 

[Phoenix]

I checked the HDD in pure DOS and all looks well. Then I started the XP OS
no complaints. THANKS!

You are a life saver!

Thanks again,

 

[Zvi Netiv]

How do I recover/repair the MBR?

Folkert told you that the BOOT SECTOR, is missing or bad. Not to confuse with
the MBR - these are different sectors, and both are critical.

You can wait for Svend's reply, or you could try RESQDISK.

If the latter, then download RESQ from http://resq.co.il/resq.php, make the RESQ
boot floppy by running the download file and following its instruction, boot
from the floppy, and run from the A: prompt RESQDISK /ASSESS.

Post here the RESQDISK.RPT report that will be created on the floppy (leave it
write enabled) and we'll take it from there.

Regards, Zvi

 

[Svend Olaf Mikkelsen]

OS: DOS 7.10 All

Disk: 2 Cylinders: 2434 Heads: 255 Sectors: 63 MB: 19093

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63 39102147 19092 0 1 1 2433 254 63 B OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 9542 16 2 9509 0 5 28 010921 9448

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0B 63 39102147 19092 0 1 1 2433*254 63 NB OK

I said:

"It is assumed that nothing was changed since Findpart was run."

Originally we had:

Disk: 2 Cylinders: 2434 Heads: 255 Sectors: 63 MB: 19093

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0+- 01 1 20739 10 0 1 1 1 75 12 B OK
0 - 0C 63 39102147 19092 0 1 1 2433 254 63 BU OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 9542 16# 2# 9542 0 0 0 010921 9448

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0C 63 39102147 19092 0 1 1 2433*254 63 NB OK

Meaning that the partition table was changed since Findpart was run
first time, and that the FAT was damaged since Findpart was run first
time.

The partition table error may not be important for Windows XP.

Windows XP may have repaired the FAT again.

I assume you are now in Windows XP. To examine this, you can do:

findpart 2 fp-a.txt

and insert the output here.

I suggest that you do not access the partition on disk 2 until it is
known that the partition is OK.

 

[Svend Olaf Mikkelsen]

I assume you are now in Windows XP. To examine this, you can do:

findpart 2 fp-a.txt

and insert the output here.

PS.

Using Findpart for Windows in Windows XP.

 

[Folkert Rienstra]

The 'BU' says your bootsector is missing or bad, probably by something
that caused Findpart to also find the false partition with ID 01.

The # after Root size/Cluster number in FAT output indicate that
your backup boot sector may not be correct either but that could
also be a flaw in Findpart because of that missing original bootsector.

So Svend, does the # in this case mean that the backup bootsec-
tor may be OK because (apparently) it is not checked by FindPart
even though the (original) bootsector is found to be flawed?
Shouldn't FindPart also check the backup bootsector in such case?

 

[Svend Olaf Mikkelsen]

So Svend, does the # in this case mean that the backup bootsec-
tor may be OK because (apparently) it is not checked by FindPart
even though the (original) bootsector is found to be flawed?
Shouldn't FindPart also check the backup bootsector in such case?

The "#" only refers to the boot sector. (Cluster size and root cluster
not confirmed in boot sector).

The backup boot sector probably is OK, but it is not confirmed.

Of course it could be done, but on the other hand it will be better to
check the partition integrity before the backup boot sector is copied
to the boot sector.

One method which can be used to verify if the partition is OK using
the backup boot sector, is this example:

chsdir 2 0 1 1 backupbootsector

I recently made a Chsdir version with this, but it may not be online
yet. Before that, if I would check the backup boot sector, I retrieved
it to a file, and looked at it manually.