red hat 7.2 lba/chs values not matching

before installing red hat 7.2 i had wxp pro installed. i just installed red hat 7.2. when i got into wxp pro i started partition magic. when installing red hat it made 3 partitions. the error partition magic give me is "error 116 starting at sector 17251920 on disk 1 the starting lba value is 17251920 and the chs value is 15482879 the lba and chs values must be equal" shoulld i let pm fix the problem? what caused the problem? i searched google and only found a few results and none were helpful. one said something about this error possibly causing data corruption or something? is this true? if so what could have been lost? i havent noticed anything yet.
LVL 1
Kitty__KongAsked:
Who is Participating?
 
The--CaptainConnect With a Mentor Commented:
It sounds like partition magic is annoyed by the partition table.  The partition table references partitions in two ways - an absolute reference from the beginning of the disk, and a CHS (cylinder,head,sector) reference.  I'm guessing partition magic is complaining that these two references do not point to the same place on the disk.  You used to see this a lot on old machines with huge drives - the bios just didn't know about huge drive geometries (well, actually there was a limit), so the CHS would always be wrong.  You also see this often on machines that have that utterly crappy EZdrive software (or one of it's numerous clones) installed - it lies to the OS about the drive geometry, often in really stupid ways.   I'm guessing whoever put wxp on the system also used EZdrive, resulting in your problem - many people who can't understand the system bios, partitions and drive geometry use it so that it can bite everyone else in the rear end later.  

To summarize, if everything works OK, you can probably ignore this error (and if you play with partition magic, you might be able to get it to shut up about the error entirely).  Calling partition magic tech support might help as well.

-Jon
0
 
Kitty__KongAuthor Commented:
i installed windows xp pro myself. its a retail copy and it made the original c partition. i then made the extended and the logical d drive with partition magic 7. then i installed red hat 7.2. it made 3 more logical drives on the extended partition. after this i booted in to win xp started partition magic and got the error.
0
 
Kitty__KongAuthor Commented:
because partition magic does not support ext3 partitions could this cause it to see the error? what i want to know is what program is right partition magic or disk druid/red hat/linux. is disk druid when partition making incorrect lba/chs values so i should let partition magic fix it?
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
haggarConnect With a Mentor Commented:
I had a very similar problem to yours. Let me quickly describe it, and the conclusions that I drew:

- on this disk (secondary master, but that's not relevant) I had a FAT16 partition (2 GB), a Linux partition, a small Linux swap partition and a BeOS partition. Important to note is that the disk was set as LBA in the BIOS.

- This setup worked fine until the day I installed Partition Magic 7. It complained about the same error message, and asked whether it should correct it. I answered by clicking on "OK", and that was the beginning of my problems. Partition Magic would not display the partition structure of this drive anymore, and I also wasn't anymore able to boot into BeOS.

- I was able to boot into Linux, and using fdisk I could inspect the partition table. To my surprise, fdisk was reporting three of my partitions ending at cylinder 1023. This obviously wasn't the case, but there doesn't seem any obviously simple way to fix this.

- What I did was I added another drive, created a FAT16 and a Linux partition on it, and backed up my Windows and Linux stuff onto them. Then I backed up the whole BeOS partition, in Linux, using the dd command:
dd if=/dev/hdc3 | bzip2 /mnt/hdb2/beos.bz
(obviously, /mnt/hdb2 is where I mounted the newly created Linux partition). Note that this is just one of the many possible ways to backup the stuff on the disk, but I chose it because the disk I added wasn't very large.

- After this, I removed Partition Magic, repartitioned the original disk, and restored my stuff.


Conclusion: if you get that error message from PM 7, and you know you have Windows and Linux partitions on that drive, better don't let it fix your partition table, or you might be in trouble.

0
 
CleanupPingCommented:
Kitty__Kong:
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1 
EXPERTS:
Post your closing recommendations!  No comment means you don't care.
0
 
Kitty__KongAuthor Commented:
split the points give either one the extra point randomly
0
 
Cyclops3590Commented:
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:
split points between haggar and The--Captain
Please leave any comments here within the next seven days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!

Cyclops3590
EE Cleanup Volunteer
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.