The good news first: F-18 Beta DVD ISO image can be booted from harddisk again, so it seems I will be able to test that installation method this time without having to research strange/new/complex entries for GRUB and loading squashfs images from remote locations.
However, I'm stuck because of the new installer GUI not letting me finish the manual partitioning. =:-/
First of all, it has become a maze to navigate, although that is not the final problem. For keyboard, timezone, language and basics I've used the "Done" button. So far so good. Many mouse-clicks and much mouse-pointer movement, but at least it accepted my changes.
The installer complains about the "installation source" (ISO) without telling me what's wrong. There's a "Verify" button, which doesn't seem to do anything.
Partition is what can drive the user mad.
It defaults to automatic partitioning, complaining about not enough free space. I've searched for a way to tell it that I want to reuse an existing logical partition. One that has a Rawhide->F18-Alpha on it. Somehow I needed to click "Continue" to reach an error dialog that again tells me there is not enough free space and that the installer will help me, so I tell it I don't need help, I want to partition myself, but I cannot escape that dialog other than with the "Reclaim space" button. Could be dangerous, but I take the risk and click it after changing the partitioning which defaults to "LVM", which should be irrelevant when I partition myself.
I reach the partitioning screen, where assigning mount points is everything other than intuitive compared with old Anaconda. Partition names are not displayed anywere, just labels, mount points and names of existing installations. It needs many mouse-clicks to open existing installations (this is a multi-boot desktop) and reuse mount-points via the "Apply changes" button. Again, so far so good, at least I can make the installer use the LUKS encrypted /home and a few /mnt/… targets. I also tell it to reformat (!) the Root ext4 partition, but:
It continues to display a yellow warning about not enough free space for automatic partitioning. Help! I can revisit the partitioning screen endlessly without any way to teach it that reformatting means the space will be available for installation. And why does it still refer to automatic partitioning, if I tell it that I partition myself? What am I missing? The begin installation button is greyed out.
Aaargh!
The good news first: F-18 Beta DVD ISO image can be booted from harddisk again, so it seems I will be able to test that installation method this time without having to research strange/new/complex entries for GRUB and loading squashfs images from remote locations.
I may have been too optimistic. :-( The following issue I've revisited:
The installer complains about the "installation source" (ISO) without telling me what's wrong. There's a "Verify" button, which doesn't seem to do anything.
There's a tiny empty area/button left of the Verify button. It's another button with no text assigned. One can click it to open a file dialog, point it at the DVD ISO image, the button then displays the path, one can even Verify the ISO image, but the installer crashes. And it's been reported before: https://bugzilla.redhat.com/879612
I guess it will not be possible to install from DVD ISO image on harddisk due to this issue in addition to the other problem I've described.
On Fri, 2012-11-30 at 14:52 +0100, Michael Schwendt wrote:
The good news first: F-18 Beta DVD ISO image can be booted from harddisk again, so it seems I will be able to test that installation method this time without having to research strange/new/complex entries for GRUB and loading squashfs images from remote locations.
I may have been too optimistic. :-( The following issue I've revisited:
The installer complains about the "installation source" (ISO) without telling me what's wrong. There's a "Verify" button, which doesn't seem to do anything.
There's a tiny empty area/button left of the Verify button. It's another button with no text assigned. One can click it to open a file dialog, point it at the DVD ISO image, the button then displays the path, one can even Verify the ISO image, but the installer crashes. And it's been reported before: https://bugzilla.redhat.com/879612
I guess it will not be possible to install from DVD ISO image on harddisk due to this issue in addition to the other problem I've described.
See 879142. It is possible if you simply ignore the 'error'. Don't go into the spoke and try and change anything, just leave it alone. It'll work.
Hi Michael, I have had problems with installing the Fedora 18 Beta DVD, not enough disk space. My first solution was an upgrade from Fedora 17, successful, but there was a problem, I need LXDE (old grafic card), which I didn't get this way. Next solution was, run Fedora 17 Live CD and format, partition. Now the Fedora 18 Beta DVD is installing. Warm regards Joeg
-----Ursprüngliche Mitteilung----- Von: Michael Schwendt mschwendt@gmail.com An: test test@lists.fedoraproject.org Verschickt: Fr, 30 Nov 2012 2:19 pm Betreff: F18-Beta installer - Aaaargh!
The good news first: F-18 Beta DVD ISO image can be booted from harddisk again, so it seems I will be able to test that installation method this time without having to research strange/new/complex entries for GRUB and loading squashfs images from remote locations.
However, I'm stuck because of the new installer GUI not letting me finish the manual partitioning. =:-/
First of all, it has become a maze to navigate, although that is not the final problem. For keyboard, timezone, language and basics I've used the "Done" button. So far so good. Many mouse-clicks and much mouse-pointer movement, but at least it accepted my changes.
The installer complains about the "installation source" (ISO) without telling me what's wrong. There's a "Verify" button, which doesn't seem to do anything.
Partition is what can drive the user mad.
It defaults to automatic partitioning, complaining about not enough free space. I've searched for a way to tell it that I want to reuse an existing logical partition. One that has a Rawhide->F18-Alpha on it. Somehow I needed to click "Continue" to reach an error dialog that again tells me there is not enough free space and that the installer will help me, so I tell it I don't need help, I want to partition myself, but I cannot escape that dialog other than with the "Reclaim space" button. Could be dangerous, but I take the risk and click it after changing the partitioning which defaults to "LVM", which should be irrelevant when I partition myself.
I reach the partitioning screen, where assigning mount points is everything other than intuitive compared with old Anaconda. Partition names are not displayed anywere, just labels, mount points and names of existing installations. It needs many mouse-clicks to open existing installations (this is a multi-boot desktop) and reuse mount-points via the "Apply changes" button. Again, so far so good, at least I can make the installer use the LUKS encrypted /home and a few /mnt/… targets. I also tell it to reformat (!) the Root ext4 partition, but:
It continues to display a yellow warning about not enough free space for automatic partitioning. Help! I can revisit the partitioning screen endlessly without any way to teach it that reformatting means the space will be available for installation. And why does it still refer to automatic partitioning, if I tell it that I partition myself? What am I missing? The begin installation button is greyed out.
Aaargh!
On Fri, 2012-11-30 at 14:19 +0100, Michael Schwendt wrote:
It defaults to automatic partitioning, complaining about not enough free space. I've searched for a way to tell it that I want to reuse an existing logical partition. One that has a Rawhide->F18-Alpha on it. Somehow I
The way to tell it this is to activate the "I want to use custom partitioning instead" checkbutton and thus enter custom partitioning by clicking the "Reclaim" button. Never has there been a feature of automatic partitioning that said "do automatic partitioning but reuse this ___ device."
needed to click "Continue" to reach an error dialog that again tells me there is not enough free space and that the installer will help me, so I tell it I don't need help, I want to partition myself, but I cannot escape that dialog other than with the "Reclaim space" button. Could be dangerous, but I take the risk and click it after changing the partitioning which defaults to "LVM", which should be irrelevant when I partition myself.
It is not irrelevant if you plan to create any new devices in custom. That same device/scheme chooser sets the default type for new devices you create as well as the default automatic partitioning scheme.
I reach the partitioning screen, where assigning mount points is everything other than intuitive compared with old Anaconda. Partition names are not displayed anywere, just labels, mount points and names of existing installations. It needs many mouse-clicks to open existing installations (this is a multi-boot desktop) and reuse mount-points via the "Apply changes" button. Again, so far so good, at least I can make the installer use the LUKS encrypted /home and a few /mnt/… targets. I also tell it to reformat (!) the Root ext4 partition, but:
You didn't mention what you did in between setting up your custom layout and being on any screen where you might see an error about automatic partitioning.
It continues to display a yellow warning about not enough free space for automatic partitioning. Help! I can revisit the partitioning screen endlessly without any way to teach it that reformatting means the space will be available for installation. And why does it still refer to automatic partitioning, if I tell it that I partition myself? What am I missing? The begin installation button is greyed out.
How are you leaving the custom partitioning screen? If you click on "Back to destination selection" your changes will not be saved because that indicates that you have changed your mind as opposed to being done. If you click on "Finish Partitioning" your changes will be saved.
-- Fedora release 17 (Beefy Miracle) - Linux 3.6.8-2.fc17.x86_64 loadavg: 1.84 0.69 0.25
On Fri, Nov 30, 2012 at 11:30:53AM -0600, David Lehman wrote:
The way to tell it this is to activate the "I want to use custom partitioning instead" checkbutton and thus enter custom partitioning by clicking the "Reclaim" button. Never has there been a feature of automatic partitioning that said "do automatic partitioning but reuse this ___ device."
No, but there's been "do automatic partitioning reusing only existing Linux partitions.
On Fri, 2012-11-30 at 12:54 -0500, Matthew Miller wrote:
On Fri, Nov 30, 2012 at 11:30:53AM -0600, David Lehman wrote:
The way to tell it this is to activate the "I want to use custom partitioning instead" checkbutton and thus enter custom partitioning by clicking the "Reclaim" button. Never has there been a feature of automatic partitioning that said "do automatic partitioning but reuse this ___ device."
No, but there's been "do automatic partitioning reusing only existing Linux partitions.
Which didn't really do what you might have thought it did: it didn't re-use the partitions, it wiped them and created new ones. oldUI had UI gotchas too. :)
On Fri, 30 Nov 2012 11:30:53 -0600, David Lehman wrote:
It defaults to automatic partitioning, complaining about not enough free space. I've searched for a way to tell it that I want to reuse an existing logical partition. One that has a Rawhide->F18-Alpha on it. Somehow I
The way to tell it this is to activate the "I want to use custom partitioning instead" checkbutton and thus enter custom partitioning by clicking the "Reclaim" button.
Which is what I've done. It's confusing nevertheless, since the dialog refers to shrinking partitions/volumes, whereas the user does not want to do that, but simply wants to reuse existing partitions/volumes. Clicking a button "Reclaim space" sounds weird in that context.
Why can't the checkbox not be turnt into a "Manual partitioning" button that one would click instead of the Reclaim button? Afterall, the section is titled "Manual partitioning", too.
Never has there been a feature of automatic partitioning that said "do automatic partitioning but reuse this ___ device."
No, but in my case it still refers to automatic partitioning _after_ I've completed the manual partitioning.
needed to click "Continue" to reach an error dialog that again tells me there is not enough free space and that the installer will help me, so I tell it I don't need help, I want to partition myself, but I cannot escape that dialog other than with the "Reclaim space" button. Could be dangerous, but I take the risk and click it after changing the partitioning which defaults to "LVM", which should be irrelevant when I partition myself.
It is not irrelevant if you plan to create any new devices in custom. That same device/scheme chooser sets the default type for new devices you create as well as the default automatic partitioning scheme.
I reach the partitioning screen, where assigning mount points is everything other than intuitive compared with old Anaconda. Partition names are not displayed anywere, just labels, mount points and names of existing installations. It needs many mouse-clicks to open existing installations (this is a multi-boot desktop) and reuse mount-points via the "Apply changes" button. Again, so far so good, at least I can make the installer use the LUKS encrypted /home and a few /mnt/… targets. I also tell it to reformat (!) the Root ext4 partition, but:
You didn't mention what you did in between setting up your custom layout and being on any screen where you might see an error about automatic partitioning.
It's 100% reproducible here, and just a few minutes ago I might have found out that order does matter. I will try to verify that once more. My steps are below:
It continues to display a yellow warning about not enough free space for automatic partitioning. Help! I can revisit the partitioning screen endlessly without any way to teach it that reformatting means the space will be available for installation. And why does it still refer to automatic partitioning, if I tell it that I partition myself? What am I missing? The begin installation button is greyed out.
How are you leaving the custom partitioning screen? If you click on "Back to destination selection" your changes will not be saved because that indicates that you have changed your mind as opposed to being done. If you click on "Finish Partitioning" your changes will be saved.
Of course I clicked "Finish Partitioning", as returning to selecting the destination would be stupid. Anyway,
1. open the Unknown partitions/volumes (don't remember the terminology right now), enter secondary password for my LUKS /home, wait for that one to become available 2. open the _old_ Fedora 18-Alpha x86_64 blahblah entry from which to reuse existing mount points 3. fill in the mount points, "Apply Changes" for each of /home, /home/sharedhome, /mnt/storage, /mnt/distimages, then /root last and check the Reformat checkbox 4. With "Finish Partitioning", I return to the main screen and see both a yellow warning at the bottom as well as a yellow exclamation mark behind the Storage field referring to the not enough space problem. Revisiting the manual partitioning does not help either.
These steps I've tried multiple times to confirm them. Roughly in an hour or so I'll revisit a different order in which to add the mount points, as I think leaving out the LUKS /home may be enough for a non-reproducer. There will be a report in bugzilla once/if I figure that out.
On Fri, 2012-11-30 at 19:39 +0100, Michael Schwendt wrote:
On Fri, 30 Nov 2012 11:30:53 -0600, David Lehman wrote:
It defaults to automatic partitioning, complaining about not enough free space. I've searched for a way to tell it that I want to reuse an existing logical partition. One that has a Rawhide->F18-Alpha on it. Somehow I
The way to tell it this is to activate the "I want to use custom partitioning instead" checkbutton and thus enter custom partitioning by clicking the "Reclaim" button.
Which is what I've done. It's confusing nevertheless, since the dialog refers to shrinking partitions/volumes, whereas the user does not want to do that, but simply wants to reuse existing partitions/volumes. Clicking a button "Reclaim space" sounds weird in that context.
Why can't the checkbox not be turnt into a "Manual partitioning" button that one would click instead of the Reclaim button? Afterall, the section is titled "Manual partitioning", too.
Never has there been a feature of automatic partitioning that said "do automatic partitioning but reuse this ___ device."
No, but in my case it still refers to automatic partitioning _after_ I've completed the manual partitioning.
needed to click "Continue" to reach an error dialog that again tells me there is not enough free space and that the installer will help me, so I tell it I don't need help, I want to partition myself, but I cannot escape that dialog other than with the "Reclaim space" button. Could be dangerous, but I take the risk and click it after changing the partitioning which defaults to "LVM", which should be irrelevant when I partition myself.
It is not irrelevant if you plan to create any new devices in custom. That same device/scheme chooser sets the default type for new devices you create as well as the default automatic partitioning scheme.
I reach the partitioning screen, where assigning mount points is everything other than intuitive compared with old Anaconda. Partition names are not displayed anywere, just labels, mount points and names of existing installations. It needs many mouse-clicks to open existing installations (this is a multi-boot desktop) and reuse mount-points via the "Apply changes" button. Again, so far so good, at least I can make the installer use the LUKS encrypted /home and a few /mnt/… targets. I also tell it to reformat (!) the Root ext4 partition, but:
You didn't mention what you did in between setting up your custom layout and being on any screen where you might see an error about automatic partitioning.
It's 100% reproducible here, and just a few minutes ago I might have found out that order does matter. I will try to verify that once more. My steps are below:
It continues to display a yellow warning about not enough free space for automatic partitioning. Help! I can revisit the partitioning screen endlessly without any way to teach it that reformatting means the space will be available for installation. And why does it still refer to automatic partitioning, if I tell it that I partition myself? What am I missing? The begin installation button is greyed out.
How are you leaving the custom partitioning screen? If you click on "Back to destination selection" your changes will not be saved because that indicates that you have changed your mind as opposed to being done. If you click on "Finish Partitioning" your changes will be saved.
Of course I clicked "Finish Partitioning", as returning to selecting the destination would be stupid. Anyway,
- open the Unknown partitions/volumes (don't remember the terminology right
now), enter secondary password for my LUKS /home, wait for that one to become available 2. open the _old_ Fedora 18-Alpha x86_64 blahblah entry from which to reuse existing mount points 3. fill in the mount points, "Apply Changes" for each of /home, /home/sharedhome, /mnt/storage, /mnt/distimages, then /root last and check the Reformat checkbox 4. With "Finish Partitioning", I return to the main screen and see both a yellow warning at the bottom as well as a yellow exclamation mark behind the Storage field referring to the not enough space problem. Revisiting the manual partitioning does not help either.
These steps I've tried multiple times to confirm them. Roughly in an hour or so I'll revisit a different order in which to add the mount points, as I think leaving out the LUKS /home may be enough for a non-reproducer. There will be a report in bugzilla once/if I figure that out.
Maybe you should report a bug. If you do, include a detailed procedure and the following log files as attachments of MIME type text/plain:
/tmp/anaconda.log /tmp/storage.log /tmp/program.log /tmp/syslog
Thanks.
On Fri, 30 Nov 2012 12:59:45 -0600, David Lehman wrote:
Maybe you should report a bug. If you do, include a detailed procedure and the following log files as attachments of MIME type text/plain:
/tmp/anaconda.log /tmp/storage.log /tmp/program.log /tmp/syslog
Bug 882351 blocks me from doing so. I haven't changed anything here, but currently, whenever I try to unlock my /home volume, the installer crashes with the same error as in bug 882351. It has mounted the ISO image, but I have no idea why I've been able to unlock /home a couple of times before opening this thread. It's almost as if it has saved state somewhere or is racy with a very high probability of crashing like this and a very low chance of manage to avoid the crash.
Sorry. Due to this I'm unable to report what I think I've found out roughly an hour ago. The LUKS /home is relevant here. I guess I'll be able to install without adding it. That'll be the only thing I'll try next, either from ISO image or USB stick, hoping that either one will succeed.
:-/
On Nov 30, 2012, at 1:14 PM, Michael Schwendt mschwendt@gmail.com wrote:
On Fri, 30 Nov 2012 12:59:45 -0600, David Lehman wrote:
Maybe you should report a bug. If you do, include a detailed procedure and the following log files as attachments of MIME type text/plain:
/tmp/anaconda.log /tmp/storage.log /tmp/program.log /tmp/syslog
Bug 882351 blocks me from doing so.
Doesn't seem like that bug blocks you from getting to a shell.
control-alt-f2 to get to a shell cd /tmp tar -zcf logs.tgz *.log scp logs.tgz ipaddress:/path/to/save/
Chris Murphy
On Fri, 30 Nov 2012 13:23:58 -0700, Chris Murphy wrote:
On Fri, 30 Nov 2012 12:59:45 -0600, David Lehman wrote:
Maybe you should report a bug. If you do, include a detailed procedure and the following log files as attachments of MIME type text/plain:
/tmp/anaconda.log /tmp/storage.log /tmp/program.log /tmp/syslog
Bug 882351 blocks me from doing so.
Doesn't seem like that bug blocks you from getting to a shell.
You misunderstand. I cannot perform the original steps anymore on how to reproduce the problem, since unlocking the LUKS volume and adding it as mount point has been essential in reaching the state where the installer doesn't let me continue. Now it crashes always and too early.
Not unlocking the LUKS volume, I get a bit further, do NOT get the "no space warning", can click the "Begin Installation" button, but see another crash as reported by others before in #879610.
Mixed results.
Booting from USB stick crashed the installer at the first mouse-click on its main screen with another traceback due to umount /mnt/sysimage being busy or something. A typical "WTF?" situation. Didn't bother reporting that from within the installer, because rebooting the USB stick and acting more slowly with the first mouse-clicks apparently was enough to not make it not crash. I made sure I didn't click anywhere before it was done with the few checks it performed, removing some of the early exclamation marks. I also avoided the LUKS /home like the plague and was able to install this thing from USB stick. Though, after this experience, I think the installer might be suffering from race-conditions for some of the crashes to occur.
On Fri, 2012-11-30 at 23:32 +0100, Michael Schwendt wrote:
Mixed results.
Booting from USB stick crashed the installer at the first mouse-click on its main screen with another traceback due to umount /mnt/sysimage being busy or something. A typical "WTF?" situation. Didn't bother reporting that from within the installer, because rebooting the USB stick and acting more slowly with the first mouse-clicks apparently was enough to not make it not crash.
Please do report all of these. We want to catch all the races. Can you reliably reproduce it by acting quickly?
I made sure I didn't click anywhere before it was done with the few checks it performed, removing some of the early exclamation marks. I also avoided the LUKS /home like the plague and was able to install this thing from USB stick. Though, after this experience, I think the installer might be suffering from race-conditions for some of the crashes to occur.
On Fri, 30 Nov 2012 17:15:47 -0800, Adam Williamson wrote:
On Fri, 2012-11-30 at 23:32 +0100, Michael Schwendt wrote:
Mixed results.
Booting from USB stick crashed the installer at the first mouse-click on its main screen with another traceback due to umount /mnt/sysimage being busy or something. A typical "WTF?" situation. Didn't bother reporting that from within the installer, because rebooting the USB stick and acting more slowly with the first mouse-clicks apparently was enough to not make it not crash.
Please do report all of these. We want to catch all the races. Can you reliably reproduce it by acting quickly?
No. It seems the large button areas on the first screen are greyed out until the initial checks have been performed. Which makes reproduciblity less easy, because the very first screen is the language selection one must leave with a first mouse-click, and perhaps mouse-clicks don't matter at all. ;-) I just described what I did when I tried to install from USB after the unsuccessful attemps from hard-disk. Maybe it crashes independent of the user activity, but dependent only on how it performs the early checks?
I don't feel like testing this too often. The developers won't spend time on it either if they cannot reproduce it easily.
The installer seems to be multi-threaded, and if it's racy indeed, eventually someone will run into the same crash. Apparently, that has not happened during pre-release testing of the Beta.
On Fri, 2012-11-30 at 14:19 +0100, Michael Schwendt wrote:
The good news first: F-18 Beta DVD ISO image can be booted from harddisk again, so it seems I will be able to test that installation method this time without having to research strange/new/complex entries for GRUB and loading squashfs images from remote locations.
However, I'm stuck because of the new installer GUI not letting me finish the manual partitioning. =:-/
First of all, it has become a maze to navigate, although that is not the final problem. For keyboard, timezone, language and basics I've used the "Done" button. So far so good. Many mouse-clicks and much mouse-pointer movement, but at least it accepted my changes.
The installer complains about the "installation source" (ISO) without telling me what's wrong. There's a "Verify" button, which doesn't seem to do anything.
This is https://bugzilla.redhat.com/show_bug.cgi?id=879142 . It appears to be basically cosmetic, you can ignore the error.
Partition is what can drive the user mad.
It defaults to automatic partitioning, complaining about not enough free space. I've searched for a way to tell it that I want to reuse an existing logical partition. One that has a Rawhide->F18-Alpha on it. Somehow I needed to click "Continue" to reach an error dialog that again tells me there is not enough free space and that the installer will help me, so I tell it I don't need help, I want to partition myself, but I cannot escape that dialog other than with the "Reclaim space" button. Could be dangerous, but I take the risk and click it after changing the partitioning which defaults to "LVM", which should be irrelevant when I partition myself.
You did everything right, but it sounds like you weren't given enough confidence in the process. But yes, what you described is exactly the route into custom partitioning. If you don't check 'I don't need help', you get the 'guided partitioning' flow where you get a dialog that lets you delete or shrink existing partitions to free up space for an autopart install.
It's not quite that it 'defaults' to automatic partitioning, it's that the checkbox you hit is the 'automatic / custom' delimiter. It sounds like that wasn't made clear enough for you.
I reach the partitioning screen, where assigning mount points is everything other than intuitive compared with old Anaconda. Partition names are not displayed anywere, just labels, mount points and names of existing installations. It needs many mouse-clicks to open existing installations (this is a multi-boot desktop) and reuse mount-points via the "Apply changes" button.
So, the basic design of newUI is to visualize not 'disks with partitions on them' but 'a computer with operating systems on it'. This is a change, and it does seem somewhat messy in complex cases, especially with multiply-mounted partitions. However, Mo and the anaconda devs feel that for some setups and some users, the 'computer with operating systems' approach on it is going to be clearer and more usable.
AIUI there've been various concepts kicked around for trying to address this, but they all feel messy so far.
Again, so far so good, at least I can make the installer use the LUKS encrypted /home and a few /mnt/… targets. I also tell it to reformat (!) the Root ext4 partition, but:
Why the (!)?
It continues to display a yellow warning about not enough free space for automatic partitioning. Help! I can revisit the partitioning screen endlessly without any way to teach it that reformatting means the space will be available for installation. And why does it still refer to automatic partitioning, if I tell it that I partition myself? What am I missing? The begin installation button is greyed out.
As David says, this is a bit unclear, as the custom part screen itself shouldn't ever say anything about free space for automatic partitioning. I agree with David that it sounds like, somehow, you left the custom part screen in a way in which the changes made on it weren't applied.
On Fri, 30 Nov 2012 10:49:50 -0800, Adam Williamson wrote:
It's not quite that it 'defaults' to automatic partitioning,
That is what it tells at the very beginning in the "Storage" section.
it's that the checkbox you hit is the 'automatic / custom' delimiter. It sounds like that wasn't made clear enough for you.
Of course. It seems "Reclaim space" does not just refer to shrinking something but also to reusing existing partitions by simply reformatting them.
Again, so far so good, at least I can make the installer use the LUKS encrypted /home and a few /mnt/… targets. I also tell it to reformat (!) the Root ext4 partition, but:
Why the (!)?
To emphasize that I told it to reformat (= reclaim?) that space, but afterwards it still complains about not enough space.
It continues to display a yellow warning about not enough free space for automatic partitioning. Help! I can revisit the partitioning screen endlessly without any way to teach it that reformatting means the space will be available for installation. And why does it still refer to automatic partitioning, if I tell it that I partition myself? What am I missing? The begin installation button is greyed out.
As David says, this is a bit unclear, as the custom part screen itself shouldn't ever say anything about free space for automatic partitioning. I agree with David that it sounds like, somehow, you left the custom part screen in a way in which the changes made on it weren't applied.
No, clearly not.
Unfortunately, the more I play with this new installer, the more breakage I encounter. Currently, I'm stuck even earlier and cannot "Unlock" my encrypted LV anymore. As soon as I try, no matter whether before or after Root, I get this crash: https://bugzilla.redhat.com/882351
That also means that I cannot revisit the original problem. As you say, I can ignore the ISO path, since filling it in crashes the installer, too, but now the installer crashes always when trying to access the /home I want to add, and I've unlocked it a few times before opening this thread. ;-)
On Fri, 2012-11-30 at 20:50 +0100, Michael Schwendt wrote:
On Fri, 30 Nov 2012 10:49:50 -0800, Adam Williamson wrote:
It's not quite that it 'defaults' to automatic partitioning,
That is what it tells at the very beginning in the "Storage" section.
it's that the checkbox you hit is the 'automatic / custom' delimiter. It sounds like that wasn't made clear enough for you.
Of course. It seems "Reclaim space" does not just refer to shrinking something but also to reusing existing partitions by simply reformatting them.
Yes, basically, it means 'reclaim space via custom partitioning', which by implication means you can do anything you like at all to reclaim the space, since it's...custom partitioning. I can see why this wasn't terribly clear to you, though. So just to make it clear, there are two versions of the screen with the checkbox on it, one that shows when you don't have enough space, and one that shows when you do.
So if you have enough free space for install, you have two options for getting off the screen: check the box and hit the 'go ahead' button, which puts you in custom partitioning. Or don't check the box and hit the 'go ahead' button, in which case partitioning is done, you get autopart in whatever free space you had available.
If you don't have enough free space for install, you again have two options: check the box and hit the 'go ahead' button, which again, puts you in custom partitioning - there is zero practical difference between the cases here, because custom part doesn't decide anything for you, you get to do everything. Or don't check the box and hit the 'go ahead' button, in which case you get the 'guided' dialog for freeing up space, which lets you delete or shrink existing partitions and doesn't let you escape until your proposed changes free up enough space for install.
That's the overall design of the bit of UI you're encountering. It sounds like the flow isn't made clear enough in the design, though, and I'm sure the devs and designers will take a look at that.
As David says, this is a bit unclear, as the custom part screen itself shouldn't ever say anything about free space for automatic partitioning. I agree with David that it sounds like, somehow, you left the custom part screen in a way in which the changes made on it weren't applied.
No, clearly not.
Unfortunately, the more I play with this new installer, the more breakage I encounter. Currently, I'm stuck even earlier and cannot "Unlock" my encrypted LV anymore. As soon as I try, no matter whether before or after Root, I get this crash: https://bugzilla.redhat.com/882351
That also means that I cannot revisit the original problem. As you say, I can ignore the ISO path, since filling it in crashes the installer, too, but now the installer crashes always when trying to access the /home I want to add, and I've unlocked it a few times before opening this thread. ;-)
Well I guess we need to fix that bug first :)
-
Adam Williamson -
Chris Murphy -
David Lehman -
Joerg Lechner -
Matthew Miller -
Michael Schwendt