Try plugging it in and giving it a minute to try to mount. Then run a fdisk -l to list all the devices. I doubt if it will find it, as it is most likely a flaky USB to SATA adapter inside the drive. I would recommend taking it back and exchanging it, if it is still within the return period.
Jason On Tue, Jan 12, 2010 at 4:52 PM, Daniel Herrington <[email protected]>wrote: > All, > > I have a usb 2.0 WD drive I bought to store vm images on. It worked long > enough to get the images on, but now doesn't seem to want to mount, on > either Linux or Windows. It's formatted NTFS and lights up and spins, > just never mounts. This is my dmesg output: > > [110125.104110] usb 4-1: new full speed USB device using uhci_hcd and > address 5 > [110125.669146] usb 4-1: device descriptor read/64, error -71 > [110125.892191] usb 4-1: device descriptor read/64, error -71 > [110126.108187] usb 4-1: new full speed USB device using uhci_hcd and > address 6 > [110126.228196] usb 4-1: device descriptor read/64, error -71 > [110126.452106] usb 4-1: device descriptor read/64, error -71 > [110126.668128] usb 4-1: new full speed USB device using uhci_hcd and > address 7 > [110127.076096] usb 4-1: device not accepting address 7, error -71 > [110127.132168] hub 4-0:1.0: unable to enumerate USB device on port 1 > [110148.617109] usb 4-1: new full speed USB device using uhci_hcd and > address 9 > [110148.737109] usb 4-1: device descriptor read/64, error -71 > [110148.960137] usb 4-1: device descriptor read/64, error -71 > [110149.176188] usb 4-1: new full speed USB device using uhci_hcd and > address 10 > [110149.296120] usb 4-1: device descriptor read/64, error -71 > [110149.521124] usb 4-1: device descriptor read/64, error -71 > [110149.737106] usb 4-1: new full speed USB device using uhci_hcd and > address 11 > [110150.148173] usb 4-1: device not accepting address 11, error -71 > [110150.204228] hub 4-0:1.0: unable to enumerate USB device on port 1 > > This is my lsusb: > Bus 007 Device 004: ID 05a9:7670 OmniVision Technologies, Inc. > Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 001 Device 006: ID 0a5c:4503 Broadcom Corp. > Bus 001 Device 005: ID 0a5c:4502 Broadcom Corp. > Bus 001 Device 004: ID 413c:8126 Dell Computer Corp. Wireless 355 Bluetooth > Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. > Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 006 Device 002: ID 0483:2016 SGS Thomson Microelectronics > Fingerprint Reader > 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 004: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse > Receiver > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > > I'm thinking a trip back to Best Buy to replace it at this point. Any > way I can debug this further? > > thanks, > -- > Daniel B. Herrington > Director of Field Services > Robert Mark Technologies > [email protected] > o: 651-769-2574 > m: 503-358-8575 > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
