Description of problem: Attempted to install Mageia-3-RC-x86_64-DVD on HP EliteBook 8560 laptop. Install failed with this screen: http://i.imgur.com/t9Jpsit.jpg "An error occurred  mkinitrd failed  (mkinitrd -v -f /boot/initrd-3.8.7-desktop-1-mga3.img 3.8.7-desktop-1-mga3)." Version-Release number of selected component (if applicable): Mageia-3-RC-x86_64-DVD install DVD How reproducible: install fails at same place in 3 attempts Steps to Reproduce: 1. boot from Mageia-3-RC-x86_64-DVD 2. Install 3. Reproducible: Steps to Reproduce:
Version: Cauldron => 3
Used ctrl-alt-f2 and ran "bug" command to create a "report.bug" text file on USB memory stick. This is available here: https://www.dropbox.com/s/gw8x83w7g9e2i36/report.bug
photo of screen when bug occurred: http://i.imgur.com/t9Jpsit.jpg
I: *** Stripping files *** I: *** Stripping files done *** I: *** Creating image file *** gzip: stdout: No space left on device cpio: write error: Broken pipe F: dracut: creation of /boot/initrd-3.8.7-desktop-1.mga3.img failed * step "setupBootloader" took: 0:00:21 * error: mkinitrd failed: (mkinitrd -v -f /boot/initrd-3.8.7-desktop-1.mga3.img 3.8.7-desktop-1.mga3) at /usr/lib/libDrakX/bootloader.pm line 137.
Seems to have been caused by the partition being full. Was this a fresh installation or an upgrade? Did you allow it to format the partition before it started? How did you partition the drive? (automatic or manually) and anything else you can think of which might help :)
CC: (none) => eeeemail
Fresh install. I partitioned manually like this: unencrypted - /boot - 128mb encrypted - <swap> - 32g encrypted - / - 16g encrypted - /usr/local - 2g encrypted - /home - the remainder (> 400 gb) I have just booted a Gparted liveCD to check the partitions sizes. Gparted is reporting my /boot as 13mb. Hmm, that could well be my error. I will re-install and this time make sure that /boot is 256mb
OK, I re-installed and made sure that /boot was 256mb. The install completed OK. My apologies: I must have created a wrongly sized /boot the first time around. I don't know how that happened. Closing bug.
Status: NEW => RESOLVEDResolution: (none) => INVALID