Bug 2920 - "mount failed: Device or resource busy" during installation
"mount failed: Device or resource busy" during installation
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.0
i386 Linux
high Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-18 22:23 EDT by Jason Bucata
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-07-07 11:30:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jason Bucata 1999-05-18 22:23:49 EDT
This bug, reported as a comment by noah@ecn.purdue.edu to
bug #2142, has occurred to me as well.
Comment 1 Anonymous 1999-05-18 23:05:59 EDT
I tried removing my /boot partition from /etc/fstab altogether,
placing boot files in the boot directory under / (where the partition
had once been mounted).  This didn't change anything; I still get the
error.  I have a *lot* of other partitions; I don't want to have to
somehow remove all of them to get this upgrade to work (if it came to
that, I'd take the opportunity to repartition anyhow, and do a
complete reinstall).
Comment 2 Jay Turner 1999-05-19 10:24:59 EDT
It is not possible to perform a hard drive installation/upgrade to the
same partition that the source files are located in, otherwise you
will receive the error that is described in this posting.
Comment 3 Anonymous 1999-06-02 00:39:59 EDT
If by "source files" you mean the RPMs, I'm upgrading from a Linux
Central CD-ROM with a boot floppy.  I'm not doing a hard drive
install.
Comment 4 Anonymous 1999-06-02 01:22:59 EDT
I looked back at the original comment, and yes, it appears that that
problem was from a hard drive install (and therefore yet another
duplicate of bug 2504, reported several times here).  This one isn't,
however.
Comment 5 Anonymous 1999-06-10 01:30:59 EDT
I tried it again, and when I got to the point where it complained, I
went over to bash, and I simply ran "umount /mnt" (where /dev/hda6 had
been mounted), and it worked fine after that.
Comment 6 Jay Turner 1999-07-07 11:30:59 EDT
*** This bug has been marked as a duplicate of 2504 ***

Note You need to log in before you can comment on or make changes to this bug.