Bug 467202

What do you see on tty5? And what happens if you run 'cryptsetup isLuks /dev/sdb3' and 'cryptsetup isLuks /dev/sda4' on tty2?

This is on ia64 again, right?

(In reply to comment #1)
> This is on ia64 again, right?

Yes, ia64.


Strange enough this time I was asked for the pass phrase for all 3 block devices in this order: sda4, sdb3, md0. Only sdb3 which is encrypted vfat seems to have problems. The UI shows it as foreign and the logs says:

sh-3.2# grep sdb3 /tmp/anaconda.log 
07:33:23 INFO    : going to get passphrase for encrypted device sdb3
07:33:28 INFO    : mapping LUKS device sdb3 to luks-53f794eb-6cf5-44ad-8095-b15555bf3e46
07:33:36 INFO    : mapping LUKS device sdb3 to luks-53f794eb-6cf5-44ad-8095-b15555bf3e46
07:33:45 INFO    : mapping LUKS device sdb3 to luks-53f794eb-6cf5-44ad-8095-b15555bf3e46
07:33:45 DEBUG   : sdb3 is encrypted; filesystem is 'None'

Still seeing this issue with all PVs encrypted and only lv_swap encrypted. Entering pass phrase & selecting "global pass phrase" shows all LVs as foreign.

So you have seen two different behaviors (comment #2 being the second). Any ideas what the differentiating factor is?

I was able to reproduce the behavior in comment #2. All LVM devices appear as they should, but the vfat device shows as foreign. The vfat is on sda2. sda3 is an encrypted PV containing an encrypted swap LV and two unencrypted ext3 LVs. I will investigate the vfat showing as foreign since that's the only part I can reproduce.

I am still working on a solution, but here's a quick update: the problem is that in RHEL5 we have only one way to detect a vfat filesystem, and that is via parted. The problem is that you cannot pass an arbitrary device to these parted methods and since the device that parted knows about is encrypted it cannot detect the vfat fs. I am looking now for potential solutions.

It looks like a fix for this is going to take more effort than is justifiable for encrypted vfat. A potential release note blurb could read something like:

  Pre-existing encrypted block devices containing vfat filesystems will
  appear as type 'foreign' in the partitioning interface. If you want
  the device to be mounted automatically during system boot, you will
  have to manually add an entry to /etc/fstab."

There is a section describing this in the installation guide that might be worth referencing. I don't know what the final URL will be, but here is a link to the content:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/ch28s04s07.html

Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
Pre-existing encrypted block devices containing vfat filesystems will appear as type 'foreign' in the partitioning interface and will not be mounted automatically during system boot. To causes such devices to be mounted automatically, manually add an entry to /etc/fstab."

Note to Ryan: 
There is a section describing this in the installation guide that might be
worth referencing. I don't know what the final URL will be, but here is a link
to the content:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/ch28s04s07.html

thanks Denise. added to RHEL5.3 release notes.

Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1,8 +1 @@
-Pre-existing encrypted block devices containing vfat filesystems will appear as type 'foreign' in the partitioning interface and will not be mounted automatically during system boot. To causes such devices to be mounted automatically, manually add an entry to /etc/fstab."
+Existing encrypted block devices that contain vfat file systems will appear as type 'foreign' in the partitioning interface; as such, these devices will not be mounted automatically during system boot. To ensure that such devices are mounted automatically, add an appropriate entry for them to /etc/fstab. For details on how to do so, refer to man fstab.-
-Note to Ryan: 
-There is a section describing this in the installation guide that might be
-worth referencing. I don't know what the final URL will be, but here is a link
-to the content:
-
-http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/ch28s04s07.html