Bug 2030

Summary:	fdisk corrupts extended partition containing OS/2
Product:	[Retired] Red Hat Linux	Reporter:	pipework
Component:	util-linux	Assignee:	Erik Troan <ewt>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
URL:	pipework@cadvision.com
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-02-07 14:15:10 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 pipework 1999-04-07 12:46:19 UTC

It appears that when fdisk writes the
partition tables to disk, it changes the
extended partition entry such that BOOT
MANAGER cannot find the OS/2 partition.

I think that it does it even if the LINUX
partitions are on another physical drive! I
don't think this was a problem on my
Infomagic developer's version of 5.1.

The only solution I found was to temporarily
resize the extended partition using
partition magic which rewrote the
information (I think).

Comment 1 Erik Troan 2001-02-06 21:13:37 UTC

Can you send before fdisk/after fdisk partition table information?

Comment 2 pipework 2001-02-07 14:15:06 UTC

Hi:

I am unable to make copies of the partition tables (before and after) as you have requested. That computer is our main one for business.
If it is of any help, I have two 4G quantum hard drives. Linux is on the second disk. BootManager,WIN98 and OS/2 are on the first disk.
For some reason, the BIOS automatically configured the first disk as 'large' and the second as LBA. By the time I had discovered this,
 I didn't feel like changing it and reinstalling everything. 

This error appeared when I installed RedHat 7. It did not occur when I installed 5.1. Also, the OS/2 partition was not damaged, it just did not
 show up in the boot manager. Deleting and reinstalling boot manager did not work. Using Partition Magic to change the extended partition
 values did fix it. This leads me to think that the extended partition entry was changed in a way that did not affect the pointers but did make
 boot manager choke.

SM

Comment 3 Erik Troan 2001-02-07 16:13:31 UTC

If you upgrade again, it would be helpful to see fdisk -l output before and
after. I'm closing this bug as I have no way to reproduce it :-(