Bug 162817 - Can't upgrade from FC2 : partition table not found on device
Can't upgrade from FC2 : partition table not found on device
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2005-07-08 18:08 EDT by Emmanuel Druon
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:
Last Closed: 2005-08-30 14:35:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Emmanuel Druon 2005-07-08 18:08:44 EDT
Description of problem:
When trying to upgrade (or install) an FC4 over a workable FC2 install (on a
dual boot system), the partition table is not read correctly with anaconda. The
installation stops with a "partition table on device hda was unreadable..."
message. If a switch to text console 2, I can do an fdisk on the disk hda
without any problem (or error message) and /tmp/syslog doesn't indicate any
error reading the partition table on hda. Having to many data on the disk
(Seagate ST380022A Ata Drive), I can't afford deleting the existing partition to
try everything from scratch.

Version-Release number of selected component (if applicable):

How reproducible:
Each time

Steps to Reproduce:
1. boot from the FC4 DVD
2. the installer don't find any previous install and displays an error message
Actual results:
Can't upgrade or install FC4

Expected results:

Additional info:
Comment 1 Jeremy Katz 2005-07-12 11:12:02 EDT
Can parted see the partition table?
Comment 2 Emmanuel Druon 2005-08-26 05:20:03 EDT
Sorry for the delay but I've been out for quite some time. Unfortunately, I
can't send any more information about this bug since to solve my problem, I've
backed up my data, deleted my "rebelous" partitions and recreated them. Doing so
solved my installation problem...
Might close this bug unless someone around has the same problem.


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