Bug 907237 - F18 Anaconda stuck in MANUAL PARTITIONING when switching /boot 'device type' field (switch to vt2 and then back results in a white-screen)
Summary: F18 Anaconda stuck in MANUAL PARTITIONING when switching /boot 'device type' ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-03 22:33 UTC by Reartes Guillermo
Modified: 2013-08-28 17:29 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-28 17:29:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
when i click 'btrfs' anaconda experiences the specified malfunction (290.08 KB, image/jpeg)
2013-02-03 22:33 UTC, Reartes Guillermo
no flags Details
after switching to vt2 and returning (while screen) i clicked the "1 storage device selected' (which was not visible) (320.77 KB, image/jpeg)
2013-02-03 22:34 UTC, Reartes Guillermo
no flags Details
clicking the invisible 'finish partitioning' results in the MAIN HUB rejecting the storage configuration, but if one returns to MANUAL PARTITIONING this is shown (268.62 KB, image/jpeg)
2013-02-03 22:37 UTC, Reartes Guillermo
no flags Details
anaconda.log (17.57 KB, text/plain)
2013-02-03 22:38 UTC, Reartes Guillermo
no flags Details
program.log (43.24 KB, text/plain)
2013-02-03 22:39 UTC, Reartes Guillermo
no flags Details
storage.log (144.20 KB, text/plain)
2013-02-03 22:39 UTC, Reartes Guillermo
no flags Details

Description Reartes Guillermo 2013-02-03 22:33:20 UTC
Created attachment 692542 [details]
when i click 'btrfs' anaconda experiences the specified malfunction

Description of problem:

I cannot perform MANUAL PARTITIONING in my Netbook with a preexisting win and fedora. I tried deleting all trees first and then i tried to create:

* swap 4096mb (standard partition)
* /,/boot the remaining space (btrfs subvols)

But Anaconda fails when changing the 'device type' field in the 'customize' tree for /boot. 

There is something wrong, then i click BTRFS anaconda seems to froze but it is not frozen. Some elements are still clickable but the screen no longer refreshes. :-(

Version-Release number of selected component (if applicable):
F18 Release

How reproducible:
always.

Steps to Reproduce:

0. Boot F18 NetInst without any kernel parameter from an USB device.

1. Leave the default at the WELCOME SCREEN.

2. Enter NETWORK and Disable the Ethernet device (Set to OFF) to stop
Anaconda from using CLOSEST MIRROR, since it is slow and i will not use it.
Press 'done' and wait in the MAIN HUB for INSTALLATION SOURCE to display
'NOTHING SELECTED'.

3. Enter NETWORK and Enable the Ethernet device (Set to ON).
I also set the hostname.

4. Enter KEYBOARD and set (in my case) a Spanish one, then return to
the MAIN HUB.

5. Enter DATE&TIME and (in my case) set America/Argentina/Buenos_Aires and 
disable NTP. Then return to the MAIN HUB.

6. Enter INSTALLATION SOURCE, select NFS, then i set and ip and path. 

7. Enter SOFTWARE SELECTION and select (in my case) KDE Plasma Workspaces with
the following ad-dons: Development Tools, KDE Applications, KDE Multimedia Support, KDE Office, LibreOffice. Then return to the MAIN HUB.

8. Enter INSTALLATION DESTINATION and select sda only.

9. In INSTALLATION OPTIONS set 'scheme' to BTRFS and select 'manual partitioning'. (I later started with lvm scheme but the issue is the same).

10. In MANUAL PARTITIONING, expand the 'Unknown Linux' and delete the whole tree.

11. In MANUAL PARTITIONING, expand the 'Unknown' and delete the whole tree. Now, there is nothing defined. 

12. Add a SWAP of 4096mb. It is created ok.

13. Add a /boot, but do not define size (it will be BTRFS). It is created ok.

14. Select the recently created /boot and expand the 'customize' tree. Change the 'device type' from 'standard partition' to 'btrfs'. Once one clicks BTRFS anaconda malfunctions. It is like frozen but it is not, the mouse cursor changes to the hand one when hoovering over the partition entries.

15. Switch to VT2 and then to Anaconda again (VT6) and the scree will be all white-gray. Also the mouse cursor changes when hoovering over the partition entries and the disk summary. In fact, the disk summary screen is clickable if one first clicked any partition entries.

16. Result: It is not possible to install F18 on this system. Removing the partitions by hand before anaconda boots most likely will work.

17. 'Finish Partitioning' is also clickable right after clicking a partition entry. Anaconda will reject the storage configuration, when one reaches again the MANUAL PARTITIONING screen, it is still white but part of the MAIN HUB is still shown.

Actual results:
cannot setup the partitions in the intended way and cannot install.

Expected results:
being able to create a btrfs fs with /,/boot as subvols and a standard partition for swap. 

Additional info:
HW: MSI Wind U100 Netbook (1024x600 Resolution).

Comment 1 Reartes Guillermo 2013-02-03 22:34:49 UTC
Created attachment 692543 [details]
after switching to vt2 and returning (while screen) i clicked the "1 storage device selected' (which was not visible)

Comment 2 Reartes Guillermo 2013-02-03 22:37:51 UTC
Created attachment 692544 [details]
clicking the invisible 'finish partitioning' results in the MAIN HUB rejecting the storage configuration, but if one returns to MANUAL PARTITIONING this is shown

Comment 3 Reartes Guillermo 2013-02-03 22:38:48 UTC
Created attachment 692545 [details]
anaconda.log

Comment 4 Reartes Guillermo 2013-02-03 22:39:18 UTC
Created attachment 692546 [details]
program.log

Comment 5 Reartes Guillermo 2013-02-03 22:39:59 UTC
Created attachment 692547 [details]
storage.log

Comment 6 Reartes Guillermo 2013-02-03 23:01:41 UTC
I tried with basic video but it was much worse.

Comment 7 Reartes Guillermo 2013-02-04 14:39:05 UTC
I reproduced this with KVM and forced resolution to 800x480. I switched to vt2 and zapped the partition table with gdisk and tried again. I could not reproduce the issue with a non-partitioned disk. Maybe something breaks when one deletes the unknown trees.

Comment 8 Chris Lumens 2013-03-26 19:42:16 UTC
Is this reproducible with Fedora 19 alpha TC?  I've tracked down a couple mystery hangs, so it's possible I've got this one already.


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