The following was filed automatically by anaconda: anaconda 11.5.0.59-1.fc11 exception report Traceback (most recent call first): File "/usr/lib/anaconda/livecd.py", line 96, in copytree raise Error, errors File "/usr/lib/anaconda/livecd.py", line 292, in _doFilesystemMangling flags.selinux) File "/usr/lib/anaconda/livecd.py", line 349, in doPostInstall self._doFilesystemMangling(anaconda) File "/usr/lib/anaconda/backend.py", line 285, in doPostInstall anaconda.backend.doPostInstall(anaconda) File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/text.py", line 712, in run anaconda.dispatch.gotoNext() File "/usr/sbin/anaconda", line 965, in <module> anaconda.intf.run(anaconda) Error: [('/mnt/sysimage//boot/elf-memtest86+-2.11', '/mnt/sysimage/mnt//boot/elf-memtest86+-2.11', '[Errno 61] No data available'), ('/mnt/sysimage//boot/config-2.6.29.6-217.2.8.fc11.i586', '/mnt/sysimage/mnt//boot/config-2.6.29.6-217.2.8.fc11.i586', '[Errno 61] No data available'), ('/mnt/sysimage//boot/vmlinuz-2.6.29.6-217.2.8.fc11.i586', '/mnt/sysimage/mnt//boot/vmlinuz-2.6.29.6-217.2.8.fc11.i586', '[Errno 61] No data available'), ('/mnt/sysimage//boot/efi/EFI/redhat/grub.efi', '/mnt/sysimage/mnt//boot/efi/EFI/redhat/grub.efi', '[Errno 61] No data available'), '/mnt/sysimage//boot/efi/EFI/redhat', '/mnt/sysimage/mnt//boot/efi/EFI/redhat', 'No data available', '/mnt/sysimage//boot/efi/EFI', '/mnt/sysimage/mnt//boot/efi/EFI', 'No data available', '/mnt/sysimage//boot/efi', '/mnt/sysimage/mnt//boot/efi', 'No data available', ('/mnt/sysimage//boot/memtest86+-2.11', '/mnt/sysimage/mnt//boot/memtest86+-2.11', '[Errno 61] No data available'), ('/mnt/sysimage//boot/System.map-2.6.29.6-217.2.8.fc11.i586', '/mnt/sysimage/mnt//boot/System.map-2.6.29.6-217.2.8.fc11.i586', '[Errno 61] No data available'), ('/mnt/sysimage//boot/grub/splash.xpm.gz', '/mnt/sysimage/mnt//boot/grub/splash.xpm.gz', '[Errno 61] No data available'), '/mnt/sysimage//boot/grub', '/mnt/sysimage/mnt//boot/grub', 'No data available']
Created attachment 358534 [details] Attached traceback automatically from anaconda.
My additional information. Steps to reproduce: 1. Run as root: "livecd-creator --config=/usr/share/doc/livecd-tools-024/livecd-fedora-server-cepreu.ks --fslabel=livecd-fedora-server-cepreu". Where is livecd-fedora-server-cepreu.ks look in attachment. 2. Create hdd image: "qemu-img create hddserver.img 4G". 3. Run from this image: "qemu-kvm -hda hddserver.img -cdrom livecd-fedora-server-cepreu.iso -boot d -m 256 -net nic -net user". 4. When virtual machine is booted, login as root and type "liveinst" in console. 5. Try to install. Because you can't create cutom disk layout, you can choose any other type in menu (eq. "Use entire disk", "Use free space" etc.). In any causes installation failed with error. But sometimes with different from this described error. This bug appers not only on virtual machine, but many times in real machines in my practice (fedora 11 always). So i found workaround for this bug. When choose "--fstype ext" in creating livecd, create custom layout with one ext3 partition for root filesystem (without /boot partition), install in this cause works normally. But in text install impossible to create custom layout, so this problem become very important for me.
Created attachment 358539 [details] Kickstart file, which was used to creating livecd
I'm a little confused about your partitioning scheme. In the attached kickstart file, you have: part / --size 3072 --fstype ext4 Is this the layout that works? In your description, you mention something about --fstype=ext. That's never going to work, because the original ext filesystem doesn't have support for the extended attributes required by selinux. Could you please explain what filesystem layout works vs. what layout causes this error?
Sorry, "--fstype ext3" i mean, just typing mistake. Work with layout when root filesystem on ext3 partition and /boot directory also on that partition. Do not work with layout when root fs is ext4/3 (does not matter) and /boot-directory is mountpoint for small partition "boot" in ext3.
What happens if you leave out selinux --disabled and just let it go with the defaults? I think the "no data available" is related to that.
If i use option "selinux --enforcing", which default in all kickstart files from spin-kickstarts, livecd just can't create. I think it because selinux disabled on my machine.
*** This bug has been marked as a duplicate of bug 508345 ***