Bug 138275
| Summary: | anaconda fails when partition cannot be mounted | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dag Wieers <dag> |
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | CC: | nobody+pnasrat |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-11-08 14:59:16 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: | |||
*** Bug 138276 has been marked as a duplicate of this bug. *** Trying without an fstype only works if you're using the mount command and not mount(2) :-) And unfortunately, we used to let you continue if one failed but that led to problems due to people doing silly things like symlinking /usr/share to another partition. So requiring you to go back to a fully installed system and fix things up is the only real safe answer. Well, it wouldn't be that hard to implement in Python. But as long as I haven't looked into Anaconda myself I'm not expecting anyone else to fix this :) Maybe it would be better if it was a feature request rather than a bug. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041020 Galeon/1.3.18 Description of problem: I noticed that when you're upgrading an existing Fedora Core 2 to Fedora Core 3 and you happen to have an entry in /etc/fstab that does not actually work (eg. an entry for /dev/hdc1 to /mnt/data2 marked as jfs, but really an ext3 or even non-existing), anaconda will uterly fail. It gives a fatal error about some partition not being formatted, in my case it was formatted for ext3 but the fstab wrongly indicated jfs (it was my second laptop HD and the bay at that point containing the ISO's was another disk). I can understand it is confused, but it's fairly easy to try and mount it without the fs-type. In most cases (and even on Fedora Core 2) this will correctly mount it as an ext3 even though fstab says jfs. So if it fails, trying without fs-type would probably fix it for most people. And even when that partition is not formatted, it could ask to continue instead of bailing out. (Only Reboot was possible). PS It was also confusing because tty3 did not specify that it was trying to mount it as jfs, only that it failed. So it took me several trial-and-errors before I found the problem in /etc/fstab. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. ... 2. 3. Additional info: