Author Message

<  Device Information  ~  Cisco AM10

PostPosted: Mon May 09, 2011 12:19 am
Posts: 8Joined: Tue Mar 29, 2011 5:05 am
I'm not sure if I did this right, so I'll post the steps I did. Do I need a working driver for the device installed for it to switch properly, or should I still be able to see the proper device in lsusb even without a working driver?

I created 5 files with the MessageContent lines, [a-e]:
a:
Code:
########################################################
# Cisco AM10

DefaultVendor=0x1307
DefaultProduct=0x1169

MessageContent="55534243f83bcd810002000080000afd000000030000000100000000000000"
MessageContent2="55534243984300820002000080000afd000000070000000100000000000000"
MessageContent3="55534243984300820000000000000afd000100071000000000000000000000"
NeedResponse=1

b:
Code:
########################################################
# Cisco AM10

DefaultVendor= 0x1307
DefaultProduct=0x1169

MessageContent="55534243984300820002000080000afd000200230000000100000000000000"
MessageContent2="55534243984300820000000000000afd000300238200000000000000000000"
MessageContent3="55534243984300820002000080000afd000200260000000100000000000000"
NeedResponse=1

c:
Code:
########################################################
# Cisco AM10

DefaultVendor= 0x1307
DefaultProduct=0x1169

MessageContent="55534243984300820000000000000afd00030026c800000000000000000000"
MessageContent2="55534243d84c04820002000080000afd000010730000000100000000000000"
MessageContent3="55534243d84c04820002000080000afd000200240000000100000000000000"
NeedResponse=1

d:
Code:
########################################################
# Cisco AM10

DefaultVendor= 0x1307
DefaultProduct=0x1169

MessageContent="55534243d84c04820000000000000afd000300241300000000000000000000"
MessageContent2="55534243d84c04820000000000000afd000110732400000000000000000000"
NeedResponse=1

e:
Code:
########################################################
# Cisco AM10

DefaultVendor= 0x1307
DefaultProduct=0x1169

MessageContent="5553424308f024820002000000000a2a0000000fc000000100000000000000"
MessageContent2="5553424330c5e2810002000000000a2a000001117000000100000000000000"
NeedResponse=1


Then I ran each file in succession:
Code:
$ sudo usb_modeswitch -c a -I

Looking for default devices ...
 Found devices in default mode, class or configuration (1)
Accessing device 015 on bus 002 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x82 (in)
Using endpoints 0x01 (out) and 0x82 (in)

USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
     Product: Cisco AM10 AM10
  Serial No.: 00000000000AA3
-------------------------
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to the message (CSW) ...
 Response reading got error -110, can probably be ignored
 Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.

$ sudo usb_modeswitch -c b -I

Looking for default devices ...
 Found devices in default mode, class or configuration (1)
Accessing device 015 on bus 002 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x82 (in)
Using endpoints 0x01 (out) and 0x82 (in)

USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
     Product: Cisco AM10 AM10
  Serial No.: 00000000000AA3
-------------------------
Looking for active driver ...
 No driver found. Either detached before or never attached
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to the message (CSW) ...
 Response reading got error -110, can probably be ignored
 Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.

$ sudo usb_modeswitch -c c -I

Looking for default devices ...
 Found devices in default mode, class or configuration (1)
Accessing device 015 on bus 002 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x82 (in)
Using endpoints 0x01 (out) and 0x82 (in)

USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
     Product: Cisco AM10 AM10
  Serial No.: 00000000000AA3
-------------------------
Looking for active driver ...
 No driver found. Either detached before or never attached
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to the message (CSW) ...
 Response reading got error -110, can probably be ignored
 Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.

$ sudo usb_modeswitch -c d -I

Looking for default devices ...
 Found devices in default mode, class or configuration (1)
Accessing device 015 on bus 002 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x82 (in)
Using endpoints 0x01 (out) and 0x82 (in)

USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
     Product: Cisco AM10 AM10
  Serial No.: 00000000000AA3
-------------------------
Looking for active driver ...
 No driver found. Either detached before or never attached
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to the message (CSW) ...
 Response reading got error -110, can probably be ignored
 Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.

$ sudo usb_modeswitch -c e -I

Looking for default devices ...
 Found devices in default mode, class or configuration (1)
Accessing device 015 on bus 002 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x82 (in)
Using endpoints 0x01 (out) and 0x82 (in)

USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
     Product: Cisco AM10 AM10
  Serial No.: 00000000000AA3
-------------------------
Looking for active driver ...
 No driver found. Either detached before or never attached
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Reading the response to the message (CSW) ...
 Response reading got error -110, can probably be ignored
 Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.


After running the code, I still didn't see the wifi device I want. Thanks again for your help. I hope we're getting closer...


Offline Profile
PostPosted: Wed May 11, 2011 7:44 am
Site AdminPosts: 4710Joined: Sat Nov 03, 2007 12:30 am
It does not make much sense to continue sending messages once you got an error (in your case a time out when waiting for the status response).

Somehow I don't think the long sequence will be useful.

But you might want to try again to use only your "e" configuration (after a fresh re-plug).


Offline Profile
PostPosted: Fri Jul 22, 2011 5:47 pm
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
I've tried configuration e without much success. It tells me the device has vanished, so that's good. But then what?

Should I add stuff like this to the codeswitch rules?

Code:
# Cisco Valet Connector (Damn this thing!) AM10 (part I)
ATTRS{idVendor}=="1307", ATTRS{idProduct}=="0169", RUN+="usb_modeswitch '%b/%k'"

# Cisco Valet Connector (Damn this thing!) AM10 (part II)
ATTRS{idVendor}=="1307", ATTRS{idProduct}=="1169", RUN+="usb_modeswitch '%b/%k'"


Also, when I look at my log file it says:

Code:
Found packed config collection /usr/share/usb_modeswitch/configPack.tar.gz
Searching overriding entries named: /etc/usb_modeswitch.d/1307:1169*
Aargh! Config file missing for 1307:1169! Exiting


So should I have made a config file for this thing? I'm curious what that config file should look like. I'm really grateful to have these printouts of SniffUSB online. I don't have windows so at least I can look through these to find relevant information. That said, it's all jibberish to me.

Oh my SQL!


Offline Profile
PostPosted: Fri Jul 22, 2011 8:36 pm
Site AdminPosts: 4710Joined: Sat Nov 03, 2007 12:30 am
Hey, that's great news!

What may seem non-spectacular to you is actually a big step forward.
I try to do a resumé of your findings, please correct me where I'm erring:

- First, you have a device with USB ID 1307:0169
- Second, you run usb_modeswitch with command (e)
- Third, you're told that the device is gone
- Fourth, you have now a device with ID 1307:1169

If so, we will get that thing running in the next step.



Offline Profile
PostPosted: Sat Jul 23, 2011 3:23 pm
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
Josh wrote:
Hey, that's great news!

What may seem non-spectacular to you is actually a big step forward.
I try to do a resumé of your findings, please correct me where I'm erring:

- First, you have a device with USB ID 1307:0169
- Second, you run usb_modeswitch with command (e)
- Third, you're told that the device is gone
- Fourth, you have now a device with ID 1307:1169

If so, we will get that thing running in the next step.



Hi Josh,

I think you're right that it's great news - and that probably we can get it working soon. Your summary is maybe a little off, though I'm not sure how much it matters. The device claims it's taking up two USB ports and both are still there after modeswitch. Here's lsusb before:

Code:
Bus 001 Device 005: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Bus 001 Device 003: ID 1307:0169 Transcend Information, Inc.


I run modeswitch whose current code is the following:

Code:
# Configuration for the usb_modeswitch package, a mode switching tool for
# USB devices providing multiple states or modes
#
# This file is evaluated by the wrapper script "usb_modeswitch_dispatcher"
# in /usr/sbin
# To enable an option, set it to "1", "yes" or "true" (case doesn't matter)
# Everything else counts as "disable"


# Disable automatic mode switching globally (e.g. to access the original
# install storage)

DisableSwitching=0


# Enable logging (results in a extensive report file in /var/log, named
# "usb_modeswitch_<interface-name>" (and probably others)

EnableLogging=1

# oms edit 2011-07-20

# Cisco Valet Connector AM10
#
# Contributor: ohmysql (quite the n00b so please help if you see errors)

# No. 1
DefaultVendor= 0x1307
DefaultProduct= 0x1169
#TargetVendor= 0x13b1
#0x1307

#TargetProduct= 0x0031
#0x0169

#MessageEndpoint=0×05

MessageContent="5553424308f024820002000000000a2a0000000fc000000100000000000000"
MessageContent2="5553424330c5e2810002000000000a2a000001117000000100000000000000"
NeedResponse=1

CheckSuccess=20

#Found these numbers here: http://linuxwireless.org/en/users/Drivers/rt2800usb/devices?highlight=%28am10%29
#DefaultVendor= 0x13b1
#DefaultProduct= 0x0031



Code:
Note: target parameter missing; success check limited
Looking for default devices ...
 Found devices in default mode, class or configuration (1)
Accessing device 005 on bus 001 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x82 (in)
Using endpoints 0x01 (out) and 0x82 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached


For some reason it hung there - usually it does the success check and it works. But Ubuntu had a USB storage device on the desktop and that just vanished.

Here's lsusb (it appears to be the same):

Code:
Bus 001 Device 005: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Bus 001 Device 003: ID 1307:0169 Transcend Information, Inc.


I'm curious what the next step would be though :) I have a feeling I'm a lot closer.

oh my SQL!!

PS I also wanted to answer a question you asked the other person earlier in the thread but I don't think the person answered. Yes, I do have write access to the USB device (I can save files there) so probably certain commands would indeed be dangerous.
PPS I also wanted to mention another place I'm having this conversation, if you'd like to see what we've tried elsewhere:

http://ubuntuforums.org/showthread.php? ... st11077654


Best,

OMS


Offline Profile
PostPosted: Sat Jul 23, 2011 9:20 pm
Site AdminPosts: 4710Joined: Sat Nov 03, 2007 12:30 am
I can already tell you that usb_modeswitch is not the right tool to load the driver.

That would be "udev". It looks at a list of rules everytime a device on the system is changed (added / removed). It can check certain things like USB IDs but also much more sophisticated properties, and trigger any action you want if all the conditions in the "rule" are met.

usb_modeswitch is using this for an automatic run each time a known device is plugged. You can just define a new rule to load the driver automatically after the switching has happened.

Re-reading the whole topic again - did you get that "13b1:0031" device at some point? Maybe the vanishing of the storage is not enough to make the wireless device appear ...

I'll have annother look at that log no. 5.



Offline Profile
PostPosted: Tue Jul 26, 2011 3:29 pm
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
Josh wrote:
I can already tell you that usb_modeswitch is not the right tool to load the driver.
Can you say a little more about why? I would think it'd be perfect because I'm trying to turn off the USB Storage part, and I think I need to change the USB address from 1307x1169 to 13b1x0031.

Quote:
That would be "udev". It looks at a list of rules everytime a device on the system is changed (added / removed). It can check certain things like USB IDs but also much more sophisticated properties, and trigger any action you want if all the conditions in the "rule" are met.

usb_modeswitch is using this for an automatic run each time a known device is plugged. You can just define a new rule to load the driver automatically after the switching has happened.
So you're saying I'd want to have udev run a USB_modeswitch and then take another action. I can only assume that action to would be load a driver, probably in ndiswrapper.

Quote:
Re-reading the whole topic again - did you get that "13b1:0031" device at some point? Maybe the vanishing of the storage is not enough to make the wireless device appear ...

I'll have annother look at that log no. 5.

I got 13b1:0031 from here:

http://linuxwireless.org/en/users/Drive ... %28am10%29

And from reading the Cisco AM10 driver for Windows XP. I hope that helps.

I'd definitely be curious what you think of the direction we're going here:

http://ubuntuforums.org/showthread.php? ... st11087521

I'm very sorry we're not both on one forum.

OMS


Offline Profile
PostPosted: Tue Jul 26, 2011 6:01 pm
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
Can you shed any light on why I can't get this device to change it's product and vendor ids to 13b1:0031. Also, I tried creating a file in /etc/usb_modeswitch.d/ called 1307:1169 but for some reason modeswitch doesn't seem to see it. Here is the content of that file:

Code:
-rw-r--r-- root/root 287 2010-06-20 18:00  1307:1169


Let me know if that seems right.

Best,
OMS


Offline Profile
PostPosted: Tue Jul 26, 2011 6:42 pm
Site AdminPosts: 4710Joined: Sat Nov 03, 2007 12:30 am
Getting the device 13b1:0031 is the whole point of our investigation here. It is hardly useful to set up the driver if the respective device just is not there yet.

If you read this whole thread, you can see what we tried already. As I said, I have to look at the sniffing log again. See
http://www.berrypi.com/UsbSnoop5.log

It clearly shows that the original devices do not go away, instead there is a new one popping up. Before this, a bunch of commands are exchanged with the original devices. The problem is to find out which of those (or which combination of those) will trigger the appearance of the new device.



Offline Profile
PostPosted: Thu Jul 28, 2011 12:57 pm
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
Josh wrote:
Getting the device 13b1:0031 is the whole point of our investigation here. It is hardly useful to set up the driver if the respective device just is not there yet.

If you read this whole thread, you can see what we tried already. As I said, I have to look at the sniffing log again. See
http://www.berrypi.com/UsbSnoop5.log

It clearly shows that the original devices do not go away, instead there is a new one popping up. Before this, a bunch of commands are exchanged with the original devices. The problem is to find out which of those (or which combination of those) will trigger the appearance of the new device.

Makes sense. Ok, I'll be curious if you see anything worth trying. I'll try reading over the thread again, because that log doesn't make sense to me (for instance, I don't understand where the new USB device appears). But let me see what I can figure out.

Thanks - I'll be curious what you come up with.

OMS


Offline Profile
PostPosted: Fri Jul 29, 2011 7:12 pm
Site AdminPosts: 4710Joined: Sat Nov 03, 2007 12:30 am
O.K., here we go.

As posted before, the moment where the new device appears is [4562 ms].
Again, any command (or event) which is triggering that appearance must be occuring ahead of that moment.

The previous poster did not follow through completely; we never checked out those "write" commands. They will transfer very little data to the storage, just one byte each time. See [1772 ms] (URB 904) and [1777 ms] (URB 907).

I will add a special function to the usb_modeswitch code to emulate those two commands.
Please stand by ...



Offline Profile
PostPosted: Fri Jul 29, 2011 9:16 pm
Site AdminPosts: 4710Joined: Sat Nov 03, 2007 12:30 am
Well, here you go. Note this is just an experiment and it may fail. Don't be too disappointed in that case.

Get this, unzip and put it in the 1.1.8 source folder:
http://www.draisberghof.de/usb_modeswit ... witch.c.gz

"make" in the source folder. Plug in your stick. Wait a moment.

Run in the folder:
Code:
./usb_modeswitch -v 1307 -p 1169 -L -I
See what happens ("lsusb", "dmesg") ... It may take a while, though.



Offline Profile
PostPosted: Sat Jul 30, 2011 1:57 am
Posts: 47Joined: Fri Jul 22, 2011 4:47 pm
Hi Josh,

Thank you - I'm really excited to try this out.

Ok, just so you know about my machine - I'm running an AMD64 processor, using Ubuntu 11.04.

Ok, I got a ton of help from chili from the ubuntu forum. I've got the driver compiled - installing usblib-dev helped a ton. I've compiled the driver with the change you added. Thanks again.

Here's what happened when I did make:

Code:
gcc -o usb_modeswitch usb_modeswitch.c -Wall -l usb
usb_modeswitch.c: In function ‘main’:
usb_modeswitch.c:536:3: warning: implicit declaration of function ‘switchCiscoMode’


Also, if you plan to keep sending me new code to try, please let me know how you'd like me to recompile the driver.

I assume it would be:

Code:
make clean
sudo make uninstall
make
sudo make install

But please do confirm.

So I did what you said, here was my usb_modeswitch code when I ran. (You didn't say to run in sudo but I assumed that was a mistake so I ran in sudo).

Code:
sudo ./usb_modeswitch -v 1307 -p 1169 -L -I

Looking for default devices ...
Found devices in default mode, class or configuration (1)
Accessing device 007 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x82 (in)

USB description data (for identification)
-------------------------
Manufacturer: Cisco Systems, Inc.
Product: Cisco AM10 AM10
Serial No.: 000000000000D9
-------------------------
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
Sending Cisco message sequence
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Trying to send message 2 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to write package 1 ...
Response reading got error -110, can probably be ignored
Device is gone, skipping any further commands
-> Run lsusb to note any changes. Bye.


lsusb says:

Code:
Bus 001 Device 007: ID 1307:1169 Transcend Information, Inc. TS2GJF210 JetFlash 210 2GB
Bus 001 Device 006: ID 1307:0169 Transcend Information, Inc.


and dmesg says:

Code:
[16308.820077] usb 1-4: new high speed USB device using ehci_hcd and address 6
[16308.971162] hub 1-4:1.0: USB hub found
[16308.972058] hub 1-4:1.0: 3 ports detected
[16309.250232] usb 1-4.1: new high speed USB device using ehci_hcd and address 7
[16309.361516] scsi5 : usb-storage 1-4.1:1.0
[16310.362416] scsi 5:0:0:0: Direct-Access Cisco AM10 0.00 PQ: 0 ANSI: 2
[16310.363668] sd 5:0:0:0: Attached scsi generic sg2 type 0
[16310.364896] sd 5:0:0:0: [sdb] 253952 512-byte logical blocks: (130 MB/124 MiB)
[16310.365946] sd 5:0:0:0: [sdb] Write Protect is off
[16310.365957] sd 5:0:0:0: [sdb] Mode Sense: 00 00 00 00
[16310.365963] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[16310.369784] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[16310.499785] sdb: sdb1
[16310.502891] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[16310.502901] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[16311.372376] FAT: Filesystem error (dev sdb1)
[16311.372384] invalid access to FAT (entry 0x00c00000)
[16311.372392] FAT: Filesystem has been set read-only
[16311.372401] FAT: Filesystem error (dev sdb1)
[16311.372405] invalid access to FAT (entry 0x00c00000)
[16311.372412] FAT: Filesystem error (dev sdb1)
[16311.372415] invalid access to FAT (entry 0x00c00000)
[16311.372421] FAT: Filesystem error (dev sdb1)
[16311.372424] invalid access to FAT (entry 0x00c00000)
[16311.372430] FAT: Filesystem error (dev sdb1)
[16311.372433] invalid access to FAT (entry 0x00c00000)
[16311.372439] FAT: Filesystem error (dev sdb1)
[16311.372442] invalid access to FAT (entry 0x00c00000)
[16311.372448] FAT: Filesystem error (dev sdb1)
[16311.372451] invalid access to FAT (entry 0x00c00000)
[16311.372456] FAT: Filesystem error (dev sdb1)
[16311.372459] invalid access to FAT (entry 0x00c00000)
[16311.372467] attempt to access beyond end of device
[16311.372474] sdb1: rw=0, want=12586911, limit=253920
[16311.372482] Buffer I/O error on device sdb1, logical block 12586910
[16311.372491] FAT: Filesystem error (dev sdb1)
[16311.372494] invalid access to FAT (entry 0x00c00000)
[16311.372503] FAT: Filesystem error (dev sdb1)
[16311.372506] invalid access to FAT (entry 0x00c00000)
[16311.372512] FAT: Filesystem error (dev sdb1)
[16311.372515] invalid access to FAT (entry 0x00c00000)
[16311.372521] FAT: Filesystem error (dev sdb1)
[16311.372524] invalid access to FAT (entry 0x00c00000)
[16311.372530] FAT: Filesystem error (dev sdb1)
[16311.372533] invalid access to FAT (entry 0x00c00000)
[16311.372539] FAT: Filesystem error (dev sdb1)
[16311.372542] invalid access to FAT (entry 0x00c00000)
[16311.372548] FAT: Filesystem error (dev sdb1)
[16311.372551] invalid access to FAT (entry 0x00c00000)
[16311.372556] FAT: Filesystem error (dev sdb1)
[16311.372559] invalid access to FAT (entry 0x00c00000)
[16311.372565] FAT: Filesystem error (dev sdb1)
[16311.372568] invalid access to FAT (entry 0x00c00000)
[16311.372577] FAT: Filesystem error (dev sdb1)
[16311.372580] invalid access to FAT (entry 0x00c00000)
[16311.372597] FAT: Filesystem error (dev sdb1)
[16311.372601] invalid access to FAT (entry 0x00c00000)
[16311.372607] FAT: Filesystem error (dev sdb1)
[16311.372610] invalid access to FAT (entry 0x00c00000)
[16311.372616] FAT: Filesystem error (dev sdb1)
[16311.372619] invalid access to FAT (entry 0x00c00000)
[16311.372625] FAT: Filesystem error (dev sdb1)
[16311.372628] invalid access to FAT (entry 0x00c00000)
[16311.372639] FAT: Filesystem error (dev sdb1)
[16311.372642] invalid access to FAT (entry 0x00c00000)
[16311.372648] FAT: Filesystem error (dev sdb1)
[16311.372651] invalid access to FAT (entry 0x00c00000)
[16311.372657] FAT: Filesystem error (dev sdb1)
[16311.372660] invalid access to FAT (entry 0x00c00000)
[16311.372665] FAT: Filesystem error (dev sdb1)
[16311.372669] invalid access to FAT (entry 0x00c00000)
[16311.372676] FAT: Filesystem error (dev sdb1)
[16311.372679] invalid access to FAT (entry 0x00c00000)
[16311.372686] FAT: Filesystem error (dev sdb1)
[16311.372689] invalid access to FAT (entry 0x00c00000)
[16311.372694] FAT: Filesystem error (dev sdb1)
[16311.372698] invalid access to FAT (entry 0x00c00000)
[16311.372703] FAT: Filesystem error (dev sdb1)
[16311.372706] invalid access to FAT (entry 0x00c00000)
[16311.372712] FAT: Filesystem error (dev sdb1)
[16311.372715] invalid access to FAT (entry 0x00c00000)
[16311.372721] FAT: Filesystem error (dev sdb1)
[16311.372724] invalid access to FAT (entry 0x00c00000)
[16311.372730] FAT: Filesystem error (dev sdb1)
[16311.372733] invalid access to FAT (entry 0x00c00000)
[16311.372739] FAT: Filesystem error (dev sdb1)
[16311.372742] invalid access to FAT (entry 0x00c00000)
[16311.372747] FAT: Filesystem error (dev sdb1)
[16311.372751] invalid access to FAT (entry 0x00c00000)
[16311.372758] FAT: Filesystem error (dev sdb1)
[16311.372761] invalid access to FAT (entry 0x00c00000)
[16311.372767] FAT: Filesystem error (dev sdb1)
[16311.372770] invalid access to FAT (entry 0x00c00000)
[16311.372776] FAT: Filesystem error (dev sdb1)
[16311.372779] invalid access to FAT (entry 0x00c00000)
[16311.372784] FAT: Filesystem error (dev sdb1)
[16311.372787] invalid access to FAT (entry 0x00c00000)
[16311.372793] FAT: Filesystem error (dev sdb1)
[16311.372796] invalid access to FAT (entry 0x00c00000)
[16311.372802] FAT: Filesystem error (dev sdb1)
[16311.372805] invalid access to FAT (entry 0x00c00000)
[16311.372811] FAT: Filesystem error (dev sdb1)
[16311.372814] invalid access to FAT (entry 0x00c00000)
[16311.372820] attempt to access beyond end of device
[16311.372827] sdb1: rw=0, want=12586911, limit=253920
[16311.372831] Buffer I/O error on device sdb1, logical block 12586910
[16311.373929] FAT: Filesystem error (dev sdb1)
[16311.373935] invalid access to FAT (entry 0x37303531)
[16311.373945] FAT: Filesystem error (dev sdb1)
[16311.373949] invalid access to FAT (entry 0x37303531)
[16311.373956] FAT: Filesystem error (dev sdb1)
[16311.373959] invalid access to FAT (entry 0x37303531)
[16311.373965] FAT: Filesystem error (dev sdb1)
[16311.373968] invalid access to FAT (entry 0x37303531)
[16311.373974] FAT: Filesystem error (dev sdb1)
[16311.373977] invalid access to FAT (entry 0x37303531)
[16311.373983] FAT: Filesystem error (dev sdb1)
[16311.373986] invalid access to FAT (entry 0x37303531)
[16311.373992] FAT: Filesystem error (dev sdb1)
[16311.373995] invalid access to FAT (entry 0x37303531)
[16311.374000] FAT: Filesystem error (dev sdb1)
[16311.374003] invalid access to FAT (entry 0x37303531)
[16311.374012] attempt to access beyond end of device
[16311.374018] sdb1: rw=0, want=925910224, limit=253920
[16311.374024] Buffer I/O error on device sdb1, logical block 925910223
[16311.374031] FAT: Filesystem error (dev sdb1)
[16311.374034] invalid access to FAT (entry 0x37303531)
[16311.374041] FAT: Filesystem error (dev sdb1)
[16311.374045] invalid access to FAT (entry 0x37303531)
[16311.374051] FAT: Filesystem error (dev sdb1)
[16311.374054] invalid access to FAT (entry 0x37303531)
[16311.374060] FAT: Filesystem error (dev sdb1)
[16311.374063] invalid access to FAT (entry 0x37303531)
[16311.374069] FAT: Filesystem error (dev sdb1)
[16311.374072] invalid access to FAT (entry 0x37303531)
[16311.374078] FAT: Filesystem error (dev sdb1)
[16311.374081] invalid access to FAT (entry 0x37303531)
[16311.374087] FAT: Filesystem error (dev sdb1)
[16311.374090] invalid access to FAT (entry 0x37303531)
[16311.374095] FAT: Filesystem error (dev sdb1)
[16311.374098] invalid access to FAT (entry 0x37303531)
[16311.374104] FAT: Filesystem error (dev sdb1)
[16311.374107] invalid access to FAT (entry 0x37303531)
[16311.374115] FAT: Filesystem error (dev sdb1)
[16311.374118] invalid access to FAT (entry 0x37303531)
[16311.374125] FAT: Filesystem error (dev sdb1)
[16311.374128] invalid access to FAT (entry 0x37303531)
[16311.374134] FAT: Filesystem error (dev sdb1)
[16311.374137] invalid access to FAT (entry 0x37303531)
[16311.374143] FAT: Filesystem error (dev sdb1)
[16311.374146] invalid access to FAT (entry 0x37303531)
[16311.374152] FAT: Filesystem error (dev sdb1)
[16311.374155] invalid access to FAT (entry 0x37303531)
[16311.374161] FAT: Filesystem error (dev sdb1)
[16311.374164] invalid access to FAT (entry 0x37303531)
[16311.374170] FAT: Filesystem error (dev sdb1)
[16311.374173] invalid access to FAT (entry 0x37303531)
[16311.374178] FAT: Filesystem error (dev sdb1)
[16311.374181] invalid access to FAT (entry 0x37303531)
[16311.374187] FAT: Filesystem error (dev sdb1)
[16311.374190] invalid access to FAT (entry 0x37303531)
[16311.374197] FAT: Filesystem error (dev sdb1)
[16311.374200] invalid access to FAT (entry 0x37303531)
[16311.374211] FAT: Filesystem error (dev sdb1)
[16311.374214] invalid access to FAT (entry 0x37303531)
[16311.374220] FAT: Filesystem error (dev sdb1)
[16311.374223] invalid access to FAT (entry 0x37303531)
[16311.374229] FAT: Filesystem error (dev sdb1)
[16311.374232] invalid access to FAT (entry 0x37303531)
[16311.374238] FAT: Filesystem error (dev sdb1)
[16311.374241] invalid access to FAT (entry 0x37303531)
[16311.374247] FAT: Filesystem error (dev sdb1)
[16311.374250] invalid access to FAT (entry 0x37303531)
[16311.374256] FAT: Filesystem error (dev sdb1)
[16311.374259] invalid access to FAT (entry 0x37303531)
[16311.374265] FAT: Filesystem error (dev sdb1)
[16311.374268] invalid access to FAT (entry 0x37303531)
[16311.374274] FAT: Filesystem error (dev sdb1)
[16311.374277] invalid access to FAT (entry 0x37303531)
[16311.374285] FAT: Filesystem error (dev sdb1)
[16311.374288] invalid access to FAT (entry 0x37303531)
[16311.374293] FAT: Filesystem error (dev sdb1)
[16311.374296] invalid access to FAT (entry 0x37303531)
[16311.374302] FAT: Filesystem error (dev sdb1)
[16311.374305] invalid access to FAT (entry 0x37303531)
[16311.374311] FAT: Filesystem error (dev sdb1)
[16311.374314] invalid access to FAT (entry 0x37303531)
[16311.374319] FAT: Filesystem error (dev sdb1)
[16311.374322] invalid access to FAT (entry 0x37303531)
[16311.374328] FAT: Filesystem error (dev sdb1)
[16311.374331] invalid access to FAT (entry 0x37303531)
[16311.374338] FAT: Filesystem error (dev sdb1)
[16311.374341] invalid access to FAT (entry 0x37303531)
[16311.374347] attempt to access beyond end of device
[16311.374352] sdb1: rw=0, want=925910224, limit=253920
[16311.374357] Buffer I/O error on device sdb1, logical block 925910223


I'll follow through to the end on this one.


Offline Profile
PostPosted: Sat Jul 30, 2011 9:02 am
Site AdminPosts: 4710Joined: Sat Nov 03, 2007 12:30 am
Can you try again?

This time, wait some more after plugging in, at least five seconds.
Then unmount ("safely remove") any storage devices that may pop up on your desktop before running the command.

You can also try to leave out the -I parameter.

It is important to re-plug each time before you start a new attempt. And yes, you always need superuser rights; don't be afraid to work in a root shell for a while ("sudo bash" or "su") - as long as you don't start to delete files you should be safe ...



Offline Profile
PostPosted: Sat Jul 30, 2011 1:32 pm
Posts: 2Location: South Carolina, USAJoined: Tue Jul 26, 2011 6:01 pm
Quote:
don't be afraid to work in a root shell for a while ("sudo bash" or "su") - as long as you don't start to delete files you should be safe ...
I believe, in Ubuntu, the preferred method is "sudo su."


Offline Profile

Display posts from previous:  Sort by:

All times are UTC + 1 hour [ DST ]
Page 2 of 9
131 posts
Go to page Previous  1, 2, 3, 4, 5 ... 9  Next
Users browsing this forum: No registered users and 0 guests
Search for:
Post new topic  Reply to topic
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum