Dist: RedHat 9; Kernel 2.4.20-8
After a few initial problems, I can now mount and use my Transcend Jetflash USB memory stick under Linux. My problem now, however, lies in disconnecting it. Unmounting goes fine, and causes no errors or problems. On other systems, though (Windows 98+, Mac OS9-X), after the drive has been unmounted (or whatever they call it) the little red LED goes off to indicate that it's no longer in use. Under Linux, though, this doesn't happen.
If I simply unplug it (after unmounting it), I get the following message:
Code:
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host = 0, driver = 08
Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready
sda : block size assumed to be 512 bytes, disk size 1GB.
I/O error: dev 08:00, sector 0
unable to read partition table
The latest from dmesg is:
Code:
usb.c: USB disconnect on device 00:04.2-2 address 2
Device not ready. Make sure there is a disc in the drive.
sda : READ CAPACITY etc, as above
From /var/log/messages:
Code:
Jun 10 20:31:15 localhost kernel: usb.c: USB disconnect on device 00:04.2-2 address 2
Jun 10 20:31:16 localhost kernel: Device not ready. Make sure there is a disc in the drive.
Jun 10 20:31:16 localhost kernel: sda : READ CAPACITY failed.
Jun 10 20:31:16 localhost kernel: sda : status = 1, message = 00, host = 0, driver = 08
Jun 10 20:31:16 localhost kernel: Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready
Jun 10 20:31:16 localhost kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
Jun 10 20:31:16 localhost kernel: sda: I/O error: dev 08:00, sector 0
Jun 10 20:31:16 localhost kernel: I/O error: dev 08:00, sector 0
Jun 10 20:31:16 localhost kernel: unable to read partition table
Jun 10 20:31:16 localhost devlabel: devlabel service started/restarted
I have discovered, by chance, that if I do:
modprobe -r usb-uhci
then the light goes off and I don't get any errors. This doesn't really strike me as a good solution since I can't do this as a non-root user (apart from which it seems like a bit of a hack).
Now despite all of this, there are no errors or problems with the memory stick afterwards. But I'm sure there's a standard way of doing such a thing.