Weird mount problem

[Christoph Georgi]

Maybe try

$ ls -L /dev | grep hd

to see whether the hdds are availible or not, if you haven't done so 
before. Maybe some permissions in the /dev folder are crooked?! Another 
thing that does not become clear from your command: are you sudoing the 
mount command?

You could also try and mount you drives in the single user mode first, 
as there really shouldn't be anything making the /mnt dir busy..

Just another few trivial ideas..

.christoph

Bob Nielsen wrote:
> On Sun, Feb 20, 2005 at 01:18:43PM -0500, Ron Peterson wrote:
> 
>>On Sun, Feb 20, 2005 at 08:24:04AM -0800, Bob Nielsen wrote:
>>
>>>On Sun, Feb 20, 2005 at 07:51:38AM +0000, Sean Miller wrote:
>>>
>>>>rpowersau at gmail.com wrote:
>>>>
>>>>
>>>>>Why hdb2? Have you tried hdb0, hdb1, ...?
>>>>>
>>>>>
>>>>
>>>>One thing you haven't told us is the mount command you are trying to use...
>>>
>>>mount -t ext3 /dev/hdb2 /mnt
>>>
>>>
>>>>If it's mount /dev/hda2 /mnt it is not going to work, because /mnt is 
>>>>not a mountpoint; it is a directory too high.
>>>
>>>Actually it is a mount point, since there were no directories or files 
>>>below that point.
>>
>>Anyplace is a mount point, the mount will just hide anything beneath it.
>>
>>
>>>There is a Win 98SE (fat32) partition at /dev/hdb1 and I get the same 
>>>error when trying to mount it:
>>>
>>>$ sudo mount -t vfat /dev/hdb1 /mnt
>>>mount: /dev/hdb1 already mounted or /mnt busy
>>
>>Make sure you're not cd'd into the directory somewhere..
>>
>>Have you tried using fuser or lsof to see what processes may be using
>>the directory?  e.g.
>>
>>fuser /mnt
>>lsof +D /mnt
> 
> 
> Neither of these commands report any results.   I am not a newbie (using 
> Linux for >10 years), but I have never seen anything like this before.
> 
> Bob
> 
>