FYI While updating my QNAP ts-109 today I got the following: Preparing to replace linux-image-2.6.25-2-orion5x 2.6.25-6 (using .../linux-image-2.6.25-2-orion5x_2.6.25-7_armel.deb) ... [...] Setting up linux-image-2.6.25-2-orion5x (2.6.25-7) ... Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Not updating initrd symbolic links since we are being updated/reinstalled (2.6.25-6 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.25-6 was configured last, according to dpkg) Running postinst hook script flash-kernel. The RootFS1 doesn't fit in flash. User postinst hook script [flash-kernel] exited with value 1 dpkg: error processing linux-image-2.6.25-2-orion5x (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: linux-image-2.6.25-2-orion5x As I don't actually use that kernel I'm not really worried about the failure itself, but it means that new installs will probably also fail. Wonder what has changed between -6 and -7 that makes the initrd to big. -rw-r--r-- 1 root root 4271347 Jul 31 14:35 initrd.img-2.6.25-2-orion5x This is with 'MODULES=most' for initramfs-tools. Changing that to 'MODULES=dep' got rid of the error but I haven't checked if the resulting initrd is functional. -rw-r--r-- 1 root root 2728644 Jul 31 14:52 initrd.img-2.6.25-2-orion5x Cheers, FJP
Attachment:
signature.asc
Description: This is a digitally signed message part.