After emerge -u world it won't boot

[linuxbum]

After completing the emerge -u world and etc-update

I booted my 2.4.23 system and got the dreaded SP error at boot prompt.

So I booted CDROM and then mounted /root and my /usr, chroot to /mnt/gentoo like install, then mounted /boot as I had in before in /mnt/gentoo/boot.

Commanded gento to silo -C /mnt/gentoo/boot/silo.conf -f as saw in post about this error ran ok shutdown and rebooted fine.

Is this normal action for emerge -u world??
I had done emerge -pvu world > file.list then emerge -u one set at time to see which ones fail.
This time decided why not the WORLD as it's never enough
Will I have to do this every time I emerge -u world ???

What did the -f force silo to do ?????

[mad man moon]

Maybe your bootloader was replaced by a newer version during the update.
Always perform "emerge -pu world" to see what will be updated.
_________________
Join the adopt an unanswered post initiative today!

[Ferris]

Yes, if silo gets updated, you really do need to run that 'silo' command.

For what it's worth, here's something I learned a few days ago from
http://www.sparc-boot.org/how.html
and is worth passing on.

Regarding that 'SILO' string: 'SIL' comes from first stage of the boot loader,
and the 'O' comes from the second stage, thus:

The 'S' means that the first part of the boot loader ('first.b' or 'ultra.b')
actually got started;

The 'I' means that it was able to read something from where it things the
second stage ('second.b' is);

The 'L' means that what got read actually looks like the second stage;

And the 'O' is printed by the second stage 'second.b' and means that it
has taken over.

So, if you see 'SI'<death>, then what the first stage believes is the second
stage is not the second stage.

[linuxbum]

Thanks Ferris.

Yes my list shows silo was touch
Will look much closer for silo next time.
Bryan