Carl Lowenstein wrote:
On 8/15/07, DJA <[EMAIL PROTECTED]> wrote:
James G. Sack (jim) wrote:
DJA wrote:
Shutdown of a box went fine last night. This morning, booting stopped
with this message:

"Device resource busy while trying to open /dev/hd3. Filesystem mounted
or opened exclusively by another program?"

Fdisk displays the drive and it's partitions as usual.

Partition types are hdc1 boot; hdc2 swap; hdc3 LVM. / (root is on hdc3.

However df shows only the / logical volume. None of the other other
logical volumes (/home, /tmp, /var, /usr/local/) seem to be mounted
which suggests that is what the message is saying.

I've never seen this message before and don't know what to do about it.
Any suggestions?

Hmm, can you boot to Knoppix or some other live CD that supports LVM?

In that environment you may get some useful error messages when trying
to do things like
 pvs
 vgs
 lvs
 and mounting stuff

Regards,
..jim
I found the problem is my bad. I'd just upgraded to FC6. I did a fresh
install so everything was nuked. After the install, I was restoring some
of the data (/home, /usr/local, etc.). I restored the /etc/fstab file.

Therein lies the problem: The current installation is using LVM. The
previous (FC4) did not.

So / gets mounted (LogGroup00-LogVol00) but the other volumes don't. I
can read fstab, mtab, do df, etc. But I cannot edit fstab as the
filesystem is mounted read-only - I only have access through the disk
repair utility (to which I was dropped during the aborted boot process).

How do I repair/replace the incorrect fstab file at this point?


# mount -o remount,rw /

# vi /etc/fstab

    carl

Thanks. I'd already done that. But still couldn't get a clean boot.

That was because, on editing fstab, I used paths to the LVM Logical Volumes as "/dev/mapper/VolGroup00/LogVolnn..." instead of the proper "/dev/VolGroup00/LogVolnn". That because I was using the mount path as shown from within the Disk Repair context. Looking at another box's fstab file straightened me out.

--
   Best Regards,
      ~DJA.


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to