Bug 16616

Summary:	partitioner failed on 100 Gb harddrive space. writes partition, but says it can't install
Product:	Mageia	Reporter:	rene van den berg <rene-64>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description rene van den berg 2015-08-19 22:57:50 CEST

Description of problem:
installer failed to recognize it's own made partitions

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


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Comment 1 Marja Van Waes 2015-08-20 19:05:16 CEST

Hi Rene,

Which iso did you use? A Live Gnome or Live KDE CD/DVD or classical installer (a non-Live iso)?

* If the Live:

  Please try again by installing after starting the Live in Live mode.
  When it says it can't install, then open a konsole or terminal and run 
  (as root):

     journalclt -a > journalctl.txt
  
     xz journalctl.txt

  And attach the resulting journalctl.txt.xz to this bug report.

* If classical

  Try installing again until you get the error.

  Then switch to tty2 by pressing the 3 keys Alt + Ctrl + F2 at the same time.

  For how to continue, please read here:

  https://wiki.mageia.org/en/Triage_guide#Traditional_installer

  (If installer managed to mount a root partition, then there's a good chance
  just typing "bug" will copy the needed log file to the USB key.
  Else, you'll need to manually copy the file /tmp/ddebug.log to the key.)

  Please don't hesitate to ask if the instructions are unclear

Thanks,
Marja

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 2 Marja Van Waes 2016-03-23 19:29:51 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 1

Status: NEW => RESOLVED
Resolution: (none) => OLD