Bug 14659 - NFS install fails immediately in stage 2
Summary: NFS install fails immediately in stage 2
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-11-25 17:53 CET by Frank Griffin
Modified: 2015-02-13 15:11 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Frank Griffin 2014-11-25 17:53:33 CET
If you try an NFS install in current cauldron it loads stage 2 but the initial GUI panel never appears.  The screen goes black, you get the "Sending termination signals" messages, and the machine reboots before you can read much of anything.

As no root partition has yet been assigned, no diagnostic files are left behind.

Reproducible: 

Steps to Reproduce:
Marja Van Waes 2014-12-03 17:35:29 CET

CC: (none) => marja11, pterjan, thierry.vignaud

Comment 1 Thierry Vignaud 2014-12-04 15:11:16 CET
Actually, if your press C^Q fast enough, you should get more info from other terms and even get the shell on tty2 in order to look at /tmp/ddebug.log (and copy it on USB)

Keywords: (none) => NEEDINFO

Comment 2 Frank Griffin 2014-12-04 15:54:05 CET
Ah, magic :-)

I'll try it.  Will this interrupt the termination, or do I have to get it in before ?  If the latter, I hope I get it in after the error and before termination.
Comment 3 Thierry Vignaud 2014-12-04 17:11:03 CET
Sorry, use C-s to freeze & C-q to unfreeze.
This is per tty.
So tty1 will be frozen but you can work with others tty.
Remember to use pgup on tty in order to find any interesting error message before looking at tty[2-5] as "pageUp history" is lost on tty switch
Comment 4 Thierry Vignaud 2015-02-06 09:08:23 CET
ping?
Comment 5 Frank Griffin 2015-02-13 15:00:35 CET
This is a memory problem.  VBox defaults to a 256MB memory allocation for a Mageia VM.  If I use C-s to freeze the display at the point where the screen clears and the next thing expected is the first GUI panel, and then pgup, I can see a message saying 

     "dmidecode: Unable to allocate memory"

If I increase the memory allocation to 512MB, the error does not occur.
Comment 6 Thierry Vignaud 2015-02-13 15:11:13 CET
Closing as we don't realistically support 256Mb machines...

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


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