Created attachment 685608 [details] working kickstart for new installation 1) Create a VirtualBox with four sata drives, each 20 GB. Boot with Fedora-18-i686-Live-KDE.iso in the optical drive. 2) Get a root terminal, then use fdisk, make the following partitions: /dev/sda1 2048 1026047 512000 83 Linux /dev/sda2 1026048 41943039 20458496 fd Linux raid autodetect /dev/sdb1 2048 1026047 512000 83 Linux /dev/sdb2 1026048 41943039 20458496 fd Linux raid autodetect /dev/sdc1 2048 1026047 512000 83 Linux /dev/sdc2 1026048 41943039 20458496 fd Linux raid autodetect /dev/sdd1 2048 1026047 512000 83 Linux /dev/sdd2 1026048 41943039 20458496 fd Linux raid autodetect 3) Do an installation: [root@localhost liveuser]# /usr/sbin/liveinst --text --kickstart=newsys.ks 4) Installation goes fine. Remove the .iso from the optical drive. Boot it, and dump various configurations (see vg.info). 5) Now, put the .iso back in and try to reuse the existing partitions. First, make sure the raid array is up: [root@localhost liveuser]# mdadm --assemble --scan mdadm: /dev/md/md0 has been started with 4 drives. [root@localhost liveuser]# cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] [raid0] [raid1] [raid10] md0 : active raid5 sda2[0] sdd2[4] sdc2[2] sdb2[1] 61324800 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU] bitmap: 0/1 pages [0KB], 65536KB chunk unused devices: <none> 6) Attempt the reuse (see also error.log, which might be more convenient to read): [root@localhost liveuser]# /usr/sbin/liveinst --text --kickstart=reuse.ks localuser:root being added to access control list Starting installer, one moment... anaconda 18.37.11 for Fedora 18 started. Starting automated install.... Generating updated storage configuration Traceback (most recent call last): File "/sbin/anaconda", line 990, in <module> anaconda._intf.setup(ksdata) File "/usr/lib/python2.7/site-packages/pyanaconda/ui/tui/__init__.py", line 144, in setup obj = klass(self._app, data, self.storage, self.payload, self.instclass) File "/usr/lib/python2.7/site-packages/pyanaconda/ui/tui/hubs/summary.py", line 48, in __init__ spoke.execute() File "/usr/lib/python2.7/site-packages/pyanaconda/ui/tui/spokes/storage.py", line 265, in execute doKickstartStorage(self.storage, self.data, self.instclass) File "/usr/lib/python2.7/site-packages/pyanaconda/kickstart.py", line 1486, in doKickstartStorage ksdata.raid.execute(storage, ksdata, instClass) File "/usr/lib/python2.7/site-packages/pyanaconda/kickstart.py", line 993, in execute r.execute(storage, ksdata, instClass) File "/usr/lib/python2.7/site-packages/pyanaconda/kickstart.py", line 1047, in execute raise KickstartValueError, formatErrorMsg(self.lineno, msg="No preexisting RAID device with the name \"%s\" was found." % devicename) pykickstart.errors.KickstartValueError: The following problem occurred on line 18 of the kickstart file: No preexisting RAID device with the name "md0" was found. 7) Notice that the raid array is no longer there: [root@localhost liveuser]# cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] [raid0] [raid1] [raid10] unused devices: <none> [root@localhost liveuser]#
Created attachment 685609 [details] non-working kickstart for reusing existing raid
Created attachment 685610 [details] raid status after booting installed system from hard-disk
Created attachment 685611 [details] error messages resulting from attempted reuse of raid
Also fails here when trying to reuse an existing layout (lvm over raid). # ks file, removed other config stuff install clearpart --none part raid.01 --onpart=sda1 (....) --noformat raid pv.01 --level=1 --device=md0 --noformat volgroup VolGroup00 pv.01 --noformat logvol / --fstype=ext4 --name=root --vgname=VolGroup00 --useexisting logvol /home --fstype=ext4 --name=home --vgname=VolGroup00 --noformat bootloader --location=mbr --timeout=5 --driveorder=sda > /usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py(1047)execute() -> raise KickstartValueError, formatErrorMsg(self.lineno, msg="No preexisting RAID device with the name \"%s\" was found." % devicename) (Pdb) bt /usr/lib64/python2.7/site-packages/pyanaconda/threads.py(91)run() -> threading.Thread.run(self, *args, **kwargs) /usr/lib64/python2.7/threading.py(504)run() -> self.__target(*self.__args, **self.__kwargs) /usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py(399)_doExecute() -> doKickstartStorage(self.storage, self.data, self.instclass) /usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py(1486)doKickstartStorage() -> ksdata.raid.execute(storage, ksdata, instClass) /usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py(993)execute() -> r.execute(storage, ksdata, instClass) > /usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py(1047)execute() -> raise KickstartValueError, formatErrorMsg(self.lineno, msg="No preexisting RAID device with the name \"%s\" was found." % devicename) (Pdb) print devicename md0 [root@localhost liveuser]# mdadm --examine --scan ARRAY /dev/md/0 metadata=1.2 UUID=8b3f8310:bc8690b4:31b53826:48b3f863 name=localhost:0
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.