Red Hat Bugzilla – Bug 1021909
Removing /boot partition - no warning when using custom "LVM Thin Provisioning"
Last modified: 2014-02-26 16:15:15 EST
Description of problem:
Using Custom partitioning with LVM Thin Provisioning. Asking anaconda to create default layout.
After removing /boot, the change is accepted. Pressing Done after confirming changes, moved to the hub where Installation destination says only: "Error checking storage configuration".
Going back to Storage configuration, select Custom partitioning, no explanation what's wrong there.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. select LVM Thin Provisioning Custom partitioning
2. ask anaconda to create default layout
3. remove /boot (which is acceptable for plain (linear) LV)
Error without further explanation.
Should the spoke have the same orange status as other spokes with errors?
I think what's being reported here is that if you enter "Installation Destination" there is a banner at the bottom you can click on to get error details, but if you click through that without looking around at all the info bar is cleared when the custom storage spoke is entered.
I got no warning at all with anaconda-20.25.1-1 (using kickstart without any storage bits) and installation happily proceeds creating unbootable system (in fact it is dual boot, so I can boot it and fix the issue...)
A normal install with 20.25.1-1 shows an error and prevents the user from starting the installation process because /boot cannot be on a thin lv, so this must be specific to using a partial kickstart.
Install without kickstart indeed displays an error in the hub, in the "Install destination" screen, but not in the "Manual partitioning" screen, which may be "work as intended" but other spokes show the "warning" where there is misconfiguration. It would inform user about the mistake before leaving the spoke and having to go back again.
With a ks there is "No bootloader selected" error in the hub, after going to "Full disk summary and bootloader..." it will disappear and the installation proceeds fine without checking /boot.
 Bug 916529 - Anaconda should install bootloader or ask when no bootloader option is present in kickstart
The kickstart looks like this:
# Use network installation
repo --name="bz1013767" --baseurl=http://192.168.144.1/repos/bz1013767/f20/x86_64/
# Run the Setup Agent on first boot
# Keyboard layouts
keyboard --vckeymap=us --xlayouts='us'
# System language
# Network information
network --bootproto=dhcp --device=ens3 --noipv6 --activate
# System authorization information
auth --enableshadow --passalgo=sha512
# Root password
# System timezone
timezone Europe/Prague --isUtc
Basically I am using the kickstart to specify defaults (repo, keyboard layout, timezone, packages,...) and I do not want it to affect disks (I want to be able to specify disk partitioning using GUI what is not unreasonable IMO)
Please attach /tmp/anaconda.log and /tmp/storage.log. Thanks.
I cant install Fedora 20 on my netbook with Thin LVM
Anaconda will not accept to take the entire disk.
Need a utiilty to wipe the disk clean!
(In reply to Leslie Satenstein from comment #7)
> I cant install Fedora 20 on my netbook with Thin LVM
> Anaconda will not accept to take the entire disk.
> Need a utiilty to wipe the disk clean!
> FEDORA 20
Please open a separate bug report and include detailed information, including the usual log files from /tmp: anaconda.log, storage.log, syslog. Thanks.
Re my #8
Since I could not get F20 to install on the Netbook, I chose Mint16 in its place. I cannot free a system to try to correct the above problem.
I am sure that F21 will have a corrected anaconda that probably will look different than the F20 version and will install properly.
Sorry to not respond sooner,