Bug 492007

Summary: can't mount fstab volumes
Product: [Fedora] Fedora Reporter: Ray Todd Stevens <raytodd>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, ben, dlehman, pjones, rmaximo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-02 18:27:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
my current fstab
none
working fstab from fedora 10
none
anaconda storage log
none
anaconda log
none
3/26/09 10am EST anaconda log
none
3/26/09 10am EST storage log
none
3/26/09 10am EST anaconda dump none

Description Ray Todd Stevens 2009-03-24 22:38:41 UTC
Description of problem:

When I run a preupgrade upgrade to rawhide for testing I have a failure.

This might be related to the fd0 problem already reported, but it doesn't say so, so I am starting a new report.

It goes into the graphic installer and shortly after the fd0 error I get a message that says that it could not mount one of the volumes in /etc/fstab and then it exits.

Comment 1 Ray Todd Stevens 2009-03-24 22:40:23 UTC
Created attachment 336568 [details]
my current fstab

If it helps here is my current fstab

Comment 2 David Lehman 2009-03-24 23:31:26 UTC
If possible, please switch to tty2 (ctl+alt+f2), run 'killall -USR2 anaconda', and then upload /tmp/anacdump.txt as an attachment to this bug.

Comment 3 Chris Lumens 2009-03-25 14:00:48 UTC
Alternatively, try with anaconda-11.5.0.37 and see what you get in the error message now.

Comment 4 Ben Dailey 2009-03-25 16:03:36 UTC
I am seeing a similar if not the same problem. Attached are my my fstab, anaconda.log and storage.log. I hope this is the needed information to help track down this bug. Please let me know what else I can help provide or if there is any other testing I can perform.

Comment 5 Ben Dailey 2009-03-25 16:06:08 UTC
Created attachment 336666 [details]
working fstab from fedora 10

Comment 6 Ben Dailey 2009-03-25 16:06:40 UTC
Created attachment 336667 [details]
anaconda storage log

Comment 7 Ben Dailey 2009-03-25 16:07:10 UTC
Created attachment 336668 [details]
anaconda log

Comment 8 Chris Lumens 2009-03-25 16:49:58 UTC
Ben - if you could try today's rawhide too, I think it'd be helpful.  I worked on the error reporting there just a little bit so maybe we can see what line in your fstab is the problem.  Thanks.

Comment 9 Ben Dailey 2009-03-26 14:20:56 UTC
Created attachment 336809 [details]
3/26/09 10am EST anaconda log

Comment 10 Ben Dailey 2009-03-26 14:21:42 UTC
Created attachment 336810 [details]
3/26/09 10am EST storage log

Comment 11 Ben Dailey 2009-03-26 14:23:29 UTC
Created attachment 336811 [details]
3/26/09 10am EST anaconda dump

Comment 12 Ben Dailey 2009-03-26 14:28:04 UTC
Sorry for the duplication in post the anaconda log and storage log wasn't aware they were included at the bottom of the dump text.

Comment 13 Ray Todd Stevens 2009-03-28 16:24:43 UTC
OK I was going to try testing this some more, but the system that I was running the test on now crashes with bug  492705 before we get to this point.   However interestingly enough it appears it might be crashing with some kind of an error relates to reading fstab????

Comment 14 Ray Todd Stevens 2009-04-01 20:53:52 UTC
Well I did a net install upgrade instead of a preupgrade and that seems so far to have worked.   Don't know if that means this is fixed or not.   Right now preupgrade is seriously broken with no real short term expectation that it will be coming back up.

Comment 15 Ray Todd Stevens 2009-04-02 17:55:38 UTC
Have successfully upgraded.   However preupgrade is still broken, so I can't test it the way the problem originally manifested.

Comment 16 Ray Todd Stevens 2009-04-02 19:10:41 UTC
I do wonder if we will not have to reopen this again once preupgrade is fixed so it actually runs.   Although right now it looks more like eventually it should be closed because it fixed itself.

Has anyone gotten this one without using preupgrade?