Dotaz: Chyba pri upgrade kernelu na verziu 2.6.32-3

[Patrik Uhrak]

Zdravim,

vcera sa mi stala nemila vec, pri upgrade kernelu na verziu 2.6.32-3 sa instalacia sekla pri polozke generating grub.cfg .  Skusal som si prejst aj postinst skript pre tento kernel a hladat, ci tam nie je nejaky preklep alebo nieco podobne. Ale / nie je to zas take velke prekvapenie  :)  / nic som tam nenasiel, tak som aspon odkomentoval riadok strict , co by malo pomoct pri zistovani chybu, co sa tyka samotneho skriptu. Tu je vypis :

root@debian:~# 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 packages have been kept back:
  libmagickcore2-extra{a} 
The following partially installed packages will be configured:
  linux-image-2.6.32-3-amd64 
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
Setting up linux-image-2.6.32-3-amd64 (2.6.32-9) ...
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 635.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 637.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 638.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 640.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 641.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 643.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 644.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 647.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 648.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 651.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 652.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 655.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 657.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 662.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 665.
Global symbol "$question" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 666.
Global symbol "$ramdisk_cmd" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 793.
Global symbol "$ramdisk_cmd" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 794.
Global symbol "$ramdisk_cmd" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 798.
Global symbol "$ramdisk_cmd" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 802.
Global symbol "$answer" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 941.
Global symbol "$answer" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 942.
Global symbol "$answer" requires explicit package name at /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 944.
Execution of /var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst aborted due to compilation errors.
dpkg: error processing linux-image-2.6.32-3-amd64 (--configure):
 subprocess installed post-installation script returned error exit status 9
Errors were encountered while processing:
 linux-image-2.6.32-3-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

Mozno, ze niekto vie co s tym alebo aspon nejake docasne riesenie. Zatial som system nerestartol, ale co som pozrel grub.cfg , tak ten kernel tam je zaznamenany a aj spravne vytvorene cesty a vsetko k tomu. Neviem, co mohlo sposobit tuto chybu, lebo som nezasahoval do systemu nijak vyrazne alebo do nicoho, co by mohlo toto sposobit. Predtym vsetko islo ok, aj posledny update kernelu pred tymto nestastnym.

 

Dakujem za kazdu pomoc .

 

p.s.: Je to debian squeeze .

 

p.s. 2: Som to aj reportol, no zatial ziadna odozva, tak dufam, ze to nie je len lokalne, aj ked by nemalo.  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574031

---

---

Odpovědi

[Patrik Uhrak]

Zdravim.

Takze sa mi to pred malou chvilou podarilo vyriesit. Postup bol naslednovny:

 

1. Kazdy balicek s kernelom ma svoje skripty pre instalaciu a odinstalaciu v /var/lib/dpkg/info/ a  tyka sa to skriptov *.{postinst,postrm,preinst,prerm}

Vsetky som ich premazal nasledovnym sposobom:

for i in /var/lib/dpkg/info/linux-image-*.{postinst,postrm,preinst,prerm}; do echo -e "#! /bin/bash\nexit 0" > "$i"; done

Cielom bolo, aby skripty koncili s exit statusom rovnym 0 .

 

2. Spustil som aptitude purge linux-image-2.6.32-3-amd64 ale hadzalo to este chyby. ( je uplne jedno, aky kernel som sa snazil odinstalovat, nainstalovat, cokolvek ) No a bol tam riadok nieco v zmysle o vykonani postrm hook script a v zatvorkach ( /usr/sbin/update-grub )

 

3.  Tak som zakomentoval obsah toho skriptu, vlastne len jeden riadok. Ono by stacilo kludne spravit aj to, co som spravil v bode 1 a netreba si tie subory ani otvarat a dopisovat exit 0 rucne.

 

4. Nasledne som konecne mohol odinstalovat vsetky kernele = vsetky neskonfigurovane kernele  a tiez grub.

 

5. Som bez kernelu a bootloader-u a dostavam o tom aj varovanie. :)

 

6. Nainstalovat grub a nasledne aj novy kernel.

 

7. Vsetko prebehlo ok a momentalne bezim uz na verzii 2.6.32-3 pre 64 bit

 

8. Bug kernelu to teda nie, kedze ten bezi. Co to sposobilo, netusim. Ale aspon som si to vyriesil.

 

p.s.: Neislo odinstalovat ani nainstalovat s uspechom ziadny kernel ani grub, nic, lebo sa snazili prv vyriesit stavajuce problemy.