Re: dpkg: error processing linux-image-2.6.26-2-686 (--configure)
> On Sun, 27 Jun 2010 05:38:50 -0400 (EDT), Mizanur Khondoker wrote:
>> Stephen Powell wrote:
>>>
>>> Please provide the following information:
>>>
>>> (1) Which boot loader are you using? =C2=A0(Grub version 1? =C2=A0Grub v=
> ersion 2?
>>> =C2=A0lilo? =C2=A0extlinux?)
>>>
>>> (2) What is the contents of /etc/kernel-img.conf?
>>>
>>> (3) What are the names of the files in the following directories?
>>>
>>> =C2=A0 /etc/kernel/preinst.d
>>> =C2=A0 /etc/kernel/prerm.d
>>> =C2=A0 /etc/kernel/postinst.d
>>> =C2=A0 /etc/kernel/postrm.d
>>>
>>> (4) What is the output of the following commands?
>>>
>>> =C2=A0 ls -Al /boot/
>>> =C2=A0 ls -Al /
>>>
>>
>> Dear Stephen,
>>=20
>> Thanks for trying to help. Please find below the information you requeste=
> d.
>>=20
>> (1)
>> debian:/home/mizanur# grub-install -v
>> grub-install (GNU GRUB 0.97)
>>=20
>> (2)
>> debian:/home/mizanur# cat /etc/kernel-img.conf
>> # Kernel image management overrides
>> # See kernel-img.conf(5) for details
>> do_symlinks =3D yes
>> relative_links =3D yes
>> do_bootloader =3D no
>> do_bootfloppy =3D no
>> do_initrd =3D yes
>> link_in_boot =3D no
>> postinst_hook =3D update-grub
>> postrm_hook =3D update-grub
>>=20
>> (3)
>>=20
>> None of these directories seem to exist. In fact there is no kernel
>> directory under /etc/.
>>=20
>> debian:/home/mizanur# ls -l /etc/kernel/preinst.d
>> ls: cannot access /etc/kernel/preinst.d: No such file or directory
>>=20
>> debian:/home/mizanur# ls -l /etc/kernel/prerm.d
>> ls: cannot access /etc/kernel/prerm.d: No such file or directory
>>=20
>> debian:/home/mizanur# ls -l /etc/kernel/postinst.d
>> ls: cannot access /etc/kernel/postinst.d: No such file or directory
>>=20
>> debian:/home/mizanur# ls -l /etc/kernel/postrm.d
>> ls: cannot access /etc/kernel/postrm.d: No such file or directory
>>=20
>> (4)
>>=20
>> debian:/home/mizanur# ls -Al /boot/
>> total 16594
>> -rw-r--r-- 1 root root 91746 2010-06-21 11:42 config-2.6.26-2-686
>> drwxr-xr-x 2 root root 1024 2010-06-26 21:08 grub
>> -rw-r--r-- 1 root root 7197441 2010-06-26 21:16 initrd.img-2.6.26-2-686
>> -rw-r--r-- 1 root root 7190250 2009-04-13 10:45 initrd.img-2.6.26-2-686.b=
> ak
>> -rw-r--r-- 1 root root 928782 2010-06-21 11:42 System.map-2.6.26-2-686
>> -rw-r--r-- 1 root root 1507408 2010-06-21 11:42 vmlinuz-2.6.26-2-686
>>=20
>> debian:/home/mizanur# ls -Al /
>> total 75
>> drwxr-xr-x 2 root root 5120 2010-06-26 20:20 bin
>> drwxr-xr-x 3 root root 1024 2010-06-26 21:16 boot
>> lrwxrwxrwx 1 root root 11 2007-11-14 20:27 cdrom -> media/cdro=
> m
>> drwxr-xr-x 16 root root 3980 2010-06-27 10:04 dev
>> drwxr-xr-x 152 root root 9216 2010-06-27 10:06 etc
>> drwxr-xr-x 5 root root 4096 2010-06-26 08:32 home
>> drwxr-xr-x 2 root root 1024 2007-11-14 20:29 initrd
>> lrwxrwxrwx 1 root root 28 2009-05-10 12:05 initrd.img -> boot/=
> initrd.img-2.6.26-1-486
>> lrwxrwxrwx 1 root root 28 2009-04-13 10:45 initrd.img.old -> b=
> oot/initrd.img-2.6.26-2-686
>> drwxr-xr-x 16 root root 9216 2010-06-23 22:04 lib
>> drwx------ 2 root root 12288 2007-11-14 20:27 lost+found
>> drwxr-xr-x 4 root root 1024 2010-06-27 10:05 media
>> drwxr-xr-x 5 root root 1024 2009-08-01 23:42 mnt
>> drwxr-xr-x 2 root root 1024 2007-11-14 20:29 opt
>> dr-xr-xr-x 163 root root 0 2010-06-27 11:03 proc
>> -rw-r--r-- 1 mizanur mizanur 4400 2008-03-31 13:04 programmes
>> -rw------- 1 root root 1024 2007-11-14 20:55 .rnd
>> drwxr-xr-x 32 root root 1024 2010-06-24 21:43 root
>> drwxr-xr-x 2 root root 6144 2010-06-26 20:20 sbin
>> drwxr-xr-x 2 root root 1024 2007-03-07 22:56 selinux
>> drwxr-xr-x 2 root root 1024 2007-11-14 20:29 srv
>> drwxr-xr-x 11 root root 0 2010-06-27 11:03 sys
>> drwxrwxrwt 12 root root 8192 2010-06-27 10:18 tmp
>> drwxr-xr-x 14 root root 4096 2008-03-31 12:52 usr
>> drwxr-xr-x 16 root root 4096 2007-11-14 20:57 var
>> lrwxrwxrwx 1 root root 25 2009-05-10 12:05 vmlinuz -> boot/vml=
> inuz-2.6.26-1-486
>> lrwxrwxrwx 1 root root 25 2009-04-13 10:45 vmlinuz.old -> boot=
> /vmlinuz-2.6.26-2-686
>
> OK, I see what's wrong. You've got your symlinks messed up.
> I'm not sure how things got into that state, but they're all
> messed up. You could fix your symlinks, but since grub doesn't
> need them, here's what I would do if it were me. Do all this as root.
>
> rm /vmlinuz
> rm /initrd.img
> rm /vmlinuz.old
> rm /initrd.img.old
>
> Then edit the file /etc/kernel-img.conf and change
>
> do_symlinks =3D yes
>
> to
>
> do_symlinks =3D no
>
> File the change. Then issue
>
> dpkg-reconfigure linux-image-2.6.26-2-686
>
> That should put you back in business.
>
> --=20
> .''`. Stephen Powell =20
> : :' :
> `. `'`
> `-
Dear Stephen,
Deleting the symlinks solved the problem.
dpkg-reconfigure did not work, but aptitude safe-upgrade
reconfigured the kernel-image.
Thanks very much for your help.
==========
debian:/home/mizanur# dpkg-reconfigure linux-image-2.6.26-2-686
/usr/sbin/dpkg-reconfigure: linux-image-2.6.26-2-686 is broken or not
fully installed
debian:/home/mizanur# aptitude safe-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following partially installed packages will be configured:
linux-image-2.6.26-2-686
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Setting up linux-image-2.6.26-2-686 (2.6.26-24) ...
Running depmod.
Running mkinitramfs-kpkg.
Running postinst hook script 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 ... found: (hd0,3)/boot/grub/grub_face1.xpm.gz
Found kernel: /boot/vmlinuz-2.6.26-2-686
Updating /boot/grub/menu.lst ... done
--
Mizanur Khondoker
Reply to: