USB Memory Stick is remounted every 10 seconds

Bug #70008 reported by flix
10
Affects Status Importance Assigned to Milestone
gnome-volume-manager (Ubuntu)
Invalid
Low
Unassigned
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Won't Fix
Undecided
R. Pereira Braga

Bug Description

Using the Edgy LiveCD, I have the following problem with my USB Memory Stick: After plugging it in, Nautilus opens and shows the contents. After 10-30s the "not savely removed"-Window pops up, and the Stick is mounted again ... for the next 30 seconds. Using the same Stick/Cable/Port with installed Dapper works fine.
My Digital Camera is recognized by Edgy as expected: No remounts.

Edgy-LiveCD dmesg says:
[17182554.816000] usb 2-1: new full speed USB device using uhci_hcd and address 3
[17182554.988000] usb 2-1: configuration #1 chosen from 1 choice
[17182554.988000] hub 2-1:1.0: USB hub found
[17182554.992000] hub 2-1:1.0: 2 ports detected
[17182555.300000] usb 2-1.1: new full speed USB device using uhci_hcd and address 4
[17182555.436000] usb 2-1.1: configuration #1 chosen from 1 choice
[17182555.640000] usb 2-1.2: new full speed USB device using uhci_hcd and address 5
[17182555.772000] usb 2-1.2: configuration #1 chosen from 1 choice
[17182556.472000] usbcore: registered new driver libusual
[17182556.748000] SCSI subsystem initialized
[17182556.960000] Initializing USB Mass Storage driver...
[17182556.960000] scsi0 : SCSI emulation for USB Mass Storage devices
[17182556.960000] usb-storage: device found at 4
[17182556.960000] usb-storage: waiting for device to settle before scanning
[17182556.960000] usbcore: registered new driver usb-storage
[17182556.960000] USB Mass Storage support registered.
[17182561.960000] usb-storage: device scan complete
[17182561.964000] Vendor: Model: Rev:
[17182561.964000] Type: Direct-Access ANSI SCSI revision: 00
[17182562.080000] SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
[17182562.084000] sda: Write Protect is off
[17182562.084000] sda: Mode Sense: 03 00 00 00
[17182562.084000] sda: assuming drive cache: write through
[17182562.088000] SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
[17182562.092000] sda: Write Protect is off
[17182562.092000] sda: Mode Sense: 03 00 00 00
[17182562.092000] sda: assuming drive cache: write through
[17182562.092000] sda: sda1 sda2
[17182562.100000] sd 0:0:0:0: Attached scsi disk sda
[17182564.764000] sd 0:0:0:0: Attached scsi generic sg0 type 0
[17182569.244000] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!

[17182607.032000] usb 2-1.1: USB disconnect, address 4
[17182607.032000] sd 0:0:0:0: rejecting I/O to device being removed
[17182607.032000] Buffer I/O error on device sda1, logical block 231
[17182607.032000] lost page write due to I/O error on sda1
[17182607.040000] usb 2-1.2: USB disconnect, address 5
[17182607.152000] usb 2-1: reset full speed USB device using uhci_hcd and address 3

[17182607.608000] usb 2-1.1: new full speed USB device using uhci_hcd and address 6
[17182607.744000] usb 2-1.1: configuration #1 chosen from 1 choice
[17182607.744000] scsi1 : SCSI emulation for USB Mass Storage devices
[17182607.748000] usb-storage: device found at 6
[17182607.748000] usb-storage: waiting for device to settle before scanning
[17182607.952000] usb 2-1.2: new full speed USB device using uhci_hcd and address 7
[17182608.088000] usb 2-1.2: configuration #1 chosen from 1 choice
[17182612.748000] usb-storage: device scan complete
[17182612.752000] Vendor: Model: Rev:
[17182612.752000] Type: Direct-Access ANSI SCSI revision: 00
[17182612.784000] SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
[17182612.788000] sda: Write Protect is off
[17182612.788000] sda: Mode Sense: 03 00 00 00
[17182612.788000] sda: assuming drive cache: write through
[17182612.796000] SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
[17182612.800000] sda: Write Protect is off
[17182612.800000] sda: Mode Sense: 03 00 00 00
[17182612.800000] sda: assuming drive cache: write through
[17182612.800000] sda: sda1 sda2
[17182612.808000] sd 1:0:0:0: Attached scsi disk sda
[17182612.808000] sd 1:0:0:0: Attached scsi generic sg0 type 0
[17182618.004000] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[17182631.424000] usb 2-1.1: USB disconnect, address 6
[17182631.424000] usb 2-1.2: USB disconnect, address 7
[17182631.652000] usb 2-1: USB disconnect, address 3

Tags: cft-2.6.27
Revision history for this message
towsonu2003 (towsonu2003) wrote :

Thanks for your bug. Could you follow the instruction of https://wiki.ubuntu.com/DebuggingRemovableDevices to get a log of what is happening?

Revision history for this message
flix (felix-hess) wrote :

I followed the instructions in the wiki. All files include one "remount", except the dmesg-output, it includes more than one remount.

buntu@ubuntu:~$ id
uid=999(ubuntu) gid=999(ubuntu) Gruppen=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),109(lpadmin),111(scanner),114(admin),999(ubuntu)
ubuntu@ubuntu:~$ id hal
id: hal: Einen solchen Benutzer gibt es nicht
ubuntu@ubuntu:~$ id haldaemon
uid=106(haldaemon) gid=110(haldaemon) Gruppen=110(haldaemon),24(cdrom),25(floppy),46(plugdev)
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686 GNU/Linux
ubuntu@ubuntu:~$

Revision history for this message
towsonu2003 (towsonu2003) wrote :

thanks. I'll leave it unconfirmed while someone with more knowledge takes a look at your output.

Changed in gnome-volume-manager:
status: Needs Info → Unconfirmed
Changed in gnome-volume-manager:
assignee: nobody → rpereira
Revision history for this message
R. Pereira Braga (rpereira) wrote :

I tried the same configuration. With a Kingston pendrive and had no problem in a Edgy Eft LiveCD.

Did you use some other configuration?

I think the problem could see bad blocks on your Pendrive. Did you try to reformat it?

--
Pereira

Revision history for this message
Martin Pitt (pitti) wrote :

This looks like either a kernel or a hardware bug:

[17180507.648000] sd 3:0:0:0: Attached scsi disk sda
[17180507.648000] sd 3:0:0:0: Attached scsi generic sg0 type 0
[17180509.912000] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[17180554.352000] usb 2-1.1: USB disconnect, address 12
[17180554.352000] sd 3:0:0:0: rejecting I/O to device being removed
[17180554.352000] Buffer I/O error on device sda1, logical block 231
[17180554.352000] lost page write due to I/O error on sda1
[17180554.360000] usb 2-1.2: USB disconnect, address 13
[17180554.472000] usb 2-1: reset full speed USB device using uhci_hcd and address 11
[17180554.928000] usb 2-1.1: new full speed USB device using uhci_hcd and address 14
[17180555.060000] usb 2-1.1: configuration #1 chosen from 1 choice

Is it possible that this might be a power surge or temporary disconnect due to a bad cable or connector? Do you get similar problems with another stick? Or with the same stick on a different computer?

Changed in gnome-volume-manager:
status: Unconfirmed → Needs Info
Revision history for this message
flix (felix-hess) wrote :

Please look in my first posting:
Using the same Stick/Cable/Port with installed Dapper works fine.
My Digital Camera is recognized by Edgy as expected: No remounts.

So for me it seems to be a Software problem with Edgy, which occures with this USB-Stick.

Revision history for this message
John Fleischauer (jflash) wrote :

This is probably fairly obvious, but have you tried it on another USB port on that computer? I've marked this as confirmed, so hopefully someone more knowledgable with this type of issue will see it and take a look.

Changed in gnome-volume-manager:
status: Unconfirmed → Confirmed
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Guys,

Just moving this bug forward to the Hardy "linux" kernel package since the 2.6.17 for Edgy has reached it's end of life for the 18 month support period. When you get a chance, please confirm this against Hardy. Thanks.

Changed in linux-source-2.6.17:
status: Incomplete → Won't Fix
Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Markus Korn (thekorn) wrote :

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks,
Markus

Changed in linux:
status: Incomplete → Won't Fix
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? May you please try the same with Karmic? Thanks in advance.

Changed in gnome-volume-manager (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gnome-volume-manager (Ubuntu):
importance: Undecided → Low
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.