Bug 16178 - Mount error during installation prevents further progress
Summary: Mount error during installation prevents further progress
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-06-22 18:49 CEST by Graeme Gemmill
Modified: 2016-03-23 18:49 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Graeme Gemmill 2015-06-22 18:49:37 CEST 
Description of problem:
Installing Mageia 5 from x_64 iso on a dual boot PC that already has Windows 7 and Mandriva 2011 fully operational.
In "Partitioning" phase, selected "custom partitioning", selected partition already created for Mageia 5 with mount point "/", agreed to format partition, then received error message
"mounting partition UUID=75....78 in directory /mnt/media/win_e failed"
The only response offered (OK button) just takes me back to the start of the partitioning phase.
Note: Windows "chkdsk" detected no errors with that partition.
Can this error not be ignored during installation? The partition is obviously recognised but not required to install Mageia 5 in the installation process in a different partition.

Version-Release number of selected component (if applicable):


How reproducible:
Every time. Also occurred when "Use current partitions" option was selected.

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 David Walser 2015-06-23 00:41:38 CEST 
Are you sure the Windows system wasn't hibernated at the time?
Comment 2 Graeme Gemmill 2015-06-23 15:03:09 CEST 
Yes, I'm sure it wasn't - every thing has closed down completely. However, I'm happy to withdraw this bug - I hadn't realised until just now that one could blank out the mount point of any partition during "custom partitioning", so that going back to the start of partitioning in fact gives one the opportunity to proceed.
Comment 3 Thierry Vignaud 2015-06-23 15:49:10 CEST 
Could you try again running into this bug.
Once you see the errror popup, please:
- attach a USB key
- go to console 2 (alt+ctrl+f2)
- run the "bug" command
- attach the report.bug file you'll find on your USB key

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud

Comment 4 Marja Van Waes 2016-03-23 18:49:24 CET 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Feel free to reopen if needed, while supplying the information that was asked for in comment 3

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.