RE: Shutdown during kernel upgrade using aptitude
SOLVED:
ls -l /vmlinuz
lrwxrwxrwx 1 root root 23 Jan 7 15:33 /vmlinuz -> boot/vmlinuz-2.6.9-2-k7
Turns out that somehow /vmlinuz was not a link but a file
containing a specific version of vmlinuz. By deleting the
file, and putting in a link aptitude can now update the
kernel. Also, "can't find file /lib/modules/2.6.9-1-k7/modules.dep<br>at boot time" error message is now gone away.
--- On Sun 12/05, J F < j1234f@excite.com > wrote:
From: J F [mailto: j1234f@excite.com]
To: debian-user@lists.debian.org
Date: Sun, 5 Dec 2004 15:45:30 -0500
Subject: Shutdown during kernel upgrade using aptitude
I keep getting error message:<br>can't find file /lib/modules/2.6.9-1-k7/modules.dep<br>at boot time. I can see the file is there.<br>At botton is the list of things I have already done.<br><br>root:/lib/modules/2.6.9-1-k7# ls -l<br>total 836<br>drwxr-xr-x 2 root root 4096 Dec 2 22:16 boot<br>drwxr-xr-x 2 root root 4096 Dec 2 22:16 initrd<br>drwxr-xr-x 10 root root 4096 Dec 2 22:16 kernel<br>-rw-r--r-- 1 root root 141154 Dec 2 22:16 modules.alias<br>-rw-r--r-- 1 root root 69 Dec 2 22:16 modules.ccwmap<br>-rw-r--r-- 1 root root 236413 Dec 2 22:16 modules.dep<br>-rw-r--r-- 1 root root 517 Dec 2 22:16 modules.ieee1394map<br>-rw-r--r-- 1 root root 1141 Dec 2 22:16 modules.inputmap<br>-rw-r--r-- 1 root root 16427 Dec 2 22:16 modules.isapnpmap<br>-rw-r--r-- 1 root root 135507 Dec 2 22:16 modules.pcimap<br>-rw-r--r-- 1 root root 106450 Dec 2 22:16 modules.symbols<br>-rw-r--r-- 1 root root 156573 Dec 2 22:16 modules.usbmap<br>lrwxrwxrwx 1
root root 87 Dec 2 22:16 source -> /home/dilinger/src/kernel/kernel-image/2.6.9-3/kernel-image-2.6.9-i386-2.6.9/install-k7<br>root:/lib/modules/2.6.9-1-k7#<br><br>-----------------------------------------------------------------<br> --- On Wed 12/01, J F < j1234f@excite.com > wrote:<br>From: J F [mailto: j1234f@excite.com]<br>Date: Wed, 1 Dec 2004 18:49:34 -0500<br>Subject: Shutdown during system upgrade<br><br>Subject: <br>Shutdown during system upgrade<br><br><br> <br><br><br><br><br>My system shutdown during system upgrade using<br>aptitude. It was sitting there warning that<br>I should not shutdown while upgrading the kernel and<br>lilo might not work.<br><br>Anyway, here is how I fixed it:<br>1. Boot Knoppix<br>2. Click on hda3 to mount it. Close the file browser window<br>and right click on hda3, select properties and <br>uncheck the read only button.<br>3. su<br>4. cd /<br>5. remove the link from /boot to the cdrom and then:<br>6. ln -s /mnt/hda3/boot .<br>7. Knoppix
is in ramdisk, so cp /mnt/hda3/etc/lilo.conf /etc/lilo.conf<br>8. rm /vmlinuz; cd /<br>ln -s /boot/kernimagewhateververion vmlinuz<br>9. I had a problem with the kernel that was<br>installing, so I deleted it out of lilo.conf and<br>then typed:<br>lilo<br> <br>Reboot into debian<br>10. If you run aptitude and get the error like<br>can't lock cache, then:<br>dpkg --configure -a<br>11. lilo<br>Fatal: open /initrd.img: No such file or directory<br>12. # mkinitrd -o /initrd.img<br>13. lilo<br>and hopefully it will work now.<br><br>Just thought somebody might run into the same problem.<br><br><br><br>_______________________________________________<br>Join Excite! - http://www.excite.com<br>The most personalized portal on the Web!<br>
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
Reply to: