Replies *below* :)
Adam Aube wrote:
Please don't top post (which is putting your reply above the original mesage) - it makes the thread harder to follow.
Simon Buchanan wrote:
Adam Aube wrote:
Simon Buchanan wrote:
Hi There, I have just completed install of debian testing on my new SMP server (xeon nocona processors) and went to install a new SMP-aware kernel and got this message:
dpkg: error processing /var/cache/apt/archives/kernel-image-2.6.8-9-em64t-p4-smp_2.6.8-5_i386.deb (--unpack): subprocess pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/kernel-image-2.6.8-9-em64t-p4-smp_2.6.8-5_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
Is this the entire output? Usually there are lines above 'dpkg: error processing' that show the actual error encountered.
I tryed the standard "kernel-image-2.6.8-1-686-smp" version and it installed correctly...
It might be a bug in this kernel package, but without the complete output, it's hard to be sure. Please post the entire output of apt-get.
Hi Adam... here is the output as requested:
mx1:/# apt-get install kernel-image-2.6.8-9-em64t-p4-smp
kernel-image-2.6.8-9-em64t-p4-smp is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. 1 not fully installed or removed.
It looks like you have a partially installed package on your system. I would suggest fixing this before proceeding (use 'apt-get install -f').
I tried this with no better results.. see below:
mx1:/boot# apt-get install -f
Reading Package Lists... Done
Building Dependency Tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up kernel-image-2.6.8-9-em64t-p4-smp (2.6.8-5) ...
cpio: (0x00000000): No such file or directory
cp: cannot stat `(0x00000000)': No such file or directory
run-parts: /usr/share/initrd-tools/scripts/e2fsprogs exited with return code 1
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.8-9-em64t-p4-smp (--configure):
subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
kernel-image-2.6.8-9-em64t-p4-smp
E: Sub-process /usr/bin/dpkg returned an error code (1)
Also, the system already has the kernel installed - use the '--reinstall' flag to apt-get to force a reinstall next time you try to install it.
Also tried the --reinstall option, where is the output:
mx1:/boot# apt-get install --reinstall kernel-image-2.6.8-9-em64t-p4-smp
Reading Package Lists... Done
Building Dependency Tree... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up kernel-image-2.6.8-9-em64t-p4-smp (2.6.8-5) ...
cpio: (0x00000000): No such file or directory
cp: cannot stat `(0x00000000)': No such file or directory
run-parts: /usr/share/initrd-tools/scripts/e2fsprogs exited with return code 1
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.8-9-em64t-p4-smp (--configure):
subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
kernel-image-2.6.8-9-em64t-p4-smp
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up kernel-image-2.6.8-9-em64t-p4-smp (2.6.8-5) ... cpio: (0x00000000): No such file or directory cp: cannot stat `(0x00000000)': No such file or directory run-parts: /usr/share/initrd-tools/scripts/e2fsprogs exited with return code 1 Failed to create initrd image. dpkg: error processing kernel-image-2.6.8-9-em64t-p4-smp (--configure): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: kernel-image-2.6.8-9-em64t-p4-smp E: Sub-process /usr/bin/dpkg returned an error code (1)
This is the error I was looking for, though I see it is different from your original error. For some reason the kernel is unable to create the initrd it needs. What kernel are you running right now - pre-built or custom?
Adam
-- This message was scanned for spam and viruses by BitDefender For more information please visit http://linux.bitdefender.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]