fedup to F20 failed

[SternData]

I made a DVD and ran

fedup --device --network 20

Everything went OK until I rebooted and selected the fedup upgrade.
After thrashing around for a while, the system went into emergency mode,
unable to find a file system.

Rebooted and tried again with the same result.

I was able to reboot back into F19 and here I am.

So...

Is there any way to capture the error messages from the fedup kernel to
report here?

Anyone else have a similar problem?

[Junk]

On Tue, 2013-12-17 at 15:04 -0600, Steven Stern wrote:
> I made a DVD and ran
>
> fedup --device --network 20
>
> Everything went OK until I rebooted and selected the fedup upgrade.
> After thrashing around for a while, the system went into emergency mode,
> unable to find a file system.
>
> Rebooted and tried again with the same result.
>
> I was able to reboot back into F19 and here I am.
>
> So...
>
> Is there any way to capture the error messages from the fedup kernel to
> report here?
>
> Anyone else have a similar problem?
>
> -- 
> -- Steve

if you want to capture the boot info while it's in emergency mode do
journalctl -xb > ~/somefileorother

Interestingly I've had a similar issue with --iso

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

Junk

[Ralf Corsepius]

On 12/17/2013 10:04 PM, Steven Stern wrote:
> I made a DVD and ran
>
> fedup --device --network 20
> Anyone else have a similar problem?

I am not having your problem but a similiar one.

Here on one system, after having run fedup on f19, when rebooting for 
upgrade, the "upgrade system" starts, but after a couple of minute 
suddenly seems to stop and reboots into the old (f19) kernel without the 
upgrade actually having been performed.

Except that I am observing selinux alerts and systemd-journald 
warnings/error during the upgrade, I don't know the cause.

I guess, I'll resort to a traditional yum upgrade.

Ralf

[Chris Murphy]

On Dec 18, 2013, at 12:13 AM, Ralf Corsepius  wrote:
> On 12/17/2013 10:04 PM, Steven Stern wrote:
> > I made a DVD and ran
> >
> > fedup --device --network 20
> > Anyone else have a similar problem?
>
> I am not having your problem but a similiar one.
>
> Here on one system, after having run fedup on f19, when rebooting for upgrade, the "upgrade system" starts, but after a couple of minute suddenly seems to stop and reboots into the old (f19) kernel without the upgrade actually having been performed.
>
> Except that I am observing selinux alerts and systemd-journald warnings/error during the upgrade, I don't know the cause.
>
> I guess, I'll resort to a traditional yum upgrade.

Update to fedup 0.8
yum update fedup --enablerepo=updates-testing

This contains the details including renaming the folders so that files already downloaded with fedup 0.7 won't be redownloaded with fedup 0.8:

https://lists.fedoraproject.org/pipermail/test-announce/2013-December/000842...

Chris Murphy