Bug 701130 - anaconda/loader does not support preupgrade on fwraid partition
Summary: anaconda/loader does not support preupgrade on fwraid partition
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-01 12:25 UTC by Adam Huffman
Modified: 2012-08-06 20:04 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
: 708061 (view as bug list)
Environment:
Last Closed: 2012-08-06 20:04:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/tmp/syslog (94.41 KB, application/octet-stream)
2011-05-01 12:25 UTC, Adam Huffman
no flags Details
/tmp/X.log (24.24 KB, text/plain)
2011-05-01 12:27 UTC, Adam Huffman
no flags Details
/tmp/anaconda.log (4.69 KB, text/plain)
2011-05-01 12:27 UTC, Adam Huffman
no flags Details
/tmp/program.log (1.96 KB, text/plain)
2011-05-01 12:28 UTC, Adam Huffman
no flags Details
/tmp/storage.log (2.48 KB, text/plain)
2011-05-01 12:28 UTC, Adam Huffman
no flags Details

Description Adam Huffman 2011-05-01 12:25:59 UTC
Created attachment 496051 [details]
/tmp/syslog

Description of problem:
I've tried using preupgrade a couple of times to upgrade my Vaio Z11 laptop to F15.  On each occasion it hasn't asked me to provide a passphrase for the encrypted volumes and hasn't been able to find the kickstart file.  I'm assigning it to anaconda, though let me know if preupgrade is more appropriate.

The log files from the attempt are attached.

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

How reproducible:
Every time

Steps to Reproduce:
1. Boot into preupgrade kernel
2.
3.
  
Actual results:
Installer can't find kickstart file and doesn't ask for LUKS passphrase

Expected results:


Additional info:

Comment 1 Adam Huffman 2011-05-01 12:27:19 UTC
Created attachment 496052 [details]
/tmp/X.log

Comment 2 Adam Huffman 2011-05-01 12:27:54 UTC
Created attachment 496053 [details]
/tmp/anaconda.log

Comment 3 Adam Huffman 2011-05-01 12:28:27 UTC
Created attachment 496054 [details]
/tmp/program.log

Comment 4 Adam Huffman 2011-05-01 12:28:58 UTC
Created attachment 496055 [details]
/tmp/storage.log

Comment 5 Adam Huffman 2011-05-01 12:31:35 UTC
There are two 64GB SSDs in a BIOS RAID1 array.  Here's the disk layout:


ll /dev/disk/by-uuid/
total 0
lrwxrwxrwx. 1 root root 10 May  1 13:01 03937b80-94be-47e2-9a7e-f05f9d6877d1 -> ../../dm-0
lrwxrwxrwx. 1 root root 13 May  1 13:01 10ECC59FECC57F88 -> ../../md127p2
lrwxrwxrwx. 1 root root 13 May  1 13:01 1E4CC64A4CC61C81 -> ../../md127p3
lrwxrwxrwx. 1 root root 13 May  1 13:01 306d1566-9788-4403-9cd1-dfc14e2986a8 -> ../../md127p5
lrwxrwxrwx. 1 root root 10 May  1 13:01 39526e12-9aa9-482d-8058-994beab47e22 -> ../../dm-2
lrwxrwxrwx. 1 root root 10 May  1 13:01 436707b2-bd80-41b0-a6d9-0bc083561ce4 -> ../../dm-4
lrwxrwxrwx. 1 root root 10 May  1 13:01 5e502c24-2d6c-4303-8218-1f72e58470f0 -> ../../dm-1
lrwxrwxrwx. 1 root root 13 May  1 13:01 628480D68480ADDB -> ../../md127p1
lrwxrwxrwx. 1 root root 10 May  1 13:06 64DB-70AC -> ../../sdc1
lrwxrwxrwx. 1 root root 10 May  1 13:01 e5a79da3-ead4-42cd-95cf-ddfcb1e69ba0 -> ../../dm-3


 df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/luks-5e502c24-2d6c-4303-8218-1f72e58470f0
                       32G   18G   13G  58% /
tmpfs                 1.8G  868K  1.8G   1% /dev/shm
/dev/md127p5          485M  232M  228M  51% /boot
/dev/mapper/luks-e5a79da3-ead4-42cd-95cf-ddfcb1e69ba0
                       16G   11G  4.6G  70% /home
/dev/sdc1             3.8G   25M  3.8G   1% /media/USB DISK



[root@vaioz ~]# lvs
  LV   VG       Attr   LSize  Origin Snap%  Move Log Copy%  Convert
  home vg_vaioz -wi-ao 16.00g                                      
  root vg_vaioz -wi-ao 32.00g                                      
  swap vg_vaioz -wi-ao  2.00g                                      
[root@vaioz ~]# pvs
  PV           VG       Fmt  Attr PSize  PFree 
  /dev/md127p6 vg_vaioz lvm2 a-   61.25g 11.25g

Comment 6 David Lehman 2011-05-02 18:43:42 UTC
You are trying to specify a kickstart config that is on an encrypted block device? That isn't going to work anytime soon. Put it on an unencrypted device.

Comment 7 Adam Huffman 2011-05-02 21:11:27 UTC
/boot/upgrade is not on an encrypted device (/dev/md127p5), though.

Comment 8 David Lehman 2011-05-02 22:47:10 UTC
Your biosraid (containing /boot/upgrade) uses md, which is probably not supported for this either. You are probably the first one to try.

Comment 9 Chris Lumens 2011-12-21 17:56:32 UTC
I believe Will's work on getting rid of loader will make this sort of thing possible.

Comment 10 Fedora End Of Life 2012-08-06 20:04:36 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 11 Fedora End Of Life 2012-08-06 20:04:36 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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