Description of problem: Today's update broke all my i586 & x86_64 M6 Plasma Vbox installs. A full up from a blank drive boot.iso x86_64 install resulted in a clean install then a boot to a black unresponsive screen. I cannot even get to a terminal. The system is completely unresponsive. I have been able to collect the /root/drakx directory by booting the M5 Live-DVD x86-64 on the system under test. That zipped directory is attached to this bug. I was not able to get the journalctl file. Once again using: Mageia-6-sta1-LiveDVD-PLASMA5-x86_64-DVD.iso 06/29/16 I created a new Vbox client from this Live-DVD. It installed cleanly and rebooted to a working desktop. I then set up the repo, updated the install and it booted to a blank non-responding Vbox Client. I was then lucky to get to a terminal on this install ( right ctrl + f2 ) and was able to collect the journalctl file from that. Is attached. :-((
Created attachment 8113 [details] drakx zip file
Created attachment 8114 [details] journalctl file
It might be a red herring, but the very last line in your journal is: Jul 03 09:42:46 localhost kernel: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Could you try again without having sdb attached (it wasn't attached, or at least not seen, when you installed, either)
CC: (none) => marja11
Ya what happened here is i just pulled the USB drive after I had transferred the data and that probably happened a couple times. Problem occurs exactly the same on the i586 Vbox client and I didn't collect anything anyway on that one. Problem always occurs at boot.
Also I discovered the problem long before I started the diagnostics. Both Vbox clients failed, no analysis attempted. Then I did the boot.iso install and that failed the same way, and then I started the diagnostics using the USB stick.
If without sdb it gets stuck, too, then please replace attachment 8114 [details] with the journal output from without sdb :-)
Rerunning this whole thing all over again, updated repo, and after a clean install and update of the Vbox clients they both rebooted back to a working desktop. I also installed, using the boot.iso x86_64, onto a blank drive. That installed without issue and booted to a working desktop. Lets call this a passing error in the repo and set this bug to resolved.
Status: NEW => RESOLVEDResolution: (none) => FIXED