If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Fixing partition table in extended partition
I have a 200GB HD with C: partition (20GB) and D: partition (147GB). While copying files to the D: partition, I passed over the 137GB threshold (more info on that issue here - http://computing.net/windowsme/wwwbo...rum/43339.html). Windows kept copying files to the beginning of the partition and overwrote my extended boot record and it's extended partition table. After a restart, my D: drive was gone since there was nothing in the partition table to define it correctly. (More info on extended partition tables at the bottom of the page here - http://tinyurl.com/4g3t4) I used Powerquest's Partition Table Editor to view the extended partition table, and put table entries 2 - 4 to all zeros, since I only need the first one to define my one logical drive. My primary partition goes to sector 40,997,817. My extended partition starts at 41,013,945 (there's ~7MB of free space between the two) and goes to 349,702,920. I'm not sure what to set the logical drive parameters at. I currently have them set as- Type- 0C (FAT32X) Boot- 00 BCyl- 1023, Head- 0, Sector- 1 ECyl- 1023, Head- 254, Sector- 63 Sectors Before- 63 Sectors- 349,702,920 Doing this allows D: to show up, but clicking on it comes up with the error "D: is not accessible- A device attached to the system is not functioning", and the D: properties show it as having zero capacity. I also have some Powerquest PartitionInfo info and error messages if that would help. Any help or direction is greatly appreciated. -- Wiggy ------------------------------------------------------------------------ Wiggy's Profile: http://extremetechsupport.com/forum/...tml?userid=366 View this thread: http://extremetechsupport.com/forum/....phtml?t=63131 |
#2
|
|||
|
|||
A well articulated post wiggy,
Although not said, but I assume you are asking how to get your partition back? I'm sure there are a few programs around that can recover it again for you. For extra advice along with those who answer here, I also know for sure there are a few programmers that can give you the advice you need who have recently been hanging out at one of the grc spinrite development groups, especially one guy named Joep but there are certainly a few others. (actually Joep used to be one of the programmers that worked on PartionMagic and their other programs at powerquest back then before Norton bought it ...also Joep is the developer now of his own recovery software http://www.diydatarecovery.nl/ ) ...Anyway, even though that group is centered around spinrite and is best to keep that in mind - but i bet if you post this post over there innocently asking if spinrite can fix it (even though it can't at this point) ..but i just bet you will get a response about how to do it otherwise. You can go here to it's webbased forum http://grc.com/discussions.htm and click the spinrite group, or so much much better would be if you have OE or an email client that accepts this link to bring it up in your client and open it right now. (..if you do, just don't forget to click subscribe to keep the group set in your client after you close it). news://news.grc.com/grc.spinrite All the best for you to succeed.. Rick Wiggy wrote: I have a 200GB HD with C: partition (20GB) and D: partition (147GB). While copying files to the D: partition, I passed over the 137GB threshold (more info on that issue here - http://computing.net/windowsme/wwwbo...rum/43339.html). Windows kept copying files to the beginning of the partition and overwrote my extended boot record and it's extended partition table. After a restart, my D: drive was gone since there was nothing in the partition table to define it correctly. (More info on extended partition tables at the bottom of the page here - http://tinyurl.com/4g3t4) I used Powerquest's Partition Table Editor to view the extended partition table, and put table entries 2 - 4 to all zeros, since I only need the first one to define my one logical drive. My primary partition goes to sector 40,997,817. My extended partition starts at 41,013,945 (there's ~7MB of free space between the two) and goes to 349,702,920. I'm not sure what to set the logical drive parameters at. I currently have them set as- Type- 0C (FAT32X) Boot- 00 BCyl- 1023, Head- 0, Sector- 1 ECyl- 1023, Head- 254, Sector- 63 Sectors Before- 63 Sectors- 349,702,920 Doing this allows D: to show up, but clicking on it comes up with the error "D: is not accessible- A device attached to the system is not functioning", and the D: properties show it as having zero capacity. I also have some Powerquest PartitionInfo info and error messages if that would help. Any help or direction is greatly appreciated. -- Wiggy ------------------------------------------------------------------------ Wiggy's Profile: http://extremetechsupport.com/forum/...tml?userid=366 View this thread: http://extremetechsupport.com/forum/....phtml?t=63131 |
#3
|
|||
|
|||
Although not said, but I assume you are asking how to get your
....i see now of course the request was in your subject line... |
#4
|
|||
|
|||
"Wiggy" wrote in message ...
I have a 200GB HD with C: partition (20GB) and D: partition (147GB). While copying files to the D: partition, I passed over the 137GB threshold (more info on that issue here - http://computing.net/windowsme/wwwbo...rum/43339.html). Windows kept copying files to the beginning of the partition and overwrote my extended boot record and it's extended partition table. After a restart, my D: drive was gone since there was nothing in the partition table to define it correctly I used Powerquest's Partition Table Editor to view the extended partition table, and put table entries 2 - 4 to all zeros, since I only need the first one to define my one logical drive. Setting 2-4 to zeros is correct, but only because there is only one logical. The first entry defines "this" logical partition, the second entry points to the next in the chain. Only if it's the last in the chain will entry 2 be a "null pointer" or all 0s. 3 & 4 don't matter in an EPBR. But again, you are correct here.. My primary partition goes to sector 40,997,817. My extended partition starts at 41,013,945 (there's ~7MB of free space between the two) and goes to 349,702,920. I'm not sure what to set the logical drive parameters at. I currently have them set as- Type- 0C (FAT32X) Boot- 00 BCyl- 1023, Head- 0, Sector- 1 Starting CHS should probably be 1023,1,1, since there is usually 1 head difference between the table and the partition. However, the CHS values are merely placeholders for a partition that exceeds the CHS boundary, so this shouldn't matter in trying to access the drive from an OS that uses LBA. ECyl- 1023, Head- 254, Sector- 63 Sectors Before- 63 Sectors- 349,702,920 "Sectors-" means "Total sectors". You said above that the extended "goes to 349,702,920". If you mean that this is the total of the extended, then the logical's total sector count in the EPBR will be that number, minus the 63 sectors from the table to the start of the logical. Or 349,702,857 (all this assuming a typical setup, and that the extended entry is correct in the MBR) Doing this allows D: to show up, but clicking on it comes up with the error "D: is not accessible- A device attached to the system is not functioning", and the D: properties show it as having zero capacity. You probably overwrote the boot sector which is usually only 63 sectors (32k) away from the EPBR. The FAT for FAT32 is typically only 32 sectors into that, so no telling how much more file system damage occured. OTOH, if the FAT is okay, then rewriting the boot sector may be all that is needed. I also have some Powerquest PartitionInfo info and error messages if that would help. Partinfo only interprets what the tables say. |
#5
|
|||
|
|||
Hi Bill,
Nice reply you gave him. You know, so many of these newsgroup question posters don't have the courtesy to ever come back and reply.. ..which can be disheartening for some who spend volunteer time to help others. I know... my grandmother told me it's to give without expecting anything in return... ...but i think a simple thanks or acknowledgement is always appropriate..! Rick |
#6
|
|||
|
|||
"Rick Chauvin" wrote in message ...
Hi Bill, Hey Rick! Nice reply you gave him. You know, so many of these newsgroup question posters don't have the courtesy to ever come back and reply.. ..which can be disheartening for some who spend volunteer time to help others. I think many just can't find their way back. For whatever reason. Not being able to find the "group", the thread, not downloading enough headers. The web-based MS-CDO interface is a major contributor to "nolo-responsum" . There probably are some that just don't bother, but I'd guess the majority do want to respond, and just can't. .. But then it can be disheartening sometimes, as you said.. I know... my grandmother told me it's to give without expecting anything in return... ...but i think a simple thanks or acknowledgement is always appropriate..! Your grandma is a wise woman.. What you give is what you get..and all those ancient undeniable truths |
#7
|
|||
|
|||
.........-..........
|
#8
|
|||
|
|||
You mean :-), or are you standing on your head?
-- Thanks or Good Luck, There may be humor in this post, and, Naturally, you will not sue, should things get worse after this, PCR "Rick Chauvin" wrote in message ... | ........-.......... | | | |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Can't Access D: Logical Drive (extended partition) | Brad | Disk Drives | 2 | August 15th 04 04:58 AM |
XP on Fat32x advice ...? | RJK | General | 6 | August 5th 04 02:24 AM |
Replacing the boot drive, w/o reinstalling Windows and the apps? | Bill in Co. | General | 50 | August 1st 04 08:30 PM |
MBR switch on FDISK | jt3 | General | 30 | June 21st 04 08:56 PM |
Zero-byte D: drive should not show, C: missing from Device Manager | *Vanguard* | General | 8 | June 12th 04 04:19 AM |