Created attachment 3238 [details] dracut error at boot This report has been written as per the request from Bug 8344. The net installer has been suffered for a week or so from a bug that prevents intrd from being created. Due to this issue I've got a non-working installation (it was a clean install during which I formatted both /root and /home partitions and I enabled also the non-free and tainted repositories). Some progress has been made for fixing this issue, so next day I downloaded a fresh boot-nonfree.iso image and performed an update to my broken installation. During this update, the kernel was also updated (from 3.7.0 rc8 to 3.7.0 final). If I choose the first boot menu or the safe boot option (which are both with kernel 3.7.0 final), the system have some hiccups but will eventually boot, but if I choose to boot with kernel 3.7.0 rc8, I've got en error about dracut (attachment provided).
Created attachment 3239 [details] boot menu entries I've tried to find out from where the long <string value> (93cf80f7-18cf-4a7d-9800-8335762cea33) is comming from ... I see the same string value in the boot option when selecting to boot in safe mode (attachment provided). I emphasize that the dracut error appeared when booting with the kernel 3.7.0 rc8 and not when choosing the safe mode entry. Whatever the first boot menu option or the safe mode boot option is chosen at boot the <string value> is the same, but this string value is different from 93cf807-18cf ... (hope you understand what I mean there) (I can make better screenshots, but I tried to make them to be small size files.)
Added Colin Guthrie to the CC list. Colin, you might consider this bug doesn't worth investigating and we can abandon it. Just tell me if you want me to keep this installation for a few more days to provide you further details. Please first read my last comment (7) from Bug 8344 which will appear there in a few minutes.
CC: (none) => mageia
I've just done a clean install and so far so good ... almost. It makes little sense for you to waste time on this bug; if I see this issue again in a scenario easy to reproduce, I will report it. Closing for now.
Status: NEW => RESOLVEDResolution: (none) => OLD