*** Bug 158018 has been marked as a duplicate of this bug. ***
*** Bug 158019 has been marked as a duplicate of this bug. ***
*** Bug 158020 has been marked as a duplicate of this bug. ***
*** Bug 158028 has been marked as a duplicate of this bug. ***
Do you have any more details to provide on how the partition table was damaged?
Yes, of course. I'm sorry. I got an "internal server error" from bugzilla,
mailed the info to the mail address in the error message and hoped they would
Anyway, please see the attached file. It contains an XML-ized version of the
Created attachment 114557 [details]
lost form data in XML.
Your initial report indicates you got a failed assertion error message. Could
you please post the text of that error message?
Not sure if this is the same bug, but after installing FC4T3 on my work laptop
(A Thinkpad T42) the partition table was incorrect. I generally dual boot, but
Windows was unable to boot up without showing me a blue screen. I stuck in a
rescue disc and attempted to use cfdisk, which reported that the hard disk
partition table was invalid (I think it said that the FC4T3 partition extended
past the end of the hard disk).
I was finally able to boot up pure fdisk, delete the FC4 partitions, and then
re-write the partition table. After following this with an MBR wipe, I was able
to boot into Windows again, and cfdisk reported everything was OK as well.
(Sorry I don't have a more detailed record of what happened. I would attempt to
reproduce, but I can't afford to risk hosing my work machine again, and I don't
have any free test boxes sitting around)
I did an extra bug report for the error message: bug 158156.
Copied & pasted from there:
The message is: "Assertion (metadata_length > 0) at disk_dos.c: 1942 in function
On the console there is also "96" printed on the next line after those messages.
Did you run into this problem only after seeing the assertion failure? What
steps did you take after seeing the message - ignore or cancel?
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product. If you have further details, feel free to
reopen the report with the additional details attached.