Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Upgrade failure
Upgrade failure
Hi there, when I try to upgrade, I always get this message:
" E: /var/cache/apt/archives/linux-image-2.6.32-5-amd64_2.6.32-35_i386.deb: failed in write on buffer copy for backend dpkg-deb during `./lib/modules/2.6.32-5-amd64/kernel/drivers/net/s2io.ko' "
Any idea how to fix it?
" E: /var/cache/apt/archives/linux-image-2.6.32-5-amd64_2.6.32-35_i386.deb: failed in write on buffer copy for backend dpkg-deb during `./lib/modules/2.6.32-5-amd64/kernel/drivers/net/s2io.ko' "
Any idea how to fix it?
-
- Posts: 728
- Joined: 2011-06-04 20:06
- Location: Valencia, Spain
Re: Upgrade failure
To what you try to upgrade exactly, to Testing, Squeeze...?
Post your sources list maybe too.
Post your sources list maybe too.
Re: Upgrade failure
Sounds like the file /var/cache/apt/archives/linux-image-2.6.32-5-amd64_2.6.32-35_i386.deb is corrupted. Delete it an a new one will be downloaded.
Re: Upgrade failure
This the content of sources.list:
#
# deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 DVD Binary-1 20110205-17:27]/ squeeze contrib main
deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 DVD Binary-1 20110205-17:27]/ squeeze contrib main
deb http://ftp.de.debian.org/debian/ squeeze main contrib non-free
deb-src http://ftp.de.debian.org/debian/ squeeze main contrib non-free
deb http://security.debian.org/ squeeze/updates main contrib non-free
deb-src http://security.debian.org/ squeeze/updates main contrib non-free
deb http://ftp.de.debian.org/debian/ squeeze-updates main contrib
deb-src http://ftp.de.debian.org/debian/ squeeze-updates main contrib
deb http://backports.debian.org/debian-backports squeeze-backports main
deb http://www.debian-multimedia.org stable main non-free
deb http://ftp.de.debian.org/debian squeeze main non-free
deb http://mozilla.debian.net/ squeeze-backports iceweasel-release
~
~
~
~
~
"sources.list" [readonly] 26 lines, 915 characters
as well I deleted the file mentioned in the above post, but same problem shows up.
#
# deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 DVD Binary-1 20110205-17:27]/ squeeze contrib main
deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 DVD Binary-1 20110205-17:27]/ squeeze contrib main
deb http://ftp.de.debian.org/debian/ squeeze main contrib non-free
deb-src http://ftp.de.debian.org/debian/ squeeze main contrib non-free
deb http://security.debian.org/ squeeze/updates main contrib non-free
deb-src http://security.debian.org/ squeeze/updates main contrib non-free
deb http://ftp.de.debian.org/debian/ squeeze-updates main contrib
deb-src http://ftp.de.debian.org/debian/ squeeze-updates main contrib
deb http://backports.debian.org/debian-backports squeeze-backports main
deb http://www.debian-multimedia.org stable main non-free
deb http://ftp.de.debian.org/debian squeeze main non-free
deb http://mozilla.debian.net/ squeeze-backports iceweasel-release
~
~
~
~
~
"sources.list" [readonly] 26 lines, 915 characters
as well I deleted the file mentioned in the above post, but same problem shows up.
-
- Posts: 728
- Joined: 2011-06-04 20:06
- Location: Valencia, Spain
Re: Upgrade failure
Looks ok to me, but what is with the second CD line, I am not sure, if you have to comment it out.kujirasan wrote:This the content of sources.list:
#
# deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 DVD Binary-1 20110205-17:27]/ squeeze contrib main
deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 DVD Binary-1 20110205-17:27]/ squeeze contrib main
Re: Upgrade failure
The backports repository should not be enabled in your sources.list. You need to let only the default Debian repositories. And before the upgrade, you need to uninstall all third-part software.
Xubuntu 14.04
Usuário #517613
Usuário #517613
-
- Posts: 728
- Joined: 2011-06-04 20:06
- Location: Valencia, Spain
Re: Upgrade failure
I still not understand to what the OP is upgrading or is it just an update?
Of course, if this should be an upgrade to Wheezy, then of course, the backports has to be removed, all third party repos etc.
Of course, if this should be an upgrade to Wheezy, then of course, the backports has to be removed, all third party repos etc.
Re: Upgrade failure
I guess it's an upgrade from Lenny to Squeeze, telling by his sources.list.
Xubuntu 14.04
Usuário #517613
Usuário #517613
Re: Upgrade failure
Thanks for the replies!
There is no up grade from Lenny , it is fresh Squeeze installation ,
I get message to upgrade when I go on line, so proceed to upgrade, and the get the error message, that is it,
There is no up grade from Lenny , it is fresh Squeeze installation ,
I get message to upgrade when I go on line, so proceed to upgrade, and the get the error message, that is it,
Re: Upgrade failure
So what happens when you delete the file? Don't remove backports - it's most likely not the problem. linux-image-2.6.32-5 is part of squeeze.kevmitch wrote:Sounds like the file /var/cache/apt/archives/linux-image-2.6.32-5-amd64_2.6.32-35_i386.deb is corrupted. Delete it an a new one will be downloaded.
Re: Upgrade failure
Have you tryed to delete /lib/modules/2.6.32-5-amd64/kernel/drivers/net/s2io.ko ? (make a back up before you do it)
Xubuntu 14.04
Usuário #517613
Usuário #517613
-
- Posts: 728
- Joined: 2011-06-04 20:06
- Location: Valencia, Spain
Re: Upgrade failure
Then it is an update problem and not an upgrade problem.
You are trying just to update your Squeeze install if understand correctly. So, let the backports where there are and proceed with kevmitch's suggestion.
Post back the results.
You are trying just to update your Squeeze install if understand correctly. So, let the backports where there are and proceed with kevmitch's suggestion.
Post back the results.
Re: Upgrade failure
Hi Kev, I deleted the the file linux-image-2.6.32-5-amd64_2.6.32-35_i386.deb and nothing happened
As well I tried to install the the bigmem linux image and the whole thing is worse now, any idea how to remove a kernel, I know first to have list it , but I don't what is the command to list all kernels, uname -r, only lists the current one.
As well I tried to install the the bigmem linux image and the whole thing is worse now, any idea how to remove a kernel, I know first to have list it , but I don't what is the command to list all kernels, uname -r, only lists the current one.
Re: Upgrade failure
By "nothing happened", do you mean, you get the same error message? Trykujirasan wrote:Hi Kev, I deleted the the file linux-image-2.6.32-5-amd64_2.6.32-35_i386.deb and nothing happened
As well I tried to install the the bigmem linux image and the whole thing is worse now, any idea how to remove a kernel, I know first to have list it , but I don't what is the command to list all kernels, uname -r, only lists the current one.
a) extracting the package manually
Code: Select all
dpkg -x /var/cache/apt/archives/linux-image-2.6.32-5-amd64_2.6.32-35_i386.deb /tmp/linux-image-2.6.32-5-amd64_2.6.32-35_i386
Code: Select all
dpkg -i /var/cache/apt/archives/linux-image-2.6.32-5-amd64_2.6.32-35_i386.deb
Re: Upgrade failure
Thank Kev, I just let it stay as it is, already lost the use of printer, tampering with kernel is not a such a good idea
Re: Upgrade failure
Removing the .deb is not tampering with the kernel. It is removing a faulty package so that a non-corrupted one can be redownloaded. What I recommended is a harmless action (all the .debs in /var/cache/apt/archives/ can be safely deleted), otherwise I wouldn't have recommended doing it. Right now you have a half installed kernel and probably other packages that are half installed as well. There are good odds that other problems you are experiencing are related to this. "If it aint broke, don't fix it" does not apply because it most definitely is broke right now.kujirasan wrote:Thank Kev, I just let it stay as it is, already lost the use of printer, tampering with kernel is not a such a good idea