My father has a dual-boot Vista/Fedora 11 machine, with Grub on the MBR. He recently enabled recommended updates in Vista, and it wanted him to install SP2, but he was unable to. At Stage 3, after rebooting, it got to 100% but then failed and reverted the changes. The associated error number was 80004005. We found that the source of the problem was that the active partition was the Fedora /boot partition, not the Windows one. By using Vista's Disk Management tool to make the Vista partition active again, the problem was solved. Grub doesn't seem to care which partition is active (at least if it's on the MBR). Looking at old saved fdisk output from 2 of my machines, I suspect that F11 changed the active partition, and that in F10 and earlier, the Windows partition was active. Is this new behavior in the F11 installer (to change the active partition, even though Grub doesn't care), and if so, is it deliberate?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 08/16/2009 04:00 PM, Andre Robatino wrote:
My father has a dual-boot Vista/Fedora 11 machine, with Grub on the MBR. He recently enabled recommended updates in Vista, and it wanted him to install SP2, but he was unable to. At Stage 3, after rebooting, it got to 100% but then failed and reverted the changes. The associated error number was 80004005. We found that the source of the problem was that the active partition was the Fedora /boot partition, not the Windows one. By using Vista's Disk Management tool to make the Vista partition active again, the problem was solved. Grub doesn't seem to care which partition is active (at least if it's on the MBR). Looking at old saved fdisk output from 2 of my machines, I suspect that F11 changed the active partition, and that in F10 and earlier, the Windows partition was active. Is this new behavior in the F11 installer (to change the active partition, even though Grub doesn't care), and if so, is it deliberate?
I went through this and the solution is obscure but easy. He needs to change the active partition to the Windows partition. Except for the SP2 install and the ability for Vista to hibernate, neither Vista nor Fedora cares about what partition is flagged as active.
http://www.sterndata.com/category/tags/sp2
- --
Steve
On 08/16/2009 05:24 PM, Steven Stern wrote:
On 08/16/2009 04:00 PM, Andre Robatino wrote:
My father has a dual-boot Vista/Fedora 11 machine, with Grub on the MBR. He recently enabled recommended updates in Vista, and it wanted him to install SP2, but he was unable to. At Stage 3, after rebooting, it got to 100% but then failed and reverted the changes. The associated error number was 80004005. We found that the source of the problem was that the active partition was the Fedora /boot partition, not the Windows one. By using Vista's Disk Management tool to make the Vista partition active again, the problem was solved. Grub doesn't seem to care which partition is active (at least if it's on the MBR). Looking at old saved fdisk output from 2 of my machines, I suspect that F11 changed the active partition, and that in F10 and earlier, the Windows partition was active. Is this new behavior in the F11 installer (to change the active partition, even though Grub doesn't care), and if so, is it deliberate?
I went through this and the solution is obscure but easy. He needs to change the active partition to the Windows partition. Except for the SP2 install and the ability for Vista to hibernate, neither Vista nor Fedora cares about what partition is flagged as active.
Yes, if you read my message again, you'll see that we already discovered this (except for the Vista hibernation part - does Fedora hibernation care which is active?). My question is, given that this is the case, why does the F11 installer change the active partition if it doesn't have to?
P.S. Prior to discovering this, everything I was able to find with a web search suggested that it was necessary to temporarily replace Grub with Vista's bootloader, then apply SP2, then put Grub back. Maybe that's completely wrong and the only reason it works is that it changes the active partition back to Vista.
On Sun, 2009-08-16 at 17:36 -0400, Andre Robatino wrote:
On 08/16/2009 05:24 PM, Steven Stern wrote:
On 08/16/2009 04:00 PM, Andre Robatino wrote:
My father has a dual-boot Vista/Fedora 11 machine, with Grub on the MBR. He recently enabled recommended updates in Vista, and it wanted him to install SP2, but he was unable to. At Stage 3, after rebooting, it got to 100% but then failed and reverted the changes. The associated error number was 80004005. We found that the source of the problem was that the active partition was the Fedora /boot partition, not the Windows one. By using Vista's Disk Management tool to make the Vista partition active again, the problem was solved. Grub doesn't seem to care which partition is active (at least if it's on the MBR). Looking at old saved fdisk output from 2 of my machines, I suspect that F11 changed the active partition, and that in F10 and earlier, the Windows partition was active. Is this new behavior in the F11 installer (to change the active partition, even though Grub doesn't care), and if so, is it deliberate?
I went through this and the solution is obscure but easy. He needs to change the active partition to the Windows partition. Except for the SP2 install and the ability for Vista to hibernate, neither Vista nor Fedora cares about what partition is flagged as active.
Yes, if you read my message again, you'll see that we already discovered this (except for the Vista hibernation part - does Fedora hibernation care which is active?). My question is, given that this is the case, why does the F11 installer change the active partition if it doesn't have to?
P.S. Prior to discovering this, everything I was able to find with a web search suggested that it was necessary to temporarily replace Grub with Vista's bootloader, then apply SP2, then put Grub back. Maybe that's completely wrong and the only reason it works is that it changes the active partition back to Vista.
Generally, for dual boot machines, I install grub in /boot and make it active. That way, I haven't touched the MBR. In case warranty service is needed (or apparently in case of the Vista SP2 update, etc.), I can just change the active partition and Windows boots as though there's nothing else on the machine.
In the past, at least, that had to be done with a rescue disk after the Fedora install, because Fedora did not change the active partition. In fact, I filed a bug at one point requesting that the user have the option to change the active partition during the install if he didn't use the default boot record. It was closed WONTFIX. I'm pretty sure the default is still to install grub in the MBR and not to change the active partition.
The active partition must be one with grub installed. If you install grub in /boot and not in MBR, then /boot must be active, and vice versa. If you somehow get grub installed in both places, then either can be active, but you need to be careful to coordinate switching active partitions and updating grub.
When I installed F11 over F10 configured with /boot active, specifying /boot as the target for grub, it did not change the active partition.
On 08/16/2009 06:38 PM, Matthew Saltzman wrote:
In the past, at least, that had to be done with a rescue disk after the Fedora install, because Fedora did not change the active partition. In fact, I filed a bug at one point requesting that the user have the option to change the active partition during the install if he didn't use the default boot record. It was closed WONTFIX. I'm pretty sure the default is still to install grub in the MBR and not to change the active partition.
I'm sure that the default is still to install Grub in the MBR, since we just accept all the installer's defaults, and we have it on the MBR in F11. But I'm also pretty sure that sometime in the last 3 years, one of the Fedora clean installs (probably F11) switches the active partition from Windows to Fedora's /boot. I have a 3-year old XP/Fedora machine, it originally had the XP partition active, and after installing F11 it was /boot, before I switched it back. On my Vista/Fedora box, I successfully upgraded to SP2 when it first came out (before F11) suggesting that the Windows partition was still active at that time. I also had to reinstall Vista after F11, and had to make the Vista partition active for it to work, so immediately after installing F11 /boot was probably active.
Can anyone on a dual-boot Windows/Linux box with Grub on the MBR and the Windows partition active, who's about to clean-install F11, check afterwards if the active partition has changed?
On Sun, 2009-08-16 at 17:36 -0400, Andre Robatino wrote:
Yes, if you read my message again, you'll see that we already discovered this (except for the Vista hibernation part - does Fedora hibernation care which is active?). My question is, given that this is the case, why does the F11 installer change the active partition if it doesn't have to?
It might be the drive partitioner, rather than grub, doing it. There's two things you'd have to check on.
It might be important for some BIOSs which partition(s) are active, but it hasn't mattered on computers I've played with in the past, as far as I can recall.
It's possibly even more important regarding hibernation, or more to the point, waking up from hibernation. I've messed around, a bit, with dual boot. And hiberating one OS, then another, it doesn't always resume the Windows hibernation, but the Linux one always resumed (and without any GRUB menu popping up for me to decide whether to resume this OS or that.
Hi "without any
GRUB menu popping up for me to decide whether to resume this OS or that"
if in the following file vi /usr/lib/pm-utils/sleep.d/01grub
you short-cirbuit the procedure default_resume_kernel()
then you can again select the OS to boot after hibernation
suomi
Tim wrote:
On Sun, 2009-08-16 at 17:36 -0400, Andre Robatino wrote:
Yes, if you read my message again, you'll see that we already discovered this (except for the Vista hibernation part - does Fedora hibernation care which is active?). My question is, given that this is the case, why does the F11 installer change the active partition if it doesn't have to?
It might be the drive partitioner, rather than grub, doing it. There's two things you'd have to check on.
It might be important for some BIOSs which partition(s) are active, but it hasn't mattered on computers I've played with in the past, as far as I can recall.
It's possibly even more important regarding hibernation, or more to the point, waking up from hibernation. I've messed around, a bit, with dual boot. And hiberating one OS, then another, it doesn't always resume the Windows hibernation, but the Linux one always resumed (and without any GRUB menu popping up for me to decide whether to resume this OS or that.
Can anyone on a dual-boot Windows/Linux box with Grub on the MBR and the Windows partition active, who's about to clean-install F11, check afterwards if the active partition has changed?
ans. it is very easy . in win xp, right click in computer logo in destop then click manage then do in disk management then select partition then right click in mouse then delect local drive whose partision you want delete . in this process you delete all Linux partition without any software. $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ वही सबसे तेज चलता है, जो अकेला चलता है।
With Warm Regards, (¨`·.·´¨) Alwayz `·.¸(¨`·.·´¨) Keep (¨`·.·´¨)¸.·´ Smiling! `·.¸.·´
A small gift for u. ._|_______________#___________._|_. ._(__)__________#___#________(__)_. ._|#|_________#_______#________.|#|_. ._|#|_______#___________#_______|#|_. ._|#|______#___ Tajmahal ___#_____|#|_. ._|#|____#_______4u _________#____|#|_. ._|#|_I___#_________________#__|__|#|_. .|##|___.*__#______________#__.*__|##|_. ._|#|_(___)_..#############___(___)_|#|_. ._|#|__|#|**|________*_________|**|#|_.|#|_. ._|#|__|#|**|______*_____*______|**|#|_.|#|_. ._|#|__|#|**|____**_______**____|**|#|__|#|_. ._|#|__|#|**|____**________**___|**|#|__|#|_. ._|#|__|#|**|____**________**___|**|#|__|#|_. ._|#|__|#|**|____**________**___|**|#|__|#|_. ._|#|__|#|**|____**________**___|**|#|__|#|_. .___ |$$$$$$$$$$$$$$$$$$$$$$$$| ________. Rameshwar Gupta M.Sc. (Final) Physics 30,Jubilee Hall, University of Delhi Delhi-110007 Mob. Number = 09891322790
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
On Sun, Aug 16, 2009 at 16:02, Andre Robatino andre@bwh.harvard.edu wrote:
Can anyone on a dual-boot Windows/Linux box with Grub on the MBR and the Windows partition active, who's about to clean-install F11, check afterwards if the active partition has changed?
On 08/16/2009 05:00 PM, Andre Robatino wrote:
My father has a dual-boot Vista/Fedora 11 machine, with Grub on the MBR. He recently enabled recommended updates in Vista, and it wanted him to install SP2, but he was unable to. At Stage 3, after rebooting, it got to 100% but then failed and reverted the changes. The associated error number was 80004005. We found that the source of the problem was that the active partition was the Fedora /boot partition, not the Windows one. By using Vista's Disk Management tool to make the Vista partition active again, the problem was solved. Grub doesn't seem to care which partition is active (at least if it's on the MBR). Looking at old saved fdisk output from 2 of my machines, I suspect that F11 changed the active partition, and that in F10 and earlier, the Windows partition was active. Is this new behavior in the F11 installer (to change the active partition, even though Grub doesn't care), and if so, is it deliberate?
Sorry for the very late followup, but after clean installing F12, I see that the F12 installer has again switched the active partition from the Windows partition (/dev/sda1) back to the Linux /boot partition (/dev/sda2). I'll have to switch it back again to avoid future problems with Windows updates.
[root@compaq-pc ~]# man fdisk Formatting page, please wait... [root@compaq-pc ~]# fdisk -l /dev/sda
Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x031a25b1
Device Boot Start End Blocks Id System /dev/sda1 1 10444 83886080 7 HPFS/NTFS /dev/sda2 * 10444 10469 204800 83 Linux /dev/sda3 10469 30401 160103424 8e Linux LVM [root@compaq-pc ~]#