Bug 158156 - Assertion (metadata_length > 0) at disk_dos.c: 1942 ... failed
Assertion (metadata_length > 0) at disk_dos.c: 1942 ... failed
Status: CLOSED DUPLICATE of bug 138419
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-19 04:26 EDT by dj
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-19 08:24:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description dj 2005-05-19 04:26:36 EDT
Description of problem:
When installing FC4T3 I got the following error message. It pops up twice always
and it doesn't seem to make any difference, if you click "ignore" or "cancel"
afterwards.

The message is: "Assertion (metadata_length > 0) at disk_dos.c: 1942 in function
add_logical_part_metadata() failed."

On the console there is also "96" printed on the next line after those messages.

After all, FC4T3 installed and can be booted fine.

How reproducible: Always.

Steps to Reproduce:
1. Boot from DVD. (Media check says it's fine.)
2. Select German language (worked for English, too)
3. Select German keyboard layout without deadkeys (worked for en_US, too)
  
Actual results:
Two popup windows (one after the other) with the mentioned error message.

Expected results:
If this assertion points to a hardware integrity problem, the user should be
informed so they can backup their data.

Additional info: During the same install, my partition table got damaged. See
bug #158017 for further information on that. I don't know, if they are related.
Comment 1 Jeremy Katz 2005-05-19 08:24:03 EDT

*** This bug has been marked as a duplicate of 138419 ***

Note You need to log in before you can comment on or make changes to this bug.