VortexBox 2.0: Update your system regularly

[divreg]

I just ran an upgrade the day after a successful Fast Upgrade to VB 2.0. *I ran both "yum clean all; yum update" from Mac Terminal and an Upgrade via the web GUI. I'm getting a similar, but different error as mentioned just above:Transaction Check Error:
file /usr/lib/libmad.so.0.2.1 from install of libmad-0.15.1b-13.fc12.i586 conflicts* with file from package libmad0-0.15.1b-4.fc16.i686

Error Summary

You can try erasing the fc12 i586 libmad (old) from the update process

yum erase libmad; yum update

and reinstall after performing a full update

yum install libmad

Check to see what dependencies are also being erased so you can reinstall those later as well.

I like your post.I understand it, the upgrade icon or the Command Line methods of upgrading VortexBox do not upgrade the Linux operating system, just the VB and LMS code. If that is correct, do you foresee any problem or have any advice for those of us who have upgraded to LMS 7.7.0, and not yet from Linux 14 to Linux 16?.However, VB 1.10 runs on Fedora 14, which is no longer being updated by Fedora. *So you will see no Fedora updates on VB 1.10.

It's an issue with terminology. You can still pick up critical security, VortexBox, and LMS updates on VB 1.10/FC14, but most other software updates have moved upstream to VB 2.0/FC16. To upgrade a VB 1.10 system to VB 2.0, see How To Upgrade VB 1.10 to VB 2.0: Fast Method.

[iainkitt]

I have just tried to update my Vortexbox Appliance as suggested using the upgrade button in the GUI. The process seemed to go OK until I got this message "Cleanup : 2:mtr-0.81-1.fc16.i686 535/535Non-fatal POSTTRANS scriptlet failure in rpm package httpd-2.2.22-2.fc16.i686' when it stopped completely. Now my VBA does not appear on my network at all. As a complete novice in all things Linux I would appreciate some help in how I go about sorting this out!

[Ron Olsen]

See http://info.vortexbox.org/tiki-index...e=Kernel+Panic

[iainkitt]

Thanks Ron. Tried that and the VBA doesn't reboot with the older kernel. Instead i get a white line going half-way across the screen with 'Fedora 16' at the right hand end and lots of churning from the hard disk! Am I going to have to do a clean install?

[iainkitt]

Spoke too soon! Has now rebooted

[iainkitt]

So after the VBA rebooted I went through the process to recover from kernel panic and it seemed to complete successfully. However when I rebooted at the end the VBA appears to still be using the corrupted kernel. Error message says that "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block." Any suggestions as to what I should do next?

[Ron Olsen]

What kernels are installed on your VB? Which one does not boot succesfully? Which one does boot successfully? See the GRUB boot screen for this info.

Try rebooting with a kernel that works, then enter

yum reinstall kernel-PAE-3.3.7*

and then

reboot

[iainkitt]

What kernels are installed on your VB? Which one does not boot succesfully? Which one does boot successfully? See the GRUB boot screen for this info.

Try rebooting with a kernel that works, then enter

yum reinstall kernel-PAE-3.3.7*

and then

reboot

Hi Ron

Thanks. Its booting from 3.1.4-1. When I try to reinstall kernel 3.3.7 I get a message saying it is available but not installed. I can now access my VBA through the GUI. is it worth trying an upgrade through that again?

[iainkitt]

Should have added that my VBA seems to be working fine now and I can access it through the GUI. does it matter if it reboots from an earlier kernel? Should I just try upgrading through the GUI again?

[Ron Olsen]

To install the latest kernel and other updates:

yum clean all; yum update

Then

reboot

to reboot with the latest kernel. After the reboot, enter

uname -r

to see which kernel is running. You should get

3.3.7-1.fc16.i686.PAE