Bug 830257 - wrong fstab entry after distribution upgrade
Summary: wrong fstab entry after distribution upgrade
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 17
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: 2012-06-08 16:32 UTC by Pavel Krivanek
Modified: 2013-01-10 06:49 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-06-18 13:23:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda logs (59.50 KB, application/x-gzip)
2012-06-08 17:54 UTC, Pavel Krivanek
no flags Details
screenshot of the boot failure (1.50 MB, image/jpeg)
2012-06-09 07:01 UTC, Pavel Krivanek
no flags Details

Description Pavel Krivanek 2012-06-08 16:32:15 UTC
I did the Fedora distribution upgrade from version 16 to 17 using DVD. I used external USB DVD drive for booting of the upgrade DVD. After the successful upgrade Fedora was not able to boot because Anaconda added this fstab entry:

none                    /vbusbf                 usbfs   rw,devgid=501,devmode=664 0 0

The boot process failed on step "starting /vbusbf" end falled into the rescue mode.

Comment 1 Jesse Keating 2012-06-08 16:51:56 UTC
Please attach the log files from /var/log/anaconda/ on your installed system (assuming you've commented out the fstab entry and booted up).

Comment 2 Pavel Krivanek 2012-06-08 17:54:32 UTC
Created attachment 590479 [details]
anaconda logs

Comment 3 David Lehman 2012-06-08 19:39:04 UTC
How did the mount fail? Does the mountpoint exist? Anaconda does not even write out a new /etc/fstab file when doing an upgrade, so this was in your fstab prior to the upgrade. I'm not sure what you expect us to do to in this case.

Comment 4 Pavel Krivanek 2012-06-09 07:01:54 UTC
Created attachment 590557 [details]
screenshot of the boot failure

Comment 5 Pavel Krivanek 2012-06-09 07:12:41 UTC
The mount point does exist. I did a screenshot of the boot failure. If I try to do "mount -a" in the living system with this uncommented line, I got:
mount: unknown filesystem type 'usbfs'
I looked at the older logs and it seems that you are right, the system mounted vbusbf before the update too but without failure. 

So it seems that it is not a bug in Anaconda. I guess it is related somehow to VirtualBox USB support.


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