Flash drive problem, Kubuntu 8.04

[hermanningjaldsson]

I have a 16GB Corsair flash drive.

Its got 8GB of data on it but when i plug it in i can only see a small portion of that data.
Only some folders appear.

And i also cannot write to the flash drive.
It gives no reason why, it just says "cannot write to flash drive".

What can i do to fix this?

sincerely,
Hermann Ingjaldsson

[Marcus Asshauer (mcas)]

Thank you for reporting this bug. Please attach the output of "dmesg" after you plug in the stick. Which filesystem do you use on the usb stick?

[hermanningjaldsson (hermannjens)]

i have no idea which filesystem i use on the stick.
how do i find out?

what do u mean by "dmesg"?
i typed that in the console after putting in the stick... and its a very
long output.
here it comes:
"
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.24-19-generic (buildd@terranova) (gcc
version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Aug 20 22:56:21 UTC 2008
(Ubuntu 2.6.24-19.41-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000003f4fe000 (usable)
[ 0.000000] BIOS-e820: 000000003f4fe000 - 000000003f509000 (reserved)
[ 0.000000] BIOS-e820: 000000003f509000 - 000000003f552000 (usable)
[ 0.000000] BIOS-e820: 000000003f552000 - 000000003f555000 (reserved)
[ 0.000000] BIOS-e820: 000000003f555000 - 000000003f5bb000 (usable)
[ 0.000000] BIOS-e820: 000000003f5bb000 - 000000003f5bf000 (reserved)
[ 0.000000] BIOS-e820: 000000003f5bf000 - 000000003f672000 (usable)
[ 0.000000] BIOS-e820: 000000003f672000 - 000000003f6bf000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000003f6bf000 - 000000003f700000 (ACPI data)
[ 0.000000] BIOS-e820: 000000003f700000 - 0000000040000000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed14000 - 00000000fed1a000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
[ 0.000000] 118MB HIGHMEM available.
[ 0.000000] 896MB LOWMEM available.
[ 0.000000] found SMP MP-table at 000fe1b0
[ 0.000000] Entering add_active_range(0, 0, 259698) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 229376
[ 0.000000] HighMem 229376 -> 259698
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 259698
[ 0.000000] On node 0 totalpages: 259698
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 1760 pages used for memmap
[ 0.000000] Normal zone: 223520 pages, LIFO batch:31
[ 0.000000] HighMem zone: 236 pages used for memmap
[ 0.000000] HighMem zone: 30086 pages, LIFO batch:7
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] DMI 2.4 present.
[ 0.000000] ACPI: RSDP signature @ 0xC00FE020 checksum 0
[ 0.000000] ACPI: RSDP 000FE020, 0024 (r2 ACRSYS)
[ 0.000000] ACPI: XSDT 3F6FE120, 0064 (r1 ACRSYS ACRPRDCT 1
1000013)
[ 0.000000] ACPI: FACP 3F6FD000, 00F4 (r4 ACRSYS ACRPRDCT ...

[Leann Ogasawara (leannogasawara)]

Hi hermanningljaldsson,

First, I'm going to reassign this to the linux kernel package as this seems to be a kernel issue.

Even before you insert the usbstick I'm seeing a flood of "APIC error on CPU0: 40(40)" errors in you dmesg output. I've seen a few of these types of reports before and they were either resolved with a BIOS update or I'd seen some comments that the newer 2.6.27 kernel available in the upcoming Intrepid Ibex 8.10 release resolved some of there. Care to maybe try the 2.6.27 kernel first? You should be able to test the newer 2.6.27 kernel by just using a LiveCD of the most recent Alpha for Intrepid - http://www.ubuntu.com/testing . Also when running the LiveCD try inserting the usb stick and see if that issue is resolved as well. If the issue still exist, please attach an updated dmesg output after you've inserted the usb stick just as you did before using the 2.6.24 kernel. Thanks.

[Leann Ogasawara (leannogasawara)]

And if the above doesn't help, first backup the data on the usb stick, then as noted in:

https://answers.edge.launchpad.net/ubuntu/+question/2252

You may want to try:

sudo dosfsck -a /dev/sdb1

[hermanningjaldsson (hermannjens)]

i have no idea what a BIOS update means, and therefore needless to say.. i
have no idea how to make that happen.

downloading the whole 8.10 operating system, installing to a cd and running
it seems like a tad too much hazzle,
especially if the issue will be solved in the next upgrade.

i tried doing "sudo dosfsck -a /dev/sdb1"
it went in the following way:
"
hermann@hermann-laptop:~$ sudo dosfsck -a /dev/sdb1
[sudo] password for hermann:
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
open /dev/sdb1:No such file or directory
hermann@hermann-laptop:~$
"

On Tue, Sep 30, 2008 at 9:10 PM, Leann Ogasawara <email address hidden> wrote:

> Hi hermanningljaldsson,
>
> First, I'm going to reassign this to the linux kernel package as this
> seems to be a kernel issue.
>
> Even before you insert the usbstick I'm seeing a flood of "APIC error on
> CPU0: 40(40)" errors in you dmesg output. I've seen a few of these
> types of reports before and they were either resolved with a BIOS update
> or I'd seen some comments that the newer 2.6.27 kernel available in the
> upcoming Intrepid Ibex 8.10 release resolved some of there. Care to
> maybe try the 2.6.27 kernel first? You should be able to test the newer
> 2.6.27 kernel by just using a LiveCD of the most recent Alpha for
> Intrepid - http://www.ubuntu.com/testing . Also when running the LiveCD
> try inserting the usb stick and see if that issue is resolved as well.
> If the issue still exist, please attach an updated dmesg output after
> you've inserted the usb stick just as you did before using the 2.6.24
> kernel. Thanks.
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: kdebase => linux
>
> --
> Flash drive problem, Kubuntu 8.04
> https://bugs.launchpad.net/bugs/276341
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Incomplete
>
> Bug description:
> I have a 16GB Corsair flash drive.
>
> Its got 8GB of data on it but when i plug it in i can only see a small
> portion of that data.
> Only some folders appear.
>
> And i also cannot write to the flash drive.
> It gives no reason why, it just says "cannot write to flash drive".
>
>
> What can i do to fix this?
>
> sincerely,
> Hermann Ingjaldsson
>
>
>

[Wrwrwr (wrwrwr)]

A BIOS update means replacing some firmware on your motherboard: usually you check the producer of your motherboard, visit their site and in some "support" section look for BIOS updates and a manual for the given model (one of sites having more info: http://www.wikihow.com/Update-Your-Computer%27s-BIOS). This would maybe solve this flood mentioned above, so maybe improve efficiency or avoid some crashes and other problems.

For the command be sure to have the flash plugged in, note that this may lead to data loss on the drive, so make a backup first (using Windows or another machine). Also, the disk might have been mapped to a different device, look for "FAT: Filesystem panic (dev sdb1)" in dmesg output and if it says something different than "dev sdb1" update the command.

[hermanningjaldsson (hermannjens)]

i did the "sudo dosfsck -a /dev/sdb1" again and now it worked.

after doing that i needed to remove the pin and reinsert it.
then the whole thing started working.

so, thanks!
Hermann

On Tue, Sep 30, 2008 at 11:31 PM, Wrwrwr <email address hidden> wrote:
>
> A BIOS update means replacing some firmware on your motherboard: usually
> you check the producer of your motherboard, visit their site and in some
> "support" section look for BIOS updates and a manual for the given model
> (one of sites having more info: http://www.wikihow.com/Update-Your-
> Computer%27s-BIOS <http://www.wikihow.com/Update-Your-Computer%27s-BIOS>).
> This would maybe solve this flood mentioned above,
> so maybe improve efficiency or avoid some crashes and other problems.
>
> For the command be sure to have the flash plugged in, note that this may
> lead to data loss on the drive, so make a backup first (using Windows or
> another machine). Also, the disk might have been mapped to a different
> device, look for "FAT: Filesystem panic (dev sdb1)" in dmesg output and
> if it says something different than "dev sdb1" update the command.
>
> --
> Flash drive problem, Kubuntu 8.04
> https://bugs.launchpad.net/bugs/276341
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Incomplete
>
> Bug description:
> I have a 16GB Corsair flash drive.
>
> Its got 8GB of data on it but when i plug it in i can only see a small
> portion of that data.
> Only some folders appear.
>
> And i also cannot write to the flash drive.
> It gives no reason why, it just says "cannot write to flash drive".
>
>
> What can i do to fix this?
>
> sincerely,
> Hermann Ingjaldsson
>
>
>

[Leann Ogasawara (leannogasawara)]

Hi hermanningjaldsson,

Based on your last comment it seems this is now resolved. It's appears the filesystem on you usb stick was corrupted so running the dosfsck resolved this. I'll go ahead and close this report. Thanks.

[hermanningjaldsson (hermannjens)]

now im trying to plug this flash drive into another computer and off course
it doesn't work.
Things pretty much never work without 2 hours of work making error reports.

now when i do dmesg it says:
"
[ 6420.929271] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 6436.332183] eth0: no IPv6 routers present
[ 6479.289693] usb 6-7: new high speed USB device using ehci_hcd and address
33
[ 6495.911801] usb 6-7: device descriptor read/64, error -110
[ 6511.154515] usb 6-7: device descriptor read/64, error -110
[ 6511.370383] usb 6-7: new high speed USB device using ehci_hcd and address
34
[ 6526.509154] usb 6-7: device descriptor read/64, error -110
[ 6541.753361] usb 6-7: device descriptor read/64, error -110
[ 6541.967746] usb 6-7: new high speed USB device using ehci_hcd and address
35
[ 6552.393400] usb 6-7: device not accepting address 35, error -110
[ 6552.505356] usb 6-7: new high speed USB device using ehci_hcd and address
36
[ 6564.434381] usb 6-7: device not accepting address 36, error -110
[ 6803.773466] usb 4-2: USB disconnect, address 4
[ 6807.030702] usb 5-1: new low speed USB device using ohci_hcd and address
4
[ 6807.266180] usb 5-1: configuration #1 chosen from 1 choice
[ 6807.276762] input: CHICONY USB Keyboard as
/devices/pci0000:00/0000:00:13.4/usb5/5-1/5-1:1.0/input/input12
[ 6807.302694] input,hidraw1: USB HID v1.10 Keyboard [CHICONY USB Keyboard]
on usb-0000:00:13.4-1
[ 6809.641101] usb 6-8: new high speed USB device using ehci_hcd and address
38
[ 6824.779872] usb 6-8: device descriptor read/64, error -110
[ 6840.022593] usb 6-8: device descriptor read/64, error -110
[ 6840.238454] usb 6-8: new high speed USB device using ehci_hcd and address
39
[ 6859.340654] usb 6-8: device descriptor read/64, error -110
[ 6877.305443] usb 6-8: device descriptor read/64, error -110
[ 6877.521331] usb 6-8: new high speed USB device using ehci_hcd and address
40
[ 6887.946973] usb 6-8: device not accepting address 40, error -110
[ 6888.059059] usb 6-8: new high speed USB device using ehci_hcd and address
41
[ 6898.484522] usb 6-8: device not accepting address 41, error -110

"

what does error -110 mean?

how can that be fixed?

On Wed, Oct 1, 2008 at 6:39 PM, Leann Ogasawara <email address hidden> wrote:

> Hi hermanningjaldsson,
>
> Based on your last comment it seems this is now resolved. It's appears
> the filesystem on you usb stick was corrupted so running the dosfsck
> resolved this. I'll go ahead and close this report. Thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> Flash drive problem, Kubuntu 8.04
> https://bugs.launchpad.net/bugs/276341
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Invalid
>
> Bug description:
> I have a 16GB Corsair flash drive.
>
> Its got 8GB of data on it but when i plug it in i can only see a small
> portion of that data.
> Only some folders appear.
>
> And i also cannot write to the flash drive.
> It gives no reason why, it just says "cannot write to flash drive".
>
>
> What can i do to fix this?
>
> sincerely,
> Hermann Ingjaldsson
>
>
>

[Wrwrwr (wrwrwr)]

Citing some other thread: "The error means the computer is unable to communicate with the flash drive. There was no response to a Get-Device-Descriptor request within the timeout limit.".

This may be a bad cable or some other hardware problem, there is one report of a hard disk with "cable select" jumper set causing such errors (but I don't suppose your flash has any jumpers :). One proposed solution is removing one driver and hoping the other (low speed ohci_hcd) will work:

sudo modprobe -r ehci_hcd
(should ask you for password)