Bug 752241

Summary: anaconda doesn't find LVM root
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-09 03:35:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
syslog
none
storage.log
none
program.log
none
anaconda.log none

Description Horst H. von Brand 2011-11-08 22:33:46 UTC
Description of problem:
After fully updating and fixing a few rpm{new,save} leftovers, I ran preupgrade-cli (Fedora 15 ~~-> 16), it got everything lined up AFAICS (downloaded 1.5 GiB, and finished normally). On reboot, it says "Examining storage devices..." and then exits saying it can't find the root of the installed system. This machine has /dev/sda (SATA disk), with MS-DOS disklabels; /boot is /dev/sda1, the rest lives under LVM (/dev/mapper/vg_laptop15-LogVol??). I do have a few non-standard repos configured, but they gave no trouble.

In vt2 of the installer I can see the volumes (lvs shows all of them), but I can't mount them.

I tried to mess around with the kernel parameters, but had no luck. Any hints?

Version-Release number of selected component (if applicable):
preupgrade-1.1.10-1.fc15.noarch

How reproducible:
Tried a few times, also reran preupgrade (GUI). Same result.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Still running Fedora 15...

Expected results:


Additional info:
It would be nice to be able to mount stuff and (re)start the update from a VT...

Comment 1 David Lehman 2011-11-08 23:03:20 UTC
Please attach the following files individually as type text/plain:

 /tmp/anaconda.log
 /tmp/storage.log
 /tmp/program.log
 /tmp/syslog


>It would be nice to be able to mount stuff and (re)start the update from a VT...

It might be nice, but it isn't going to happen. There's more going on than you might guess, and this is not possible.

Comment 2 Horst H. von Brand 2011-11-08 23:29:05 UTC
Created attachment 532423 [details]
syslog

As requested

Comment 3 Horst H. von Brand 2011-11-08 23:29:35 UTC
Created attachment 532424 [details]
storage.log

Comment 4 Horst H. von Brand 2011-11-08 23:30:11 UTC
Created attachment 532425 [details]
program.log

Comment 5 Horst H. von Brand 2011-11-08 23:30:44 UTC
Created attachment 532426 [details]
anaconda.log

Comment 6 Chris Lumens 2011-11-09 00:22:28 UTC
Do you have /var on a separate LV or partition?

Comment 7 Horst H. von Brand 2011-11-09 00:33:32 UTC
/var, /var/tmp are separate LVs. Excerpts from /etc/mtab:

/dev/sda1 /boot ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_laptop15-LogVol00 / ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_laptop15-LogVol01 /usr ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_laptop15-LogVol02 /var ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_laptop15-LogVol03 /home ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_laptop15-LogVol00 /tmp ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_laptop15-LogVol02 /var/tmp ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/mapper/vg_laptop15-LogVol03 /home ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0

Comment 8 Chris Lumens 2011-11-09 03:35:51 UTC

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