Created attachment 5405 [details]
journalctl -a of normal + multi-user.target + rescue boots

Just in case it is usefull at all (is it???): attaching "journalctl -a" output from the installed Mageia of 
* a normal boot at 10:53h CEST (which crashed), 
* a multi-user.target boot (impossible to log in) at 10:55h
* the rescue boot at 11:03h, which worked fine.

I confirm the problem. I have the same message during the net-installation.
I also have:
script failed for cdrkit-1.1.11-4, cdrkit-genisoimage and samba-client.
By reboot, I have grub, plymouth screen, then a wait, then the computer stops.

CC: (none) => paiiou

I have a similar experience with network install (minimal install with X) using boot.iso dated September 3rd. "Script failed for systemd and samba-client"
Now the boot is very unreliable . Mostly it reaches DM but before I can login it dissapeares and computer shuts down. Sometimes it freezes after DM window dissapears and at about 20% cases DM window reappeares and I'm able to login.

CC: (none) => jyri2000

I suggest to incrementing the severity, because it is not possible to restart correctly.

Severity: normal => critical

(In reply to Georges Eckenschwiller from comment #4)
> I suggest to incrementing the severity, because it is not possible to
> restart correctly.

Yeah, you're righ, this not being possible to boot normally into the new install makes it a release blocker, too.

CC'ing QA team leaders
Added "after 5alpha2" to the whiteboard, so it'll show up when you search for 5alpha2 release blockers.... it'll probably get fixed before 5beta1 QA testing starts, though ;-)

Whiteboard: (none) => after 5alpha2
Priority: Normal => release_blocker
CC: (none) => davidwhodgins, eeeemail, wilcal.int

Thanks for adding us Marja. IIRC from dev ml there were some issues Colin was fixing with the new systemd. We can certainly test a network install when beta1 testing begins though in a few weeks.

There are actually quite a few problems with network
installing using boot.iso or boot-non-free.iso.
Maybe this is a good time for me to go through
again and document them. One is that both boot.iso
and boot-non-free.iso do not work if you attempt
an ftp install where the ftp point requires an
ID & PW. Also if you attempt an http install
and the local repo, like mine, uses something
other then a common URL like:

http://mirrors.kernel.org/mageia/distrib/4/i586

Example, attempting to install from:

http://192.168.1.2:8080/~mageia/distrib/4/i586

Will not work. It used to work in M3 but M4 lost
that ability.

Could we please stay on the original issue ?

For me, the problem is solved.

Thanks

Cool. If someone else can confirm and close the bug that would be great! :)

(In reply to Colin Guthrie from comment #10)
> Cool. If someone else can confirm and close the bug that would be great! :)

Sorry, can't test yet because I have only WPA encryopted wlan where I am now (so impossible to connect when using boot.iso)

So I should create a private mirror (which was on my todo-list, anyway), or I should wait for the QA pre-beta1 traditional iso.

I'll try to go for both options and just use what I get first.

Btw, according to mirror.readme 
> The expected size of the mirror is around 700GB.

If that's really all, then I don't need to go out and buy a new ext. HD

(In reply to Colin Guthrie from comment #10)
> Cool. If someone else can confirm and close the bug that would be great! :)

The systemd script error is fixed in today's pre-5beta1 dual iso, so closing 

(In reply to Jüri Ivask from comment #3)
> I have a similar experience with network install (minimal install with X)
> using boot.iso dated September 3rd. "Script failed for systemd and
> samba-client"

That issue still exists 
If we don't have a separate report for it, then MrsB will create it

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

s/that/the samba-client/