Bug 2265

Summary: System boot fails after seemingly successful install
Product: Mageia Reporter: Robert Gasch <rgasch>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: critical    
Priority: Normal CC: davidwhodgins, fri, marja11, nextwavecs, stormi-mageia
Version: 1Keywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: report.bug.gz of 64bit system

Description Robert Gasch 2011-07-24 22:41:39 CEST
Description of problem:
-----------------------
When trying to boot into Magia after installation I get the following:
1) In standard mode: Could not start boot splash: no such file or directory FAILED
2) In safe mode: the last thing I see on the screen is the following: nash_hotplug (56) /proc/56/oom_adj ist deprecated please use /proc/56/oom_score_adj
In both standard and safe mode the boot process then stops; the hard disk light flashes every once in a while but nothing further happens. 
This happens both after installing the 32bit and/or the 64bit release. 


Version-Release number of selected component (if applicable):
------------------------------------------------------------- 
Mageia 1 DVD Install


How reproducible:
-----------------
It is probably entirely related to my specific hardware configuration, which is relatively new: 
Intel Core i7-2600K Sandy Bridge 3.4GHz (3.8GHz Turbo Boost) Quad-Core
ASUS Sabertooth P67 B3 revision
Marvell PCIe SATA 6.0 Gb/s controller
JMicron JMB 362 SATA Controller
ASUS NVIDIA GeForce GTX 460 1GB GDDR5
8192MB DDR3 Dual Channel 1333MHz (PC3-10600)
Western Digital Caviar Blue 1000GB, SATA 6Gb/s (WD10EALX)

Please note that I'm 99.9% sure that it's not a hardware issue since Windows7 installs and works fine on this system. As stated above, the Mageia install process seem to work without any issues; the problem arises after finishing the installation and rebooting from hard disk. 


Steps to Reproduce:
-------------------
See above. I would be more than happy to help you diagnose this and verify a solution but I have no clue how to be of help. If you tell how I can help I'll gladly do my best.
Manuel Hiebel 2011-08-30 10:08:22 CEST

Component: Security => RPM Packages

Comment 1 Samuel Verschelde 2011-10-01 10:08:00 CEST
Hi, I'm not sure we can debug this without having the hardware, but one piece of information that could be useful is the file /root/drakx/report.bug.gz that was produced by the installer (you can use a live CD to reach it).

You could also test whether Mageia's live CD boots or not, as it is more or less equivalent to an installed system.

Thanks in advance and sorry for the delay.

Keywords: (none) => NEEDINFO
CC: (none) => stormi

Comment 2 Scott Fulford 2011-10-17 22:20:48 CEST
@Robert

I can confirm that I have the exact same issue while trying to use x64 version of Mageia 1. LiveCD GNOME i586 works, but when I tried to install the x64, everything installed fine, but when it came to reboot, all I got was a screen full of crazy graphics, and a periodic flashing HDD light. This problem is not reproducible with the LiveCD. 

Using an HP/Compaq F565CA laptop with 4GB of RAM, 320GB hard drive, and a geforce 6100 video. 

If there is anything we can do in order to get around this, I'd be happy to provide any further info.

Scott

CC: (none) => nextwavecs
Hardware: All => x86_64

Comment 3 Scott Fulford 2011-10-18 23:33:47 CEST
Created attachment 977 [details]
report.bug.gz of 64bit system

Ok.. I booted with a LiveCD and attached the report.bug file which was inside the report.bug.gz file.  I hope this will help with troubleshooting this issue.

Scott
Comment 4 Dave Hodgins 2011-10-21 05:38:13 CEST
What happens if you try booting to run level 3, without any splash kernel
parameter?

CC: (none) => davidwhodgins

Comment 5 Morgan Leijström 2011-11-01 22:01:42 CET
Could you try installing again, this time let it use some extra media so it pulls in updates during install?

I ask because i had the problem that if i test the graphics during install it hangs there, but it works after reboot (newer kernel or whatever than what the installer runs, i *guess*)

And also avoid any fancy partitioning (LVM, encryption) ; i think that is my current cause my second attempt last minute ends with same symptom as described above.

CC: (none) => fri

Comment 6 Marja Van Waes 2011-12-27 15:01:12 CET
No response to the questions of October 21st and November 1st 


If this issue turns out to still be reproducible, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD