Red Hat Bugzilla – Bug 492007
can't mount fstab volumes
Last modified: 2009-04-02 15:10:41 EDT
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.
Created attachment 336568 [details]
my current fstab
If it helps here is my current fstab
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.
Alternatively, try with anaconda-22.214.171.124 and see what you get in the error message now.
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.
Created attachment 336666 [details]
working fstab from fedora 10
Created attachment 336667 [details]
anaconda storage log
Created attachment 336668 [details]
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.
Created attachment 336809 [details]
3/26/09 10am EST anaconda log
Created attachment 336810 [details]
3/26/09 10am EST storage log
Created attachment 336811 [details]
3/26/09 10am EST anaconda dump
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.
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????
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.
Have successfully upgraded. However preupgrade is still broken, so I can't test it the way the problem originally manifested.
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?