Bug 465460

Created attachment 319360 [details]
anaconda.log

/dev/sda1 vfat mounted under /boot/efi 

I can reproduce reliably on one system at least.

Created attachment 319378 [details]
updates image to determine point of failure

Please try it again with this updates image. It should cause the full exception to be displayed so I can see what is happening instead of the message box.

Alexander, did yoiu have any luck with the updates.img?

Created attachment 320050 [details]
anacdump.txt

Attaching requested file. Traceback is:

Traceback (most recent call first):
  File "/tmp/updates/fsset.py", line 994, in labelDevice
    raise SystemError, "dosfslabel failed on device %s: %s" % (devicePath, msg)
  File "/tmp/updates/fsset.py", line 1048, in migrateFileSystem
    self.labelDevice(entry, chroot)
  File "/tmp/updates/fsset.py", line 1985, in migrateFilesystems
    chroot)
  File "/usr/lib/anaconda/packages.py", line 127, in doMigrateFilesystems
    anaconda.id.fsset.migrateFilesystems (anaconda.rootPath)
  File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext
    self.moveStep()
  File "/usr/lib/anaconda/gui.py", line 1151, in nextClicked
    self.anaconda.dispatch.gotoNext()
  File "/usr/lib/anaconda/iw/progress_gui.py", line 251, in renderCallback
    self.intf.icw.nextClicked()
  File "/usr/lib/anaconda/gui.py", line 1178, in handleRenderCallback
    self.currentWindow.renderCallback()
SystemError: dosfslabel failed on device /tmp/sda1: /boot/efi  



/boot/efi is vfat and is only required on ia64

What do you see on tty5 after the traceback occurs?

I'm connected via serial console so I don't think I can even get to tty5. If you tell me which file it's written to I will attach it.

First, let me say that I don't see how this could possibly depend on encryption in any way.

Unfortunately, the tty5 messages do not get written to a file.

Martin, assigned to you since you are located near the IA64 box. Can you please work on this Monday ASAP with atodorov?

After some poking around, we figured what causes the error message.. we are still not sure what causes the underlying error though.

(the logs are not part of the tree, use updates image below)

updates image to add more verbosity (and to see the traceback):
http://msivak.fedorapeople.org/anaconda/label.img

relevant parts of the anaconda.log:
14:46:34 DEBUG   : Launching <fsset.FATFileSystem instance at 0x2000000002a6fcf8
  fsystem: vfat format: 0                                                       
  ismounted: 1  options: 'defaults'                                             
  bytesPerInode: 4096 label: /boot/efi                                          
 /mnt/sysimage                             

14:46:34 DEBUG   : Launching dosfslabel /tmp/sda1 /boot/efi1                    
14:46:34 DEBUG   : Result of dosfslabel /tmp/sda1 /boot/efi1 is 1               
14:46:34 ERROR   : dosfslabel failed on device /tmp/sda1: /boot/efi1

anacdump.txt:
see the traceback above, it is identical

pieces and bit from playing with the vt2 console:
sh-3.2# dosfslabel /tmp/sda1 /boot/efi1         
sh-3.2# echo $?                                 
1
sh-3.2# dosfslabel /tmp/sda1           
/boot/efi1 

sh-3.2# parted  /dev/sda -l   

Model: HP 146 G MAX3147NC (scsi)
Disk /dev/sda: 147GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End    Size   File system  Name  Flags
 1      17.4kB  105MB  105MB  fat16              boot 
 2      105MB   147GB  147GB                     lvm

*** Bug 467812 has been marked as a duplicate of this bug. ***

Ryan, I added a release note that is only going to be needed for the Beta.

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:
In the RHEL 5.3 Beta release, an upgrade from an earlier version of RHEL 5 to the Beta will fail with the error:

"An error occurred trying to migrate sda1.  This problem is serious and the
install cannot continue"

This problem will be fixed in the next Beta update.

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,6 +1,6 @@
-In the RHEL 5.3 Beta release, an upgrade from an earlier version of RHEL 5 to the Beta will fail with the error:
+In the Red Hat Enterprise Linux 5.3 Beta release, an upgrade from an earlier version of Red Hat Enterprise Linux 5 to the Beta will fail with the error:
 
 "An error occurred trying to migrate sda1.  This problem is serious and the
 install cannot continue"
 
-This problem will be fixed in the next Beta update.+This issue will be fixed in the next Beta update.

*** Bug 468784 has been marked as a duplicate of this bug. ***

This is fixed by 468162, Stefan's update of the dosfstools package. But in order to reference this in the errata and more accurately reflect the actual problem, we would like to mark this as a blocker.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0164.html