Upgrading to VortexBox 1.5 on Fedora 14

[andrew]

We are ready to start testing upgrades to Fedora 14. This is an ALPHA process but seems to work well here in the lab. Please help test and post your results. Don't try this on a production system.

Start by getting the latest version of VortexBox



yum clean all
yum update

Then make sure there are no problems with your software packages.

cleanup-packages



If there are no errors proceed to the next step. If there are problems resolve them and then run this step again.


fedora-update-stage1

this will take quite a long time and update over 500+ packages. When it's done reboot


reboot


you now have Fedora 13 run the next step to clean up your system and install Fedora 14


fedora-update-stage2




this will take quite a long time and update over 500+ packages. When it's done reboot



reboot



now run the next step to clean up your new Fedora 13 system



fedora-update-stage3





You should probably reboot one more time once this is done. You now have an updated system to Fedora 14.

[Dennis A]

Thanks Andrew,


Will this upgrade process produce a different system configuration than the ISO installation of VB version 1.5 on Fedora version 14?


Is this a test of the upgrade process to allow a system that has media files to retain those files?

[cphan]

Andrew, looks like http://dl.atrpms.net/ and it's mirrors are no longer hosting the f11 repos. This breaks the update process before it starts. How should I proceed?

[andrew]

cphan said:Andrew, looks like http://dl.atrpms.net/ and it's mirrors are no longer hosting the f11 repos. This breaks the update process before it starts. How should I proceed?


Yes, I noticed that happend in the past few days. But that shouldn't stop the upgrade from working.

[cphan]

I get a whole series of errors because the f11 reference is broken. Should I ignore these and move forward?





[vortexbox.localdomain ~]# cleanup-packages
Cleaning up Everything


/var/tmp/rpm-tmp.Y6vb0t: line 851: IntegrateWithGNOME: command not found/var/tmp/rpm-tmp.2oYMsb: line 851: IntegrateWithGNOME: command not foundyum.Errors.RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: atrpms. Please verify its path and try again raise Errors.RepoError, msg File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1382, in _getRepoXML repoXML = property(fget=lambda self: self._getRepoXML(), File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1386, in repoXML = self.repoXML File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1222, in _check_db_version return repo._check_db_version(mdtype) File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 222, in _check_db_version if self._check_db_version(repo, mydbtype): File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 164, in populate sack.populate(repo, mdtype, callback, cacheonly) File "/usr/lib/python2.6/site-packages/yum/repos.py", line 277, in populateSack self.repos.populateSack(which=repos) File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 538, in _getSacks pkgSack = property(fget=lambda self: self._getSacks(), File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 702, in pkgSack = self.pkgSack File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 111, in _getTsInfo self._getTsInfo(remove_only) File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 100, in _getTs return self._getTs() File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 85, in doTsSetup my.doTsSetup() File "/usr/bin/package-cleanup", line 60, in initYum my = initYum(opts) File "/usr/bin/package-cleanup", line 460, in main main() File "/usr/bin/package-cleanup", line 499, in Traceback (most recent call last):Setting up yumNo problems foundProcessing all local requiresReading local RPM databaseSetting up yumNo dupes to cleanSetting up yumkernel-PAE-2.6.30.10-105.2.4.fc11.i686kernel-PAE-2.6.30.10-105.fc11.i686I will remove the following 2 kernel related packages:Setting up yumError: Cannot retrieve repository metadata (repomd.xml) for repository: atrpms. Please verify its path and try againTrying other mirror.http://www.mirrorservice.org/sites/download.atrpms.net/f11-i386/atrpms/stable/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not FoundTrying other mirror.http://dl.atrpms.net/f11-i386/atrpms/stable/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found


If you didn't see any errors this worked. If there where errors correct them and re-run.

[andrew]

Did you ever make any custom modifications to your VortexBox such as installing Gnome graphical desktop?

[cphan]

No changes to my VBA. Configuration as shipped.

[andrew]

OK try this





rpm -e --nodeps atrpms-release





(That's double dash nodeps)




Then run the upgrade again.

[cphan]

OK, I made some progress, but I'm stuck in f13,




I've passed fedora-update-stage2 but on stage 3 I get a cmd not found.

[vortexbox.localdomain ~]# fedora-update-stage3
-bash: fedora-update-stage3: command not found


So I poked around and found the following to keep the process moving


(From: http://fedoraproject.org/wiki/....._Fedora_14 (http://fedoraproject.org/wiki/YumUpgradeFaq#Fedora_13_-.3E_Fedora_14))



yum update yum yum --releasever=14 update --skip-broken

[andrew]

Did you run a yum update before you started the process? That's how you get fedora-update-stage3

[cphan]

I had a dependency issue, so I left your instructions to resolve that, and then came back, but that may have been were it went wrong.


My VBA is now:


VortexBox SW Version: 1.6


Linux OS Version: Fedora release 14 (Laughlin)


The SBS is working but I've got a list of packages that didn't upgrade because of dependency issues that I'm now going to sort through.

[andrew]

Sounds like your almost there.


If you follow the instructions exactly you won't have any dependency issues. I have tested it quite a few times here.

[koshpal]

Hey Andrew,


[vortexbox.localdomain ~]# fedora-update-stage3
-bash: fedora-update-stage3: command not found




yum update yum
&
yum --releasever=14 update --skip-broken


or


rpm -e –nodeps atrpms-release




doesn´t bring my vbs to


VortexBox SW Version: 1.6


Linux OS Version: Fedora release 14 (Laughlin)


What can i do?




Thanks

[andrew]

Sounds like you didn't upgrade to the latest code first so I'm not sure.

[dsdreamer]

Hi,




I just wanted to report that I had a failure trying the update process as I interpreted it from what is described here:




rpm -e --nodeps atrpms-release


yum update




This resulted in:


atrpms-release is needed by vortexbox-1.5-9.fc11.i586Unsatisfied dependencies for vortexbox-1.5-9.fc11.i586:




But I pressed ahead anyway and did a:


fedora-update-stage1




This resulted in:


Total download size: 353 M
Upgrade 464 Package(s)Install 131




After downloading 595 new packages, installing them and running their cleanup scripts I got to the following conclusion:


If you didn't see any errors this worked. If there where errors correct them and re-run.


Complete!






In fact the only error I saw was:


lame.i686 0:3.98.4-21.fc13 Skipped (dependency problems):




So I dared to do a reboot, which caused the machine to hang on its way back up.




I still don't know what went wrong. I could not recover even by using various Linux boot media with the rescue kernel boot parameter. I also found that the machine would hang when trying to install from the fc14 live CD (both x86 and 64-bit versions).




I was able to download, burn and install the latest vortexbox-1.6.iso (with MD5 10e3dbb6c5654690d64270241c83f60f) which is how I recovered Vortexbox functionality.




Is there anything in the sequence of commands that I used that could explain the failure to preserve a bootable machine? Is there any known reason why the latest FC 14 live CD would fail to boot on this D510 Atom hardware? (model name : Intel(R) Atom(TM) CPU D510 @ 1.66GHz).




I knew I was taking a risk by trying to update this way, and I have no complaints. Just wanting to share the info in case it can be useful to someone.




--dsdreamer

[andrew]

No sounds like you did the right thing. The problem is we can only test the update procedure on the VortexBox appliance. This may have been an incompatibility with your hardware.




When you say "hang" was there an error message of any kind?

[dsdreamer]

Thanks Andrew.




After reboot there was nothing to see on the monitor other than a blinking cursor.




Purely for information, this failure was on a MSI 6676-001BUS Intel Atom D510 (1.66GHz, dual-core) Intel NM10 Intel GMA 3150 machine.




Given all the warnings and work-arounds in http://fedoraproject.org/wiki/....._using_yum (http://fedoraproject.org/wiki/Upgrading_Fedora_using_yum), I was expecting trouble and not too upset when I got some trouble :-)




Finally, installing Vortexbox-1.6 from the ISO was glitch-free and restoring my music collection with a single rsync command was painless too.




--dsdreamer.

[avalx]

I have the same problem as dsdreamer http://vortexbox.org/wp-content/forum-smileys/sf-frown.gif


After reboot there is nothing on screen but the blinking cursor. I have the VortexBox applience and did as instructed in this post.


Now I wll try with the iso media, so I'm gonna lost some changes that I did in the config files (I have some backup files but am not sure if it is all I need).

[andrew]

If you get the blinking cursor you may want to just power the unit off and wait a little while then power it on. Not sure why but that has helped a few people.

[avalx]

Before reading your answer I allready started a clean install from CD, so I couldn't test this. I had some problems when I tried to do Advanced Install - the appliance crashed a couple of times during initial boot. With normal install there was no problem, I only had to reconfigure the keyboard layout manually.


Anyway it works now and the configuration was even easier to restore (from my backup config files) than expected. I only lost my Favorites radio stations and have to do some setting in the SBS again. Not very important but I would like to know which config files are relevant for SBS settings?


Thanks again for great work in this upgrade.

[avalx]

After upgrade everything looks OK only one thing bothers me.


Everytime I turn on the VBA there is a lot of disk activity going on for quite some time. It's due to forked-daapd doing something – maybe reindexing all the files? If I restart this service the activity stops. Even if I let this activity to end by itself and then reboot, the disk is very active again and I have to stop the service.


This is what is in the log file:


main: Forked Media Server Version 0.12 taking off
main: mDNS init
mdns: Avahi state change: Client running
ffmpeg: invalid id 207
ffmpeg: invalid id 207


And after reboot:


mdns: Avahi state change: Client failure
mdns: Avahi Server disconnected, reconnecting
mdns: Avahi state change: Client connecting
main: Got SIGTERM or SIGINT
main: Stopping gracefully
main: mDNS deinit
main: Remote pairing deinit
main: HTTPd deinit
main: Player deinit
main: File scanner deinit
main: Database deinit
main: Exiting.


Any idea why this is happening every time?

[wizardofoz]

Damn now I read the part about 1.6 iso….why no announcement?

[Hajaz]

i was already on f13 vb1.5... is there anyway to upgrade to 1.6 f14 from that?


cant get the stage3 upgrade to work

[jistirling]

Hi Guys,




My experiance, back up your music and any config changes you made and install the 1.6iso.




http://vortexbox.org/forum/hel.....this-done/ (http://vortexbox.org/forum/help/upgrading-from-1-5-to-1-6-how-is-this-done/)




Many others have had the same pain. We had similair problems going from Fedora 9 to Fedora 11 (I think).




Cheers,


James

[andrew]

Hajaz said:

i was already on f13 vb1.5... is there anyway to upgrade to 1.6 f14 from that?


cant get the stage3 upgrade to work




If your already on F13 just run a



yum -y --releasever=14 distro-sync --skip-broken


and you should be fine. Basically it's the lst two steps of the upgrade.

http://vortexbox.org/documenta.....fedora-14/ (http://vortexbox.org/documentation/how-do-i-update-my-vortexbox-to-veriosn-1-6-fedora-14/)