Bug 902128 - SwapSpaceError: format has not been created
Summary: SwapSpaceError: format has not been created
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ae10080f243c4ed916e8dc78159...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-21 01:10 UTC by Simona Avornicesei
Modified: 2014-02-05 15:28 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 15:28:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: anaconda.log (88.11 KB, text/plain)
2013-01-21 01:10 UTC, Simona Avornicesei
no flags Details
File: environ (780 bytes, text/plain)
2013-01-21 01:10 UTC, Simona Avornicesei
no flags Details
File: packaging.log (304.13 KB, text/plain)
2013-01-21 01:11 UTC, Simona Avornicesei
no flags Details
File: program.log (201.84 KB, text/plain)
2013-01-21 01:11 UTC, Simona Avornicesei
no flags Details
File: storage.log (524.93 KB, text/plain)
2013-01-21 01:11 UTC, Simona Avornicesei
no flags Details
File: syslog (113.83 KB, text/plain)
2013-01-21 01:11 UTC, Simona Avornicesei
no flags Details
File: anaconda-tb (1.39 MB, application/octet-stream)
2013-01-21 01:11 UTC, Simona Avornicesei
no flags Details

Description Simona Avornicesei 2013-01-21 01:10:50 UTC
Description of problem:
I'm trying to install F18 on an HP ProBook 4740s, with i7 IvyBridge CPU and AMD Radeon 7650M video card.
Deleted previous partitions, created by F17 install and repartitioned the hdd the same as before:
2Mb BIOS boot partition
1Gb     /boot    ext4
30Gb   /           ext4
603Gb /data    ext4 luks-encrypted
10Gb  /home   ext4 luks-encrypted
4Gb                 swap
rest of the disk unallocated

Then Anaconda requested the luks password, the GUI to install (my option was KDE) and then the root password. It failed at "creating biosboot on /dev/sda1".
Not sure if it's related but I could not delete the swap partition.
The following was filed automatically by anaconda:
anaconda 18.37.11 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/swap.py", line 130, in setup
    raise SwapSpaceError("format has not been created")
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2825, in turnOnSwap
    device.format.setup()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1650, in turnOnSwap
    upgrading=upgrading)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 189, in turnOnFilesystems
    storage.turnOnSwap()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 114, in doInstall
    turnOnFilesystems(storage)
  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 91, in run
    threading.Thread.run(self, *args, **kwargs)
SwapSpaceError: format has not been created

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda
cmdline_file:   initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2018\x20x86_64 quiet BOOT_IMAGE=vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.6.10-4.fc18.x86_64
other involved packages: 
package:        anaconda-18.37.11
product:        Fedora
release:        Cannot get release name.
type:           libreport
version:        18

Comment 1 Simona Avornicesei 2013-01-21 01:10:54 UTC
Created attachment 683992 [details]
File: anaconda.log

Comment 2 Simona Avornicesei 2013-01-21 01:10:57 UTC
Created attachment 683993 [details]
File: environ

Comment 3 Simona Avornicesei 2013-01-21 01:11:03 UTC
Created attachment 683994 [details]
File: packaging.log

Comment 4 Simona Avornicesei 2013-01-21 01:11:07 UTC
Created attachment 683995 [details]
File: program.log

Comment 5 Simona Avornicesei 2013-01-21 01:11:15 UTC
Created attachment 683996 [details]
File: storage.log

Comment 6 Simona Avornicesei 2013-01-21 01:11:19 UTC
Created attachment 683997 [details]
File: syslog

Comment 7 Simona Avornicesei 2013-01-21 01:11:30 UTC
Created attachment 683998 [details]
File: anaconda-tb

Comment 8 Fedora End Of Life 2013-12-21 10:38:08 UTC
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.

Comment 9 Fedora End Of Life 2014-02-05 15:28:09 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.