Red Hat Bugzilla – Bug 862948
KickstartValueError: The following problem occurred on line 0 of the kickstart file: Requested boot drive vdb doesn't exist
Last modified: 2013-05-30 12:51:33 EDT
Description of problem:
entered storage, it bombed after i deselected all disk and leave storage.
Version-Release number of selected component:
libreport version: 2.0.14
cmdline: /usr/bin/python /sbin/anaconda
:The following was filed automatically by anaconda:
:anaconda 18.11 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 314, in execute
: msg="Requested boot drive %s doesn't exist" % self.bootDrive)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1557, in doKickstartStorage
: ksdata.bootloader.execute(storage, ksdata, instClass)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 333, in _doExecute
: doKickstartStorage(self.storage, self.data, self.instclass)
: File "/usr/lib64/python2.7/threading.py", line 504, in run
: self.__target(*self.__args, **self.__kwargs)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 87, in run
: threading.Thread.run(self, *args, **kwargs)
:KickstartValueError: The following problem occurred on line 0 of the kickstart file:
:Requested boot drive vdb doesn't exist
Created attachment 621244 [details]
Created attachment 621245 [details]
Created attachment 621246 [details]
Created attachment 621247 [details]
Created attachment 621248 [details]
Created attachment 621249 [details]
Created attachment 621250 [details]
Created attachment 621251 [details]
Created attachment 621252 [details]
Created attachment 621253 [details]
Created attachment 621254 [details]
Created attachment 621255 [details]
Created attachment 621256 [details]
Created attachment 621257 [details]
I can't reproduce this with anaconda-18.12 which is in the Beta TC2 compose.
Can you retest?
Created attachment 621881 [details]
I could not reproduce it (on two kvm guests) but i got this instead
it says "no disk selected" and remains greyed out (reboot needed to relaunch anaconda).
Ok, I'm going to close this bug. A new bug can be opened if you can reproduce the issue you just mentioned (after giving it a few minutes to reset)
Created attachment 624371 [details]
the bug is alive
i will try to reproduce it again to note the steps in detail, it took me by surprise to see this.
By the way, ABRT does not open another bug, it points to this one.
can this bug be re-opened?
i was trying to reproduce another bug.
i was switching back and forth manual to automatic partitioning and with either one, two disks.
OS Release: Fedora release 18-Beta-TC4
F18b TC5 (anaconda 18.18)
OS Release: Fedora release 18-Beta-TC5
*** Bug 868525 has been marked as a duplicate of this bug. ***
Are you still hitting this with anaconda-18.28 or later?
1) booted LiveCD of Fedora 18 in order to upgrade/reinstall the installation on harddrive
I have created bootable USB disk for that
2) I choosed to install to harddrive
3) Clicked "Storage" in order to choose partitions which to overwrite
4) Clicked "Encrypt my data" as the LVM volume and standalone partitions I have are already encrypted
5) in "Installation options" popup dialog I choosed "I do not need help; let me customize disk partitioning"
and pushed "Reclaim space"
6) Manual partitioning dialog pop-ed up, but after while it crashes
I have really non-standard partitioning - I guess that some of that freaks the installator to death:
Device size Id System
/dev/sda1 050G 07 HPFS/NTFS/exFAT
/dev/sda2 004G 83 /boot ext3
/dev/sda3 016G 83 Ubuntu / ext3 encrypted
/dev/sda4 05 Extended
/dev/sda5 016G 83 / for Fedora - LUKS encrypted ext3
/dev/sda6 016G 83 /home - LUKS encrypted ext3
/dev/sda7 004G 83 swap - LUKS encrypted swapfs
/dev/sda8 050G 07 HPFS/NTFS/exFAT
/dev/sda9 320G 8e LUKS encrypted LVM volume with 3 logical drives
OS Release: Fedora release 18
Trying to repartition drive.
OS Release: Fedora release 18
Closing this bug due to inactivity. Please reopen this bug and attach logs (/tmp/anaconda-tb-*) if you see this bug in Fedora 19 Beta or later.