FedoraForum.org - Fedora Support Forums and Community
Page 3 of 4 FirstFirst 1 2 3 4 LastLast
Results 31 to 45 of 58
  1. #31
    Join Date
    Dec 2013
    Location
    France
    Posts
    1

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    For me updating fedup doesn't work:

    $ sudo yum --enablerepo=updates-testing update fedup
    Loaded plugins: langpacks, refresh-packagekit
    No packages marked for update

    $ rpm -qi fedup
    Name : fedup
    Version : 0.7.3
    Release : 4.fc19
    Architecture: noarch
    (...)
    Any ideas?

  2. #32
    Join Date
    Dec 2008
    Location
    Vancouver, BC
    Posts
    4,327

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    It's moving between updates-testing and updates right now. If you try again soon it should work, or you can grab it from koji if you must have it now:

    http://koji.fedoraproject.org/koji/b...buildID=484014
    Adam Williamson | awilliam AT redhat DOT com
    Fedora QA Community Monkey
    IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
    http://www.happyassassin.net

  3. #33
    Join Date
    May 2010
    Location
    Midwest USA
    Age
    50
    Posts
    514

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    Quote Originally Posted by shenwei356
    Hi, all. Thanks you again.

    I wrote a upgrade guide on my blog by your valuable advices:

    -------------------------------------------------------------
    It will fail to upgrade Fedora 19 to Fedora 20 directly by running fedup sudo fedup --network 20, you must do this firstly, following vbraun's advice.

    sudo yum --enablerepo=updates-testing update fedup

    If you have failed with fedup 0.7, you can do this to avoid redownload packages, following AdamW's advice.

    sudo mv /var/lib/fedora-upgrade /var/lib/system-upgrade
    sudo mv /var/tmp/fedora-upgrade /var/tmp/system-upgrade


    And then, import GPG-KEY, following Sayen's advice:

    sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-20

    Finally,

    sudo fedup --network 20
    Yep, same issue as everyone else, that solution worked just fine for me.

    Code:
    Linux 3.11.10-301.fc20.x86_64 #1 SMP Thu Dec 5 14:01:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
    And again, just like after the F18 > F19 fedup, the RPMfusion Nvidia binary blog was working just fine after, without me having to actually do anything.

    CronoCloud
    Last edited by CronoCloud; 19th December 2013 at 08:27 PM.
    Running Fedora 25 64-bit on a HP/Compaq Presario CQ5320F 2.8GHz Quad-core Phenom II CPU, 8GB RAM, EVGA GT640 SC 1GB GDDR5 rev2 video card.
    Vizio E221-A1 22" 1080p HDTV with HDMI, using 1080P (1920x1080) over HDMI

  4. #34
    Join Date
    Nov 2006
    Location
    Detroit
    Posts
    6,669

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    Just upgraded from F19 to F20 today using fedup. The only issue I had was with SELinux. After selecting the System Upgrade option in grub, the system just hanged with a message saying something like "systemd[1]: Failed to initialize SELinux context ...". I waited to see if it would change, no dice. I have always had SELinux turned off, so my guess is that fedup didn't anticipate that.

    So I did some digging around and found a solution: append the following to the System Upgrade menu item in grub (the line that starts with "linux ..."):
    Code:
    selinux=0 enforcing=0
    After doing that, the System Upgrade option worked, and the rest of the upgrade went smoothly.

    It's possible that this might fix the problem that others are having. I'm surprised that fedup apparently assumes that people are using SELinux. That's the first thing I disable when I install a new Fedora system, and I bet a lot of other people do too.
    OS: Fedora 27 x86_64 | Machine: HP Pavilion a6130n | CPU: AMD 64 X2 Dual-Core 5000+ 2.6GHz | RAM: 7GB PC5300 DDR2 | Disk: 400GB SATA | Video: ATI Radeon HD 4350 512MB | Sound: Realtek ALC888S | Ethernet: Realtek RTL8201N

  5. #35
    Join Date
    Dec 2008
    Location
    Vancouver, BC
    Posts
    4,327

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    Quote Originally Posted by RupertPupkin
    Just upgraded from F19 to F20 today using fedup. The only issue I had was with SELinux. After selecting the System Upgrade option in grub, the system just hanged with a message saying something like "systemd[1]: Failed to initialize SELinux context ...". I waited to see if it would change, no dice. I have always had SELinux turned off, so my guess is that fedup didn't anticipate that.

    So I did some digging around and found a solution: append the following to the System Upgrade menu item in grub (the line that starts with "linux ..."):
    Code:
    selinux=0 enforcing=0
    After doing that, the System Upgrade option worked, and the rest of the upgrade went smoothly.

    It's possible that this might fix the problem that others are having. I'm surprised that fedup apparently assumes that people are using SELinux. That's the first thing I disable when I install a new Fedora system, and I bet a lot of other people do too.
    I just tested this, and couldn't exactly reproduce it. If I install F19 and disable selinux by adding it to the kernel parameters for the default kernel, when I run fedup, 'selinux=0' is appended to the parameters of the fedup System Upgrade boot menu entry too. That's not surprising, as fedup just calls new-kernel-pkg to set up its bootloader entry, just like a normal kernel install.
    Adam Williamson | awilliam AT redhat DOT com
    Fedora QA Community Monkey
    IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
    http://www.happyassassin.net

  6. #36
    Join Date
    Nov 2006
    Location
    Detroit
    Posts
    6,669

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    Quote Originally Posted by AdamW
    If I install F19 and disable selinux by adding it to the kernel parameters for the default kernel
    I've never disabled SELinux that way. I do it by setting SELINUX=disabled in /etc/sysconfig/selinux.
    OS: Fedora 27 x86_64 | Machine: HP Pavilion a6130n | CPU: AMD 64 X2 Dual-Core 5000+ 2.6GHz | RAM: 7GB PC5300 DDR2 | Disk: 400GB SATA | Video: ATI Radeon HD 4350 512MB | Sound: Realtek ALC888S | Ethernet: Realtek RTL8201N

  7. #37
    Join Date
    Dec 2008
    Location
    Vancouver, BC
    Posts
    4,327

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    sigh, there's always three damn ways to do every damn thing.
    Adam Williamson | awilliam AT redhat DOT com
    Fedora QA Community Monkey
    IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
    http://www.happyassassin.net

  8. #38
    Join Date
    Dec 2008
    Location
    Vancouver, BC
    Posts
    4,327

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    can't reproduce even that way. the upgrade proceeds successfully, though selinux=0 isn't on the command line. perhaps it needs a dirtier system?
    Adam Williamson | awilliam AT redhat DOT com
    Fedora QA Community Monkey
    IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
    http://www.happyassassin.net

  9. #39
    Join Date
    Nov 2004
    Location
    MT USA
    Posts
    883

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    FWIW, I always have selinix disabled too via the /etc/sysconfig/selinux file as well. My upgrade on two machines had no problem with selinx disabled during the upgrade. Note that the selinux module files/libs are still present, I just disable it. Also, I don't use LVM either if that has anything to do with it... I now just have the fstab nfs problem which I can get around for now by manually mounting after boot. I will explore the problem more when I have time.
    Last edited by rclark; 20th December 2013 at 06:09 AM.

  10. #40
    Join Date
    May 2010
    Location
    Midwest USA
    Age
    50
    Posts
    514

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    I have SELinux disabled as well, all the upgrade did for me in regards to SELinux was to do a required re-label or something of that sort, early on. I thought that was strange, since I have it disabled...didn't seem to do any harm.

    CronoCloud
    Running Fedora 25 64-bit on a HP/Compaq Presario CQ5320F 2.8GHz Quad-core Phenom II CPU, 8GB RAM, EVGA GT640 SC 1GB GDDR5 rev2 video card.
    Vizio E221-A1 22" 1080p HDTV with HDMI, using 1080P (1920x1080) over HDMI

  11. #41
    Join Date
    Aug 2009
    Posts
    8,464

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    Quote Originally Posted by RupertPupkin
    Just upgraded from F19 to F20 today using fedup. The only issue I had was with SELinux. After selecting the System Upgrade option in grub, the system just hanged with a message saying something like "systemd[1]: Failed to initialize SELinux context ...". I waited to see if it would change, no dice. I have always had SELinux turned off, so my guess is that fedup didn't anticipate that.

    So I did some digging around and found a solution: append the following to the System Upgrade menu item in grub (the line that starts with "linux ..."):
    Code:
    selinux=0 enforcing=0
    After doing that, the System Upgrade option worked, and the rest of the upgrade went smoothly.

    It's possible that this might fix the problem that others are having. I'm surprised that fedup apparently assumes that people are using SELinux. That's the first thing I disable when I install a new Fedora system, and I bet a lot of other people do too.
    I would have tried with just the enforcing=0 option first. In fact, I use that every time I do an upgrade now since I got bit a few versions back where I had a hosed system due to SELinux not allowing some files when it upgraded packages, and I ended up with packages installed, but their files were zero byte files

    My usual upgrade procedure now is to boot with enforcing=0 to do the actual upgrade, then I also run a complete SELinux relabel once the upgrade is done. The relabel is probably unnecessary, but it does make sure that any differences in SELinux contexts between releases are taken care of.

    Note that the selinux=0 option is a big hammer (so to speak) and your SELinux contexts won't get updated on anything installed while disabled. You will pretty much have to do the complete relabel once the upgrade is done if you use it and usually run with SELinux on.

    I run with SELinux in enforcing mode, and after getting used to configuring it, I would not run any other way. SELinux has kept me from messing up my own system, plus locked it down so others can't either. It's not too hard to use SELinux and allow just about anything you need, but still keep the protection it offers.

  12. #42
    Join Date
    Jun 2005
    Location
    Oulu, Finland
    Posts
    74

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    As the originator of this thread I felt I should report my own progress.

    After fedup 0.8 was announced as a solution, I've now successfully upgraded two installations. The other one had SELinux enabled and the other one didn't. After updating FedUp I didn't have any problems with either one.

  13. #43
    Join Date
    Jun 2012
    Location
    San Jose
    Posts
    2

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    I'm seeing similar problems to this thread. I'm using fedup 0.8, which seems to download everything without errors. After a reboot, the GUI login displays, but the upgrade never starts.
    Disabling selinix has no affect on the problem. There are no obvious problems in syslog, other than the firewall and lsb failing to start. Any ideas on where to look?

  14. #44
    Join Date
    Dec 2013
    Location
    UK
    Posts
    1

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    I have upgraded 4 systems to Fedora 20, two worked and two have failed due to (I believe) selinux issues. In both cases during the upgrade i.e. after re-booting into system upgrade, the upgrade/selinux has relabelled. (i'm not sure which partitions) and then rebooted. On reboot the upgrade eventually times out with a dependency on one of the partitions. I tried commenting the non-system partitions out from /etc/fstab but it stll hung on /var. I have selinux disabled on both systems. I tried selinux=0 enforcing=0 on the upgrade kernel but whilst it got further, firewalld failed and I was dropped back to a fedora 19 kernel. I am now proceeding with a yum update to F20 but I would like to know have to avoid this situation. Should I re-label before the upgrade?

  15. #45
    Join Date
    Dec 2008
    Location
    Vancouver, BC
    Posts
    4,327

    Re: Use fedup 0.8 to upgrade to Fedora 20! (FedUp F19->F20 fails after reboot)

    It's known that upgrade fails if you have separate /var partition. https://fedoraproject.org/wiki/Commo...-var-partition
    Adam Williamson | awilliam AT redhat DOT com
    Fedora QA Community Monkey
    IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
    http://www.happyassassin.net

Page 3 of 4 FirstFirst 1 2 3 4 LastLast

Similar Threads

  1. Fedora 19->20 fedup upgrade fails
    By digiscuro in forum Installation, Upgrades and Live Media
    Replies: 6
    Last Post: 18th December 2013, 03:10 AM
  2. Another failed upgrade: f17->f19 with fedup
    By sidebrnz in forum Installation, Upgrades and Live Media
    Replies: 6
    Last Post: 30th September 2013, 10:20 AM
  3. Apache fails to load after fedup to F19
    By joecurtis in forum Installation, Upgrades and Live Media
    Replies: 2
    Last Post: 13th August 2013, 01:37 PM
  4. Replies: 3
    Last Post: 12th August 2013, 01:59 AM
  5. Fedup to upgrade F18 to F19 with Live iso
    By grishi111 in forum Installation, Upgrades and Live Media
    Replies: 1
    Last Post: 4th July 2013, 06:39 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •