No boot after upgrade

[avalx]

After the latest upgrade via GUI (this afternoon) the VBA does not boot anymore.


After attaching the monitor and keyboard I found out there was a new kernel installed and it looks like this is the problem:



#rpm -q kernel-PAE
kernel-PAE-2.6.35.9-99.fc14.i686
kernel-PAE-2.6.35.10-74.fc14.i686
kernel-PAE-2.6.35.11-83.fc14.i686



When booting the default kernel 2.6.35.11-83 here is a kernel panic message on the monitor, something like this:





Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block (0,0)


Pid: 1, comm: swapper Not Tainted 2.6.35.11-83.fc14.i686.PAE #1


…..



When manually choosing the other boot entry 2.6.35.10-74.fc14.i686 the VBA boot and work OK.


Any ideas what went wrong?

[andrew]

I have never seen this problem before but I googled the error you got and found this.




http://heuristically.wordpress.....n-block00/




Seems like un-install and reinstall of the kernel worked for this guy.

[avalx]

Thanks for the tip. After doing reinstall and reboot first all I got was a blank screen with blinking cursor, but after a hard reset the VBA rebooted OK with the new kernel and it works .


But now I get a strange message on the console regarding eth1 and br0 devices (I don't remember if this was present before):



eth1: error fetching interface information: Device not found


br0: error fetching interface information: Device not found



I've checked log files (dmesg and messages) and there is nothing about those devices. Also in the /etc/sysconfig/networking/devices/ there is only ifcfg-eth0. And ifconfig and system-config-network only show the eth0 networking device.


As the system works as expected I'm not much worried about this, but I'm still wondering where is this coming from .

[andrew]

This was a bug a while back. Did you update?

[avalx]

Yes, I did update (I do it every couple of days). As of yesterday those messages were still present. Do I need to reinstall some packages maybe?

[andrew]

Not sure why you would still get these messages. But as you mentioned they don't cause a problem.

[avalx]

I can live with that

[radish112]

Andrew and avalx,


For what it's worth, I also get the following on reboot:


eth1: error fetching interface information: Device not found


br0: error fetching interface information: Device not found


Steve

[Ron Olsen]

radish112 said:

Andrew and avalx,


For what it's worth, I also get the following on reboot:


eth1: error fetching interface information: Device not found


br0: error fetching interface information: Device not found


Steve




I've seen these messages too -- they occur on reboot when the VB GUI tries to determine the IP address of the VortexBox, but the network isn't up yet. Once the network comes up, the IP address calculation succeeds and things are good.


These errors are non-fatal and can be ignored. It might be possible to modify the VB GUI code to make sure the network is up before it tries to determine the VB IP address, but I don't know if it's worth the trouble. The code that does the IP address calculation is in


/var/www/html/libs/vortexbox_defs.php.


FYI, if you look in any of the log files like /var/log/messages and /var/log/squeezeboxserver/server.log, you'll see lots of non-fatal error messages; don't let them make you crazy; they're nothing to worry about if your system is operating normally.


Same holds true for some non-fatal error messages that occur at boot time; they are best ignored.

[radish112]

Ron,


Thanks for your reassuring and (as always) helpful post.


Steve