Making Fedora Core 2 and Windows play well together [LWN.net]

Making Fedora Core 2 and Windows play well together

Posted Nov 7, 2004 12:03 UTC (Sun) by maxo (guest, #12091)
Parent article: Making Fedora Core 2 and Windows play well together

OK well I found you don't even need to follow the above. Just go into your BIOS and in your hard disk settings (in Phoenix BIOS, it's the first selected option when you go into BIOS, then select your hard drive), then you just change one of the settings from 'Auto' to 'LBA'. And then Windows will boot.

(Log in to post comments)

Making Fedora Core 2 and Windows play well together

Posted Nov 14, 2004 3:13 UTC (Sun) by itismike (guest, #26017) [Link]

Excellent. I am glad that there is an easy fix for many, but some (newer)motherboards do not have the LBA option.

The sfdisk trick worked for me...Windows is up and running. However, it broke my Fedora core3 installation. I can boot to root (full graphical mode) but 'df' shows that my LVM2 volume is completly full. Perhaps I set the partition table values wrong...

Wish me luck!,

Mike

Linux LVM 100% full?

Posted Nov 21, 2004 18:23 UTC (Sun) by itismike (guest, #26017) [Link]

I'm still stuck with a barely operating install. Can anyone give me a hint where I can start looking? I've been seaching forums and google for two weeks now, and am empty-handed. Perhaps this isn't the right place to ask this, but there seem to be people here that have tried the same fix...has noone else had this 100% full / partition after the fix?

I don't even understand what these numbers mean, but here's some data:
sfdisk gives the following:

[root@localhost ~]# sfdisk -d /dev/hdb
# partition table of /dev/hdb
unit: sectors

/dev/hdb1 : start= 63, size= 205002, Id=83, bootable
/dev/hdb2 : start= 205065, size= 12389895, Id=8e
/dev/hdb3 : start= 0, size= 0, Id= 0
/dev/hdb4 : start= 0, size= 0, Id= 0
[root@localhost ~]#

-----

here's my df results:
[root@localhost ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
4031680 3968824 0 100% /
/dev/hdb1 99250 12189 81936 13% /boot
none 768584 0 768584 0% /dev/shm
/dev/hda6 713448 704104 9344 99% /media/hda6
/dev/hda7 38337728 13344864 24992864 35% /media/hda7
/dev/hdc 716308 716308 0 100% /media/cdrecorder
[root@localhost ~]# sfdisk -d /dev/hdb
# partition table of /dev/hdb
unit: sectors

/dev/hdb1 : start= 63, size= 205002, Id=83, bootable
/dev/hdb2 : start= 205065, size= 12389895, Id=8e
/dev/hdb3 : start= 0, size= 0, Id= 0
/dev/hdb4 : start= 0, size= 0, Id= 0
[root@localhost ~]#

-----

and here's fdisk:

Disk /dev/hdb: 6448 MB, 6448619520 bytes
15 heads, 63 sectors/track, 13328 cylinders
Units = cylinders of 945 * 512 = 483840 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 * 1 217 102501 83 Linux
/dev/hdb2 218 13328 6194947+ 8e Linux LVM
[root@localhost ~]#

Thanks for ANY insight!!!

Mike

why is it so quiet in here?

Posted Dec 18, 2004 1:19 UTC (Sat) by itismike (guest, #26017) [Link]

Wow. I forgot that I posted this. Just in case anyone was concerned, the solution was to find a bigger disk...it was just a coincidence that after I resolved the boot problem as stated above, the disk just happened to become critically full. It's now developed S.M.A.R.T. errors, so I won't have the chance to prove this, but I'm pretty sure this was all a silly mistake.

Mike