windows-fedora dual boot
jvian10 at charter.net
Sun Jun 27 03:44:07 UTC 2004
On Sat, 2004-06-26 at 10:22, william jones wrote:
> In updating to kernal(2.4.22-1.2194.npt1) I was unable to boot Windows
> Me which resides on a separate ,removable disk.The message,"no fat file
> present",was displayed.Upon booting Fedora 1 ,the 2.4.22-1.2115.npt1
> kernal was selected from the grub choice,then shutdown,and the Windows
> disk inserted and this time booted successfully.Going back to the
> Fedora disk for a second time the(2.4,22-1.2194.npt1) choice was again
> made,booted,shutdown, the Windows disk inserted and booted successfully
> this second time.
> Why would the upgrade temporarily disable the boot loader,giving the
> impression that the situation suggested a Windows XP comparison?
> Being completely ignorant of Linux and computer know-how,the situation
> could have easily appeared more problematic to a novice like me.Perhaps
> it was only because my Windows disk had been partitioned to accept a
> Linux distro ,though still unused,that the corruption happened at all.
> I thought I should record this event since removable drives are
> recommended as an excellent choice for anyone moving to Linux from
> Windows and other Windows distros appear not to be immune from kernal
> upgrade related problems.It has been my experience that removable drives
> are an excellent approach and that Fedora Core 1 is a great choice for
> anyone new to Linux;just don't be in a rush to upgrade.
I have never had your problem with any version of RH, nor with FC1, but
XP is by far not the only version of windows to suffer from this type
problem with FC2.
In my case a 20gb drive, holding a Win98 install was the master drive.
FC2 was installed as a clean install on the slave drive (hdb). NOTHING
was supposed to be written to the partition table of hda, but I now have
the following partitions on hda.
In this case, I allowed Disk Druid to manage the partitions of hdb, so I
have to wonder if this may have been aggravated by the tendency of DD to
do its own thing with your drives.
[root at goliath root]# fdisk -l /dev/hda
Disk /dev/hda: 20.4 GB, 20490559488 bytes
255 heads, 63 sectors/track, 2491 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 2481 19922458+ 83 Linux
/dev/hda2 * 1025 2491 11783677+ c W95 FAT32 (LBA)
Notice that the single fat32 partition that was the only partition
originally on the drive and was a full 20gb in size is now only 12gb and
is the second partition (hda2). It also is contained entirely within
the first partition (hda1) that was created by installing FC2 on the
I can boot Win98 with grub as /dev/hda2 and everything seems to work OK,
but I really got bitten by the bug with anaconda on FC2 in spite of
making all the recommended preparations and taking steps to be sure the
LBA problem did not surface.
More information about the fedora-list