Self-filing on behalf of Lau Wee Lip Jonathan <firstname.lastname@example.org>.
USB disk stopped working after an upgrade to 2.4.18-5.
usb.c: USB disconnect on device 2
printer.c: usblp0: removed
hub.c: USB new device connect on bus1/1, assigned device number 4
usb.c: USB device 4 (vend/prod 0xdbf/0x300) is not claimed by any active
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi2 : SCSI emulation for USB Mass Storage devices
usb-uhci.c: interrupt, status 3, frame# 1156
Vendor: ST313620 Model: A Rev: 3.07
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
SCSI device sdb: 26692776 512-byte hdwr sectors (13667 MB)
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4
USB Mass Storage support registered.
Device not ready. Make sure there is a disc in the drive.
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host = 0, driver = 08
Current sd00:00: sense key Not Ready
Additional sense indicates Medium not present
sda : block size assumed to be 512 bytes, disk size 1GB.
sda: I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
unable to read partition table
Observe that the media is not actually removable.
The sense may be faked by usb-storage.
Created attachment 65887 [details]
The boot-up dmesg
Thought I fixed it for bug 84814? Closing.
I see this with kernel-2.4.21-20.1.2024.2.1.nptl of Severn when I use usb-key.
The workaround is to do "rmmod usb-storage" after umount and before physical
disconnection of the device.