You already have a NoLOADER configuration in /etc/grub.conf

confused_bof · 07-22-2008, 02:46 AM

I am experiencing the following when running apt-get ugrade on a MythBuntu (8.04 Hardy) box:

Quote:

After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up linux-image-2.6.24-19-generic (2.6.24-19.36) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.24-19-generic
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.24-19.34 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.24-19.34 was configured last, according to dpkg)
Running postinst hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.24-19-generic
Found kernel: /boot/vmlinuz-2.6.24-18-generic
Found kernel: /boot/vmlinuz-2.6.24-12-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

You already have a NoLOADER configuration in /etc/grub.conf
Running boot loader as requested
Running /usr/sbin/grub ...
Boot loader failed to run
dpkg: error processing linux-image-2.6.24-19-generic (--configure):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
linux-image-2.6.24-19-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have tried

sudo apt-get clean
sudo apt-get autoremove
sudo apt-get update
sudo apt-get dist-upgrade

but it didn't help.

As best as I can figure the "Linux-image-2.6.24-19-nn" isn't being updated.

As I have pretty much exhausted google and other forums to try and sort this out I am hoping someone here might have an idea about the cause and solution.

TIA

b0uncer · 07-23-2008, 12:49 PM

If it's simply something in /etc/grub.conf (funny; I think it should officially be /boot/grub/menu.lst, but whatever..), have you tried to take a backup copy of the file, then empty the original file and then run apt? Does it still fight back?

The backup copy is taken in case something goes wrong, when you can just put it back and "revert" the changes.

In terminal, use bash if you're not sure:

Code:

su -
cp /etc/grub.{conf,conf.bak}
echo "" > /etc/grub.conf
exit

And if you want the original file back,

Code:

su -
cp /etc/grub.{conf.bak,conf}
exit

That's just a guess, but try it out by all means.

confused_bof · 07-23-2008, 02:50 PM

Quote:

Originally Posted by b0uncer

In terminal, use bash if you're not sure:

Code:

su -
cp /etc/grub.{conf,conf.bak}
echo "" > /etc/grub.conf
exit

And if you want the original file back,

Code:

su -
cp /etc/grub.{conf.bak,conf}
exit

Thanks, but either emptying or even deleting /etc/grub.conf I get the same error. Oddly, I have a four other Ubuntu based PCs around me, yet none of them have a file called /etc/grub.conf

BTW, if I delete /etc/grub.conf it gets re-created. All lines in it are commented out, so it seems it doesn't even serve a purpose.

Maybe I need to rebuild the mythbuntu box?

Thanks

confused_bof · 09-12-2008, 05:42 PM

Quote:

Originally Posted by confused_bof

I am experiencing the following when running apt-get ugrade on a MythBuntu (8.04 Hardy) box:

For the benefit of anyone else who might be struck down by this,

Quote:

sudo rm /etc/grub.conf
sudo apt-get update
sudo apt-get install

should fix it