Bug 20472

Summary:	The upgrade stopped with a message that mounting a Partition (a hidden Windows partition) failed!
Product:	Mageia	Reporter:	Daniel Kalweit <d.kalweit>
Component:	Installer	Assignee:	Mageia tools maintainers <mageiatools>
Status:	NEW ---	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	Error Report

Description Daniel Kalweit 2017-03-14 10:02:05 CET

I tried to install Mageia 6 sta2 and missed the option to install Grub2 on a PBR.
When I check "Do not touch ESP or MBR" I am not able to chainload Mageiea 6 from XOSL which is my "Masterbootloader".
So the only way to use Mageia 6 ist to install Grub2 to the MBR.

But with Grub2 I'm not able to hide/unhide several partitions for my 2 Windows installations.

Second way to install Mageia 6 was to upgrade from Mageia 5 and leave Grub legacy as bootloader in the Mageia Partition, but installation stopped with a message that it is not possible to write to a partition where Windows was located on.... ?? Why do Mageia wants to write on Windows partitions???

Comment 1 Daniel Kalweit 2017-03-14 10:05:28 CET

I already reported it here:

https://bugs.mageia.org/show_bug.cgi?id=18761

seems to be the same Problem.

Comment 2 Marja Van Waes 2017-03-14 15:37:09 CET

(In reply to Daniel Kalweit from comment #0)

We can only handle one problem in one bug report. Since bug 18761 already covers the missing option to install Grub2 on a PBR, I'll keep this report for the upgrade issue, thanks for informing us about the problem:

> 
> Second way to install Mageia 6 was to upgrade from Mageia 5 and leave Grub
> legacy as bootloader in the Mageia Partition, but installation stopped with
> a message that it is not possible to write to a partition where Windows was
> located on.... ?? Why do Mageia wants to write on Windows partitions???

Can you please reproduce that 5=>6 upgrade problem and when you see that message again do the following:

* Switch to tty2 with Ctrl+Alt+F2
* insert a USB key
* type:
        
         bug 

  (report.bug will then be written to the USB key)

*  attach report.bug to this bug report.

Thanks :-)

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Assignee: bugsquad => mageiatools
Summary: can't chainload grub2 => upgrading stopped with a message that it is not possible to write to a partition where Windows was located on.

Comment 3 Daniel Kalweit 2017-03-16 22:23:48 CET

Sorry, for the incorrect error report...


The upgrade stopped with a message that mounting a Partition (a hidden Windows partition) failed!

I attached the bug report.



...just want to say that I got this boot Problem (no chainloading with my bootmanager possible), the proprietary nVidia driver didn't work, got an error in the installer script (vcdimager missing, ...I think...) and update from MG5  didn't work.

Comment 4 Daniel Kalweit 2017-03-16 22:25:09 CET

Created attachment 9107 [details]
Error Report

Daniel Kalweit 2018-05-17 10:41:18 CEST

Summary: upgrading stopped with a message that it is not possible to write to a partition where Windows was located on. => The upgrade stopped with a message that mounting a Partition (a hidden Windows partition) failed!

Comment 5 Daniel Kalweit 2018-05-17 10:46:35 CEST

I changed the title, it was still incorrect, sorry.
For me it is not necessary to solve the bug anymore.

Marja Van Waes 2021-07-06 17:26:56 CEST

Keywords: NEEDINFO => (none)