Red Hat Bugzilla – Bug 856958
problems with custom disk partitioning during the F18 installation (ALPHA/RC3)
Last modified: 2012-09-13 13:19:47 EDT
Description of problem:
I have a box with 2 disks. First, I think, the disk parti
I choose the first disk with review toggle button for creating a / and a swap partition on that disk. Then I go back, unselect the first and select the second disk (with review toggle too). Then I create additional entries for /tmp and /home with some size, and select "finish partitioning". Then pressing "back" complains about missing bootable root partition which I created in the first step for the first disk. So I fear:it's not possible to create partitions for /tmp and /home on a second disk in that manner.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The set of disks you last selected is the full set of disks visible to the installer. You cannot control which disk a given partition goes on. This might be added later, but no guarantees.
Joachim, do you have a specific reason / need to have / and swap on disk 1 and /tmp /home on disk 2?
1. I have small disks and few memory so I wanted to test if it's possible to put /tmp and the user data into a partition of a separate disk. Only for testing purposes.
2. As a second step (only for testing purposes too) I plan during the anaconda step of installation to move the swap onto the second disk.
I thought that step 1&2 can be done in one anaconda installation step, but it seems that this is not possible for the moment.
But there is one important aspect: Imagine, you have only 1 disk, and on this disk you have important data (in some partition on this disk) which should not be erased, how can you force the installer to leave this partition untouched but using the rest of the disk for installation? I fear that's not possible too!
"But there is one important aspect: Imagine, you have only 1 disk, and on this disk you have important data (in some partition on this disk) which should not be erased, how can you force the installer to leave this partition untouched but using the rest of the disk for installation? I fear that's not possible too!"
Joachim, the desired behavior you describe of leaving pre-existing partitions untouched is definitely the default behavior.
If you have only one disk that has a partition with data on it and click on it, by default, anaconda will only use space on the disk that is not already allocated. If there is not enough space left on the disk, it will ask you what to do:
We offer to:
- Shrink the pre-existing file system if it's a FS type we can shrink;
- Let you modify your software selection so less software gets installed, requiring less space;
- Add more disks if you have more to add.
If you want to simply wipe the disk, you use the custom partitioning checkbox to open the disk up in the custom partition UI and you can delete the partitions if you like.
The new UI is definitely very, very risk averse to removing any data - much more so than previously.
Does this make more sense now? What do you think?
(In reply to comment #4)
Hi Máirín Duffy,
> We offer to:
> - Shrink the pre-existing file system if it's a FS type we can shrink;
> - Let you modify your software selection so less software gets installed,
> requiring less space;
> - Add more disks if you have more to add.
> If you want to simply wipe the disk, you use the custom partitioning
> checkbox to open the disk up in the custom partition UI and you can delete
> the partitions if you like.
> The new UI is definitely very, very risk averse to removing any data - much
> more so than previously.
> Does this make more sense now? What do you think?
Ooops, that's really very helpful, it makes indeed more sense now.
Thank you very much for your hints.
Joachim, as a caution - the alpha does not currently behave the way I described, and I apologize sincerely. What I described was the intention / design, and is how it will work by the final release. There are some shortcuts in the alpha release that won't be present in the beta.
Thanks for helping us test alpha, we really appreciate it!
Hi Máirín Duffy,
I don't know whether this is the right place, but I saw some more issue:
In the meantime I attached a third disk for additional testing. But now, the window for selecting the disk to manage has a scrollbar, and if I select the well known "customize" dialog for installing the system on this third disk, the disk editor is positioned on the left upper side of the anaconda window, and the menu moving/adding partitions is very difficult to operate because this window
1. is very tiny and
2. the usage of the scrollbars makes it very difficult to add/remove/manage partitions. I guess the size of this (sub)windows is about 100x50.
It should be greater. This is a very urgent request!!!
Thanx and kind regards
Joachim - can you file that as a separate bug and attach a screenshot, if possible? That definitely needs to be looked at - thanks!