Bug 627789

Problem was a race between unmounting the iso and deactivating the loopback. mount can now handle mounting iso's with loop without needing losetup.

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

Still persist in Beta RC2 and the same error (Device or resource Busy).

Adding as a F14Blocker, this prevents you from using livecd-iso-to-disk to make usb install media with non-live-cd iso's as covered by 3.2.2.1.2. Making Fedora USB Media with livecd-tools

(In reply to comment #4)
> Adding as a F14Blocker, this prevents you from using livecd-iso-to-disk to make
> usb install media with non-live-cd iso's as covered by 3.2.2.1.2. Making Fedora
> USB Media with livecd-tools

I meant F14Beta, not F14Blocker

jlaska and I agree that this is at least nice-to-have, though we're not sure about blockeriness. Please include the fix in the next anaconda build for Beta. Thanks!

This bug is not mentioned in the list of bugs fixed in the latest anaconda build:

https://admin.fedoraproject.org/updates/anaconda-14.17.4-1.fc14

It appears to be the only bug blocking the Beta at the moment (if I understand the criteria).

yeah, it appears the fix was missed (intentionally or not we're not sure). this is not an AcceptedBlocker, though, and jlaska and I provisionally classed it as a nice-to-have.

BTW, It'll block F14 (release) since it prevents hard disk install.

Log files would always be nice.

IIRC it doesn't log anything (or if it does, nothing useful). Next time I hit it I'll look to make sure.

(In reply to comment #9)
> BTW, It'll block F14 (release) since it prevents hard disk install.

Note, I completed a hard disk ISO install several times on F-14-Beta without trouble.  This issue doesn't appear to block that installation case.

Look at bug #634940. It just didn't work from Fedora Alpha to Beta RC2 for me.

This was discussed at the go/no-go meeting today. We have no specific criteria covering iso-to-usb functionality, but we discussed it on merit, and agreed it wasn't a Beta blocker, though we may wish to make it a Final blocker. Putting on the final blocker list for further review.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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

This is what had hit me with F14 RC3 i386. After the "Device or resource busy" dialog, the installer automatically enabled a stale http base repo with old packages, and I didn't pay attention to that or the actual package installation step.

(In reply to comment #16)
> This is what had hit me with F14 RC3 i386. After the "Device or resource busy"
> dialog, the installer automatically enabled a stale http base repo with old
> packages, and I didn't pay attention to that or the actual package installation
> step.

Are you able to upload /tmp/anaconda.log when you encounter this error?

Created attachment 449481 [details]
Anaconda log up to error dialog

Not sure that's helpful as the last lines don't tell anything about the loop-mounted image.

Created attachment 449482 [details]
logs

This is fixed in commits 7fefb17c908c1bb6b0fbac1daddc770855d2d568 and 11c71a20afc87d5a1c43ed56c281cfe30bdfe6c6, it just barely missed making it into Beta, but should be included in the final release.

For anything hitting this problem in F-14-Beta, bcl has created an updates.img to work around this problem.  The image is available at http://bcl.fedorapeople.org/updates/627789.img

For information on using an updates.img, please see https://fedoraproject.org/wiki/Anaconda/Updates

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

Seems to be fixed for me (however, if you go forward and them come back and then try to go forward again, it says "error mounting an already mounted iso" during a hard disk installation, but its a different bug).

Well, I was wrong! When I run the installer using KVM on my system, the error doesn't appear and I can select the packages to install. But when I run the installer after boot, I still receive the "Device or resource busy" error before the repository selection dialog.
(I've put the updated image file in the images directory in hard disk beside F14 beta RC3 iso. I put 2 copies, one with 627789.img name and another copy with update.img name)

Oops, sorry. I renamed update.img to updates.img and made sure that it is really applied during installer bootup.
This time, instead of the "Device or resource busy" error I got an exception! But I didn't saved the exception in a proper place. I'll reproduce the error and attach the exception in a few hours.

I encountered this bug when installing F14-beta-rc3 with repo=nfsiso: (the nfs directory contained multiple isos). 

After I applied the updates image on comment#21, I can retrieve the repo successfully.

With updates.img no bug for me anymore.

I tried again and this time the exception didn't occur. Anyway, at least the "Device or resource busy" bug is solved for me too.

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

The mentioned updates.img fixes this.

The updates.img did indeed fix my problem from bug 638788.

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

Is there an official build and bodhi update that addresses this issue?

we have the acceptance test run due tomorrow: it would be good to have anaconda 14.18 available to do that test run with.

dlehman built it last night

Brian, you had the most consistent reproducer, are you still seeing this?

Moving to ON_QA as this is available for testing (see https://admin.fedoraproject.org/updates/anaconda-14.19-1.fc14)

(In reply to comment #37)
> Moving to ON_QA as this is available for testing (see
> https://admin.fedoraproject.org/updates/anaconda-14.19-1.fc14)

Yes, works fine for me with the netinst.iso image using anaconda-14.18

Verified it fixed in anaconda 14.19.

14.22 is in stable.