Dear Group, I have an apparently dead USB key. This was last used on a windows box (xp or newer) at Victoria University. It was correctly unmounted but now appears to be dead. Plug it in and the light flashes for ever but won't mount on two Linux systems Ubuntu (Natty and Precise) or a windows 7 box. The following is the best I can find are there any other suggestions on how to recover this. Most if not all of the files are backed up I just want to learn more about how to recover files or format the key so I can reuse it. stripes@stripes-desktop:~$ lsusb Bus 008 Device 004: ID 413c:2011 Dell Computer Corp. Multimedia Pro Keyboard Bus 008 Device 003: ID 413c:1005 Dell Computer Corp. Multimedia Pro Keyboard Hub Bus 008 Device 002: ID 046d:c063 Logitech, Inc. Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 004: ID 048d:1168 Integrated Technology Express, Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0924:3cf0 Xerox Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub stripes@stripes-desktop:~$ tail -f /var/log/messages Aug 3 14:09:36 joanna-desktop gnome-screensaver-dialog: pam_sm_authenticate: username = [joanna] Aug 3 14:09:36 joanna-desktop gnome-screensaver-dialog: pam_sm_authenticate: /home/joanna is already mounted Aug 3 14:10:00 joanna-desktop kernel: [ 9693.808014] usb 2-2: new high speed USB device using ehci_hcd and address 4 Aug 3 14:10:00 joanna-desktop kernel: [ 9693.987092] Initializing USB Mass Storage driver... Aug 3 14:10:00 joanna-desktop kernel: [ 9693.987197] scsi4 : usb-storage 2-2:1.0 Aug 3 14:10:00 joanna-desktop kernel: [ 9693.987388] usbcore: registered new interface driver usb-storage Aug 3 14:10:00 joanna-desktop kernel: [ 9693.987389] USB Mass Storage support registered. Aug 3 14:10:01 joanna-desktop kernel: [ 9694.988476] scsi 4:0:0:0: Direct-Access XXXXXXXX U168CONTROLLER 0.00 PQ: 0 ANSI: 2 Aug 3 14:10:01 joanna-desktop kernel: [ 9694.988914] sd 4:0:0:0: Attached scsi generic sg2 type 0 Aug 3 14:10:01 joanna-desktop kernel: [ 9694.991332] sd 4:0:0:0: [sdb] Attached SCSI removable disk stripes@stripes-desktop:~$ sudo fdisk -l [sudo] password for joanna: Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00087384 Device Boot Start End Blocks Id System /dev/sda1 * 1 7305 58670012+ 7 HPFS/NTFS /dev/sda2 7305 19458 97618945 5 Extended /dev/sda5 7305 18958 93604864 83 Linux /dev/sda6 18958 19458 4013056 82 Linux swap / Solaris stripes@stripes-desktop:~$ dmesg | grep usb [ 4.199275] usbcore: registered new interface driver usbfs [ 4.199275] usbcore: registered new interface driver hub [ 4.199275] usbcore: registered new device driver usb [ 5.102585] usb 1-4: new high speed USB device using ehci_hcd and address 2 [ 5.644015] usb 8-1: new low speed USB device using uhci_hcd and address 2 [ 5.830254] usbcore: registered new interface driver hiddev [ 5.845557] input: DELL DELL USB Laser Mouse as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/input/input2 [ 5.845636] generic-usb 0003:046D:C063.0001: input,hidraw0: USB HID v1.10 Mouse [DELL DELL USB Laser Mouse] on usb-0000:00:1d.2-1/input0 [ 5.845652] usbcore: registered new interface driver usbhid [ 5.845653] usbhid: USB HID core driver [ 6.060043] usb 8-2: new full speed USB device using uhci_hcd and address 3 [ 6.525105] usb 8-2.1: new low speed USB device using uhci_hcd and address 4 [ 6.707479] input: Dell Dell Multimedia Pro Keyboard as /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2.1/8-2.1:1.0/input/input3 [ 6.707526] generic-usb 0003:413C:2011.0002: input,hidraw1: USB HID v1.10 Keyboard [Dell Dell Multimedia Pro Keyboard] on usb-0000:00:1d.2-2.1/input0 [ 6.758162] input: Dell Dell Multimedia Pro Keyboard as /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2.1/8-2.1:1.1/input/input4 [ 6.758224] generic-usb 0003:413C:2011.0003: input,hidraw2: USB HID v1.10 Device [Dell Dell Multimedia Pro Keyboard] on usb-0000:00:1d.2-2.1/input1 [ 15.703664] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x0924 pid 0x3CF0 [ 15.703856] usbcore: registered new interface driver usblp [ 16.942996] usb 1-4: usbfs: interface 0 claimed by usblp while 'usb' sets config #1 [ 9693.808014] usb 2-2: new high speed USB device using ehci_hcd and address 4 [ 9693.987197] scsi4 : usb-storage 2-2:1.0 [ 9693.987388] usbcore: registered new interface driver usb-storage Thanks in advance for any suggestions. All the best Stripes
On 3 August 2012 14:24, stripes theotoky <stripes.theotoky@googlemail.com>wrote:
Dear Group,
I have an apparently dead USB key.
This was last used on a windows box (xp or newer) at Victoria University. It was correctly unmounted but now appears to be dead. Plug it in and the light flashes for ever but won't mount on two Linux systems Ubuntu (Natty and Precise) or a windows 7 box. The following is the best I can find are there any other suggestions on how to recover this. Most if not all of the files are backed up I just want to learn more about how to recover files or format the key so I can reuse it.
Have you tried testdisk/photorec? They should be available as packages. -- Colin Fee tfeccles@gmail.com
On 03/08/2012, at 2:38 PM, Colin Fee wrote:
Have you tried testdisk/photorec? They should be available as packages.
As you can see from the O.P.'s output, the drive (sdb) does not appear in fdisk's output. Therefore photorec/testdisk will be useless. Unless, of course, /dev/sdb actually does work still.
Have you tried testdisk/photorec? They should be available as packages.
As you can see from the O.P.'s output, the drive (sdb) does not appear in fdisk's output. Therefore photorec/testdisk will be useless. Unless, of course, /dev/sdb actually does work still.
No /dev/sdb doesn't work as you suspected testdisk can't find it the drive just sits there with the light flashing forever. Thanks for the suggestions. Stripes
_______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
stripes theotoky <stripes.theotoky@googlemail.com> wrote:
No /dev/sdb doesn't work as you suspected testdisk can't find it the drive just sits there with the light flashing forever.
At this point I don't think you have any recovery options other than specialized hardware that can read the flash memory on the drive directly. I'm sure it exists somewhere; just as there are hard drive recovery firms, there will be those that can handle flash devices as well, eventually, at least.
No /dev/sdb doesn't work as you suspected testdisk can't find it the drive just sits there with the light flashing forever.
At this point I don't think you have any recovery options other than specialized hardware that can read the flash memory on the drive directly. I'm sure it exists somewhere; just as there are hard drive recovery firms, there will be those that can handle flash devices as well, eventually, at least.
Interesting to know but certainly there is nothing on the stick that would make it worth going down that route just send it back to Corsair for replacement under warranty. Thanks for the advice Stripes
_______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
Dear Group,
I have an apparently dead USB key.
stripes@stripes-desktop:~$ lsusb Bus 008 Device 004: ID 413c:2011 Dell Computer Corp. Multimedia Pro Keyboard Bus 008 Device 003: ID 413c:1005 Dell Computer Corp. Multimedia Pro Keyboard Hub Bus 008 Device 002: ID 046d:c063 Logitech, Inc. Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 004: ID 048d:1168 Integrated Technology Express, Inc. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0924:3cf0 Xerox Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Is one of those your USB key? Maybe 048d:1168? lsusb -v of that device might be useful too, although based on the stuff you posted below it looks like the device is presenting the correct interface (mass storage).
stripes@stripes-desktop:~$ tail -f /var/log/messages Aug 3 14:09:36 joanna-desktop gnome-screensaver-dialog: pam_sm_authenticate: username = [joanna] Aug 3 14:09:36 joanna-desktop gnome-screensaver-dialog: pam_sm_authenticate: /home/joanna is already mounted Aug 3 14:10:00 joanna-desktop kernel: [ 9693.808014] usb 2-2: new high speed USB device using ehci_hcd and address 4 Aug 3 14:10:00 joanna-desktop kernel: [ 9693.987092] Initializing USB Mass Storage driver... Aug 3 14:10:00 joanna-desktop kernel: [ 9693.987197] scsi4 : usb-storage 2-2:1.0 Aug 3 14:10:00 joanna-desktop kernel: [ 9693.987388] usbcore: registered new interface driver usb-storage Aug 3 14:10:00 joanna-desktop kernel: [ 9693.987389] USB Mass Storage support registered. Aug 3 14:10:01 joanna-desktop kernel: [ 9694.988476] scsi 4:0:0:0: Direct-Access XXXXXXXX U168CONTROLLER 0.00 PQ: 0 ANSI: 2 Aug 3 14:10:01 joanna-desktop kernel: [ 9694.988914] sd 4:0:0:0: Attached scsi generic sg2 type 0 Aug 3 14:10:01 joanna-desktop kernel: [ 9694.991332] sd 4:0:0:0: [sdb] Attached SCSI removable disk
Is this sdb your usb device?, or something else? Or an example of your usb device when it was working? Assuming that sdb is your usb key, but /dev/sdb doesn't exist, do you have a /dev/sg2? Basically, USB storage is just scsi packets inside USB packets. You might be able to sniff these USB packets like this howto demonstrates http://biot.com/blog/usb-sniffing-on-linux - i've done it before, but a long time ago and I don't know if anything has changed. So remove your usb stick, start capturing USB packets (make the USB as idle as possible etc unplug printer, mouse, keyboard and access remotely if you want to make it easier), then have a look at the capture in a reasonably current version of wireshark. The capture might show you if the USB packets are succeeding or not, and if they are succeeding, if the scsi packets inside are succeeding or not. Based on the results of that, if the USB commands are working and you have a /dev/sg2 device, you might be able to sg tools... I think sg_read might be able to dump the data from a scsi device. If the USB commands start to work but then encounter an error, you might be able to write an application to just blindly send scsi read commands encapsulated in USB packets to read the whole disk, maybe reading past the error that Linux is giving up on. That's a bit of a long shot though. Most of the above is speculation about what might be possible based on the information you provided. If you can capture the usb packets for ~30 seconds after inserting the device while Linux probes the device, send it to me and I can have a look. Be aware that any passwords you type on an attached usb keyboard while tracing will be visible in the trace unless you filter out the events. Some other ideas... see if there are any debug options to turn on in the usb modules (most such options are available via the /sys interfaces) - maybe something useful will be printed. Also try plugging into a USB 1.1 port if you have such an old machine lying around. James
participants (5)
-
Colin Fee -
James Harper -
Jason White -
Jeremy Visser -
stripes theotoky