grub 2 install unsuccesful and now can't run update manager

[robert]

can't run synaptic or update manager after trying to upgrade to grub 2. New message reading can't lock device because either apt-get or aptitude is running please close program. here is the following message I get when trying to run either program :E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
E: _cache->open() failed, please report. when attempting to run that very command then the first message comes up.

[Nicola Ferralis (feranick)]

Thanks for taking the time to submit this report. It seems something went wrong during an update. I would recommend to run, from the terminal (Applications->Accessories->Terminal):

sudo apt-get install -f

That should fix it. Please let us know if that is the case. Thanks.

[robert (raweinstein)]

 sudo apt-get install -f
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
 The same message appears.

[Nicola Ferralis (feranick)]

I assumed you tried already to follow what the actual error message suggested, that is to run in the terminal:

sudo dpkg --configure -a

Alternatively, also try:

sudo apt-get upgrade -f

Please let us know.

[robert (raweinstein)]

 │ In order to replace the Legacy version of GRUB in your system, it is ▒
 │ recommended that /boot/grub/menu.lst is adjusted to chainload GRUB 2 ▒
 │ from your existing GRUB Legacy setup. This step may be automaticaly ▒
 │ performed now. ▒
 │ ▒
 │ It's recommended that you accept chainloading GRUB 2 from menu.lst, and ▒
 │ verify that your new GRUB 2 setup is functional for you, before you ▒
 │ install it directly to your MBR (Master Boot Record). ▒
 │ ▒
 │ In either case, whenever you want GRUB 2 to be loaded directly from MBR, ▒
 │ you can do so by issuing (as root) the following command: ▒
 │ ▮
 │ upgrade-from-grub-legacy

   Most people when they report bugs do have some basic knowledge, so with that said of course I have tried both commands and update from grub-legacy with no success. Now one of my cpu's are at 100% capacity so something is definitely wrong here. I have supplied all the information that could be possibly relevant to this issue. when this first happened I had to reboot to bring one of my cpu's back to normal operating range. I should have never tried to change my grub to grub 2 without noticing that there are bugs with this to be worked out!!! Thanks for the advice so far but to no avail, I can't even do updates because of this very issue. Let's try something else to get different results. Thank you.

[Nicola Ferralis (feranick)]

You would be1000 surprised to hear that many bug reported actually can be fixed by those simple commands.

Anyway I will assign this bug to the grub2 package so the developers can llok through it. If you feel that another package is better fit, than please change it accordingly.

[robert (raweinstein)]

O.K. so now were back were we started and nothing gets resolved. The above message it exactly what appears when I try and issue those exact commands. Either sudo dpkg --configure -a or upgrade-from-grub-legacy or sudo apt-get upgrade -f. The main problem is how to complete this process : │ In order to replace the Legacy version of GRUB in your system, it is ▒
 │ recommended that /boot/grub/menu.lst is adjusted to chainload GRUB 2 ▒
 │ from your existing GRUB Legacy setup. This step may be automaticaly ▒
 │ performed now. ▒
 │ ▒
 │ It's recommended that you accept chainloading GRUB 2 from menu.lst, and ▒
 │ verify that your new GRUB 2 setup is functional for you, before you ▒
 │ install it directly to your MBR (Master Boot Record). ▒
 │ ▒
 │ In either case, whenever you want GRUB 2 to be loaded directly from MBR, ▒
 │ you can do so by issuing (as root) the following command: ▒
 │ ▮
 │ upgrade-from-grub-legacy. This is were it all began to go down hill. So basically if those 2 commands don't work there is no other option from here just pass it on to the grub2 developers. Thanks for your participation and hopefully I can get this resolved soon.

[robert (raweinstein)]

Whe I try to run update manager i get this message: Unable to get exclusive lock

This usually means that another package management application (like apt-get or aptitude) is already running. Please close that application first. I opened my menu.lst and I don't see where I can accept chainloading grub2.

[Rolf Leggewie (r0lf)]

Not sure what's going on here, grub is obviously in some kind of loop it cannot get out of. Did this ever occur in lucid or later?

[Rolf Leggewie (r0lf)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!