我装的是FC2,请您看看我的grub.conf里面有问题吗？
我刚刚装了FC2，装好了，可以进去，单是我的win2000却进不去了，我该怎么办呢？我的grub.conf 里面是这样的：
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,2)
# kernel /boot/vmlinuz-version ro root=/dev/hdc3
# initrd /boot/initrd-version.img
#boot=/dev/hdc
default=1
timeout=10
splashimage=(hd0,2)/boot/grub/splash.xpm.gz
password --md5 $1$7Pcau1Hn$lV9pBuBWetlz2J.KPIuzj0
title Fedora Core (2.6.5-1.358)
root (hd0,2)
kernel /boot/vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.5-1.358.img
title Other
rootnoverify (hd0,0)
chainloader +1 # This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Windows XP-SP2
root (hd0,0)
savedefault
makeactive
chainloader +1
举例如上，具体的得自己研究一下(hd x,y)要设置对 我现在用别人的机子上网，因为我的机子要装锐捷才可以，我现在进不去win
也就没有for linux 的锐杰了，我该怎么办呢？ 锐接是虾米…… 您能帮帮我吗？我该怎样进入我的Win2000呢？谢谢您！ 那进入WIN2000时有什么提示吗？ 在引导界面选择other后提示是：
Booting 'Other'
rootnoverify(hd0,0)
Chainloader +1
您看看我该怎么办呢？ 可以按e编辑，然后仿造我的打，多尝试一下。google一下也会有很多解释阿。
root (hd0,0)
savedefault
makeactive
chainloader +1 谢谢您！
我也试了您说的
title Windows 2000 Ser
root (hd0,0)
savedefault
makeactive
chainloader +1
可是，系统提示
Filesystem type unknown,partition type 0x7
我试了很多方法，就是进不去!
难道linux这么烂?
我好心痛呀，我的D,E,F盘还有很多的资料呢！ 难道你碰上了FC2和windows nt系统双启动的bug，你先恢复原来的grub.conf ,然后在bios中将硬盘的access mode设为LBA，试试看。 好的，我现在就去试一下，谢谢您！ :P 放弃fc2吧:P
去下个hiweed-debian trytry:P
还是不行呀！
还是不行呀！我是了您说的，可是还是不行呀！
谢谢您！ :-( 我不知道你的问题是否和这有关，这里有针对这个bug的解决办法。不过是英文的，你能否先仔细阅读一下，不要动手做，因为这个涉及硬盘分区表等，一定要理解透彻，才能实践，切记！切记！！
Solution to the Windows, Fedora Core 2
Dual Boot Problem
Bill Moss
Updated May 26, 2004
Introduction
The purpose of this note is to serve as a warning to users planning to dual boot Windows 2000/XP and Fedora Core 2 (FC2) and provide a solution for users who have reported that Windows cannot be booted after the installation of FC2. This is not a how-to article on dual booting but rather a note about a couple of additional steps that can be added to a traditional dual boot setup that will avoid the disk geometry problem that is now being widely reported.
Here is summary of the steps. Details follow in the next section. This note covers the case of dual boot installation on a single IDE drive /dev/hda.
1. Assume that Windows 2000/XP has been installed and hard disk free space has been made available for FC2 or else an existing dual boot partition table will be used.
2. Insert FC2 disc 1 and boot in rescue mode
boot: linux rescue
At the prompt type
fdisk -l /dev/hda
and record the hard disk geometry reported as three integers XXX,YYY,ZZZ (cylinders, heads, sectors).
3. Reset and boot the FC2 installer
boot: linux hda=XXX,YYY,ZZZ
4. When you reach the point in the installation script where grub is set up, type the kernel parameter
hda=XXX,YYY,ZZZ
If you have windows installed on one disk and plan to put FC2 on a second disk, I would suggest that you repeat the above procedure to find the geometry of both disks and then boot the installer with a kernel parameter for each disk as in
boot: linux hda=XXX,YYY,ZZZ hdb=RRR,SSS,TTT
Otherwise, user reports suggest that the FC2 installer may change both partition tables.
Details
I have a Dell C600 laptop dual booted with Windows 2000 and FC1. Partition Magic reports the disk geometry (cylinders, heads, sectors) as 2432,255,63. When booted to FC1, the same values are reported by the commands
fdisk -l /dev/hda
parted /dev/hda
and by the 2.4 kernel in
/proc/ide/hda/settings
When I boot FC2 disc 1 to rescue mode, the 2.6 kernel reports the disk geometry as 38760,16,63, while fdisk reports it as 2432,255,63, and parted reports it as 38760,16,63.
The reports of other users suggest that if new partitions are created during FC2 installation, then Disk Druid will create a new partition table using the geometry 38760,16,63 because Disk Druid uses parted. In this case, Windows will not boot. If new partitions are not created during FC2 installation, that is, the current partition table is used, then Disk Druid will not create a new partition table. In this case, Windows will boot.
What is needed is a method of overriding the disk geometry that the 2.6 kernel is using during installation and thereafter. This can be done by using a kernel parameter. If I insert FC2 disc 1 and boot in rescue mode using a kernel parameter
boot: linux hda=2432,255,63 rescue
I see that the 2.6 kernel, fdisk, and parted all report the geometry as 2432,255,63. Based on this experiment, I believe that I can do a FC2 dual boot install by inserting FC2 disc 1 and booting the installer with a kernel parameter
boot: linux hda=2432,255,63
During installation, the kernel parameter hda=2432,255,63 can be input as part of the grub configuration. This will insure that parted works correctly after installation.
At least one user has reported that Partition Magic will report and fix errors after the installation. I have noticed the same behavior after past dual boot installations but these errors have never caused any problems. Partition Magic is reported to have a restrictive definition of a partition table.
Windows Will Not Boot
If Windows will not boot after installation of FC2, do not reinstall Windows or try to rewrite your MBR. You have not lost any data. All you need to do is to modify your partition table using the sfdisk command. The FC2 installer changed the number of heads recorded in the partition table. Assuming that your head count was 255 before the installation, you can fix your partition table by booting FC2 disc 1 to rescue mode and using
sfdisk -d /dev/hda | sfdisk --no-reread -H255 /dev/hda
Note that a few users have reported that their head count before installation was 240.
还有一篇
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.
Prevention:
This bug can be avoided entirely by using some preventative steps while
installing Fedora Core 2.Thanks go out to Cero ([email protected]) for
discovery and testing of this solution.
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.
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 )
Download and burn the Fedora Core 2 Rescue 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.
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).
You can now reboot the computer by simultaneously holding down the keys
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.
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.
Recovery:
You have installed Fedora Core 2 and find that you cannot boot Windows.
Typically the boot process will terminate with the words
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.
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 notcorrupted.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.
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:
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:
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).
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
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.
页:
[1]
2