Bug 714697 - upgrade fc13 -> fc14... automounting of USB drives no longer works
Summary: upgrade fc13 -> fc14... automounting of USB drives no longer works
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-20 13:12 UTC by brad.banko
Modified: 2012-08-16 12:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 12:04:06 UTC
Type: ---


Attachments (Terms of Use)

Description brad.banko 2011-06-20 13:12:06 UTC
Description of problem:
upgrade fc13 -> fc14... automounting of USB drives no longer works

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

How reproducible:
every time

Steps to Reproduce:
1.  login (to user account)
2.  plug in usb drive
3.  can see usb drive on "Computer" list in gnome... it has no "icon".  When I try to access/open it, I get "Not authorized."
  
Actual results:
"Not Authorized."  On attempts to access.

Expected results:
Nautilus file manager window opens and displays the files.

Additional info:

Comment 1 Fedora Admin XMLRPC Client 2011-09-12 13:40:31 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 brad.banko 2011-09-12 14:07:03 UTC
I had the same problem carry through to fedora 15 when I tried upgrading to fix it.

I finally had a look at the fstab file, and found that sometime along the way, the usb drive had been assigned a mounting status which I commented out and fixed the problem:

Here is the /etc/fstab file:

#
# /etc/fstab
# Created by anaconda on Tue Jun 21 01:21:02 2011
#
# Accessible filesystems, by reference, are maintained under '/dev/
disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more
info
#
/dev/mapper/VolGroup-lv_root /                       ext4
defaults        1 1
UUID=36757e9e-f25b-422f-b056-a0e3f74a183f /boot
ext4    defaults        1 2
# UUID=4EEA-A404          /boot/efi               vfat
umask=0077,shortname=winnt 0 0
/dev/mapper/VolGroup-lv_home /home                   ext4
defaults        1 2
/dev/mapper/VolGroup-lv_swap swap                    swap
defaults        0 0
tmpfs                   /dev/shm                tmpfs
defaults        0 0
devpts                  /dev/pts                devpts
gid=5,mode=620  0 0
sysfs                   /sys                    sysfs
defaults        0 0
proc                    /proc                   proc
defaults        0 0

The commented line "UUID=4EEA-A404" is the culprit.  I will have to
learn more about fstab and this UUID stuff. 

I figured this out thanks to the drive "configurations" tool in fedora 15... I noticed that the drive in question kept mounting at /boot/efi for reasons that I didn't understand until I saw the /etc/fstab line.

Comment 3 Lukáš Nykrýn 2011-09-15 12:06:47 UTC
How did you make upgrade from fc13 to fc14? Was it through yum or through anaconda (install cd).

Comment 4 Lukáš Nykrýn 2011-10-18 08:13:11 UTC
Because Brad did not provide some more information, my only suspect for this situation is upgrade trough anaconda using live usb drive.

Comment 5 brad.banko 2011-10-18 13:06:12 UTC
Lukas,

Sorry that I have not responded before.  I had upgraded first through yum (the native upgrade through the OS) from fc13->fc14, and I think that for fc14 to fc15, I downloaded an install DVD.  

I think that maybe this was caused by some problem with the initial upgrade path on the fstab file... having the USB drive attached during the upgrade process?  

But commenting out the involved line in the fstab file fixed the problem completely.

Brad Banko

Comment 6 Chris Lumens 2011-10-18 13:46:56 UTC
anaconda only writes out a new fstab on upgrades in one specific circumstance - if you migrate your filesystem from ext2 to ext3, or from ext3 to ext4.  Did you do that?

Comment 7 brad.banko 2011-10-18 14:17:20 UTC
I think that I did migrate to ext4 along the way.  Yes.

Comment 8 Fedora End Of Life 2012-08-16 12:04:09 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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