Bug 907229

Summary: Failed to install Fedora 18, crashed with "unknown filesystem"
Product: [Fedora] Fedora Reporter: Arnold Wang <arnold.x.wang>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-08 15:02:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screen shot of grub rescue
none
another screen shot none

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