Bug#380010: usb mass storage device: can not plug it and mount it a second time
Package: kernel-image-2.6.8-2-686
Version: 2.6.8-16
when i plug the 1GB usb mass storage device i recently purchased, all seems well: the device is mounted automatically (has a single FAT16 partition that occupyes whole disk), but when i umount it "#umount /dev/sda" then unplug it, and then plug it, it does not mouts automatically, and any attempt to mount or access the device causes the process doing it (
e.g. "dd if=/dev/sda of=contents.raw bs=1k count=1" or "lsusb" or "mount /dev/sda /mnt") to hang and not being killed even by "kill -9 pid".
it happens to me on two computers with debian
3.1 sarge. on the same computers, under windows xp, i can plug the device several times, and works well.
so i can only plug the usb key one time per boot.
below is the (hopefully) relevant output of dmesg:
(...)
eth0: no IPv6 routers present
usb 1-1: new full speed USB device using address 2
usb 1-1: can't set config #1, error -71
usb 1-1: new full speed USB device using address 3
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Model: Rev: 2.00
Type: Direct-Access ANSI SCSI revision: 02
USB Mass Storage device found at 3
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
SCSI device sda: 2040319 512-byte hdwr sectors (1045 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
/dev/scsi/host0/bus0/target0/lun0: unknown partition table
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
usb 1-1: USB disconnect, address 3
usb 1-2: new full speed USB device using address 4
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: Model: Rev: 2.00
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 2040319 512-byte hdwr sectors (1045 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
the first time i plug it, all seems ok, but second time it does not automatically mount, and any apttempt to access it blocks the process.
Reply to: