Bug 819604

Please attach /tmp/anaconda.log, /tmp/program.log, and /var/log/syslog as individual files to this bug report.

Created attachment 583051 [details]
/tmp/syslog

Created attachment 583052 [details]
/tmp/program.log

Created attachment 583053 [details]
/tmp/anaconda.log

Created attachment 583054 [details]
/tmp/lvdisplay.log

Here you are. I added also the output of the lvdisplay command.

They are listed as inactive because you first have to activate them in order to use them.  I don't see anything in your logs that indicated anaconda even attempted to find logical volumes.  If still available, can you please also grab /tmp/storage.log?  Thanks.

Created attachment 586463 [details]
storage.log

I seem to be hitting the same problem, I have the following partitioning and LVM layout:

# lsblk /dev/sda
NAME                                                 MAJ:MIN RM   SIZE RO MOUNTPOINT
sda                                                    8:0    0 298.1G  0 
├─sda1                                                 8:1    0 245.9G  0 
│ └─luks-f1191002-0333-4759-ac9f-161507f8191b (dm-0) 253:0    0 245.9G  0 
│   ├─vgwd300-LogVol01 (dm-1)                        253:1    0  14.7G  0 /
│   ├─vgwd300-LogVol02 (dm-2)                        253:2    0     1G  0 [SWAP]
│   ├─vgwd300-LogVol00 (dm-3)                        253:3    0  14.7G  0 /f13root
│   └─vgwd300-LogVol03 (dm-4)                        253:4    0 215.6G  0 /home
├─sda2                                                 8:2    0    50G  0 /windows
├─sda3                                                 8:3    0     1K  0 
├─sda5                                                 8:5    0   251M  0 /boot
└─sda6                                                 8:6    0     2G  0 

Installing with Fedora 17, the partition tool does not show any of the logical volumes for vgwd300, so I can't install to vgwd300-LogVol00 (currently /f13root), and leave the other partitions (my current "/", swap, and /home) as-is.

This worked fine when installing Fedora 15, and it works fine with CentOS 6.2 - with those, I can see and select vgwd300-LogVol00 for "/" root file system.

Any suggested (and of course safe) workarounds are very much appreciated ...

(In reply to comment #8)
> Created attachment 586463 [details]
> storage.log

For some reason udev is not reporting your PV (sda4) as having any recognizable formatting of any kind. Something is wrong either in udev or blkid if that device is indeed an LVM PV.

(In reply to comment #9)
<snip>
> Installing with Fedora 17, the partition tool does not show any of the
> logical volumes for vgwd300, 
<snip>

Please attach /tmp/storage.log (as an attachment of type text/plain) so we can get an initial idea of what is happening.

Created attachment 593961 [details]
f17 install storage.log

My /tmp/storage.log created while trying to install Fedora 17.

(In reply to comment #12)
> Created attachment 593961 [details]
> f17 install storage.log
> 
> My /tmp/storage.log created while trying to install Fedora 17.

Everything looks normal in there. Your lvs are correctly recognized by the installer. Please attach /tmp/anaconda.log so we can investigate further. If you want to go ahead and attach /tmp/program.log and /tmp/syslog now as well, feel free -- we may need them at some point. Please do attach them individually, though -- no archives.

Created attachment 595471 [details]
fedora 17 /tmp/anaconda.log for failed LVM partition non-usage

Created attachment 595472 [details]
fedora 17 /tmp/program.log for failed LVM partition non-usage

Created attachment 595473 [details]
fedora 17 /tmp/syslog for failed LVM partition non-usage

(In reply to comment #16)
> Created attachment 595473 [details]
> fedora 17 /tmp/syslog for failed LVM partition non-usage

How about attaching a screenshot of the main partitioning screen so I can see exactly what you are talking about.

(In reply to comment #17)
> (In reply to comment #16)
> > Created attachment 595473 [details]
> > fedora 17 /tmp/syslog for failed LVM partition non-usage
> 
> How about attaching a screenshot of the main partitioning screen so I can
> see exactly what you are talking about.

It'll be another week or two before I can try to install again.

This problem is a show-stopper for me, I'll probably have to switch to CentOS or something that is still supported.

Have you tried to reproduce the problem?

Create or use an encrypted LUKS partition, create a file system on it.

Install, and try to access the file system.

(In reply to comment #18)
> Have you tried to reproduce the problem?

Yes. See below.

> 
> Create or use an encrypted LUKS partition, create a file system on it.
> 
> Install, and try to access the file system.

I did exactly that. I installed an lvm-on-encrypted-pv setup using the F17 installer, rebooted, then provided the luks passphrase when asked. The custom partitioning screen correctly showed the lvs.

(In reply to comment #17)
> (In reply to comment #16)
> > Created attachment 595473 [details]
> > fedora 17 /tmp/syslog for failed LVM partition non-usage
> 
> How about attaching a screenshot of the main partitioning screen so I can
> see exactly what you are talking about.

I re-ran the install today, and the partitions showed up as expected, and I was able to install Fedora 17.

I don't *think* I did anything different, given I tried this 3 times before, and that I was also able install CentOS 6.3. 

I have the log files, and can upload them if you want.

The log files from a successful install won't tell me anything about the previous failure in this case. I'm going to close this bug since it appears to have been a transient failure.