Bug 11991 - FATAL ERROR IN INIT: fatal error finishing initialization (could not create symlinks)
Summary: FATAL ERROR IN INIT: fatal error finishing initialization (could not create s...
Status: RESOLVED DUPLICATE of bug 14544
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-15 01:45 CET by Christian Bryant
Modified: 2015-05-19 12:26 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

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

Description Christian Bryant 2013-12-15 01:45:35 CET 
Description of problem: FATAL ERROR IN INIT: fatal error finishing initialization (could not create symlinks)


Version-Release number of selected component (if applicable): Mageia 4 Beta 2 (Cauldron) x86_64


How reproducible: Every time I try to install Mageia 4 Beta 2 x86_64


Steps to Reproduce:
1. Insert new Mageia 4 Beta 2 DVD x86_64
2. Boot to DVD - DVD Starts to boot
3. Loading Linux Kernal
4. Loading programs into memory - hangs at 52%
5. Crashes:

Error opening symlink definition file '/tmp/stage2/usr/share/symlinks'

FATAL ERROR IN INIT: fatal error finishing initialization (could not create symlinks)

I can't recover from this, please reboot manually and file a bug report



Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-12-22 15:16:56 CET 
Is the md5/sha1 good ? (you are the first one to report such issue, which is strange)

also can you reproduce with the i586 or dual iso ?
Comment 2 trem 2014-02-08 13:53:01 CET 
I've reproduced this issue with qemu avec the i586 dvd install.
The issue was fixed by adding -m 512 to the qemu command line.

So I suppose that this issue is caused when there isn't enough
memory on the box.

How many memory have you got ?

CC: (none) => tremyfr

Comment 3 Thierry Vignaud 2015-05-19 12:26:44 CEST 
Dup

*** This bug has been marked as a duplicate of bug 14544 ***

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