problema con usb

[Tuso]

mi venenux no reconoce usb, al usar estos comandos fdisk -l no me meustra la usb

al usar lsusb sale esto

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 002: ID 0930:6544 Toshiba Corp. Kingston DataTraveler 2.0 Stick (2GB)

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 002: ID 064e:a103 Suyin Corp. Acer/HP Integrated Webcam [CN0314]

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

sale kignston 2gb, y en l amemoria dice que es de 4gb

probando otro comando 

 lsmod | grep usb

usbnet                 17626  3 rndis_wlan,rndis_host,cdc_ether

mii                    12595  1 usbnet

usb_storage            34951  0 

scsi_mod              134523  6 usb_storage,uas,sg,sr_mod,sd_mod,libata

usbcore               103522  12 cdc_acm,rndis_wlan,rndis_host,cdc_ether,usbnet,cdc_phonet,usb_storage,uas,uvcvideo,uhci_hcd,ehci_hcd

usb_common             12338  1 usbcore

y otro 

dmesg | grep usb

[12899.115108] usb 2-5: New USB device found, idVendor=0930, idProduct=6544

[12899.115112] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[12899.115114] usb 2-5: Product: DT 100 G2       

[12899.115116] usb 2-5: Manufacturer: Kingston

[12899.115118] usb 2-5: SerialNumber: 00147809022FCB7185570A6C

[12899.117153] scsi5 : usb-storage 2-5:1.0

aun sabiendo estos datos, no tengo ni idea que hacer para solucionar el problema de la memoria usb...

[PICCORO McKAY Lenz]

me gusta como abordaste el problema, al menos nome hiciste perder el tiempo, porqe ya e pusiste al tanto..

ok, el ultimo comando te servira pra sarber l "verdad":

inical el linux sin ningun usb, una vez iniciado ve a una consola, alli ahora coloca el usbdrive en el puerto usb, entonces ejecuta :
dmesg | tail -n 60
entonces ve si hay alguna linea que diga /dev/sdX donde X puede ser b o c o d y pega lo que diga.

una vez sepas que letra es (supongamos la b) ejecuta esto:

hdparm -I /dev/sdX (donde X puede ser b o c o d, supongamos la b aqui)

el resultado primero te identifica el dispositivo, el segundo te lo verifica, si ambos dicen 2G te estafaron, si algno discrepa algun otro dispositivo lo daño.

una vez me dieron un usb de 50M como 5G lo modificaron usando fdisk, con fdisk puedes volver reasignar lo valores reales

si este no es el caso, como dijhe pega lo resultados en el siguiente correo pra ver cual es el problema

--
Comunidad de discusion privada VENENUX GNU/Linux "venenuxsarisari". Sin limitaciones, para soft privado usar venenuxmassenkoh
*->To post mail to venenux...@googlegroups.com
*->To unpost : venenuxsarisa...@googlegroups.com
 
http://groups.google.com/group/venenuxsarisari?hl=es

--
Lenz McKAY Gerardo (PICCORO)

http://qglochekone.blogspot.com

[Tuso]

el primer comando este fue el resultado

dmesg | tail -n 60

[   10.435524] fuse init (API version 7.17)

[   12.009656] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input11

[   13.502948] Bluetooth: Core ver 2.16

[   13.502985] NET: Registered protocol family 31

[   13.502987] Bluetooth: HCI device and connection manager initialized

[   13.502990] Bluetooth: HCI socket layer initialized

[   13.502992] Bluetooth: L2CAP socket layer initialized

[   13.503223] Bluetooth: SCO socket layer initialized

[   13.539907] Bluetooth: RFCOMM TTY layer initialized

[   13.539911] Bluetooth: RFCOMM socket layer initialized

[   13.539914] Bluetooth: RFCOMM ver 1.11

[   13.550476] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

[   13.550479] Bluetooth: BNEP filters: protocol multicast

[   13.584330] Bridge firewalling registered

[   13.659725] lp: driver loaded but no devices found

[   13.735038] ppdev: user-space parallel port driver

[   17.209118] sky2 0000:02:00.0: eth0: enabling interface

[   17.209331] ADDRCONF(NETDEV_UP): eth0: link is not ready

[   17.222030] ADDRCONF(NETDEV_UP): wlan0: link is not ready

[   17.767825] Disabling lock debugging due to kernel taint

[   17.779997] vboxdrv: Found 1 processor cores.

[   17.781376] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.

[   17.781379] vboxdrv: Successfully loaded version 4.0.10_Debian (interface 0x00180000).

[  126.772262] wlan0: direct probe to 00:26:44:5c:c5:71 (try 1/3)

[  126.774067] wlan0: direct probe responded

[  126.774082] wlan0: authenticate with 00:26:44:5c:c5:71 (try 1)

[  126.776431] wlan0: authenticated

[  126.776465] wlan0: associate with 00:26:44:5c:c5:71 (try 1)

[  126.779732] wlan0: RX AssocResp from 00:26:44:5c:c5:71 (capab=0x411 status=0 aid=1)

[  126.779736] wlan0: associated

[  126.780440] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

[  137.664023] wlan0: no IPv6 routers present

[  317.276037] usb 2-5: new high-speed USB device number 2 using ehci_hcd

[  317.411294] usb 2-5: New USB device found, idVendor=0930, idProduct=6544

[  317.411298] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[  317.411300] usb 2-5: Product: DT 100 G2       

[  317.411302] usb 2-5: Manufacturer: Kingston

[  317.411304] usb 2-5: SerialNumber: 00147809022FCB7185570A6C

[  317.479134] usbcore: registered new interface driver uas

[  317.497775] Initializing USB Mass Storage driver...

[  317.497882] scsi4 : usb-storage 2-5:1.0

[  317.498031] usbcore: registered new interface driver usb-storage

[  317.498033] USB Mass Storage support registered.

[  318.527579] scsi 4:0:0:0: Direct-Access     Kingston DT 100 G2        1.00 PQ: 0 ANSI: 0 CCS

[  318.529399] sd 4:0:0:0: Attached scsi generic sg2 type 0

[  318.535931] sd 4:0:0:0: [sdb] READ CAPACITY failed

[  318.535935] sd 4:0:0:0: [sdb]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

[  318.535938] sd 4:0:0:0: [sdb]  Sense Key : Unit Attention [current] 

[  318.535942] sd 4:0:0:0: [sdb]  Add. Sense: Not ready to ready change, medium may have changed

[  318.537588] sd 4:0:0:0: [sdb] Write Protect is off

[  318.537592] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00

[  318.538265] sd 4:0:0:0: [sdb] No Caching mode page present

[  318.538269] sd 4:0:0:0: [sdb] Assuming drive cache: write through

[  318.543685] sd 4:0:0:0: [sdb] READ CAPACITY failed

[  318.543688] sd 4:0:0:0: [sdb]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

[  318.543692] sd 4:0:0:0: [sdb]  Sense Key : Unit Attention [current] 

[  318.543696] sd 4:0:0:0: [sdb]  Add. Sense: Not ready to ready change, medium may have changed

[  318.544936] sd 4:0:0:0: [sdb] No Caching mode page present

[  318.544940] sd 4:0:0:0: [sdb] Assuming drive cache: write through

[  318.544943] sd 4:0:0:0: [sdb] Attached SCSI removable disk

no encontre el /dev/sd que decias, solo encontre el sdb y con el sdb probe el otro comando que mencionabas a ver que pasaba y este fue el resutlado

/dev/sdb:

SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

ATA device, with non-removable media

Standards:

Likely used: 1

Configuration:

Logical max current

cylinders 0 0

heads 0 0

sectors/track 0 0

--

Logical/Physical Sector size:           512 bytes

device size with M = 1024*1024:           0 MBytes

device size with M = 1000*1000:           0 MBytes 

cache/buffer size  = unknown

Capabilities:

IORDY not likely

Cannot perform double-word IO

R/W multiple sector transfer: not supported

DMA: not supported

PIO: pio0 

[PICCORO McKAY Lenz]

errrrr

ok primero explicarte a ver si aprendes algo:

On Thu, Oct 4, 2012 at 4:59 PM, Tuso <kdeme...@gmail.com> wrote:

el primer comando este fue el resultado

este es la parte que te einteresaba

[  317.498033] USB Mass Storage support registered.

[  318.527579] scsi 4:0:0:0: Direct-Access     Kingston DT 100 G2        1.00 PQ: 0 ANSI: 0 CCS

[  318.529399] sd 4:0:0:0: Attached scsi generic sg2 type 0

[  318.535931] sd 4:0:0:0: [sdb] READ CAPACITY failed

aqui fallo:
 

[  318.535931] sd 4:0:0:0: [sdb] READ CAPACITY failed

y despeu ste dio el nombre del dispositivo (sdb):

[  318.535935] sd 4:0:0:0: [sdb]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

[  318.535938] sd 4:0:0:0: [sdb]  Sense Key : Unit Attention [current] 

[  318.535942] sd 4:0:0:0: [sdb]  Add. Sense: Not ready to ready change, medium may have changed

[  318.537588] sd 4:0:0:0: [sdb] Write Protect is off

[  318.537592] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00

[  318.538265] sd 4:0:0:0: [sdb] No Caching mode page present

[  318.538269] sd 4:0:0:0: [sdb] Assuming drive cache: write through

[  318.543685] sd 4:0:0:0: [sdb] READ CAPACITY failed

[  318.543688] sd 4:0:0:0: [sdb]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

[  318.543692] sd 4:0:0:0: [sdb]  Sense Key : Unit Attention [current] 

[  318.543696] sd 4:0:0:0: [sdb]  Add. Sense: Not ready to ready change, medium may have changed

[  318.544936] sd 4:0:0:0: [sdb] No Caching mode page present

[  318.544940] sd 4:0:0:0: [sdb] Assuming drive cache: write through

[  318.544943] sd 4:0:0:0: [sdb] Attached SCSI removable disk

ahora sobre el segundo

no encontre el /dev/sd que decias, solo encontre el sdb y con el sdb probe el otro comando que mencionabas a ver que ç

como dije antes el primer comando te deca cual era, y pecisamente era el dev/sdb el dispositivo de usb
 

pasaba y este fue el resutlado

todo el resto se resume en qu se fu al caño, arreglarlo implicaria que yo este aya y de paso que teng otro dispositivo exactamete igual, lo qu paso es ue se monto mal o era paticonado con guindo/winbuntu, al estar mal particionado y escribir/sacarlo mal del computador, se daño.. 

/dev/sdb:

SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Esta infomacion es la decripcion tecnica el disco usb, y ya no hay nada que hacer porque estas muy ljos para yo ir.. lo siento. no particones con inbuntu o windos..
NOTA: si particionas con linux venenux y no creas estas particiones bien, resultara en lo mimo, las particiones deben crearse con fdisk.