Bug 122247

Summary:	after install, could not boot any partition due to inconsistant partition table
Product:	[Fedora] Fedora	Reporter:	George Hein <zweistein>
Component:	parted	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED DUPLICATE	QA Contact:	Brock Organ <borgan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-21 19:02:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description George Hein 2004-05-02 14:21:09 UTC

Description of problem: It appears that during install the FAT32
partition table entry was modified at hda5 for no reason.  The install
was successful onto an existing reiserfs on hda9 using manual
partitioning. 

The problem was catastrophic in that I could not boot any partition.
(I am using AirBoot boot manager which sits in HDA-MBR (master boot
record) with W2K and several LINUX bootable partitions, each with a
separate GRUB).  

Using "BusinessCardLinux" I tried FDISK to repair problem to no avail,
then used PARTED where everything looked OK, so forced an update to
HDA5-FAT32 with a PARTED RESIZE using identical size.  This apparently
corrected the problem. 

The only previous time that I have had such a problem was when GRUB
install was to HD0 instead of the LINUX partition, thus wiping out 
AirBoot in MBR. Then I simply reloaded AirBoot from floppy.
 
Both AirBoot and BusinessaCardLinux (upon loading) indicated some
problem with FAT32 partition although the latter had no problem
displaying it.

This may be a mere fluke, hardware error or who knows - BUT if anyone
else sees it perhaps there is an install problem.

HARDWARE:IBM THINKPAD T20.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 George Hein 2004-05-21 14:12:13 UTC

this appears to be a dupe of 155980, 120128, 113201 etc

Problem re-occurred with FEDORA CORE 2 final (as well as test2)
 
In both cases I (finally) resolved problem with PARTED-RESIZE of a fat
partition - this caused a rewrite of partition table which fixed it.
Similar attempts with FDISK were unsuccessful.  

After first time I reformatted hd, all but first W2K partition.

First time fat was on hda5, second time (fed-core2-final) on hda9.

Comment 2 Jeremy Katz 2004-06-25 19:47:00 UTC


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

Comment 3 Red Hat Bugzilla 2006-02-21 19:02:56 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.