Hish Posted January 15, 2006 Posted January 15, 2006 (edited) 2 days ago I opened my computer to put in my other 40GB harddisk. It all went as planned until i first opened the computer and booted it using Partition Magic 8.0. Then this thing appeared and said like: "Cylinder range in harddrive unconsistent. Do you want Partition Magic to fix it?" Usually i thought well, this is Partition Magic, a reliable program, so I pressed Yes. Then in Partition Magic i saw that my original harddisk with all my stuff in it, was currupt. It said, "Partition Table Error #110" So I panicked and rebooted the computer. Then i got this message saying, "Media cable faliure, check cable" or something. Then I really got scared. I then went into my other computer and read about this error ("Partition Table Error #110"). It seemed that it was something called a partition table, and that the values in it were wrong. After alot of researching, i found out there was a program in the partition magic boot disk that could edit the partition tables. I opened up ptedit.exe and i didnt understand a thing.Later i did this. There is a program called partinfo, it tells you whats wrong and what the values should be. So i started the program but i couldnt read it because there was much information and i couldnt scroll up in DOS. So i did this: "A:\> partinfo.exe > partinfo.txt". Then i had the information in the txt document. The problem was that i couldnt read it cause i didnt have the edit.com program. And my other computer doesnt have floppy drive. So i took the disk to school and put in edit.com. I also took out this document. Partition Information ProgramSep 16 2002 - DOS32 VersionCopyright © 1994-2002, PowerQuest CorporationPermission is granted for this utility to be freely copied so longas it is not modified in any way. All other rights are reserved.PowerQuest, makers of PartitionMagic®, Drive Image and DriveCopy, can be reached at Voice: 801-226-6834 Web site: http://www.powerquest.com/support/ Fax: 801-226-8941 Email: help@powerquest.comBiosExtensions: 0x2100 Subsets (0x00000005): Access EDDEGeo 0x0000 0 0 0 78165360 0 512============================================================================Disk 0: 4865 Cylinders, 255 Heads, 63 Sectors/Track.BiosExtensions: 0x2100 Subsets (0x00000005): Access EDDThe BIOS supports INT 13h extensions for this drive.============================ Partition Tables ==============================Partition -----Begin---- ------End----- Start NumSector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects---------- - ---- ---- ---- ---- -- ---- ---- ---- ---------- ---------- 0 3 80 [ 0 1 1] 0F [1023 254 63] 63 92630727 [Large Drive Placeholders] 0 1 1 5765 254 63 Actual ValuesError #109: Partition ends after end of disk. ucEndCylinder (5765) must be less than 4865.Warning: The OS reported too few cylinders. 4865 cylinders are present. 63 0 72 [ 256 97 36] 0D [ 370 10 20] 543908792 543450478 [Large Drive Placeholders] 33856 192 57 2148 250 60 Actual ValuesWarning: Partition boot flag expected to be 0x00 or 0x80, not 0x72. This should not be a problem.Error #107: Partition begins after end of disk. ucBeginCylinder (33856) must be less than 2149.Info: Partition didn't begin on head boundary.ucBeginHead expected to be 0 or 1, not 192.Info: Partition didn't begin on head boundary. ucBeginSector expected to be 1, not 57.Info: Partition didn't end on cylinder boundary. ucEndHead expected to be 254, not 250.Info: Partition didn't end on cylinder boundary. ucEndSector expected to be 63, not 60.Error #110: Number of sectors in partition is inconsistent. ucSectors = 543450478 end - begin = 3785581934 63 1 43 [ 370 10 21] 2B [ 371 65 44] 1818575978 1922328096 [Large Drive Placeholders] 47665 30 24 36252 129 47 Actual ValuesWarning: Partition boot flag expected to be 0x00 or 0x80, not 0x43. This should not be a problem.Error #107: Partition begins after end of disk. ucBeginCylinder (47665) must be less than 2149.Info: Partition didn't begin on head boundary.ucBeginHead expected to be 0 or 1, not 30.Info: Partition didn't begin on head boundary. ucBeginSector expected to be 1, not 24.Error #109: Partition ends after end of disk. ucEndCylinder (36252) must be less than 2149.Info: Partition didn't end on cylinder boundary. ucEndHead expected to be 254, not 129.Info: Partition didn't end on cylinder boundary. ucEndSector expected to be 63, not 47.Error #116: Starting sector of partition is inconsistent. ulStartSect = 1818575978 Begin C,H,S = 765740138Error #110: Number of sectors in partition is inconsistent. ucSectors = 1922328096 end - begin = 4111623712 63 2 20 [ 371 111 45] 74 [ 372 97 50] 167774796 0 [Large Drive Placeholders] 10443 127 1 10443 126 63 Actual ValuesWarning: Partition boot flag expected to be 0x00 or 0x80, not 0x20. This should not be a problem.Error #107: Partition begins after end of disk. ucBeginCylinder (10443) must be less than 2149.Info: Partition didn't begin on head boundary.ucBeginHead expected to be 0 or 1, not 127.Error #109: Partition ends after end of disk. ucEndCylinder (10443) must be less than 2149.Info: Partition didn't end on cylinder boundary. ucEndHead expected to be 254, not 126.Info: This partition unexpectedly contains no sectors.Disk[0], Part[63]: Warning #113: EPBR partition starting at 63 overlaps extended partition.Disk[0], Part[167774796]: Error #113: Logic starting at 167774796 overlaps extended partition.Disk[0], Part[167774796]: Info: Logical starting at 167774796 is not one head away from EPBR.Disk[0], Part[543908792]: Error #113: Logic starting at 543908792 overlaps extended partition.Disk[0], Part[543908792]: Info: Logical starting at 543908792 is not one head away from EPBR.Disk[0], Part[1818575978]: Error #113: Logic starting at 1818575978 overlaps extended partition.Disk[0], Part[1818575978]: Info: Logical starting at 1818575978 is not one head away from EPBR.BiosExtensions: 0x2100 Subsets (0x00000005): Access EDDEGeo 0x0000 0 0 0 80063424 0 512============================================================================Disk 1: 4983 Cylinders, 255 Heads, 63 Sectors/Track.BiosExtensions: 0x2100 Subsets (0x00000005): Access EDDThe BIOS supports INT 13h extensions for this drive.============================ Partition Tables ==============================Partition -----Begin---- ------End----- Start NumSector # Boot Cyl Head Sect FS Cyl Head Sect Sect Sects---------- - ---- ---- ---- ---- -- ---- ---- ---- ---------- ---------- 0 0 00 0 1 1 07 [1023 254 63] 63 80035767 [Large Drive Placeholders] 0 1 1 4981 254 63 Actual Values==================================================================================Disk 0: 16857.3 Megabytes============================= Partition Information ==============================Volume Partition Partition Start TotalLetter:Label Type Status Size MB Sector # Sector Sectors------------- --------------- -------- -------- ---------- - ---------- ---------- ExtendedX Pri,Boot 45229.8 0 3 63 92630727 EPBR Log 81921.3 None - 63 167774733 Type 74 Log,Boot 0.0 63 2 167774796 0 Type 0D Log,Boot 265356.7 63 0 543908792 543450478 Type 2B Log,Boot 938636.8 63 1 1818575978 1922328096==================================================================================Disk 1: 39087.8 Megabytes============================= Partition Information ==============================Volume Partition Partition Start TotalLetter:Label Type Status Size MB Sector # Sector Sectors------------- --------------- -------- -------- ---------- - ---------- ---------- QNX, UN*X Pri 39080.0 0 0 63 80035767 Unallocated Pri 7.8 None - 80035830 16065The thing is that how do i correct the problems. And with what program. !! Edited January 15, 2006 by Hish
ripken204 Posted January 15, 2006 Posted January 15, 2006 disconect and reconect the sata/ide cables for the hdd's. if that doesnt work then put ur old hdd in another computer to see if you can get your data back. also try installing windows on the new 40gig hdd to see if you can access the old hdd.
atomizer Posted January 15, 2006 Posted January 15, 2006 ...Then i got this message saying, "Media cable faliure, check cable"as per ripken204's advice, check your cables.once you know for a fact that the cables are properly connected and, if it still doesn't work, then it may be possible you have a bad cable.also, are you sure you have the correct cable for the drive (40 pin, 80 pin, SATA or whatever)?
Hish Posted January 15, 2006 Author Posted January 15, 2006 (edited) disconect and reconect the sata/ide cables for the hdd's.I've checked the cables, and i dont get that message anymore, however i still have problems with my Partition table, same errors and everything. I'll try putting the harddrive in another computer and see if i can take the information from there. But the thing is, would the other computer recognise it? In Partinfo, it said that the harddrive is like 90TB or something, wouldnt that be a problem?also try installing windows on the new 40gig hdd to see if you can access the old hdd.When I tried to install windows, it said that the drive was not compatible with windows. It also said [MBR] beside the drive name. But why, there is no problems in this drive. Edited January 15, 2006 by Hish
jaclaz Posted January 15, 2006 Posted January 15, 2006 Usually i thought well, this is Partition Magic, a reliable program, so I pressed Yes.Yep, that is the main problem, though usually Partition Magic works very well, it has on some peculiar configurations, disastrous effects. The best thing you can do at this point is trying to RE-Build the Partition Table.If you remember, more or less, how the disk was partitioned before the diasaster, please post this information, together with EXACT model/make of the disk, it could help make some sense out of the PARTINFO data you already posted to help you rebuild it manually.Alternatively you could try using TESTDISK:http://www.cgsecurity.org/testdisk.htmlread my posts here:http://www.msfn.org/board/index.php?showtopic=50179http://www.msfn.org/board/index.php?showtopic=43132http://www.msfn.org/board/index.php?showtopic=59145http://www.msfn.org/board/index.php?showtopic=30378&st=30jaclaz
Hish Posted January 15, 2006 Author Posted January 15, 2006 (edited) Harddrive 1 (the one with the bigtime problems) Seagate ST340015A (40GB)Harddrive 2 (this one works... i think..)Fujitsu MPG3409AT (40GB)Harddrive 1 was partioned like this i think(roughly) :C:\ = ~19GB (Where the OS is; Used about ~13GB)D:\ = ~20GB (Used about ~16) Edited January 15, 2006 by Hish
Hish Posted January 15, 2006 Author Posted January 15, 2006 I think this might help, it how Harddisk 1 is divided up:http://www.seagate.com/support/disc/specs/ata/st340015a.html
LLXX Posted January 16, 2006 Posted January 16, 2006 (edited) Get a disk editor (make sure it supports LBA and direct communication with the drive), read up on how partition tables work, and recreate the partition table manually. From my experience, "automated recovery" programs tend to sometimes mess up more than they fix.http://en.wikipedia.org/wiki/Partition_tablehttp://www.ata-atapi.com/hiwtab.htmWhat is most important is locating the partition superblocks and the Extended Partition Table. The superblock for the first partition should be very close to the beginning of the disk; it can be recognised due to its distinct structure and also ending with the bytes 55,AA. Once you have found this, you can put its address into the partition table as the Primary partition and also set its size (which will be indicated in the partition superblock itself). Add this size to the start of the disk and go to ~20Gb into the drive, and look around there for the Extended Partition Table. Once that has been located, put its address and the size of the remainder of the disk into the primary partition table, and your partition table should've been rebuilt. Edited January 16, 2006 by LLXX
Hish Posted January 16, 2006 Author Posted January 16, 2006 (edited) jaclaz : what should i do when inside testdisk?In the Seagate website, it sais that my harddrive is divided up like thisCylinders: 1023Heads: 256Sectors: 63 When i go inside testdisk and go into change geometry is sais like thisCylinders: 4866 Heads: 255Sectors 63Sector size: 512Should i change this? Edited January 16, 2006 by Hish
Hish Posted January 16, 2006 Author Posted January 16, 2006 YES!!!!I managed to correct the partition table with Testdisk!!but now i want to change the disk to "Primary Bootable" so it can boot.
atomizer Posted January 17, 2006 Posted January 17, 2006 i used testdisk a few days ago to fix my bootsector after an application i installed hosed it. good little utility.
jaclaz Posted January 17, 2006 Posted January 17, 2006 YES!!!!I managed to correct the partition table with Testdisk!!but now i want to change the disk to "Primary Bootable" so it can boot.Simplest way is using beeblebrox:http://students.cs.byu.edu/~codyb/Make sure you select the RIGHT drive in the drop down box.Change the number in the "boot" editbox of the RIGHT Primary partition you want to boot from to "80" (without quotes).jaclaz
supaplex030 Posted March 26, 2011 Posted March 26, 2011 Awsome, TestDisk also worked for me! I was trying to repair a micro SD card (I don't know what it haves exactly), well, so I opened PartitionMagic and got 110 error on disk 1, then I opened Windows Disks Manager to check drive numbers, my hard drive was disk0, and the micro SD card was disk1 so I clicked yes to fix the error, the program didn't opened because of other error, so I restarted my computer to assure everything was fine. First I saw a program whitout icon on the taskbar so I knew something bad happened, my second partition disappeared (D:), I entered Windows's Disks Manager again and the second partition appeared as unallocated. Then I entered Acronis Disk Director, there was both partitions (C: and D:) and plus the unallocated space corresponding to second partition (about 800 GB more than the physical disks really have) I've tried Acronis Recovery Expert but no luck, at leas I could explore the disk from Acronis, all my files were there. Then I start searching in Google and immediately found this thread, I tried TestDisk and the problem seems to be fixed (I hope there are no corrupted files, I can't check them one by one), I also passed Windows Scan Disk and there was no errors reported.Thanks a lot for the information, hope it helps more people.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now