[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [OT]usb stick



This happens to me sometimes,try reloading the usb-storage module
rmmod usb-storage
modprobe usb-storage

On 7/9/06, Owen Heisler < owenh000@gmail.com> wrote:
On Sat, 2006-07-08 at 16:54 +0530, L.V.Gandhi wrote:
> I have Transend usb pen drive. It was working OK. I gave to my nephew
> for backup. He used in some other PC. Now it is not working. Now when
> I insert nothing happens. I mean no message in syslog.
> But in the same machine with other USB stick I get as
> Jul  8 16:52:29 localhost kernel: usb 3-5: new high speed USB device
> using ehci_hcd and address 3
> Jul  8 16:52:29 localhost kernel: Initializing USB Mass Storage
> driver...
> Jul  8 16:52:29 localhost kernel: scsi0 : SCSI emulation for USB Mass
> Storage devices
> Jul  8 16:52:29 localhost kernel: usb-storage: device found at 3
> Jul  8 16:52:29 localhost kernel: usb-storage: waiting for device to
> settle before scanning
> Jul  8 16:52:29 localhost kernel: usbcore: registered new driver
> usb-storage
> Jul  8 16:52:29 localhost kernel: USB Mass Storage support registered.
> Jul  8 16:52:29 localhost usb.agent[10831]:      usb-storage: loaded
> successfully
> Jul  8 16:52:34 localhost kernel:   Vendor: SanDisk   Model: Cruzer
> Micro      Rev: 0.2
> Jul  8 16:52:34 localhost kernel:   Type:   Direct-Access
> ANSI SCSI revision: 02
> Jul  8 16:52:34 localhost kernel: usb-storage: device scan complete
> Jul  8 16:52:35 localhost kernel: SCSI device sda: 1000944 512-byte
> hdwr sectors (512 MB)
> Jul  8 16:52:35 localhost kernel: sda: Write Protect is off
> Jul  8 16:52:35 localhost kernel: sda: Mode Sense: 03 00 00 00
> Jul  8 16:52:35 localhost kernel: sda: assuming drive cache: write
> through
> Jul  8 16:52:35 localhost kernel: SCSI device sda: 1000944 512-byte
> hdwr sectors (512 MB)
> Jul  8 16:52:35 localhost kernel: sda: Write Protect is off
> Jul  8 16:52:35 localhost kernel: sda: Mode Sense: 03 00 00 00
> Jul  8 16:52:35 localhost kernel: sda: assuming drive cache: write
> through
> Jul  8 16:52:35 localhost kernel:  sda: sda1
> Jul  8 16:52:35 localhost kernel: Attached scsi removable disk sda at
> scsi0, channel 0, id 0, lun 0
> Jul  8 16:52:35 localhost scsi.agent [10918]:      sd_mod: loaded
> sucessfully (for disk)
> Jul  8 16:52:35 localhost udev[10951]: configured rule in
> '/etc/udev/rules.d/z_hal-plugdev.rules[2]' applied, 'sda' becomes '%k'
> Jul  8 16:52:35 localhost udev[10951]: creating device node '/dev/sda'
> Jul  8 16:52:35 localhost udev[10970]: configured rule in
> '/etc/udev/rules.d/local.rules[1]' applied, added symlink 'flash'
> Jul  8 16:52:35 localhost udev[10970]: configured rule in
> '/etc/udev/rules.d/local.rules[1]' applied, 'sda1' becomes '%k'
> Jul  8 16:52:35 localhost udev[10970]: creating device node
> '/dev/sda1'
> What might have gone wrong with that non-working drive? How to make it
> usable?

It doesn't look like anything is that "wrong" here.  Does "fdisk -l"
find the drive?  If so, it may just need to be
reformatted/repartitioned.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: