Bug 907229 - Failed to install Fedora 18, crashed with "unknown filesystem"
Summary: Failed to install Fedora 18, crashed with "unknown filesystem"
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-03 21:34 UTC by Arnold Wang
Modified: 2013-03-08 15:02 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-03-08 15:02:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screen shot of grub rescue (3.35 MB, image/jpeg)
2013-02-03 21:34 UTC, Arnold Wang
no flags Details
another screen shot (3.56 MB, image/jpeg)
2013-02-05 17:09 UTC, Arnold Wang
no flags Details

Description Arnold Wang 2013-02-03 21:34:03 UTC
Created attachment 692524 [details]
screen shot of grub rescue

Description of problem:
I tried to install Fedora 18 to my laptop with Fedora 17 installed. The way I tried to install was via NFS exported ISO image. After I customized the settings at the initial screen, I was prompted "root password not set" screen. While I tried to enter the root password, the installer crashed with "unknown error" message. At that point, I didn't have any other option than reboot. The system rebooted and now I'm at the grub rescue prompt with "unknown filesystem" error. According to grub, the original ext4(for /boot) and LVM/ext4(for rest of FS) file systems became "msdos" file system now somehow.  
Another thing might worth be mentioned is I didn't choose to reformat all the existing file systems. I tired to keep the old /home. 

Version-Release number of selected component (if applicable):
Fedora 18

How reproducible:
Not sure whether this is something can be reproduced "reliably", hope not. J 

Steps to Reproduce:
1. As described above.
2.
3.
  
Actual results:
System crashed in grub rescue prompt

Expected results:
The installation process continues with crash in the first place. Even it crashes, the file system need be kept intact so I can try the installation again.

Additional info:
I attached a screen shot of the grub rescue prompt I was in.

Comment 1 Chris Lumens 2013-02-05 15:16:42 UTC
If it crashed during installation, it's likely either no bootloader was installer or not enough bootloader was installed to be helpful.  Unfortunately without the /tmp/anaconda-tb-* file from the original crash, there's not enough information for us here to determine what the problem was that caused things to go wrong.  If you are able to boot up via the rescue disk and mount your filesystems, you may be able to get some logs out of /var/log/anaconda, though.

Comment 2 Arnold Wang 2013-02-05 17:07:43 UTC
I tried to boot from the DVD and it seems the file systems were corrupted for some reason. I have another screen shot attached.
I plan to upgrade my desktop soon, I will see if the same problem will happen again. If it happens again, I will try to save the log file.
Thanks.

Comment 3 Arnold Wang 2013-02-05 17:09:07 UTC
Created attachment 693490 [details]
another screen shot


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