Help - Search - Members - Calendar
Full Version: Unable To Mount Usb-key After Re-formatting It
OESF Forums > Distros, Development, and Model Specific Forums > Model Specific Forums > C1000/3x00 General discussions
mbagsh55
Hi Guys,
Firstly apologies for starting yet another "how to mount xxx on a c3x00" thread, but I could not find the answer through searching and I felt it was rude to hijack one of the threads that were specifically about mounting HDD, mobile phones, ZIP disks, etc.

My problem is that the USB key (thumbdrive) I routinely use for swapping files from work to home got corrupted and I needed to reformat it. Since the re-format I have been unable to use it on my Zaurus (SL-C3100, sharp rom with Meanies automouter 0.5.0).

Two other USB-keys work so it isn't the Z-usbport (phew) or the host cable.

The USB-key is detected in system info:

Vendor: Silicon Integrated Systems Corp.
Product: USB Mass Storage Device
Class: Mass-Storage
ID: 0457/0151
Driver: usb-storage

But is not automounted, or seems to be correctly mapped to sda/sdb.

>fdisk -l /dev/sda
Cannot open /dev/sda

>dmesg | tail
usb-storage: *** thread sleeping.
jffs2: attempt to mount non-MTD device 08:01
usb-storage: queuecommand() called
usb-storage: *** thread awakened.
usb-storage: Command ALLOW_MEDIUM_REMOVAL (6 bytes)
usb-storage: 1e 00 00 00 00 00 04 c0 00 ea 6e c3
usb-storage: Bulk command S 0x43425355 T 0x77e Trg 0 LUN 0 L 0 F 0 CL 6
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: Bulk status result = 0
usb-storage: Bulk status Sig 0x53425355 T 0x77e R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usbd_device_configuration_instance: configuration out of range: 0 1 1


The USB-Key is acessible OK from my Windows 98 machine, and my work Windows XP box. I have tried both FAT-16 anf FAT-32 format, but the Z reacted the same in both cases.

Any advise appreciated.

Thanks and regards,
Marcus

p.s. Happy New Year to all OESF members biggrin.gif
Drake01
QUOTE(mbagsh55 @ Jan 5 2007, 10:00 AM)
My problem is that the USB key (thumbdrive) I routinely use for swapping files from work to home got corrupted and I needed to reformat it.  Since the re-format I have been unable to use it on my Zaurus (SL-C3100, sharp rom with Meanies automouter 0.5.0).
...
The USB-Key is acessible OK from my Windows 98 machine, and my work Windows XP box.  I have tried both FAT-16 anf FAT-32 format, but the Z reacted the same in both cases.
*

If you reformatted in Windoze, I wonder if your problem is related to the issue mentioned in this post.
mbagsh55
QUOTE(Drake01 @ Jan 6 2007, 12:20 PM)
If you reformatted in Windoze, I wonder if your problem is related to the issue mentioned in this post.
*

Hi Drake,
Thanks for the reply, I think you are right that this is related to the problem reported in the message you linked.

When I fsck.vfat /dev/sda1 on the Z it reported that "Currently only 2 FATs are supported not 186" blink.gif
I tried mkfs.vfat /dev/sda1 and the USB-key light flashes for a bit and then nothing else happens.

When I tried fdisk /dev/sda1, it allowed me to write a partition, set to FAT32 and write to disk (or so it reported). When I removed the USB-key and then retrieved mkfs.vfat though the same thing happened a bit of activity (flashing light) tthen a long wait, and after 5 minutes I just removed the USB-key and restarted the Z.

Rather curiously despite all this the USB-key is still visible on Win98, reports no problems in the Windows DiskChecker and the files are still present. When inserted in the Z, there is no change in the dmesg output Very stange.

A bit of a mystery (especially with my very limited Linux knowledge).
Drake01
QUOTE(mbagsh55 @ Jan 6 2007, 05:57 AM)
When I tried fdisk /dev/sda1, it allowed me to write a partition, set to FAT32 and write to disk (or so it reported).  When I removed the USB-key and then retrieved mkfs.vfat though the same thing happened a bit of activity (flashing light) tthen a long wait, and after 5 minutes I just removed the USB-key and restarted the Z.
*

What do you get if you try fdisk /dev/sda? If there are any partitions listed, try deleting them and recreating them. If there are no partitions listed, just create one. Then try creating a filesystem on the partition you created.

/dev/sda1 should be a single partition, not the whole device. I don't know what fdisk is actually showing you if you open /dev/sda1 with fdisk.
mbagsh55
QUOTE(Drake01 @ Jan 8 2007, 07:52 AM)
What do you get if you try fdisk /dev/sda?  If there are any partitions listed, try deleting them and recreating them.  If there are no partitions listed, just create one.  Then try creating a filesystem on the partition you created.


Hi Drake,
Well done that fixed it!

As you suspected it was the same basic problem as reported in the other post with SD cards. I run fdisk /dev/sda and four partitions with dubious information (512 GB usb partition tongue.gif ) were displayed. Removing them and creating a single partition that then responded correctly to mkfs.vfat /dev/sda1.

My usb-key works perfectly now, and as an added bonus seems to mount and un-mount much more quickly than before the initial crash.

Many thanks for the Linux lesson and solving my problem,
Marcus
Drake01
QUOTE(mbagsh55 @ Jan 8 2007, 06:49 AM)
Many thanks for the Linux lesson and solving my problem,
Marcus
*

Glad I could help!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.