cannot copy extracted data for './boot/vmlinuz-3.16.0-34-generic' to '/boot/vmlinuz-3.16.0-34-generic.dpkg-new': unexpected end of file or stream

Bug #1465117 reported by dodobird
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
New
Undecided
Unassigned

Bug Description

while upgrading from kubuntu 14.04 to 14.10, I received the following error;

"cannot copy extracted data for './boot/vmlinuz-3.16.0-34-generic' to '/boot/vmlinuz-3.16.0-34-generic.dpkg-new': unexpected end of file or stream"

prior to this, I received an error message which I did not report at the time because I was busy/pressed for time. That error message said something to the effect of [cannot create ramfs...].

Prior to the errors mentioned above and before starting the upgrade, I noticed some unusual behaviour when I ran the muon software updater today; The muon software updater showed that there were no updates available before and after I instructed it to check for update. However, after saying there were no updates, the update notification appeared on the notification area at the bottom right side of the screen saying the a system update was available. After receiving that notification, I started the muon software updater once more and was informed by the updater there were still no updates available. I repeated that process 2-3 times and still kept being notified there was a system update available by the small blue icon at the bottom right side of the screen.

I believe that before all this happened, I'd performed as system restart after receiving a notification that one was necessary to complete/update my system.

before everything described above, I had installed a number (4-5 I believe) of software packages via the muon software package/app manager and received a message each time to the effect that the installation had completed "with errors". Checking the "details;" indicator revealed that there was some dependency problem with what I suspect was a kernel module of some kind. That error appeared with each new package I installed today.

Prior to all of this, I noticed nothing unusual about my system.

additional information; I've received the failed to [create/write to?] ramfs.. error message in the past with this current machine and found that the only solution was to re-install ubuntu from scratch. My best guess with respect to the cause is that the machine I'm using (a Dell GX270 Optiplex) is known to have issues with it's capacitors and this seems to have lead to possible RAM data corruption in the past.

I hope someone can find a fix because I really would prefer not to have to go through the entire reinstall & update process yet again.

I hope this report is helpful.

Regards;
Alain Paquette

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.