atroph

Hello I joined since I am having issues as well with a SanDisk USB drive. I went to my local store and purchased another drive and it works as it should. Working: May 23 23:19:41 e-Masheen kernel: [679753.566880] scsi 16:0:0:0: Direct-Access SanDisk Cruzer Glide 1.26 PQ: 0 ANSI: 5 May 23 23:19:41 e-Masheen kernel: [679753.570821] sd 16:0:0:0: [sdd] 7821312 512-byte logical blocks: (4.00 GB/3.72 GiB) May 23 23:19:41 e-Masheen kernel: [679753.573656] sd 16:0:0:0: [sdd] Write Protect is off May 23 23:19:41 e-Masheen kernel: [679753.573668] sd 16:0:0:0: [sdd] Mode Sense: 43 00 00 00 May 23 23:19:41 e-Masheen kernel: [679753.574424] sd 16:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA May 23 23:19:41 e-Masheen kernel: [679753.581464] sd 16:0:0:0: Attached scsi generic sg4 type 0 May 23 23:19:41 e-Masheen kernel: [679753.589343] sdd: sdd1 May 23 23:19:41 e-Masheen kernel: [679753.592927] sd 16:0:0:0: [sdd] Attached SCSI removable disk May 23 23:25:33 e-Masheen kernel: [680105.660864] sdd: detected capacity change from 4004511744 to 0 May 23 23:25:43 e-Masheen kernel: [680115.623203] usb 1-10: USB disconnect, device number 36 Non-Working: May 23 23:39:17 e-Masheen kernel: [680929.329203] scsi 20:0:0:0: Direct-Access SanDisk Firebird 1.07 PQ: 0 ANSI: 2 May 23 23:39:17 e-Masheen kernel: [680929.333701] sd 20:0:0:0: Attached scsi generic sg4 type 0 May 23 23:39:17 e-Masheen kernel: [680929.336552] sd 20:0:0:0: [sdd] 131072 512-byte logical blocks: (67.1 MB/64.0 MiB) May 23 23:39:17 e-Masheen kernel: [680929.338570] sd 20:0:0:0: [sdd] Write Protect is off May 23 23:39:17 e-Masheen kernel: [680929.338582] sd 20:0:0:0: [sdd] Mode Sense: 03 00 00 00 May 23 23:39:17 e-Masheen kernel: [680929.341906] sd 20:0:0:0: [sdd] No Caching mode page present May 23 23:39:17 e-Masheen kernel: [680929.341917] sd 20:0:0:0: [sdd] Assuming drive cache: write through May 23 23:39:17 e-Masheen kernel: [680929.381172] sd 20:0:0:0: ioctl_internal_command return code = 8070000 May 23 23:39:17 e-Masheen kernel: [680929.381177] : Sense Key : Hardware Error [current] May 23 23:39:17 e-Masheen kernel: [680929.381182] : Add. Sense: No additional sense information May 23 23:39:17 e-Masheen kernel: [680929.387629] sd 20:0:0:0: [sdd] No Caching mode page present May 23 23:39:17 e-Masheen kernel: [680929.387634] sd 20:0:0:0: [sdd] Assuming drive cache: write through May 23 23:39:17 e-Masheen kernel: [680929.390995] sdd: unknown partition table May 23 23:39:17 e-Masheen kernel: [680929.394213] sd 20:0:0:0: [sdd] No Caching mode page present May 23 23:39:17 e-Masheen kernel: [680929.394219] sd 20:0:0:0: [sdd] Assuming drive cache: write through May 23 23:39:17 e-Masheen kernel: [680929.394222] sd 20:0:0:0: [sdd] Attached SCSI removable disk May 23 23:39:17 e-Masheen kernel: [680929.437292] sd 20:0:0:0: ioctl_internal_command return code = 8070000 May 23 23:39:17 e-Masheen kernel: [680929.437297] : Sense Key : Hardware Error [current] May 23 23:39:17 e-Masheen kernel: [680929.437301] : Add. Sense: No additional sense information My take is Firebird is a SanDisk internal codename. Similar to a bootstrap or failsafe waiting for a device or program to flash the drive controller hardware. Unfortunately there is no actual hope on the SanDisk forums other than to replace it. The two log files are from identical drives. I tried every trick that I could find to bring this drive to life but it seems as if it needs a firmware load since the device name is not correct. It is interesting that it is readable and not garbage like the firmware is corrupt. My 0.02 is to replace the drive. It would be nice if there was a release from sandisk to flash this device but I don't think their engineering team would ever let that out since some devices use the same chips and the actual disk size is limited by the firmware in the controller.