Hi all, While I was testing kernel 2.6.30-rc2, I lost one of my USB sticks. The stick is no longer usable in any machine, all I get is "sdb: unknown partition table". So apparently the partition table was corrupted by the problem I hit. Here is what the logs have to say about what happened: Apr 17 10:48:16 hyperion kernel: usb 2-2.2: new full speed USB device using uhci_hcd and address 3 Apr 17 10:48:16 hyperion kernel: usb 2-2.2: not running at top speed; connect to a high speed hub Apr 17 10:48:16 hyperion kernel: usb 2-2.2: configuration #1 chosen from 1 choice Apr 17 10:48:16 hyperion kernel: Initializing USB Mass Storage driver... Apr 17 10:48:16 hyperion kernel: scsi4 : SCSI emulation for USB Mass Storage devices Apr 17 10:48:16 hyperion kernel: usbcore: registered new interface driver usb-storage Apr 17 10:48:16 hyperion kernel: USB Mass Storage support registered. Apr 17 10:48:16 hyperion kernel: usb-storage: device found at 3 Apr 17 10:48:16 hyperion kernel: usb-storage: waiting for device to settle before scanning Apr 17 10:48:21 hyperion kernel: scsi 4:0:0:0: Direct-Access USB007 mini-USB2BU 0.00 PQ: 0 ANSI: 2 Apr 17 10:48:21 hyperion kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0 Apr 17 10:48:21 hyperion kernel: usb-storage: device scan complete Apr 17 10:48:21 hyperion kernel: sd 4:0:0:0: [sdb] 2015231 512-byte hardware sectors: (1.03 GB/983 MiB) Apr 17 10:48:21 hyperion kernel: sd 4:0:0:0: [sdb] Write Protect is off Apr 17 10:48:21 hyperion kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 00 00 00 Apr 17 10:48:21 hyperion kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through Apr 17 10:48:21 hyperion kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through Apr 17 10:48:21 hyperion kernel: sdb: sdb1 Apr 17 10:48:21 hyperion kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk Apr 17 10:48:25 hyperion hald: mounted /dev/sdb1 on behalf of uid 501 Apr 17 10:50:41 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:50:41 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:50:41 hyperion kernel: File system has been set read-only Apr 17 10:50:41 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:50:41 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:50:46 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:50:46 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:50:46 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:50:46 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:50:50 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:50:50 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:50:50 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:50:50 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:50:50 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:50:50 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:50:50 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:50:50 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:50:51 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:50:51 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:50:51 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:50:51 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:51:06 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:51:06 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:51:06 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:51:06 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:51:06 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:51:06 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:51:06 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:51:06 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:51:06 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:51:06 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:51:06 hyperion kernel: FAT: Filesystem panic (dev sdb1) Apr 17 10:51:06 hyperion kernel: fat_get_cluster: invalid cluster chain (i_pos 0) Apr 17 10:51:11 hyperion kernel: sd 4:0:0:0: [sdb] Unhandled sense code Apr 17 10:51:11 hyperion kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 17 10:51:11 hyperion kernel: sd 4:0:0:0: [sdb] Sense Key : Data Protect [current] Apr 17 10:51:11 hyperion kernel: sd 4:0:0:0: [sdb] Add. Sense: Write protected Apr 17 10:51:11 hyperion kernel: end_request: I/O error, dev sdb, sector 161 Apr 17 10:51:11 hyperion kernel: Buffer I/O error on device sdb1, logical block 98 Apr 17 10:51:11 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:11 hyperion kernel: sd 4:0:0:0: [sdb] Device not ready Apr 17 10:51:11 hyperion kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 17 10:51:11 hyperion kernel: sd 4:0:0:0: [sdb] Sense Key : Not Ready [current] Apr 17 10:51:11 hyperion kernel: sd 4:0:0:0: [sdb] Add. Sense: Medium not present Apr 17 10:51:11 hyperion kernel: end_request: I/O error, dev sdb, sector 407 Apr 17 10:51:11 hyperion kernel: Buffer I/O error on device sdb1, logical block 344 Apr 17 10:51:11 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:12 hyperion kernel: sd 4:0:0:0: [sdb] 2015231 512-byte hardware sectors: (1.03 GB/983 MiB) Apr 17 10:51:12 hyperion hald: unmounted /dev/sdb1 from '/media/disk' on behalf of uid 0 Apr 17 10:51:12 hyperion kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Unhandled sense code Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Sense Key : Data Protect [current] Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Add. Sense: Write protected Apr 17 10:51:25 hyperion kernel: end_request: I/O error, dev sdb, sector 166 Apr 17 10:51:25 hyperion kernel: Buffer I/O error on device sdb1, logical block 103 Apr 17 10:51:25 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Device not ready Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Sense Key : Not Ready [current] Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Add. Sense: Medium not present Apr 17 10:51:25 hyperion kernel: end_request: I/O error, dev sdb, sector 159 Apr 17 10:51:25 hyperion kernel: Buffer I/O error on device sdb1, logical block 96 Apr 17 10:51:25 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:25 hyperion kernel: Buffer I/O error on device sdb1, logical block 97 Apr 17 10:51:25 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:25 hyperion kernel: Buffer I/O error on device sdb1, logical block 98 Apr 17 10:51:25 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:25 hyperion kernel: Buffer I/O error on device sdb1, logical block 99 Apr 17 10:51:25 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Device not ready Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Sense Key : Not Ready [current] Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Add. Sense: Medium not present Apr 17 10:51:25 hyperion kernel: end_request: I/O error, dev sdb, sector 167 Apr 17 10:51:25 hyperion kernel: Buffer I/O error on device sdb1, logical block 104 Apr 17 10:51:25 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:25 hyperion kernel: Buffer I/O error on device sdb1, logical block 105 Apr 17 10:51:25 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:25 hyperion kernel: Buffer I/O error on device sdb1, logical block 106 Apr 17 10:51:25 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:25 hyperion kernel: Buffer I/O error on device sdb1, logical block 107 Apr 17 10:51:25 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:25 hyperion kernel: Buffer I/O error on device sdb1, logical block 108 Apr 17 10:51:25 hyperion kernel: lost page write due to I/O error on sdb1 Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Device not ready Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Sense Key : Not Ready [current] Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Add. Sense: Medium not present Apr 17 10:51:25 hyperion kernel: end_request: I/O error, dev sdb, sector 174 Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Device not ready Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Sense Key : Not Ready [current] Apr 17 10:51:25 hyperion kernel: sd 4:0:0:0: [sdb] Add. Sense: Medium not present Apr 17 10:51:25 hyperion kernel: end_request: I/O error, dev sdb, sector 180 Apr 17 10:51:55 hyperion kernel: usb 2-2.2: reset full speed USB device using uhci_hcd and address 3 Apr 17 10:51:58 hyperion kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through Apr 17 10:51:58 hyperion kernel: sdb: unknown partition table This happened as I was asking Thunar (Xfce's file manager) the properties of the USB stick. So it was counting all the files and there were a lot of them (about 8500 if memory serves). As the stick isn't mine, I have no idea if the file count was correct or not. I remember that the cumulative size looked plain wrong to me, something like 400 GB while the stick is supposed to be 1 GB total. I would also like to mention that my system had been hit by bug #13135 one hour before that. I have no idea if this may be related or not: http://bugzilla.kernel.org/show_bug.cgi?id=13135 Andrew Morton seems to think that one is a false positive, so probably it isn't related, but I thought I'd mention it just in case. I presume that the USB stick might just have been defective, either physically or at the filesystem level... It isn't mine, so I can't tell much about this. But in any case I find it weird that I ended up losing the partition table due to these errors. -- Jean Delvare -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
