Bug 947666 - F19 Alpha TC3 network installs getting stuck in post-install
Summary: F19 Alpha TC3 network installs getting stuck in post-install
Keywords:
Status: CLOSED DUPLICATE of bug 928287
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-03 00:50 UTC by Adam Williamson
Modified: 2013-04-03 16:29 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-03 16:29:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda.log from a stuck netinst (12.15 KB, text/plain)
2013-04-03 00:51 UTC, Adam Williamson
no flags Details
program.log from a stuck netinst (49.77 KB, text/plain)
2013-04-03 00:52 UTC, Adam Williamson
no flags Details
storage.log from a stuck netinst (192.67 KB, text/plain)
2013-04-03 00:53 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2013-04-03 00:50:14 UTC
I've tried several installs of F19 Alpha TC3 netinst.iso and the ones that haven't failed earlier all seem to get stuck in \performing post-installation setup tasks'. After some time, the X screen seems to go black or grey. The logs really don't give much detail about what's going on. top sometimes shows anaconda at 100%, sometimes not, but always seems to show a long-running 'ext4lazyinit' process. Google on that gives some interesting results suggesting install processes should pass noinit_itable as an ext4 mount option, but that doesn't seem really new, so it may be a red herring. I'll attach the logs from my latest stuck attempt. Note that the logs have not been written to since 00:22; it's now 00:49 and the install process does not appear to have completed. It's been stuck with no apparent progress for that whole 27 minutes. I've had this happen in a VM and on bare metal with both BIOS and UEFI boot.

Comment 1 Adam Williamson 2013-04-03 00:51:14 UTC
Created attachment 731011 [details]
anaconda.log from a stuck netinst

Comment 2 Adam Williamson 2013-04-03 00:52:09 UTC
Created attachment 731012 [details]
program.log from a stuck netinst

Comment 3 Adam Williamson 2013-04-03 00:53:38 UTC
Created attachment 731013 [details]
storage.log from a stuck netinst

Comment 4 satellitgo 2013-04-03 01:21:09 UTC
Fedora-19-Alpha-TC3-x86_64-netinst.iso
Test in VirtualBox 4.2.10
2048 memory 16.GB HD 
Bridged Network

basicx + ldxe 

default install 

root and user setup
( 1302 files)
Timing:
 6:01 post install set up
 6:06 bootloader  
 6:07 done  reboot 6:08 Pm logged in to ldxe  I used 2048 memory 16.GB HD default virtualbox basicx + ldxe 

Boots fine

Comment 5 Adam Williamson 2013-04-03 01:23:49 UTC
for me the installed system boots if I just force a reset, but I cannot log in as root with the password I set during install (111111).

Comment 6 Adam Williamson 2013-04-03 16:29:30 UTC
Now I read kparal's later comments on 928287, I'm pretty sure this is actually just that. Will re-open if it isn't.

*** This bug has been marked as a duplicate of bug 928287 ***


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