Ubuntu
linux package

0644:0000 won't mount usb floppy

Bug #899803 reported by Edward
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I just got a teac usb external floppy drive and it won't mount. I looked a little bit on forums and will continue to look, and I have tried the below in terminal so far.

edward@SelfmadeDesktop:~$ sudo gedit /etc/modules
[sudo] password for edward:
edward@SelfmadeDesktop:~$ cd /media
edward@SelfmadeDesktop:/media$ dir
ATTACHE\ FLASH\ DRIVE floppy floppy0 Transcend VirtualMachines-13.7GB
edward@SelfmadeDesktop:/media$ sudo mount -t vfat /dev/sdc /media/floppy -o uid=1000
mount: /dev/sdc already mounted or /media/floppy busy
edward@SelfmadeDesktop:/media$ dir
ATTACHE\ FLASH\ DRIVE floppy floppy0 Transcend VirtualMachines-13.7GB
edward@SelfmadeDesktop:/media$ cd floppy
edward@SelfmadeDesktop:/media/floppy$ dir
edward@SelfmadeDesktop:/media/floppy$ cd ..
edward@SelfmadeDesktop:/media$ sudo rmdir floppy
rmdir: failed to remove `floppy': Not a directory
edward@SelfmadeDesktop:/media$ sudo umount /dev/sdc
umount: /dev/sdc: not mounted
edward@SelfmadeDesktop:/media$ sudo mount -t vfat /dev/sdc /media/floppy -o uid=1000
mount: /dev/sdc already mounted or /media/floppy busy
edward@SelfmadeDesktop:/media$ sudo umount /dev/sdc
umount: /dev/sdc: not mounted
edward@SelfmadeDesktop:/media$

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: mount 2.17.2-0ubuntu1.10.10.2
ProcVersionSignature: Ubuntu 2.6.35-31.62-generic 2.6.35.13
Uname: Linux 2.6.35-31-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Dec 3 20:19:19 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: util-linux

Revision history for this message
Edward (edwardtisdale-2004) wrote :
Revision history for this message
Edward (edwardtisdale-2004) wrote :

Here's some more info:

edward@SelfmadeDesktop:~$ lsusb
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 011: ID 03f0:5c11 Hewlett-Packard PhotoSmart C4200 Printer series
Bus 001 Device 010: ID 0644:0000 TEAC Corp. Floppy
Bus 001 Device 009: ID 8564:1000
Bus 001 Device 007: ID 090c:1000 Feiya Technology Corp. Flash Drive
Bus 001 Device 005: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 001 Device 004: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 001 Device 002: ID 0ace:1215 ZyDAS ZD1211B 802.11g
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
edward@SelfmadeDesktop:~$

Revision history for this message
Edward (edwardtisdale-2004) wrote :

edward@SelfmadeDesktop:~$ lsusb -v -d 0644:0000

Bus 001 Device 010: ID 0644:0000 TEAC Corp. Floppy
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x0644 TEAC Corp.
  idProduct 0x0000 Floppy
  bcdDevice 2.00
  iManufacturer 1
  iProduct 2
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 39
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
      (Bus Powered)
    MaxPower 98mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 4 Floppy (UFI)
      bInterfaceProtocol 0 Control/Bulk/Interrupt
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0002 1x 2 bytes
        bInterval 127
cannot read device status, Operation not permitted (1)

Revision history for this message
Edward (edwardtisdale-2004) wrote :

As far as the operation not permitted thing, I tried using chmod on the /media/floppy and /media/floppy0 but still nothing.

edward@SelfmadeDesktop:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda7 258488676 6242208 239115972 3% /
none 1408584 288 1408296 1% /dev
none 1415452 208 1415244 1% /dev/shm
none 1415452 96 1415356 1% /var/run
none 1415452 0 1415452 0% /var/lock
/dev/sda2 9611492 5096900 4026352 56% /part1
/dev/sda3 15364496 169176 14414828 2% /part3
/dev/sda5 20157308 20157300 0 100% /part2
/dev/sdc1 7959928 4024096 3935832 51% /media/ATTACHE FLASH DRIVE
/dev/sde1 15836016 15683552 152464 100% /media/Transcend
edward@SelfmadeDesktop:~$

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

We would like to collect some additional information about your system. From a terminal, please run the following:

apport-collect 899803

affects: util-linux (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Also, would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Thanks in advance.

tags: added: needs-upstream-testing
Revision history for this message
Edward (edwardtisdale-2004) wrote : Re: [Bug 899803] Re: won't mount usb floppy

On 12/06/2011 07:35 AM, Joseph Salisbury wrote:
> Also, would it be possible for you to test the latest upstream kernel?
> It will allow additional upstream developers to examine the issue. Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please
> test the latest v3.2-rcN kernel (Not a kernel in the daily directory).
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag(Only that one tag, please leave the other tags).
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the 'needs-
> upstream-testing' text.
>
> If this bug is fixed by the mainline kernel, please add the following
> tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel
> version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-
> upstream-v3.2-rc1'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream'. If you
> believe this bug does not require upstream testing, please add the tag:
> 'kernel-upstream-testing-not-needed'.
>
>
> Thanks in advance.
>
> ** Tags added: needs-upstream-testing
>
 So then the floppy drive problem is related to the kernel? I'll see
about doing this on a VM.

Revision history for this message
Edward (edwardtisdale-2004) wrote :

On 12/06/2011 07:35 AM, Joseph Salisbury wrote:
> Also, would it be possible for you to test the latest upstream kernel?
> It will allow additional upstream developers to examine the issue. Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please
> test the latest v3.2-rcN kernel (Not a kernel in the daily directory).
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag(Only that one tag, please leave the other tags).
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the 'needs-
> upstream-testing' text.
>
> If this bug is fixed by the mainline kernel, please add the following
> tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel
> version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-
> upstream-v3.2-rc1'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream'. If you
> believe this bug does not require upstream testing, please add the tag:
> 'kernel-upstream-testing-not-needed'.
>
>
> Thanks in advance.
>
> ** Tags added: needs-upstream-testing
>
 Actually, if I do it on a VM it won't be 64 bit. Would that be okay?

Revision history for this message
Edward (edwardtisdale-2004) wrote :

On 12/06/2011 07:35 AM, Joseph Salisbury wrote:
> Also, would it be possible for you to test the latest upstream kernel?
> It will allow additional upstream developers to examine the issue. Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please
> test the latest v3.2-rcN kernel (Not a kernel in the daily directory).
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag(Only that one tag, please leave the other tags).
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the 'needs-
> upstream-testing' text.
>
> If this bug is fixed by the mainline kernel, please add the following
> tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel
> version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-
> upstream-v3.2-rc1'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream'. If you
> believe this bug does not require upstream testing, please add the tag:
> 'kernel-upstream-testing-not-needed'.
>
>
> Thanks in advance.
>
> ** Tags added: needs-upstream-testing
>
 I guess, looking at the instructions, it should be pretty easy without
using a vm. Sure I'll try it out.

Revision history for this message
Edward (edwardtisdale-2004) wrote :

On 12/06/2011 07:35 AM, Joseph Salisbury wrote:
> Also, would it be possible for you to test the latest upstream kernel?
> It will allow additional upstream developers to examine the issue. Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please
> test the latest v3.2-rcN kernel (Not a kernel in the daily directory).
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag(Only that one tag, please leave the other tags).
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the 'needs-
> upstream-testing' text.
>
> If this bug is fixed by the mainline kernel, please add the following
> tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel
> version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-
> upstream-v3.2-rc1'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream'. If you
> believe this bug does not require upstream testing, please add the tag:
> 'kernel-upstream-testing-not-needed'.
>
>
> Thanks in advance.
>
> ** Tags added: needs-upstream-testing
>
 Another problem. I wasn't planning on upgrading to Natty or Oneiric
because well Natty is fine, but I didn't like the changes in Oneiric.
I'll just have to go back to my idea of using a vm, and use Oneiric in
order to use the 3.2 rcl kernel. What do you think?

Revision history for this message
Edward (edwardtisdale-2004) wrote :

On 12/06/2011 07:35 AM, Joseph Salisbury wrote:
> Also, would it be possible for you to test the latest upstream kernel?
> It will allow additional upstream developers to examine the issue. Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please
> test the latest v3.2-rcN kernel (Not a kernel in the daily directory).
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag(Only that one tag, please leave the other tags).
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the 'needs-
> upstream-testing' text.
>
> If this bug is fixed by the mainline kernel, please add the following
> tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel
> version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-
> upstream-v3.2-rc1'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream'. If you
> believe this bug does not require upstream testing, please add the tag:
> 'kernel-upstream-testing-not-needed'.
>
>
> Thanks in advance.
>
> ** Tags added: needs-upstream-testing
>
 Just letting you know that I re-upgraded to Oneiric and with the Gnome
fallback working better now I am happy with it. I will proceed now to
install thev3.2-rc4-oneiric kernel.

Revision history for this message
Edward (edwardtisdale-2004) wrote :

On 12/06/2011 07:35 AM, Joseph Salisbury wrote:
> Also, would it be possible for you to test the latest upstream kernel?
> It will allow additional upstream developers to examine the issue. Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please
> test the latest v3.2-rcN kernel (Not a kernel in the daily directory).
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag(Only that one tag, please leave the other tags).
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the 'needs-
> upstream-testing' text.
>
> If this bug is fixed by the mainline kernel, please add the following
> tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel
> version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-
> upstream-v3.2-rc1'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream'. If you
> believe this bug does not require upstream testing, please add the tag:
> 'kernel-upstream-testing-not-needed'.
>
>
> Thanks in advance.
>
> ** Tags added: needs-upstream-testing
>
 wouldn't install kernel. Trying v3.2-rc2-oneiric.

Revision history for this message
Edward (edwardtisdale-2004) wrote :

On 12/06/2011 07:35 AM, Joseph Salisbury wrote:
> Also, would it be possible for you to test the latest upstream kernel?
> It will allow additional upstream developers to examine the issue. Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please
> test the latest v3.2-rcN kernel (Not a kernel in the daily directory).
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag(Only that one tag, please leave the other tags).
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the 'needs-
> upstream-testing' text.
>
> If this bug is fixed by the mainline kernel, please add the following
> tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel
> version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-
> upstream-v3.2-rc1'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not
> boot, please add the tag: 'kernel-unable-to-test-upstream'. If you
> believe this bug does not require upstream testing, please add the tag:
> 'kernel-upstream-testing-not-needed'.
>
>
> Thanks in advance.
>
> ** Tags added: needs-upstream-testing
>
 My computer didn't want to but past the first blank screen with the rc
kernels. Maybe if I had waited longer. Would you expect it take a long time?

penalvch (penalvch)
summary: - won't mount usb floppy
+ 0644:0000 won't mount usb floppy
Revision history for this message
penalvch (penalvch) wrote :

Edward, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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