Bug 9046 - Network install of mga3 fails in bootloader.pm
Summary: Network install of mga3 fails in bootloader.pm
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 3beta2
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-12 13:16 CET by Derek Jennings
Modified: 2013-02-13 17:29 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
mkinitrd failure in install log (43.82 KB, image/png)
2013-02-12 13:20 CET, Derek Jennings
Details
mkinitrd executed manually (33.77 KB, image/png)
2013-02-12 13:21 CET, Derek Jennings
Details

Description Derek Jennings 2013-02-12 13:16:52 CET
When installing Mgeia3 beta2 in a vbox using a network install, the installation fails while creating the bootloader with the message

"mkinitrd failed"

I have tried the install the following combinations of installation.

boot.iso with an NFS mount to Mga3b2 - failed
boot.iso with an FTP install from Cauldron - failed
boot.iso with Mga3b2 DVD mounted on a second drive - failed

 However a direct install using the Mga3b2 DVD succeeds.

Looking at the boot log the failing command is in /usr/lib/libDrakX/bootloader.pm at line 137

Execuring the same command in the command line gives the failure message
"/mnt/bin/dracut: line 588 : mktemp : command not found"
Derek Jennings 2013-02-12 13:18:01 CET

Whiteboard: (none) => 3beta2

Comment 1 Derek Jennings 2013-02-12 13:20:26 CET
Created attachment 3511 [details]
mkinitrd failure in install log

install log from a network install of mga3b2
Comment 2 Derek Jennings 2013-02-12 13:21:56 CET
Created attachment 3512 [details]
mkinitrd executed manually
Manuel Hiebel 2013-02-12 23:31:30 CET

Priority: Normal => release_blocker
CC: (none) => mageia, thierry.vignaud

Comment 3 Derek Jennings 2013-02-13 00:13:14 CET
I should have mentioned in the original report that the failure mode of an FTP install from Cauldron was different to the NFS and CDROM installs,

That install failed during package installation with the install log repeatedly dislaying the message

"install.sh does not contain root(hd..) line
no way to magically adapt device.map
error output in file /mnt/etc/fstab failed
no such file or directory"

Another user reported the same problem in the forum today.
Comment 4 Derek Jennings 2013-02-13 14:10:15 CET
Closing as INVALID.  I was using an old version of boot.iso.  
I tried again with the latest boot.iso and it worked.

Why it should make a difference so late in the install process I do not know.

There may still be a problem with an FTP install. I will do more tests and open a new bug if necessary.

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

Comment 5 Manuel Hiebel 2013-02-13 16:07:50 CET
we have some recent bugs about the installer, and ftp install too, 


"install.sh does not contain root(hd..) line
no way to magically adapt device.map
error output in file /mnt/etc/fstab failed

I have seen the same with an http install, maybe my cauldron repo was broken but I don't think so :/
Comment 6 Derek Jennings 2013-02-13 17:29:53 CET
I have just done a successful install from a local ftp image of mga2b2, but cauldron still does not work. Hopefully it is just a temporary thing with caildron.

Note You need to log in before you can comment on or make changes to this bug.