Bug 893138 - Anaconda installer fall back to Emergency Shell
Summary: Anaconda installer fall back to Emergency Shell
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-08 17:33 UTC by Takanori MATSUURA
Modified: 2013-12-19 21:31 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-19 21:31:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl command output (86.01 KB, text/plain)
2013-01-08 17:33 UTC, Takanori MATSUURA
no flags Details
Screenshot (1.82 MB, image/jpeg)
2013-01-09 13:56 UTC, Takanori MATSUURA
no flags Details
journalctl command output (F18-RC4) (85.94 KB, application/octet-stream)
2013-01-14 14:21 UTC, Takanori MATSUURA
no flags Details
dmesg command output (F18-RC4) (65.26 KB, application/octet-stream)
2013-01-14 14:21 UTC, Takanori MATSUURA
no flags Details
blkid command output (F18-RC4) (516 bytes, application/octet-stream)
2013-01-14 14:22 UTC, Takanori MATSUURA
no flags Details

Description Takanori MATSUURA 2013-01-08 17:33:22 UTC
Created attachment 674975 [details]
journalctl command output

Description of problem:
Anaconda installer fall back to Emergency Shell and Fedora can not be installed on Sony VAIO.


Steps to Reproduce:
1. Write F18-RC2 ISO image file (DVD, netinst, Live Desktop) to USB stick using dd.
2. Boot from USB stick.
3.


Additional info:
VAIO model name: SVT13129CJS
BIOS/UEFI: UEFI
Secure boot: both enabled and disabled are tested.

Comment 1 Chris Lumens 2013-01-08 18:24:56 UTC
What steps did you take that led to this problem?  Can you attach a screenshot from when you hit the shell?

Comment 2 Takanori MATSUURA 2013-01-09 13:56:05 UTC
Created attachment 675560 [details]
Screenshot

Boot process is stopped at the stage in this screenshot. This means I never reach to Anaconda GUI.

Comment 3 Chris Lumens 2013-01-10 16:13:46 UTC
There are unfortunately a whole lot of reasons why this emergency shell thing can happen.  It looks to me like your procedure for writing the image to USB is incorrect.  I don't think just dd alone can do it.  Brian will know for sure, though.

Comment 4 Brian Lane 2013-01-10 16:34:15 UTC
What does the output of blkid look like from the emergency shell? There should be a partition labeled "Fedora 18 x86_64", if it isn't showing up then I'd try using livecd-iso-to-disk to create the USB stick. It looks like this is a UEFI system so you would run it like this:

livecd-iso-to-disk --format --reset-mbr --efi ./path/to/iso /path/to/usb

Comment 5 Takanori MATSUURA 2013-01-14 14:21:08 UTC
Created attachment 678240 [details]
journalctl command output (F18-RC4)

Comment 6 Takanori MATSUURA 2013-01-14 14:21:40 UTC
Created attachment 678241 [details]
dmesg command output (F18-RC4)

Comment 7 Takanori MATSUURA 2013-01-14 14:22:10 UTC
Created attachment 678242 [details]
blkid command output (F18-RC4)

Comment 8 Takanori MATSUURA 2013-01-14 14:33:58 UTC
I created the USB stick with liveusb-creator on Windows instead of livecd-iso-to-disk because I don't have working Fedora now.
I tested the F18-RC4 DVD installer and the result is the same as the previous one.

Comment 9 Brian Lane 2013-01-16 00:10:11 UTC
Last time I checked liveusb-creator didn't know how to make UEFI sticks. If you can write the iso directly to the USB (whatever the windows equivalent of dd is) that should work.

Comment 10 Takanori MATSUURA 2013-01-16 03:16:04 UTC
The USB stick for the initial report is written with dd on MacBook.
So I think this bug does not depend on how to write the ISO image to the USB stick.

Comment 11 Brian Lane 2013-01-24 00:35:23 UTC
Please retry with F18 final and using dd to write it.

Comment 12 Takanori MATSUURA 2013-01-27 03:52:26 UTC
(In reply to comment #11)
> Please retry with F18 final and using dd to write it.

Things do not change.


BTW, is the choice of "Components: anaconda" right for this bug? If not right, which component is the better one to be assigned?

Comment 13 Brian Lane 2013-01-28 20:04:03 UTC
What does blkid show when using the dd'd iso? Your previous attachment looks like the USB stick isn't showing up at all. There should be a partition with the label "Fedora 18 x86_64" as shown by blkid. If not then I'll move it over to dracut.

Comment 14 Steve Tyler 2013-01-29 14:33:13 UTC
The dmesg attachment shows the USB stick:
[   10.428933] sd 6:0:0:0: [sdc] 7831552 512-byte logical blocks: (4.00 GB/3.73 GiB)

So blkid may need to be run as root:
$ sudo blkid | sort


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