Bug 23696 - Mount of vfat partition doesn't work after upgrade
Mount of vfat partition doesn't work after upgrade
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.0
i386 Linux
low Severity low
: ---
: ---
Assigned To: Brock Organ
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-01-10 02:32 EST by Lucien Roesch
Modified: 2005-10-31 17:00 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-20 16:15:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lucien Roesch 2001-01-10 02:32:13 EST
My server had to OS, NT 4 and RH 6.1 and worked fine for over a year. It has one vfat partition which is accessible from both OS.
After the upgrade from RH 6.1 to 7.0 I get the message
/dev/hda6 has wrong major or minor number when I issue the command
mount -t vfat /dev/hda6 /nt
Comment 1 Bernhard Rosenkraenzer 2001-01-12 09:16:33 EST
I can't reproduce this - I have no problems whatsoever mounting a fat filesystem
(generated by DOS, though, no Microsoft products in here).

Does mount -t msdos work?

Is the partition there if you look at fdisk -l /dev/hda?
Comment 2 Lucien Roesch 2001-01-12 09:58:11 EST
After complete reinstallation of RH 7.0, the problem disappeared, but there must be something wrong with the upgrade script. One of my friend at the 
research center experienced exactly the same on a dual boot server.
Comment 3 Bernhard Rosenkraenzer 2001-01-12 10:01:39 EST
Assigning to anaconda
Comment 4 Michael Fulbright 2001-01-12 10:29:23 EST
Requesting QA try to reproduce this issue.
Comment 5 Brock Organ 2001-02-20 16:14:55 EST
unfortunately, we haven't seen this problem in our tests here (using generic
test lab hardware) upgrading from a minimal 6.2 -> 7.0 ... if you find any
additional details that help us reproduce what you saw, please reopen the issue
... :)

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