F18 -> F19 distro-sync with yum

I woke up this morning to see my F18 instance not giving me the GNOME login screen. It just hangs after systemd brings up wpa_supplicant.service. And, throws this message:

systemd-readahead

Failed to read event: value too large for defined datatype

I fired up an F18 live-usb to see open a browser and check if there any existing bugs. Indeed there was one. It’s in ASSIGNED state. But I haven’t delved deep into the issue.

I quickly tried a few things :

  • Start the systemd-readahead-replay service manually
     $ systemctl start systemd-readahead-replay.service</ 
  • Try to invoke Xorg from a virtual terminal with the below CLI
    $ Xorg :0 -background none -verbose \
      -seat seat0 -nolisten tcp vt1
  • Boot into runlevel 3, and type init 5
  • Remove quiet from Kernel command-line, to find more verbos logs. No errors absolutely in /var/log/Xorg.* or /var/log/messages

All to no avail. I was drawing a blank and didn’t have any alternative, I’m working remote currently, and I only have this Lenovo X220 with me. I decided to just upgrade to Schrödinger’s Cat (i.e. Fedora-19). Why not? – I’ve been working for months with Fedora-19 composes on more than 5 servers just fine (but they’re all just minimal @core only virt hosts). I invoked the below command and went for my lunch…

$ yum update yum; yum clean all \
  yum --releasever=19 distro-sync --nogpgcheck -y

…voila — after download/update/cleanup/verify of 4770 packages, Schrödinger’s Cat is ready !

Advertisements

9 Comments

Filed under Uncategorized

9 responses to “F18 -> F19 distro-sync with yum

  1. disi

    I used fedup and had no problems at all. :)

  2. Juhani Jaakola

    I upgraded successfully from Fedora 17 to 18 with fedup. The only annoyance was that the Fedora 18 .iso could not reside on a removable media (my USB memory). I would expect that it works at least as well when upgrading from Fedora 18 to 19?

    fedup has the advantage of not updating the system which runs the upgrade – yum, rpm and glibc for example.

  3. John

    Tried fedup for 17-18, but it had issues (I think with nvidia drivers). Got fed up and went back to distrosync which worked fine. Was just googling for issues prior to doing 18-19 the same way.

  4. johnm

    if you are having trouble with fedup and read-only filesystems errors after reboot, check out this bug:

    https://bugzilla.redhat.com/show_bug.cgi?id=969648

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s