Red Hat Bugzilla – Bug 154480
ppc nfs install fails says "this directory does not appear to contain a Fedora Core installation tree"
Last modified: 2007-11-30 17:11:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)
Description of problem:
When trying to do an nfs install of FC4-test1-ppc on an imac 333, I get the following error:
this directory does not appear to contain a Fedora Core installation tree
In looking at the other ttys I can see that it mounted my nfs directory on /mnt/source
then the lines go like this:
unable to access /mnt/source/Fedore/base/stage2.img
mntloop loop7 on /tmp/loopimage as /mnt/source/FC4-test1-ppc-disc1.iso fd is 27
mntloop loop0 on /mnt/runtime as /tmp/loopimage/Fedora/base/fdstg2.img fd is 27
unmounting loopback /tmp/runtime loop0
LOOP_CLR_FD failed for /tmp/runtime loop0 (Device or resource busy)
unmounting loopback /tmp/loopimage loop7
LOOP_CLR_FD failed for /tmp/loopimage loop7 (Device or resource busy)
Path to balid iso is /mnt/source/FC4-test1-ppc-disc1.iso
mntloop loop1 on /mnt/source2 as /mnt/source/FC4-test1-ppc-disc1.iso fd is 26
mntloop loop0 on /mnt/runtime as /tmp/loopimage/Fedora/base/stage2.img fd is 26
LOOP_SET_FD failed: Device or resource busy
unmounting loopback /tmp/source2 loop1
The directory contains all the binary ISOs and the SHA1SUM file
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Begin an nfs install on the ppc
2. nfs install fails to start with the error specified.
Was this with an exploded tree, or just exported NFS of the ISOs? If it was the
latter, there was a bug that caused said issue. If it was an exploded tree (i.e.
your nfs mount had:
autorun headers RPM-GPG-KEY-beta
boot_image images RPM-GPG-KEY-fedora
etc ppc RPM-GPG-KEY-fedora-rawhide
eula.txt README-Accessibility RPM-GPG-KEY-fedora-test
Fedora repodata RPM-GPG-KEY-rawhide
GPL RPM-GPG-KEY yumgroups.xml
) then this bug is new.
It was just the ISOs. I'll give it a try tonight with the ISOs from test2.
*** This bug has been marked as a duplicate of 150887 ***