Bug 870430
| Summary: | Unable to add mount points manually | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Levine <levinedl> | ||||
| Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | g.kaviyarasu, jonathan, tydeman, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-02-05 22:51:04 UTC | Type: | Bug | ||||
| 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
David Levine
2012-10-26 13:11:12 UTC
The alpha is quite old now. Can you try one of the latest Beta test composes? http://dl.fedoraproject.org/pub/alt/stage/18-Beta-TC6/ Created attachment 634035 [details]
anaconda error when attempting to add mount point
The problem is still present in this beta:
Oct 19 22:23 Fedora-18-Beta-TC6-x86_64-Live-XFCE.iso
though the behavior is different than the alpha.
On the MANUAL PARTITIONING screen, I see three groups in the left hand pane:
+ New Fedora 18 Installation
- Fedora Linux 17 for x86_64
DATA
Sda7
Home
SYSTEM
Root
Swap
+ Unknown
Sda7 is ext4 but empty (75 GB), so I want to use it for /. And I want to mount
Home on /home. So I do the following:
1) Click on Sda7, then click on -, then confirm deletion from Fedora Linux 17.
2) Expand "New Fedora 18 Installation"
3) Click +, enter / for the mount point, click Add Mount Point (IIRC)
Then I get "An unknown error has occurred". I tried clicking "Report Bug" but
that causes other problems. I attached the bug report to this one.
My partitions are out of order (partition 3 (of 7) occupies the highest sectors
), that's the only thing I expect is odd in my setup. Other than me trying to manually partition.
I should mention that I'm guessing at how I'm supposed to use the + and - buttons to set up my mount points. I'm comfortable with the way mount points were set up through Fedora 17, is there some different with 18 that I'm missing? If you want to use sda7 as your root device, here's what you do: 1) select it 2) set the mountpoint (near the top on the right side) 3) click the "Customize" expander on right side of screen 4) choose a filesystem type 5) activate the "Reformat" checkbutton 6) click on "Apply Changes" button + means "add a new device/filesystem" - means "remove the selected device" Alright, that allowed me to install TC8. But, I am no longer able to boot my existing Fedora 17 installation (on /dev/sda5): Dependency failed. Aborted start of /mnt/sda7 Dependency failed. Aborted start of Relabel all filesystems, if necessary Dependency failed. Aborted start of Mark the need to relabel after reboot and it gives me the choice of entering the root password for maintenance or Control-D to continue. I tried Control-D but no progress. I have not tried to boot Fedora 18 after the install. Should I, or will that wreck my chance of ever being able to boot Fedora 17 again? Or, what can I do to disable the relabel after reboot attempt? Never mind: I was able to boot my Fedora 17 by removing the /mnt/sda7 mountpoint from its fstab. Apparently the F18 install changed the UUID on that partition. And F18 TC8 boots! I'm not sure if I'm supposed to close this bug. I believe it can be closed now. *** Bug 875404 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is 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 change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |