This forum is no longer active. Please post your questions to our new community site

Forums Joomla!

apt-get upgrade

Subscribe to apt-get upgrade 5 post(s), 3 voice(s)

 
Avatar ctdh 8 post(s)

Hi I hope someone can help…

I have launched the Joomla EBS based ami on EC2 and when I run apt-get update and apt-get upgrade I get stuck with a dialogue saying:

You chose not to install GRUB to any devices. If you continue, the boot loader may not be properly configured, and when your computer next starts up it will use whatever was previously in the boot sector.
If there is an earlier version of GRUB 2 in the boot sector, it may be unable to load modules or handle the current configuration file.
If you are already running a different boot loader and want to carry on doing so, or if this is a special environment where you do not need a boot loader, then you should continue anyway. Otherwise, you should install GRUB somewhere.
Continue without installing GRUB?

If I click NO then the dialogue is returned again, selecting yes makes the machine un-bootable! I have clicked YES and then tried installing GRUB but it does no recognise device /dev/sda1.

How do I upgrade the joomla ami?
How do I install grub on the joomla ami?

Thanks
Charles

 
Avatar jabond 20 post(s)

I have the exact same problem with Wordpress AWS EC distro. The upgrade really f**ks up the entire server. What should we do to reverse? and install?

 
Avatar jabond 20 post(s)

and the first dialogue box we receive when upgrading is this one:

Configuring grub-pc â The following Linux command line was extracted from /etc/default/grub or â â the `kopt’ parameter in GRUB Legacy’s menu.lst. Please verify that it â â is correct, and modify it if necessary. â â â â Linux command line: â â
 
Avatar jabond 20 post(s)

Please any help on that. still can’t update because of that grub interruption. Any advice?

 
Avatar Beltrán Rueda Administrator 3,714 post(s)

Hi,

This is know Ubuntu issue https://blueprints.launchpad.net/ubuntu/+spec/s…. We will work to implement a workaround to fix this issue.

Forums Joomla!