Bug 591931 - Cannot mount volume
Summary: Cannot mount volume
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.5
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-13 14:01 UTC by Scott Weigand
Modified: 2010-12-16 16:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-16 16:10:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Scott Weigand 2010-05-13 14:01:54 UTC
Description of problem:

Upon plugging in my SanDisk 4gig jump drive (without U3 installed), a message displays saying "Cannot mount volume. The volume '_PNG' uses the vfat file system which is not supported by your system."

I have used this jump drive many times and never had an issue up to this point.

Version-Release number of selected component (if applicable):

Up-to-date as of 2010 May 13

How reproducible:

Might be able to reproduce.

Steps to Reproduce:
1. Plug the jump drive in
2. Error displays
Actual results:

Pop up displays, device does not mount.

Expected results:

Device should mount and display its root directory.

Additional info:


Comment 1 Jeremy West 2010-12-16 15:26:25 UTC
Hi Scott,

In order to make sure that this issue gets handled appropriate, please contact Red Hat Support.  See this page for more info (www.redhat.com/support)  Red Hat bugzilla is not a support tool, i.e. it's not used by the support team to handle issues such as the one you've reported.  If you have any questions on how to contact support, please let me know.

Jeremy West
Red Hat Support Supervisor

Comment 2 Scott Weigand 2010-12-16 15:32:32 UTC
Thanks for the reply. This was taken care of at some time, can't think of the how/why.

Take care,

Comment 3 Ric Wheeler 2010-12-16 16:10:07 UTC
Thanks - I will close this one then. Please reopen (via RH support) if you see this again.

Note You need to log in before you can comment on or make changes to this bug.