Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Summary: Installer fails to inclde Windowss => drakboot fails to detect Windows
There is no description of your problem, and please attach screenshots to the bug report rather than a dropbox link, which is not guaranteed to be always available. Please also attach the /root/drakx/report.bug.xz file that was produced during the installation (yeah, I know what's the problem since I follow the QA Team mailing list, but we still need a true description in this bug report).
The bug rteport was prematurely filed by the system before I had finished it! I have restored the original Summary that I entered, which says it all. (The installer *did* detect Windows: "Computing size of MS Windows partition" but seemed to have forgotten all about it when constructuing the GRUB boot menu.)
Summary: drakboot fails to detect Windows => Installer detects Windows, but fails to include in GRUB boot menu
CC: (none) => maurice
> Please also attach the /root/drakx/report.bug.xz file that was > produced during the installation See: https://dl.dropboxusercontent.com/u/10969499/root-drakx-report-bug-xz
(In reply to Maurice Batey from comment #3) > > Please also attach the /root/drakx/report.bug.xz file that was > > produced during the installation > > See: https://dl.dropboxusercontent.com/u/10969499/root-drakx-report-bug-xz Please, I said "attach" (see in the bug report page, Attachments section), not upload to dropbox. Attach both the report.bug.xz file and the screen shot. Copying what you wrote in your e-mail, which gives more context: ----------------- Installed well, BUT failed to include WIndows in the GRUB boot menu... (Earlier, it did say "Computing size of MS Windows partition".) Before it wrote to MBR I aborted it, and re-installed. Same result. Can still boot Windows, but only via Mageia-4 boot menu.
I confirm that the classical installer (also on i586) doesn't add Windows to the boot loader automatically. It's actually been this way for years, although in the distant past it used to work.
Hardware: x86_64 => All
> I said "attach" (see in the bug report page, Attachments section), not upload > to dropbox. Tried that but file too big: "The file you are trying to attach is 1765 kilobytes (KB) in size. Attachments cannot be more than 1000 KB. We recommend that you store your attachment elsewhere and then paste the URL" - which I did (in Dropbox).
Yeah our 1000KB limit is a bit tight... TJ just stated on the qa-discuss list that it still works for him with XP, so perhaps it's just Windows 7 and similar that it doesn't work with? Those are unique that they have three partitions instead of one as it was with XP. I have no idea what sda1 is for, but sda2 is the partition you have to use in the GRUB config, even though sda3 is the actual Windows data partition.
Mageia-4 installer had no problem with Windows 7.
(In reply to Maurice Batey from comment #6) > > I said "attach" (see in the bug report page, Attachments section), not upload > to dropbox. > > Tried that but file too big: > For upgrades, the file is not compressed because the report.bug.xz from the former install already exists. However, if you compress the file you uploaded to dropbox with xz: xz root-drakx-report-bug-xz then it'll be small enough to attach ;-)
CC: (none) => marja11
Detecting MS partitions is different from detecting a root MS drive.
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaudSummary: Installer detects Windows, but fails to include in GRUB boot menu => Windows7 is not included in GRUB-legacy boot menu (whereas XP is)
(In reply to David Walser from comment #7) > Yeah our 1000KB limit is a bit tight... > > TJ just stated on the qa-discuss list that it still works for him with XP, > so perhaps it's just Windows 7 and similar that it doesn't work with? Those > are unique that they have three partitions instead of one as it was with XP. > I have no idea what sda1 is for, but sda2 is the partition you have to use > in the GRUB config, even though sda3 is the actual Windows data partition. The Windows "3 partition default layout" is: - one partition is the "boot" partition where bootmanager lives - one partition is "Microsoft Reserved" wich is in place in case MS wants/needs more space for bootmanager or wants to re-design it during an upgrade... - one partitition holds actual data (Windows, Program Files...) Now if you pre-create one single partition for windows before the windows install, it will not do the 3 partition layout, instead it will happily install all on a single partition.
CC: (none) => tmb
Does omission mean that a newcomer to Mageia wanting to dual boot between Windows and Mageia will find no WIndows option in the GRUB boot menu, so will not be able to boot Windows at all? If so, that doesn't that say that this shortcoming is a release blocker? (Or is it just that the Windows option is only omitted if the installer found other Mageia installs?)
Assignee: bugsquad => thierry.vignaudWhiteboard: (none) => FOR_ERRATASeverity: normal => major
(In reply to Maurice Batey from comment #12) > Does omission mean that a newcomer to Mageia wanting to dual boot between > Windows and Mageia will find no WIndows option in the GRUB boot menu, so > will > not be able to boot Windows at all? > > If so, that doesn't that say that this shortcoming is a release blocker? > > (Or is it just that the Windows option is only omitted if the installer > found other Mageia installs?) It's too late for a release blocker, everybody in yesterday's meeting voted for the release of Mageia 5. Fortunately lots of people report it to be working. Still, we need to add a note in the Errata page. Could you propose a text that I could add there?
How about: "If you have only Windows installed on your machine, there is a possibility that Mageia-5's installer will fail to include a 'Windows' option in the boot menu it constructs. This means that when you reboot after installation it will only offer Mageia in the boot menu. If that happens,....." and add on the end there a suitable re-phrasing of Tony Blackwell's text in the QA-discuss mailing list today: "...this is easily fixed after installation, as re-configuring boot from within the newly-installed M5 (or earlier) via MCC usually results in grub finding the windows partition and correctly installing a boot option for it." and then: "YOU HAVE BEEN WARNED" For the sake of Mageia's reputation, I hope not many 'Windows only' people will try to install Mageia-5 with this shortcoming, especially if they do not have the confidence to apply the 'Blackwell' fix. N.B. Could that fix not be applied via a software update?) I cringe at the prospect of reviews in e.g. Linux Format such as "When I tried to install Mageia-5 to dual boot with Windows, I was - on reboot - denied all access to Windows. So much for the Linux boast of 'Can dual boot with Windows..'" I think it was a bad decision to launch Mageia-5 with this installer fault, and one we shall rue.
I for one never experienced this issue, and some claimed that it has been around for several Mageia releases, so I don't think we should put "YOU HAVE BEEN WARNED" or advise people against installing Mageia 5.
Isn't that what 'ERRATA' does?! So don't warn them, let them press on with anticipation, only later to find that they can't access their beloved Windows, then they will say "Why wasn't there a warning?'. Mageia's name will then be 'mud' (English expression), possibly in some publication.
Errata means "Known issues". It doesn't mean "Shoot ourselves in the foot and tell everyone that Mageia 5 is a bad release". Which would be very wrong by the way.
Note that I didn't say it should not go to the errata, I'm just saying we should not be overly dramatic about this. Your proposal without the "YOU HAVE BEEN WARNED" seems perfectly fine to me.
> It doesn't mean "Shoot ourselves in the foot and tell everyone > that Mageia 5 is a bad release". Which is precisely what I was trying to avoid them doing!
I'll test again an install on real hw next to Windows 8.1 with legacy BIOS to see if I can reproduce with the latest ISOs.
Just a thought: In my case Windows 7 is on /dev/sdA, but the Mageia-5 install was on /dev/sdB. Perhaps the latest installer GRUB code forgot to look on /dev/sda?
Looking at the report.bug linked above (comment 3), it indeed looks like Windows is the only system left out by grub: Those partitions were found by the installer: * running: blkid -o udev -p /dev/sda1 * blkid gave: ntfs-3g 48186C68186C574A System_Reserved * running: blkid -o udev -p /dev/sda2 * blkid gave: ntfs-3g 4A1071C31071B713 * running: blkid -o udev -p /dev/sda3 * blkid gave: ext3 f3393016-63e1-4eb1-a968-67fbf94e5a23 photos * running: blkid -o udev -p /dev/sda5 * blkid gave: ext3 d75ac5d7-53ac-405d-9221-53d3b2eb6315 Mageia-3-root * running: blkid -o udev -p /dev/sda6 * blkid gave: swap 748c3632-e4cb-429b-83de-1d374e1b2ee8 * running: blkid -o udev -p /dev/sda7 * blkid gave: ext3 abe67990-4c19-44b2-91ea-c57d8a529300 Mageia-3-home * running: blkid -o udev -p /dev/sdb1 * blkid gave: ext3 dadf36a3-c82a-4802-b756-c41b18511355 * running: blkid -o udev -p /dev/sdb5 * blkid gave: swap a905f8d9-f77c-404f-8823-b35f1edd77f6 * running: blkid -o udev -p /dev/sdb6 * blkid gave: ext3 6e42b0a4-f9f7-473b-a757-69a7b7772d1c * running: blkid -o udev -p /dev/sdb7 * blkid gave: ext3 e6f5a3da-6053-4160-bbec-9279744330e1 PCLinuxOS-root * running: blkid -o udev -p /dev/sdb8 * blkid gave: ext3 d6011cdb-371b-4564-94b2-ee986640d6c3 PCLinuxOS-home * running: blkid -o udev -p /dev/sdb9 * blkid gave: ext3 4a99695f-ce98-4201-bd28-8102e04fcff9 Mageia-4-root * running: blkid -o udev -p /dev/sdb10 * blkid gave: ext3 e9afe8fb-7473-44be-940e-65d0507abb27 Mageia-4-home * running: blkid -o udev -p /dev/sdb11 * blkid gave: ext3 a3933009-e1cd-459f-b8f8-57b8f296a64a Mageia-5Final-ro * running: blkid -o udev -p /dev/sdb12 * blkid gave: ext4 e3f05c7d-ee35-4d60-b5cc-963b54669aec Mageia-5Final-ho i.e.: - sda2: Windows (at least that's what diskdrake assumes in another part of the log) - sda5: Mageia 3 - sdb1: Mandriva (not shown here but grub's menu.lst confirms that) - sdb7: PCLinuxOS - sdb9: Mageia 4 - sdb11: Mageia 5 But grub reports only: ******************************************************************************** * grub: menu.lst ******************************************************************************** timeout 10 color black/cyan yellow/cyan gfxmenu (hd1,10)/boot/gfxmenu default 1 title Mageia-5-Final kernel (hd1,10)/boot/vmlinuz BOOT_IMAGE=Mageia-5-Final root=LABEL=Mageia5Fin-root nokmsboot splash quiet noiswmd resume=UUID=a905f8d9-f77c-404f-8823-b35f1edd77f6 vga=788 root (hd1,10) initrd /boot/initrd.img title Mageia-4 root (hd1,8) configfile /boot/grub/menu.lst title linux-nonfb kernel (hd1,10)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=Mageia5Fin-root nokmsboot resume=UUID=a905f8d9-f77c-404f-8823-b35f1edd77f6 root (hd1,10) initrd /boot/initrd.img title failsafe kernel (hd1,10)/boot/vmlinuz BOOT_IMAGE=failsafe root=LABEL=Mageia5Fin-root nokmsboot failsafe noiswmd root (hd1,10) initrd /boot/initrd.img title Mandriva Linux (Official) root (hd1,0) configfile /boot/grub/menu.lst title PCLinuxOS (PCLinuxOS) root (hd1,6) configfile /boot/grub/menu.lst title alt_Mageia (Official) root (hd0,4) configfile /boot/grub/menu.lst It did found Mageia 3 on sda (hd0), so it's not that it missed the entire disk.
Priority: Normal => High
Comment 22 shows that Maurice's configuration is a bit unusual though (lots of partitions on two disks with many systems), and the installer also reports issues with the two NTFS partitions: * running: blkid -o udev -p /dev/sda * found a dos partition table on /dev/sda at sector 0 * guess_geometry_from_partition_table sda: 77825/255/63 * is_geometry_valid_for_the_partition_table failed for (sda1, 2048): 0,32,32 vs 0,107,15 with geometry 293764/224/19 * is_geometry_valid_for_the_partition_table failed for (sda1, 206847): 12,223,18 vs 48,134,13 with geometry 293764/224/19 * is_geometry_valid_for_the_partition_table failed for (sda2, 206848): 48,134,14 vs 12,223,19 with geometry 77825/255/63 * is_geometry_valid_for_the_partition_table failed for (sda2, 629532671): 1023,223,18 vs 1023,152,5 with geometry 77825/255/63 So we really need other testers to confirm this issue on various hardware before we can decide if we want to hold Mageia 5 back again.
Look, I just provided a draft of what I thought should be said, as requested. Those more familiar with the crafting of Errata can weave their magic as is appropriate. If that weakens the message, so be it. Good luck!
Priority: High => Normal
I think we can keep it on high priority until we understand better what this bug is about, and whether it's a corner case or a major issue that will affect most Windows 7 users.
(In reply to Maurice Batey from comment #24) > Look, I just provided a draft of what I thought should be said, as requested. > > Those more familiar with the crafting of Errata can weave their magic as is > appropriate. If that weakens the message, so be it. > > Good luck! Thanks for the text. We're not going to weaken a message, if it's proved to concern all Windows 7 installations, it will be made one the first entries in the Errata page and probably in bold. However "YOU HAVE BEEN WARNED" is unneeded. Errata is already a synonym for "you have been warned". I prefer to say "caution, read carefully" than "you've been warned dude!" :)
Just tested, in vbox, Mageia 5 final, windows 7 64 bits, 2 partitions for windows (no data partition), the installer didn't add windows to the bootloader. Will attach report.bug.xz
Created attachment 6760 [details] Stormi's report.bug.xz
Stormi's report looks similar to Maurice's indeed: * running: blkid -o udev -p /dev/sda1 * blkid gave: ntfs-3g 68A4F5EBA4F5BC1E System_Reserved * running: blkid -o udev -p /dev/sda2 * blkid gave: ntfs-3g 0044F64E44F64646 ******************************************************************************** * fstab ******************************************************************************** # Entry for /dev/sda5 : UUID=f512983c-0126-4acb-a43c-f658c03566dc / ext4 relatime,acl 1 1 # Entry for /dev/sda2 : UUID=0044F64E44F64646 /media/windows ntfs-3g defaults,nofail 0 0 none /proc proc defaults 0 0 ******************************************************************************** * grub: menu.lst ******************************************************************************** timeout 10 color black/cyan yellow/cyan gfxmenu (hd0,4)/boot/gfxmenu default 0 title linux kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=f512983c-0126-4acb-a43c-f658c03566dc nokmsboot splash quiet noiswmd root (hd0,4) initrd /boot/initrd.img title failsafe kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=f512983c-0126-4acb-a43c-f658c03566dc nokmsboot failsafe noiswmd root (hd0,4) initrd /boot/initrd.img
(In reply to Rémi Verschelde from comment #29) > Stormi's report looks similar to Maurice's indeed: > > * running: blkid -o udev -p /dev/sda1 > * blkid gave: ntfs-3g 68A4F5EBA4F5BC1E System_Reserved > * running: blkid -o udev -p /dev/sda2 > * blkid gave: ntfs-3g 0044F64E44F64646 Which is the windows boot partition, sda1 or sda2 ? If this is sda1, it could be ignored due to its label "System_Reserved". System_Reserved is now seen as a recovery partition (2015-05-28) http://gitweb.mageia.org/software/drakx/commit/?id=ecee84c40b6a3d6daee350581877a80843465485 and it seems that recovery partition are ignored by bootloader http://gitweb.mageia.org/software/drakx/tree/perl-install/bootloader.pm#n1197 Thierry, could you confirm ?
CC: (none) => lmenut
> Which is the windows boot partition, sda1 or sda2 ? (sda1 in my Windows7 = /media/win_c): ls /media/win_c Boot/ bootmgr* BOOTSECT.BAK* System Volume Information/
> "...this is easily fixed after installation, as re-configuring boot from > within the newly-installed M5 (or earlier) via MCC usually results in grub > finding the windows partition and correctly installing a boot option for it" Just tried this on my Mageia-5. It did work (and later booted Windows 7), BUT when doing MCC/Boot and selecting 'Add' then 'Windows', for some strange reason it shows "fd0" as the default Windows partition! (That should be changed later?) To specify which Windows partition to use, in the provided drop-down list select 'sda1', which then does what is needed. I suggest this clarification (or words to that effect) be worked into Errata...
Added to errata, but I'm not familiar with this bug, nor am I a grub legacy user. Please check whether it is correct https://wiki.mageia.org/en/Mageia_5_Errata#Grub_doesn.27t_detect_Windows_on_some_systems
Whiteboard: FOR_ERRATA => IN_ERRATA
> Tony Blackwell's text in the QA-discuss mailing list today: > "...this is easily fixed after installation, as re-configuring boot > from within the newly-installed M5 (or earlier) via MCC usually > results in grub finding the windows partition and correctly installing > a boot option for it." I found that GRUB needed to be TOLD which is the Windows partition to use (i.e. sda1), rather than finding it itself.
(In reply to Maurice Batey from comment #34) > > Tony Blackwell's text in the QA-discuss mailing list today: > > > "...this is easily fixed after installation, as re-configuring boot > > from within the newly-installed M5 (or earlier) via MCC usually > > results in grub finding the windows partition and correctly installing > > a boot option for it." > > I found that GRUB needed to be TOLD which is the Windows partition to use > (i.e. sda1), rather than finding it itself. Yes, you need to manually configure it, it won't magically find it itself. For standard Windows 7 installations with the three-partition setup, it will be sda2. For other non-standard configurations, you'll just have to try the various Windows partitions to see which one it is.
> For standard Windows 7 installations with the three-partition setup, > it will be sda2. I believe it is always *sda1* that Grub needs to boot, regardless of how many other partitions Windows may have.
> For standard Windows 7 installations with the three-partition setup, > it will be sda2 That surprises me. Can anyone here confirm their boot menu Windows7 stanza reflects that? I find it difficult to believe that Windows' boot partition would move from sda1. Seems pointless. (But then there are so many pointless things about Windows :-) ) Why do that and potentially mess up so many bootloaders?
This has just affected me with Win8.1 Pro 64-bit on a Fujitsu Lifebook E751 It has only 4GB RAM and 160GB hdd. I used Windows Shrink Volume to get the max free - about 60GB on hdd. After that the hdd had 2 partitions for Windows: a reserved one of about 350MB and then C: of about 80GB. The Mageia installer found Windows OK and also the free space I had created through Windows Shrink Volume. All was well until I rebooted, but as with this bug report no sign of Windows in the boot menu. I shall try the Errata way to add Windows to the grub menu. I am posting to confirm that older Mageia (and indeed Mandriva et al) worked for me with older laptops and desktop PCs so to me this is a new bug. Thanks for the Errata - if it works - but not very friendly to someone who unlike me has not used Linux before. John
CC: (none) => johns9872003
I have observed a similar problem with Mageia 6 cauldron: Trying to configure a dual boot system with Windows-10 (ordinary layout with 3-partitions within an extended partition) with Cauldron Dev-1: no windows record generated in /boot/grub/menu.lst. Dual boot works perfectly when I, later, manually edit menu.lst and add the missing record. Before installing Linux, I had disabled "Fast Startup" on windows to be avoid any potential problems due to mount rejects in case windows is hibernating The problem only happens on my quite recent Dell Optiplex 7040 - on an old Dell Optiplex 990 (still has windows 7) cauldron installs and generates a correct windows record in menu.lst (is this related to the hardware platform? to the version of windows?, to some other fancy but non-evident issue?). Like John, in the past I never observed this problem, always found an automatically generated menu-item for windows.
CC: (none) => juergen.harms
Same here with 64-bit 6sta1 on real hardware. As with Mageia-5 pre-release (when I first reported this), the installer does see the Windows partition ("..sizing Windows..."). (Yes, the Windows stanza can be added during the GRUB setup in installer, but how many Windows users trying out dual-boot with Mageia will be up to that, and will assume Mageia will provide a Windows boot option?)
Keywords: (none) => 6sta1
Does it work better if you choose grub2?
Have always avoided GRUB2 wherever possible, but will try on the next install. (A Windows user trying Linux for the first time is liable to take the default, i.e. Grub legacy.)
Grub2 is what will be used in Mga6
Status: NEW => RESOLVEDResolution: (none) => WONTFIX
Source RPM: (none) => grub
Component: Installer => RPM Packages
Will check when I return to base,Thierry. (Currently on holiday in Le Crotoy, Picardy...)
I can confirm that the GRUB2 boot menu from 64-bit Mageia-6-sta1 does include a Windows stanza, and it does boot Windows7. (Interestingly, though, when I tried to boot Mageia-5 from that menu, the kernel threw a panic!. To boot Mageia-5 I had to select the other Mageia-5 'special' stanza, which then showed a secondary menu whose Mageia-5 stanza did boot Mageia-5, so will raise a bug report for that...)