[Sussex] Unable to umount - device is busy

Colin Tuckley colin at tuckley.org
Wed Feb 7 09:00:13 UTC 2007


Fay Zee wrote:
> I rebboted and now:
> 
> # mount /media/kingston/
> mount: /dev/sda1 is not a valid block device
> # mount /dev/sdb1
> mount: /dev/sdb1 is not a valid block device

Is that with *TWO* USB devices plugged in?

I think you are misunderstanding how USB devices are allocated. It is *not*
slot dependent, the devices are created dynamically when the drive is
plugged in.

So the first one will always be /dev/sda1 no matter which USB socket it's
put in and /dev/sdb1 will only exist when you plug a second one in.

If you run dmesg after plugging each one in you will see messages about it
finding the drive and allocating the device for it.

If you get a device busy when trying to umount it then try running lsof +L1
as root and see which files are busy.

Colin

-- 
Colin Tuckley      |  colin at tuckley.org  |  PGP/GnuPG Key Id
+44(0)1903 236872  |  +44(0)7799 143369  |     0x1B3045CE

A door is what a cat is perpetually on the wrong side of. - adapted from
Ogden Nash




More information about the Sussex mailing list