11:19 p.m.
System: AMD Opteron 2216 server, 2GB RAM
250GB SATA-300 HDD
ATI X1600 PCI-X video card
Running Fedora 17 on an encrypted volume
The system was decomissioned pending hardware repairs for quite a while
(since July-2012). Once I finally gotba spare new hdd and monitor, it was
brought back to life and fetched over 1,400 updates. After that it rebooted
fine to an "as fresh as one can possibly get a F17 installation".
So I thought it would be a nice opportunity to test that "FedUp" thing I
keep reading about... and preserve my nice Gnome 3 tweaks of F17 in the
latest greatest F19....
I told FedUp to use a repo upgrade, as the FedUp wiki recommended that
approach over media install. I thought it'd be also a nice opportunity to
test my 30Mbit FTTH link. Before I knew it it was fetching packages like
there was no tomorrow and the list of packages was scrolling on the screen
faster than one could read it.
It went through several install phases until I was told everything was
ready to proceed with the upgrade which would begin after the reboot.
After the reboot a new entry appeared on the Grub boot menu labeled "FedUp
upgrade" or something along those lines.
After selecting it, the familiar "f"logk appeared alomg with a progress bar
below it. The progress bar completed to 99% or therabouts and then it
stalled. It could have been at 95% or 100% I do not recall (there also was
no numerical reading next to the progress bar so it was hard to tell the
percentage of completion.
After I few minutes it just stood there... I thought Id give it a couple of
HOURS so I could conclude if the process hanged or was just waiting too
long.
Two hours later I came back and saw the screen with the same output I saw
before.
So I grudgingly hit the reset button, thinking that maybe if the process
was incomplete it would re-start after a reboot or Id be shown with some
error mesage about the outcome of the upgrade process.
I was wrong.
In the current state, boot menu no longer shows the FedUp option, only
showing:
Fedora (3.9.10-100.fc17.i686)
Fedora (3.9.10-100.fc17.i686.PAE)
Fedora (3.4.6-2.fc17.i686)
Fedora (3.4.6-2.fc17.i686.PAE)
Fedora (3.4.4-3.fc17.i686.PAE)
Fedora (3.4.4-3.fc17.i686)
NO MATTER what I select, it hangs. Ive tried all kernels. It hangs right
after the [f] logo has its glow, and just stays there.
I would really appreciate any ideas of what might have gone wrong, and I
hope my feedback is of use to FedUp devs. If you want logs etc, I can look
them up and paste to pastebin... as long as I can get back a working
bootable system in the first place.
Thanks in advance...
FC
--
During times of Universal Deceit, telling the truth becomes a revolutionary
act
Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto
Revolucionario
- George Orwell
6 a.m.
On 03/11/13 05:50, Fernando Cassia wrote:
On Sun, Nov 3, 2013 at 2:38 AM, Joe Zeff <joe(a)zeff.us
<mailto:joe@zeff.us>> wrote:
You may have run afoul of this:
https://bugzilla.redhat.com/__show_bug.cgi?id=980543
<https://bugzilla.redhat.com/show_bug.cgi?id=980543> Yes, it refers
to 18-19, but it hit me on an upgrade from 17-19. Also, the
maintainers are claiming that it's caused by a process that's just
taking longer than expected to complete. My suggestion is that you
try using distro-sync once you get to a CLI.
Thanks for the tip. Yeah it looks like it :-/
Seriously, if the devs cant create an upgrade GUI that gives some visual
feedback about what is going on, they should reconsider their line of
work. I would suggest agriculture... or arts.... fields where "nothing
happened for hours" can be actually desirable or intended...
FC
I remember that I said this as part of a post on another subject on the
rpmfusion-users list in August. That was f17 > f18:
No problem with the upgrade, starting from a fully updated system
with all relevant repos enabled. Really very impressive, but the screen display after the
reboot into it was useless; only a static blue bar while intense disk activity went on
for around 90 minutes. Hitting 'escape' brought up the rolling upgrade log, but I
only realised I could do that after a long time watching nothing change and wondering
about infinite loops.
John P
5:30 a.m.
NO MATTER what I select, it hangs. Ive tried all kernels. It hangs right
after the [f] logo has its glow, and just stays there.
>> Have you tried booting to level 3?
>>
> Fedora 19's been doing this intermittently on my machines for months.
> More so on the little Dell1520 laptop.
> There are no error messages and nothing in the logs.
> I just restart.
> Roge
Wait a minute!
I've had occasional problems in which F19 gets to a certain point and
then "fails out" of the GUI. I get a message saying that Plymouth has
failed. Then it goes for a few more processes and seems to sit
there--in command-line mode.
I don't think it's hardware related. I have noticed that since the last
3 upgrades, 3-4 days, it has not happened on my desktop machine and only
once yesterday on the dell but that was before the last upgrade.
Myst watch tomorrow.
Roger
4:32 a.m.
On 11/03/2013 01:43 AM, Roger wrote:
On 11/03/2013 04:18 PM, Ed Greshko wrote:
> On 11/03/13 12:19, Fernando Cassia wrote:
>> NO MATTER what I select, it hangs. Ive tried all kernels. It hangs
>> right after the [f] logo has its glow, and just stays there.
> Have you tried booting to level 3?
>
Fedora 19's been doing this intermittently on my machines for months.
More so on the little Dell1520 laptop.
There are no error messages and nothing in the logs.
I just restart.
Roge
Wait a minute!
I've had occasional problems in which F19 gets to a certain point and
then "fails out" of the GUI. I get a message saying that Plymouth has
failed. Then it goes for a few more processes and seems to sit there--in
command-line mode.
Last time that happened, I tried restarting. Seven failed restarts
later, I just left it alone for half an hour. And then, though it
"failed out" of Plymouth, it eventually got to a login screen--while
paging to beat the band almost the whole time. And that session went on
with everything taking five times as long as usual--again while paging
constantly. As if it had to repair the journal, perhaps. And after that,
the delays went away.
I thought my hardware was at fault. But I ran hardware diagnostics. My
CPU, memory, and drive all passed.
Temlakos
1:43 a.m.
On 11/03/2013 04:18 PM, Ed Greshko wrote:
On 11/03/13 12:19, Fernando Cassia wrote:
> NO MATTER what I select, it hangs. Ive tried all kernels. It hangs right after the
[f] logo has its glow, and just stays there.
Have you tried booting to level 3?
Fedora 19's been doing this intermittently on my machines for months.
More so on the little Dell1520 laptop.
There are no error messages and nothing in the logs.
I just restart.
Roge
12:22 a.m.
On Sun, Nov 3, 2013 at 2:18 AM, Ed Greshko <Ed.Greshko(a)greshko.com> wrote:
Have you tried booting to level 3?
No, I wanted to know first if this was a known scenario, before I went to
the command line and started messing up things further ;).
But yes, that sounds like the right step
FC
--
During times of Universal Deceit, telling the truth becomes a revolutionary
act
Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto
Revolucionario
- George Orwell
12:50 a.m.
On Sun, Nov 3, 2013 at 2:38 AM, Joe Zeff <joe(a)zeff.us> wrote:
You may have run afoul of this: https://bugzilla.redhat.com/
show_bug.cgi?id=980543 Yes, it refers to 18-19, but it hit me on an
upgrade from 17-19. Also, the maintainers are claiming that it's caused by
a process that's just taking longer than expected to complete. My
suggestion is that you try using distro-sync once you get to a CLI.
Thanks for the tip. Yeah it looks like it :-/
Seriously, if the devs cant create an upgrade GUI that gives some visual
feedback about what is going on, they should reconsider their line of work.
I would suggest agriculture... or arts.... fields where "nothing happened
for hours" can be actually desirable or intended...
FC
--
During times of Universal Deceit, telling the truth becomes a revolutionary
act
Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto
Revolucionario
- George Orwell
12:39 a.m.
On Sun, Nov 3, 2013 at 2:18 AM, Ed Greshko <Ed.Greshko(a)greshko.com> wrote:
Have you tried booting to level 3?
OK, here's what I see after booting in runlevel 3 with quiet and rgbh
removed:
systemd[1]: dbus.service start request repeated too quickly, refusing to
start
systemd[1]: Unit dbus.socket entered a failed state
systemd.logind[819]: Failed to get system D-Bus connection
systemd.logind[819]: Failedbto fully start up daemon: Connection refused
systemd[1]: Unit systemd-logind.service entered a failed state
systemd[1]: systemd-logind.service holdoff time over,scheduling restart
systemd[1]: systemd-logind.service start request repeated too quickly,
refusing to start
Then hundreds of avc denials relating to networkmanager...
FC
--
During times of Universal Deceit, telling the truth becomes a revolutionary
act
Durante épocas de Engaño Universal, decir la verdad se convierte en un Acto
Revolucionario
- George Orwell
12:38 a.m.
On 11/02/2013 10:22 PM, Fernando Cassia wrote:
No, I wanted to know first if this was a known scenario, before I
went
to the command line and started messing up things further ;).
You may have run afoul of this:
https://bugzilla.redhat.com/show_bug.cgi?id=980543 Yes, it refers to
18-19, but it hit me on an upgrade from 17-19. Also, the maintainers
are claiming that it's caused by a process that's just taking longer
than expected to complete. My suggestion is that you try using
distro-sync once you get to a CLI.
3820
days inactive
3820
days old
9 comments
6 participants
participants (6)
-
Ed Greshko -
Fernando Cassia -
Joe Zeff -
John Pilkington -
Roger -
Temlakos