I recently bought a snazzy new 16GB USB pen drive from the local store - it was only $29! I have several drives that are 8GB and smaller from the same store that are the same brand.
Imagine my surprise when: * The 16GB drive is not accessible on either F9 or F10 Snap 3 * The 8GB drives all work just fine on both F9 and F10 Snap 3 * The 16GB drive works fine on Windows XP * The 16GB drive also works on a Windows XP VM running on top of F9!!!
I can only conclude from this that something is a miss that causes F9 to not be able to access and use USB pen drives that are bigger than 8GB, and that this most likely has something to do with a file system driver or such.
Anyone else seen this yet? Is there a fix / work-around?
Here's the dmesg output for those who might be interested:
============================================== usb 1-2.3: new high speed USB device using ehci_hcd and address 13 usb 1-2.3: configuration #1 chosen from 1 choice scsi1264 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 13 usb-storage: waiting for device to settle before scanning usb 1-2.3: New USB device found, idVendor=090c, idProduct=1000 usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-2.3: Product: USB Flash Drive usb 1-2.3: Manufacturer: USB 2.0 usb 1-2.3: SerialNumber: AA20000000000306 usb-storage: device scan complete scsi 1264:0:0:0: Direct-Access USB 2.0 USB Flash Drive 1100 PQ: 0 ANSI: 0 CCS sd 1264:0:0:0: [sdb] 31326208 512-byte hardware sectors (16039 MB) sd 1264:0:0:0: [sdb] Write Protect is off sd 1264:0:0:0: [sdb] Mode Sense: 43 00 00 00 sd 1264:0:0:0: [sdb] Assuming drive cache: write through sd 1264:0:0:0: [sdb] 31326208 512-byte hardware sectors (16039 MB) sd 1264:0:0:0: [sdb] Write Protect is off sd 1264:0:0:0: [sdb] Mode Sense: 43 00 00 00 sd 1264:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 1264:0:0:0: [sdb] Attached SCSI removable disk sd 1264:0:0:0: Attached scsi generic sg3 type 0 ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata5.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata5.00: status: { DRDY } ata5: soft resetting link ata5: nv_mode_filter: 0x1&0x1f01f->0x1, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:600:0x13) ata5.00: configured for PIO0 ata5: EH complete ==============================================
Cheers,
Chris
Christopher A. Williams wrote:
I recently bought a snazzy new 16GB USB pen drive from the local store - it was only $29! I have several drives that are 8GB and smaller from the same store that are the same brand.
Imagine my surprise when:
- The 16GB drive is not accessible on either F9 or F10 Snap 3
- The 8GB drives all work just fine on both F9 and F10 Snap 3
- The 16GB drive works fine on Windows XP
- The 16GB drive also works on a Windows XP VM running on top of F9!!!
I can only conclude from this that something is a miss that causes F9 to not be able to access and use USB pen drives that are bigger than 8GB, and that this most likely has something to do with a file system driver or such.
Anyone else seen this yet? Is there a fix / work-around?
Here's the dmesg output for those who might be interested:
============================================== usb 1-2.3: new high speed USB device using ehci_hcd and address 13 usb 1-2.3: configuration #1 chosen from 1 choice scsi1264 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 13 usb-storage: waiting for device to settle before scanning usb 1-2.3: New USB device found, idVendor=090c, idProduct=1000 usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-2.3: Product: USB Flash Drive usb 1-2.3: Manufacturer: USB 2.0 usb 1-2.3: SerialNumber: AA20000000000306 usb-storage: device scan complete scsi 1264:0:0:0: Direct-Access USB 2.0 USB Flash Drive 1100 PQ: 0 ANSI: 0 CCS sd 1264:0:0:0: [sdb] 31326208 512-byte hardware sectors (16039 MB) sd 1264:0:0:0: [sdb] Write Protect is off sd 1264:0:0:0: [sdb] Mode Sense: 43 00 00 00 sd 1264:0:0:0: [sdb] Assuming drive cache: write through sd 1264:0:0:0: [sdb] 31326208 512-byte hardware sectors (16039 MB) sd 1264:0:0:0: [sdb] Write Protect is off sd 1264:0:0:0: [sdb] Mode Sense: 43 00 00 00 sd 1264:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 1264:0:0:0: [sdb] Attached SCSI removable disk sd 1264:0:0:0: Attached scsi generic sg3 type 0 ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata5.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata5.00: status: { DRDY } ata5: soft resetting link ata5: nv_mode_filter: 0x1&0x1f01f->0x1, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:600:0x13) ata5.00: configured for PIO0 ata5: EH complete ==============================================
Cheers,
Chris
Chris,
Looks good. Did you try mounting the drive and see if you can get a directory list?
James
On Mon, 2008-10-27 at 17:05 -0400, James Kosin wrote:
Christopher A. Williams wrote:
I recently bought a snazzy new 16GB USB pen drive from the local store - it was only $29! I have several drives that are 8GB and smaller from the same store that are the same brand.
Imagine my surprise when:
- The 16GB drive is not accessible on either F9 or F10 Snap 3
- The 8GB drives all work just fine on both F9 and F10 Snap 3
- The 16GB drive works fine on Windows XP
- The 16GB drive also works on a Windows XP VM running on top of F9!!!
<snip...>
Here's the dmesg output for those who might be interested:
============================================== usb 1-2.3: new high speed USB device using ehci_hcd and address 13 usb 1-2.3: configuration #1 chosen from 1 choice scsi1264 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 13 usb-storage: waiting for device to settle before scanning usb 1-2.3: New USB device found, idVendor=090c, idProduct=1000 usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-2.3: Product: USB Flash Drive usb 1-2.3: Manufacturer: USB 2.0 usb 1-2.3: SerialNumber: AA20000000000306 usb-storage: device scan complete scsi 1264:0:0:0: Direct-Access USB 2.0 USB Flash Drive 1100 PQ: 0 ANSI: 0 CCS sd 1264:0:0:0: [sdb] 31326208 512-byte hardware sectors (16039 MB) sd 1264:0:0:0: [sdb] Write Protect is off sd 1264:0:0:0: [sdb] Mode Sense: 43 00 00 00 sd 1264:0:0:0: [sdb] Assuming drive cache: write through sd 1264:0:0:0: [sdb] 31326208 512-byte hardware sectors (16039 MB) sd 1264:0:0:0: [sdb] Write Protect is off sd 1264:0:0:0: [sdb] Mode Sense: 43 00 00 00 sd 1264:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 1264:0:0:0: [sdb] Attached SCSI removable disk sd 1264:0:0:0: Attached scsi generic sg3 type 0 ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata5.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) ata5.00: status: { DRDY } ata5: soft resetting link ata5: nv_mode_filter: 0x1&0x1f01f->0x1, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:600:0x13) ata5.00: configured for PIO0 ata5: EH complete ==============================================
Chris,
Looks good. Did you try mounting the drive and see if you can get a directory list?
Interesting... Indeed if I manually try to mount the drive as root to a specific mount point, it does work.
So it seems it's automount that does not work. Neither does attempting to mount the drive manually from a Nautilus window (right-click the "USB Drive" icon and selecting "Mount Volume", or just double-clicking it). All i get is an error window saying "Unable to mount drive".
What's strange is that automounting my 8GB drive of the same brand (as well as an 8GB drive of a different brand) _does_ work. I don't have to be root and mount it to a specific point manually to get to it.
What could be causing that...?
Cheers,
Chris
Christopher A. Williams wrote:
I recently bought a snazzy new 16GB USB pen drive from the local store - it was only $29! I have several drives that are 8GB and smaller from the same store that are the same brand.
Imagine my surprise when:
- The 16GB drive is not accessible on either F9 or F10 Snap 3
- The 8GB drives all work just fine on both F9 and F10 Snap 3
- The 16GB drive works fine on Windows XP
- The 16GB drive also works on a Windows XP VM running on top of F9!!!
I can only conclude from this that something is a miss that causes F9 to not be able to access and use USB pen drives that are bigger than 8GB, and that this most likely has something to do with a file system driver or such.
Anyone else seen this yet? Is there a fix / work-around?
I've seen several USB pen drives with inconsistent partition tables, such as a CHS geometry that leaves a few unallocated sectors (no great surprise) but a partition with a sector count that goes beyond the claimed last cylinder and does use the entire device. Automount is deliberately made sensitive to such anomalies.
Take a look at what "fdisk -l" and "fsck.msdos" have to say about the drive. Errors such as "Partition has different physical/logical endings" should be cause for concern. You might need to repartition the device and/or rebuild the filesystem.
On Tue, 2008-10-28 at 00:23 -0500, Robert Nichols wrote:
Christopher A. Williams wrote:
I recently bought a snazzy new 16GB USB pen drive from the local store - it was only $29! I have several drives that are 8GB and smaller from the same store that are the same brand.
Imagine my surprise when:
- The 16GB drive is not accessible on either F9 or F10 Snap 3
- The 8GB drives all work just fine on both F9 and F10 Snap 3
- The 16GB drive works fine on Windows XP
- The 16GB drive also works on a Windows XP VM running on top of F9!!!
<snip...>
I've seen several USB pen drives with inconsistent partition tables, such as a CHS geometry that leaves a few unallocated sectors (no great surprise) but a partition with a sector count that goes beyond the claimed last cylinder and does use the entire device. Automount is deliberately made sensitive to such anomalies.
Take a look at what "fdisk -l" and "fsck.msdos" have to say about the drive. Errors such as "Partition has different physical/logical endings" should be cause for concern. You might need to repartition the device and/or rebuild the filesystem.
Thanks - This made complete sense to me - and you were right! Here's the output of fdisk: Disk /dev/sdb: 16.0 GB, 16039018496 bytes 75 heads, 40 sectors/track, 10442 cylinders Units = cylinders of 3000 * 512 = 1536000 bytes Disk identifier: 0xc3072e18
Device Boot Start End Blocks Id System /dev/sdb1 * 1 10443 15663084 c W95 FAT32 (LBA)
...And here's a summary of what fsck.msdos said: dosfsck 2.11, 12 Mar 2005, FAT32, LFN There are differences between boot sector and its backup. Differences: (offset:original/backup) 0:eb/00, 1:58/00, 2:90/00, 3:4d/00, 4:53/00, 5:44/00, 6:4f/00, 7:53/00 , 8:35/00, 9:2e/00, 10:30/00, 12:02/00, 13:10/00, 14:24/00, 16:02/00
...
, 497:74/00, 498:0d/00, 499:0a/00, 505:ac/00, 506:cb/00, 507:d8/00 , 510:55/00, 511:aa/00 1) Copy original to backup 2) Copy backup to original 3) No action ?
...followed by messages about cluster size mismatches, and the like.
So I repartitioned and re-formatted the drive (had to use my Windows XP VM for that - see question below), and voila!
Now, one last question: what's the flag to format a FAT32 partition with mkfs? I saw options for pretty much everything but that. I'm probably just suffering from not having had my first cup of coffee... :)
Cheers,
Chris
-- ================================== By all means marry; If you get a good wife, you'll be happy. If you get a bad one, you'll become a philosopher.
--Socrates
On Mon, 2008-10-27 at 14:49 -0600, Christopher A. Williams wrote:
I recently bought a snazzy new 16GB USB pen drive from the local store
it was only $29! I have several drives that are 8GB and smaller from the same store that are the same brand.
Imagine my surprise when:
- The 16GB drive is not accessible on either F9 or F10 Snap 3
- The 8GB drives all work just fine on both F9 and F10 Snap 3
- The 16GB drive works fine on Windows XP
- The 16GB drive also works on a Windows XP VM running on top of F9!!!
I can only conclude from this that something is a miss that causes F9 to not be able to access and use USB pen drives that are bigger than 8GB, and that this most likely has something to do with a file system driver or such.
Anyone else seen this yet? Is there a fix / work-around?
I had the same behavior with a 4GB drive. What I found was that the operation of the USB drive was screwed up by all the Windows oriented software (such as Skype) that the manufacturer puts on the drive as a bonus. Once I removed all that extra contents the pen drive worked under Linux. -- ======================================================================= "I thought you were trying to get into shape." "I am. The shape I've selected is a triangle." ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
Christopher A. Williams wrote:
On Tue, 2008-10-28 at 00:23 -0500, Robert Nichols wrote:
Christopher A. Williams wrote:
Now, one last question: what's the flag to format a FAT32 partition with mkfs? I saw options for pretty much everything but that. I'm probably just suffering from not having had my first cup of coffee... :)
The manpage for mkfs has some suggestions in the "SEE ALSO" section. You have your choice of:
mkfs -t vfat mkfs.vfat mkdosfs mkfs.msdos
The last 3 are all hard links to the same program. The first is just a wrapper that invokes the mkfs.xxxx appropriate to the requested type.
Christopher A. Williams wrote:
I recently bought a snazzy new 16GB USB pen drive from the local store - it was only $29! I have several drives that are 8GB and smaller from the same store that are the same brand.
Imagine my surprise when:
- The 16GB drive is not accessible on either F9 or F10 Snap 3
- The 8GB drives all work just fine on both F9 and F10 Snap 3
- The 16GB drive works fine on Windows XP
- The 16GB drive also works on a Windows XP VM running on top of F9!!!
I can only conclude from this that something is a miss that causes F9 to not be able to access and use USB pen drives that are bigger than 8GB, and that this most likely has something to do with a file system driver or such.
Anyone else seen this yet? Is there a fix / work-around?
I had issues as well with various drives.
First rule is don't get any drive with U3 software. Remove this as I have had data losses due to it. It also affects the USB bus.
My Corsair had issues and I submitted a bug report with Corsair. There is a timing issue
It may not be the same with yours but could be important to others. Just something that I thought I would share.
http://www.asktheramguy.com/forums/showthread.php?t=73036
Whenever you create multiple partitions or a non fat(32) file system in a partition on the stick the inquiry of the stick timeouts. The default linux timeout is set for 5 secs, and the stick takes 14.5 seconds. So if you set the timeout to 15 seconds or more, and reinsert the stick, the stick should be mountable and readable. Just remember to add this to your boot scripts, or repeat it every time you reboot the kernel.
The inquiry timeout can be set to 15 sec with the following command line: Code:
echo 15 >/sys/module/scsi_mod/parameters/inq_timeout
Or if you prefer the grub command line is : Code:
scsi_mod.inq_timeout=15
I hope this longer timeout will someday be standard for the kernel. Or maybe part of an exception list when a prolific 2528 stick is detected.
Christopher A. Williams wrote:
...
Now, one last question: what's the flag to format a FAT32 partition with mkfs? I saw options for pretty much everything but that. I'm probably just suffering from not having had my first cup of coffee... :)
I deal with this often, as its part of my job to produce bootable pen drives and CF cards. I like using pungi and revisor to roll a product specific distro, and using livecd tools for copying them to the pen drives.
Most of this is scripted for convenience, but all new drives go through a process like this:
Stomp on the MBR:
cat /usr/lib/syslinux/mbr.bin >/dev/${disc}
That particular file is a generic GPL MBR. Its part of the syslinux rpm.
Run fdisk to delete all partitions and recreate just what is necessary -- the script for that is kinda hard to read unless you are intimate with fdisk, so I won't post it here to prevent confusion.
Be sure to tag the primary (assuming 1 here) partition as bootable.
Then to format:
mkfs -t vfat -F 32 -n "$name" /dev/${disc}1
Some vendors like to really mess with their thumb drives, requiring a bad sector check during format. Add a -c to the above for that. It takes a bit longer, but might help on a stubborn drive.
Good luck!
On Fri, 2008-10-31 at 11:52 -0600, Phil Meyer wrote:
Christopher A. Williams wrote:
...
Now, one last question: what's the flag to format a FAT32 partition with mkfs? I saw options for pretty much everything but that. I'm probably just suffering from not having had my first cup of coffee... :)
I deal with this often, as its part of my job to produce bootable pen drives and CF cards. I like using pungi and revisor to roll a product specific distro, and using livecd tools for copying them to the pen drives.
Most of this is scripted for convenience, but all new drives go through a process like this:
Stomp on the MBR:
cat /usr/lib/syslinux/mbr.bin >/dev/${disc}
That particular file is a generic GPL MBR. Its part of the syslinux rpm.
Run fdisk to delete all partitions and recreate just what is necessary -- the script for that is kinda hard to read unless you are intimate with fdisk, so I won't post it here to prevent confusion.
Be sure to tag the primary (assuming 1 here) partition as bootable.
Then to format:
mkfs -t vfat -F 32 -n "$name" /dev/${disc}1
Some vendors like to really mess with their thumb drives, requiring a bad sector check during format. Add a -c to the above for that. It takes a bit longer, but might help on a stubborn drive.
Exactly what I was looking for - thanks a bunch!
Cheers,
Chris
-- ========================================= "In theory there is no difference between theory and practice. In practice there is."
--Yogi Berra
-
Aaron Konstam -
Christopher A Williams -
James Kosin -
Matthew Flaschen -
Phil Meyer -
Robert Nichols -
Robin Laing