Making Fedora Core 2 and Windows play well together (分区工具对磁盘CHS的影响)

: · No Linux up to this point has had this issue, neither should FC2.

关键字：
Dual Booting Issues With Fedora Core 2 and Windows: Prevention & Recovery
多启动，预防和恢复

NOTICE: Please read this document in its entirety.

This guide was inspired by the solution developed by Radu Cornea and 
Alexandre Oliva in this thread: 
http://www.redhat.com/archives/fedora-test-list/2004-May/msg02114.html . 
This guide aims to integrate the original solution with the refinements 
evolved in that thread.  This guide offers an explanation of why the 
refinements are beneficial and some workarounds to problems that may prevent 
the uninitiated from using the solution. It also provides a means of 
preventing the problem entirely.(解释了该文章的主要来源以及要旨)

Primer:

        There is a bug in Fedora Core 2 that causes the hard disk geometry as 
reported in the partition table to be altered during installation.  This 
change may cause Windows boot failure.  Although this bug is severe, it is 
recoverable and no data should be lost.  It is important not to panic if and 
when this happens so you do not cause further problems or cause actual loss 
of data in the process of recovering from the error. 在Fedora Core 2安装过程中会提示硬盘物理分区表
改变的事实是一个bug，这会导致已经安装的win启动失败，虽然这是一个很严重的问题，但它是可以恢复的；当遇到这种情况
时，再没有导致进一步的问题发生和数据丢失的情况下，你没有必要恐慌，因为这时是可以从错误中恢复。

Prevention:预防

        This bug can be avoided entirely by using some preventative steps while 
installing Fedora Core 2.  Thanks go out to Cero (cero@coolnetworx.net) for 
discovery and testing of this solution.预防步骤，感谢Cero的测试和解决方案。

        To avoid the hard disk geometry to be altered you may enter it manually 
during installation by using the hdN=<drive geometry> parameter (where N is 
the letter representing the drive with the MBR you will use).  To discover 
the current geometry before installing Fedora Core 2 you should use a 
utility that can read the drive geometry as reported in the partition table. 
It is important to understand that some tools may not be reporting the 
actual data from this location, but, rather, some derived value, so your 
surest way is to use the fdisk utility.  You can get this information by 
following these steps.可以通过直接输入磁盘的参数来避免，首先用fdisk根据来获取磁盘的CHS；有
的工具报告的并不是真实的CHS，这是一种假象，所以先在其它系统上用fdisk工具来获取该磁盘的物理参数。
我理解的geometry应该就是CHS 的值，因为用fdisk也只能获取这些信息了，除了分好的分区信息。

Note: This example will assume you are looking at /dev/hda, which is the 
master on the primary IDE interface. If your MBR is located on another 
device you should use its name (eg: /dev/hde )这里实例是/dev/hda 

Download and burn the Fedora Core 2 Rescue CD. 下载刻录 FC2 的急救CD

Boot from the Rescue CD (there is no need to start networking or mount 
drives) 从急救盘启动

Issue the command: fdisk -l /dev/hda   to print the current partition table 
to screen in non-interactive mode.  用fdisk -l /dev/hda 显示当前磁盘分区表信息

Write down the drive geometry as reported at the beginning of the output 
from fdisk. This is reported as number of Cylinders, Heads, and Sectors 
(hence the name CHS).从这里可以看出 geometry 就是CHS ，记住该值

You can now reboot the computer by simultaneously holding down the keys 
Ctrl-Alt-Delete. 用 Ctrl-Alt-Delete重启

You can now boot the Fedora Core 2 installation CD. At the first menu prompt 
you should now choose to run the installer with the known geometry.
用FC2的安装CD启动，在启动菜单的提示符中加入 linux hda=14594,255,63这个CHS值就是刚才记下的值

Example: linux hda=14593,255,63

        The installer should now run normally and not alter your partition table 
geometry entry.  If, for any reason, this geometry should be changed 
regardless of this preventative step, please use the recovery steps to 
correct the geometry of the drive as reported by the partition table.
此时安装就不会改变你的CHS了；如果使用上面的预防步骤的情况下，仍然会改变CHS，就使用恢复步骤来校正CHS值
就是下面的恢复步骤。

Recovery:恢复

        You have installed Fedora Core 2 and find that you cannot boot Windows.  
Typically the boot process will terminate with the words 此时FC2已经安装，但是win无法启动
典型的win的启动如下所示:

        Rootnoverify(hd0,0)
        Chainloader +1

        These are the boot parameters from your Grub configuration.  The parameters 
are likely to be correct, but Windows fails to boot because Fedora Core 2 
altered the hard disk geometry as reported by the drives partition table.
这是使用grub作为bootloader的启动方式，这看起来没有什么不妥，但是由于CHS的改变导致win的无法正确启动。

IMPORTANT: Do not panic and do not begin using multiple tools in an attempt 
to correct this error. Automated tools can be very dangerous. The actual 
changes that need to be made are minor and benign.  By running 3rd party 
applications to recover a bootable Windows installation may cause you to 
lose your data.  You have been warned.
重要提示：不要试图使用第三发工具来修复该问题，尤其自动化工具非常危险，我们不知道它做了什么，有
可能会导致数据的丢失；因为实际此时需要作的工作却很少（没有第三方工具‘想象’的那么多）

        For those who are technically inclined I include here a brief explanation 
of what is going on.  The drive has not been damaged and your partition 
table is fine.  The problem is that Windows demands a "sane" CHS table.  
This table has been altered by Fedora Cores installer and Windows hangs.  
Luckily, the actual table, in LBA format, is not  corrupted.  For those 
seeing a strange partition table, take note that you are probably looking at 
the table in CHS values and these values are derived from the geometry.  The 
GNU/Linux operating system does not use these values and operates purely 
with LBA values.  Windows should not be using CHS either, but for some 
reason it at least checks this geometry and can be prevented from booting by 
them being bad.  Changing the drive geometry changes the CHS partition table 
because this is a virtualization of the true state of affairs on the drive 
which are best described as being mystical.  Think of CHS geometry as a 
compass.  If you change the geometry you have recalibrated where the 
needles reference point is and you are no longer looking at true north.
解释了此时的分区表状态，以及win自己认为什么样的CHS是正确的并且说明了此时的CHS处于什么样的
状态；总之，解释了出现该问题的原因。

        The solution to this problem is very simple, but it may confuse people 
because most people will question why they are seeing strange values 
reported from their partition table in CHS format.  If you do not trust this 
solution or your ability to follow these steps then you should stop and seek 
hard disk recovery consulting services.  The Fedora Project is in no way 
liable for any data loss and this guide is offered without guarantees.  You 
are taking responsibility for what happens.  Now, let us go through the 
solution.对该问题的解决方案非常简单，作者再次说明该方案不负商业责任^_^

        Because only the drive geometry is altered there is no need for manual 
intervention in the form of discovering and entry of partition information.  
The information in your partition table is correct.  However, you need to 
alter the geometry entry and normally this would require you to re-enter the 
partition table by hand using a tool like fdisk.  This is where the 
application sfdisk comes to the rescue. Sfdisk can be very powerful in 
non-interactive mode, it can output information that can be used as input 
elsewhere, and it can accept data as input at run-time.  This makes sfdisk 
ideal for this solution because you can ask it to read the partition table 
and deliver the result in a way that itself can write back when you tell it 
to change your drive geometry.  This makes the process fast and less prone 
to human error as very few values need to be supplied.  The solution can be 
summed up in a single line with two commands:由于这仅仅是由于CHS的入口导致的问题，所以就
没有必要再研究分区的信息了，因此只需要一个工具来校正CHS 分区的入口就OK了，接下来解释了sfdisk
对该任务的完全胜任和sfdisk工具的强大，下面就是该问题的解决方案，一条命令：

        sfdisk -d /dev/hda | sfdisk --no-reread -H255 /dev/hda

        So that the reader may better understand what is going on here, lets go 
through what each section does and what the parameters mean.为了更好的理解这条命令，下面解释：

sfdisk -d /dev/hda

This part runs sfdisk non-interactively and dumps the partition table in a 
format that sfdisk can also use for input (as we are doing).  Try this 
command by itself to see your partition table as it is very safe.  You will 
want to check to check for warnings in the output.  Warnings pose a problem 
because they interfere with the use of this data as input. Output containing 
a warning may look like the example below:可以完全放心的运行这条命令，它数据磁盘的分区表信息
内容如下面所示

$ sfdisk -d /dev/hda
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
# partition table of /dev/hda
unit: sectors

/dev/hda1 : start=       63, size= 16771797, Id= 7, bootable
/dev/hda2 : start= 16771860, size=217632555, Id= f
/dev/hda3 : start=        0, size=        0, Id= 0
/dev/hda4 : start=        0, size=        0, Id= 0
/dev/hda5 : start= 16771923, size=104856192, Id= 7
/dev/hda6 : start=121628178, size=112776237, Id= 7

For reasons unknown, using the option -- quiet does not suppress all 
warnings so it becomes the task of the user to discover a way to still use 
the output as input.  The simplest way is to write the output to a plain 
text file, editing out the warning in that text file, and using the edited 
text file as the input, thus:使用--quiet选项并不能完全屏蔽所有的警告信息，你可以用
下面的命令将分区信息输入到一个文件 MyPartitionTable.txt

sfdisk -d /dev/hda > MyPartitionTable.txt

        editing MyPartitionTable.txt to remove the warnings, saving the edited 
text, and 编辑该文件去掉警告信息，然后用下面的命令和上面这条代替最初的命令

cat MyPartitionTable.txt | sfdisk --no-reread -H255 /dev/hda

The output from "sfdisk -d /dev/hda" should begin like this (this is the 
edited version of the example given before):

# partition table of /dev/hda
unit: sectors

/dev/hda1 : start=       63, size= 16771797, Id= 7, bootable
/dev/hda2 : start= 16771860, size=217632555, Id= f
/dev/hda3 : start=        0, size=        0, Id= 0
/dev/hda4 : start=        0, size=        0, Id= 0
/dev/hda5 : start= 16771923, size=104856192, Id= 7
/dev/hda6 : start=121628178, size=112776237, Id= 7

        Note that "cat MyPartitionTable.txt" takes the place of "sfdisk -d 
/dev/hda" as these are now equivalent. In this case the warning portion has 
been stripped, preserving the needed data used by sfdisk in step two of the 
command.

sfdisk --no-reread -H255 /dev/hda

        This portion of the two-part command performs the actual change to your 
hard disk.  This main operation is in -H255. This tells sfdisk to write a 
head count of 255 into the drive geometry.  This command executed by itself 
would ask for user input of the partition table (just like fdisk).  However, 
by piping the table we just read in the first command, this is avoided and 
work is saved and we know the data is correct (or, at least, unchanged).  
This is why sfdisk is used.这条命令是校正的主要操作，它接受一个分区表信息，我们这里使用了
管道从前面的命令中得到的分区传递到这里作为输入。

        The --no-reread option allows the command to run even when the disk has a 
mounted partition.  Some users may find they need to further force the 
operation to complete. This is done by using --force (sfdisk --no-reread 
--force -H255 /dev/hda).
--no-reread 选项是在用户已经挂载磁盘的情况下照样执行的选项，同样 --force也是这样。

        In this example we are only changing the number of heads in the geometry.  
If you know the correct number of cylinders before the Fedora Core 
installation changed these values you may also write back this number.   An 
example with 14,593 cylinders is provided below.

sfdisk -d /dev/hda | sfdisk --no-reread -H255 -C14593 /dev/hda
这里的 -H -C -S 分别对应正确的CHS值

        The number of reported sectors (S) should not have changed and remained as 
63.

        This is the part most likely to be met with the question "if I change the 
number of heads, must I not also change the the number of cylinders?"  The 
answer to this question is "no."  When the geometry was changed the number 
of heads changed from 255 to 16 and the number of cylinders was increased to 
compensate.  As long as the values are large everything should be ok.  Only 
the pedantic need worry about changing the number of cylinders manually.  If 
you do not know the value from before you are best off not supplying this 
number.

        By using this method there is no need, and indeed you should not, run a 
program that wipes the MBR (like fdisk /mbr).  Doing so will cause you to 
lose the Grub pointer installed in the MBR and you will have to use the 
Recovery CD to regain access to your Fedora Core installation.

        Updating Grub after installation seems to have no effect on the drive 
geometry as the problem seems strictly limited to the Fedora Core installer.

Good luck and join us on the IRC at #fedora on irc.freenode.net for any 
questions you have or contributions to the community you wish to make.

-- 
fedora-devel-list mailing list
fedora-devel-list@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-devel-list