Bug 753392 - Anaconda upgrade cannot find Previous F15 Installation
Summary: Anaconda upgrade cannot find Previous F15 Installation
Keywords:
Status: CLOSED DUPLICATE of bug 748119
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: x86_64
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: 2011-11-12 07:53 UTC by Michael
Modified: 2011-11-12 15:26 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-11-12 15:26:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Anaconda log (6.90 KB, text/x-log)
2011-11-12 07:53 UTC, Michael
no flags Details
syslog (130.25 KB, text/x-log)
2011-11-12 07:58 UTC, Michael
no flags Details

Description Michael 2011-11-12 07:53:23 UTC
Created attachment 533216 [details]
Anaconda log

Description of problem:

Yesterday I tried to upgrade to Fedora 16 with installation DVD but do not find my previous Fedora 15 for upgrade !
Until fedora 15 this procedure works without problems.

My PC has software RAID 1 installed from Fedora.

At syslog i get the following errors :

16:15:54,0 WARNING systemd: Cannot add dependency job for unit fedora-readonly.service, ignoring: Unit fedora-readonly.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-readonly.service' for details.
16:15:54,0 WARNING systemd: Cannot add dependency job for unit fedora-wait-storage.service, ignoring: Unit fedora-wait-storage.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-wait-storage.service' for details.
16:15:54,0 WARNING systemd: Cannot add dependency job for unit systemd-remount-api-vfs.service, ignoring: Unit systemd-remount-api-vfs.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-remount-api-vfs.service' for details.
16:15:54,0 WARNING systemd: Cannot add dependency job for unit fedora-storage-init.service, ignoring: Unit fedora-storage-init.service failed to load: No such file or directory. See system logs and 'systemctl status fedora-storage-init.service' for details.
16:15:54,0 WARNING systemd: Cannot add dependency job for unit lvm2-monitor.service, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
16:15:54,0 WARNING systemd: Cannot add dependency job for unit avahi-daemon.socket, ignoring: Unit avahi-daemon.socket failed to load: No such file or directory. See system logs and 'systemctl status avahi-daemon.socket' for details.
16:15:54,0 WARNING systemd: Cannot add dependency job for unit rpcbind.socket, ignoring: Unit rpcbind.socket failed to load: No such file or directory. See system logs and 'systemctl status rpcbind.socket' for details.
16:15:54,0 WARNING systemd: Cannot add dependency job for unit dm-event.socket, ignoring: Unit dm-event.socket failed to load: No such file or directory. See system logs and 'systemctl status dm-event.socket' for details.
16:15:54,0 WARNING systemd: Cannot add dependency job for unit ip6tables.service, ignoring: Unit ip6tables.service failed to load: No such file or directory. See system logs and 'systemctl status ip6tables.service' for details.
16:15:54,0 WARNING systemd: Cannot add dependency job for unit iptables.service, ignoring: Unit iptables.service failed to load: No such file or directory. See system logs and 'systemctl status iptables.service' for details.







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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Michael 2011-11-12 07:57:03 UTC
Trying to start rescue mode from install media DVD can't find any linux partitions !

The errors :

"Error cannot open Package Database  /mnt/sysimage/var/lib/rpm"

and after awhile 

"You don't have any Linux partitions. Press return to get a shell.
the system will reboot automatically when you exit from the shell"

Comment 2 Michael 2011-11-12 07:58:13 UTC
Created attachment 533217 [details]
syslog

Comment 3 Michael 2011-11-12 08:01:42 UTC
With preupgrade i had the following error 


Traceback (most recent call last):
  File "/usr/share/preupgrade/preupgrade-gtk.py", line 259, in on_assistant_apply
    self._do_main()
  File "/usr/share/preupgrade/preupgrade-gtk.py", line 278, in _do_main
    self.main_preupgrade()
  File "/usr/share/preupgrade/preupgrade-gtk.py", line 497, in main_preupgrade
    extra_args += " ks=%s" % self.pu.generate_kickstart()
  File "/usr/lib/python2.7/site-packages/preupgrade/__init__.py", line 607, in generate_kickstart
    return dev.bootpath_to_anacondapath(targetfile, UUID=True)
  File "/usr/lib/python2.7/site-packages/preupgrade/dev.py", line 91, in bootpath_to_anacondapath
    raise PUError, "/boot is on RAID device %s" % bootdev
preupgrade.error.PUError: /boot is on RAID device md0

Comment 4 Chris Lumens 2011-11-12 15:26:36 UTC

*** This bug has been marked as a duplicate of bug 748119 ***


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