SCIENTIFIC-LINUX-USERS Archives

November 2006

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Art Wildman <[log in to unmask]>
Reply To:
Date:
Wed, 29 Nov 2006 01:58:05 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Ioannis Vranos wrote:
> Jaroslaw Polok wrote:
>>
>> There is no standalone program (well, a one that you
>> could run just for this purpose): the rescue
>> functionality is defined in the rescue.py script in
>> anaconda (which does device detection, filesystem label
>> scanning .. etc).
>>
>> You should be able to unmount /mnt/sysimage
>> whether it is in ro or rw mode: but first you will
>> probably need to unmount what is mounted 'below',
>> ie for example:
>>
>> df shows:
>>
>> /dev/mapper/VolGroup00-LogVol00    /mnt/sysimage
>> /dev/hda1                       /mnt/sysimage/boot
>>
>> in above example you will need to unmount /mnt/sysimage/boot
>> before unmounting /mnt.sysimage
>
>
> I unmounted both /mnt/sysimage/boot and /mnt/sysimage/dev, leaving no 
> mount "below" /mnt/sysimage, but still /mnt/sysimage refuses to unmount.
>

I hate to admit that I've done this, but make sure no open console 
(CTRL-ALT-F1-6) shell prompts are in CWD path to /mnt/sysimage  .. cd 
back to the ramdisk. If 'lsof' is on the rescue disk it may be used to 
grep for the path. Also if you chrooted the environment, it will not 
unmount. - GL Art

ATOM RSS1 RSS2