Red Hat Bugzilla – Bug 984059
kickstart to multipath disk with existing LVM fails as does not accept any name for disk drive
Last modified: 2016-07-06 11:18:05 EDT
Description of problem:
Attemtping to kickstart an HP DL350 G5 but cannot find any value that works for the --drives argument to clearpart or bootloader options.
Version-Release number of selected component (if applicable):
Fedora 19 x86_64
1. Manually install F19 via DVD so end up with LVM partitions.
2. Then attempt to kickstart (boot from DVD, add "text ks=...") using any of the following values for the --drives argument to clearpart or bootloader:
kickstart config for disks was:
# Partition clearing information
clearpart --all --initlabel --drives=disk/by_id/cciss-3600508b1001038323120202020200000
bootloader --location=mbr --drives=disk/by_id/cciss-3600508b1001038323120202020200000
Either error message about disk not existing or get dropped into
installer question about destination disk.
Same effect with graphical installer, just faster to test with text mode.
Output of 'multipath -ll' after installer stops:
mpatha (3600508b1001038323120202020200000) dm-0 HP ,LOGICAL VOLUME
size=137G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
`- 0:0:0:0 cciss/c0d0 104:0 active ready running
Note the it is by-id/ -- not by_id/
Please try again, using either mpatha or by-id/.... and attach /tmp/storage.log to this bug report so I can try to figure out what the problem is. Thanks.
Created attachment 773024 [details]
Using mpatha drops into installer saying no destination disk selected.
Created attachment 773033 [details]
Using by-id/.... also drops back into the installer saying no destination disk selected.
ks config was:
learpart --all --initlabel --drives=disk/by-id/cciss-3600508b1001038323120202020200000
#clearpart --all --initlabel --drives=mpatha
bootloader --location=mbr --drive=disk/by-id/cciss-3600508b1001038323120202020200000
I have a patch ready for testing. To test it, add the following argument to your boot command line when booting the installer:
Let me know how it goes. Thanks.
Created attachment 775745 [details]
fix1 by-id storage.log
With inst.updates=... added (used local copy of updates-984059.0.img as firewall issues here) and kickstart file using by-id (as per comment 3) the installer stopped with error message:
Started automated install.....
Generating updated storage configuration
storage configuration failed: Not enough free space on disks for automatic partitioning
Created attachment 775746 [details]
fix1 mpatha storage.log
With inst.updates and kickstart config of:
clearpart --all --initlabel --drives=mpatha
bootloader --location=mbr --drive=mpatha
this now works (i.e. fully automatic kickstart).
Note this attempt was directly after the failed attempt with the by-id config - I forgot to check if that did something to the parition table before it failed.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.
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.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This should have been fixed a long time ago. If the problem persists please reopen this report.