Really slow to mount USB stick in dolphin!

I just recently applied all the updates recommended by kupdateapplet and now when I’m in doplhin and I double-click on a USB stick’s icon to show its files, it’s REALLY slow and does nothing for about 8-10 seconds, then it shows the folders.

The first time I click on any folder it’s also slow (about 5 seconds) and then it goes into the next folder fairly normally. HOWEVER, when i paste a file into the usb stick, it “freezes” for about 7 seconds before a window pops up saying it’s transferring it and then it does it super fast.

This never happened before and now it’s been happening for three days straight!

Any ideas?

You tried running dmesg immediately after one of the actions causing problems to see if anything shows up?

No, how do I use dmesg to do that? Do I grep for anything?

Just run *dmesg *a root in a terminal. It will present a lot of lines, but you will only be interrested in the last 20 or so (when you do this shortly after inserting the device).

OK, I did that. So what am I looking for? I have no idea how to interpret this stuff.

Just plug in a stick, wait ten seconds or so to let it mount, open it in dolphin have a nose around, unmount it again…

Then open a terminal, run dmesg, and paste the last section of output. It should be fairly obvious when you plugged the stick in (it will start talking about sdX, so it helps to know what it’s been designated) - paste everything after that.

OK, I did this (typed dmesg right after it mounted the stick) but here’s what’s weird is I get a gazillion lines that have nothing to do with it (I think) all like this:

SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=01:00:4f:00:30:01:02:13:59:5a:2c:a4:07:00 SRC=192.168.1.1 DST=223.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=01:00:4f:02:00:a3:00:12:64:c7:53:51:05:00 SRC=192.168.1.103 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=40418 OPT (92030000) PROTO=2
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=01:00:4f:00:30:01:02:13:59:5a:2c:a4:07:00 SRC=192.168.1.1 DST=223.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=01:00:4f:02:00:a3:00:12:64:c7:53:51:05:00 SRC=192.168.1.103 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=42110 OPT (92030000) PROTO=2
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=01:00:5a:00:a1:ca:00:3f:62:4e:8f:21:02:00 SRC=192.168.1.102 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=11171 OPT (92030000) PROTO=2
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=01:00:4f:00:30:01:02:13:59:5a:2c:a4:07:00 SRC=192.168.1.1 DST=223.0.0.1 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC=01:00:5a:00:a1:ca:00:3f:62:4e:8f:21:02:00 SRC=192.168.1.102 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=11172 OPT (92030000) PROTO=2

But I “grep-ed” for “sd” lines (dmesg | grep sd" and got this:

sd 0:0:0:0: [sda] 71132959 512-byte hardware sectors: (36.4 GB/33.9 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: b3 00 00 08
sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 71132959 512-byte hardware sectors: (36.4 GB/33.9 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: b3 00 00 08
sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
EXT3 FS on sda2, internal journal
sd 1:0:0:0: [sdb] 15695871 512-byte hardware sectors: (8.03 GB/7.48 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 45 00 00 08
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] 15695871 512-byte hardware sectors: (8.03 GB/7.48 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 45 00 00 08
sd 1:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 1:0:0:0: [sdb] Attached SCSI removable disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
Adding 971892k swap on /dev/sda1.  Priority:-1 extents:1 across:971892k
EXT3 FS on sda3, internal journal

The problem with grepping is you may well be missing out important details. This, for reference, is what my debian install says when I put in a USB stick.


  537.352080] usb 1-2: new high speed USB device using ehci_hcd and address 6
  537.487092] usb 1-2: New USB device found, idVendor=0951, idProduct=1603
  537.487108] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  537.487121] usb 1-2: Product: DataTraveler 2.0
  537.487130] usb 1-2: Manufacturer: Kingston
  537.487139] usb 1-2: SerialNumber: 0019E02CB6E45A89150A0330
  537.487466] usb 1-2: configuration #1 chosen from 1 choice
  537.490365] scsi3 : SCSI emulation for USB Mass Storage devices
  537.492912] usb-storage: device found at 6
  537.492927] usb-storage: waiting for device to settle before scanning
  542.492556] usb-storage: device scan complete
  542.493298] scsi 3:0:0:0: Direct-Access     Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
  542.495902] sd 3:0:0:0: [sdd] 15679488 512-byte hardware sectors: (8.02 GB/7.47 GiB)
  542.497605] sd 3:0:0:0: [sdd] Write Protect is off
  542.497628] sd 3:0:0:0: [sdd] Mode Sense: 23 00 00 00
  542.497642] sd 3:0:0:0: [sdd] Assuming drive cache: write through
  542.500655] sd 3:0:0:0: [sdd] Assuming drive cache: write through
  542.500680]  sdd:
  542.610755] sd 3:0:0:0: [sdd] Attached SCSI removable disk
  548.313075] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!

As you can see, quite a lot of those lines don’t have 'sd’anything in. I’d have a look through and see if you can find the whole relevant block of text. You might find you need to increase the buffer in the profile options of the terminal emulator you’re using in order to scroll back far enough. Then pray for a guru, because I have no idea what any of it means.

It is interesting that it seems to be talking about eth0 though. It’s a long shot, but have you tried disconnecting your network and seeing if it still gives the same problem?

Is dmesg in chronological order?

Because did dmesg first (to get a “diff” ) then I mounted the drive, I opened a folder (two actually) and then waited a bit and when I hit dmesg, there was NOTHING new! What could make that happen?

(And yes, I’m doing it as root user)

OK, I did it again and got:

usb 1-2: USB disconnect, address 3
usb 1-2: new full speed USB device using ohci_hcd and address 4
usb 1-2: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb 1-2: New USB device found, idVendor=0781, idProduct=5406
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2: Product: U3 Cruzer Micro
usb 1-2: Manufacturer: SanDisk
usb 1-2: SerialNumber: 43173202C011B670
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
scsi 4:0:0:0: Direct-Access SanDisk Cruzer 8.01 PQ: 0 ANSI: 0 CCS
sd 4:0:0:0: [sdb] 15695871 512-byte hardware sectors: (8.03 GB/7.48 GiB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 45 00 00 08
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] 15695871 512-byte hardware sectors: (8.03 GB/7.48 GiB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 45 00 00 08
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 4:0:0:0: [sdb] Attached SCSI removable disk
sd 4:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete

Can someone tell me if this shows any issues?

Anyone know what could be wrong or how to diagnose this?