Package linux-image-4.4.0-65-generic needs to be reinstalled
I've a very strange problem.
Yesterday everything was fine, today I've launched Ubuntu and I've got this message:
package linux-image-4.4.0-65-generic needs to be reinstalled, but I can't find an archive for it
I've searched for some solution online but I haven't found anything.
package-management archive
edited Mar 5 '17 at 17:24
Zanna
50.5k13133241
asked Mar 3 '17 at 11:55
JackJack
9318
|
show 1 more comment
I've a very strange problem.
Yesterday everything was fine, today I've launched Ubuntu and I've got this message:
package linux-image-4.4.0-65-generic needs to be reinstalled, but I can't find an archive for it
I've searched for some solution online but I haven't found anything.
package-management archive
edited Mar 5 '17 at 17:24
Zanna
50.5k13133241
asked Mar 3 '17 at 11:55
JackJack
9318
Have you triedsudo apt install linux-image-4.4.0-65-generic? The "no archive" would DS like it means it's just not in your cache.
– Nonny Moose
Mar 3 '17 at 13:06
An update was offered yesterday for linux-generic for a brief time which included this kernel, but then it seems to have been pulled. One of my xenial systems got this update, the other didn't. You may have gotten caught in the transition. You shpuld probably fall back to -64. I'm not decided what to do on my one system that got this now-orphaned update.
– Organic Marble
Mar 3 '17 at 13:20
@NonnyMoose thanks for the help but it didn't work. Anyway I've found a solution by myself.
– Jack
Mar 3 '17 at 13:35
1
@ Organic Marble thanks! With your suggestion I managed to find a solution!
– Jack
Mar 3 '17 at 13:36
Just download and re install the kernel using dpkg -i and you should be fine. ubuntuupdates.org/package/canonical_kernel_team/xenial/main/…
– Tomas
Mar 14 '17 at 15:01
|
show 1 more comment
I've a very strange problem.
Yesterday everything was fine, today I've launched Ubuntu and I've got this message:
package linux-image-4.4.0-65-generic needs to be reinstalled, but I can't find an archive for it
I've searched for some solution online but I haven't found anything.
package-management archive
edited Mar 5 '17 at 17:24
Zanna
50.5k13133241
asked Mar 3 '17 at 11:55
JackJack
9318
I've a very strange problem.
Yesterday everything was fine, today I've launched Ubuntu and I've got this message:
package linux-image-4.4.0-65-generic needs to be reinstalled, but I can't find an archive for it
I've searched for some solution online but I haven't found anything.
package-management archive
package-management archive
edited Mar 5 '17 at 17:24
Zanna
50.5k13133241
asked Mar 3 '17 at 11:55
JackJack
9318
edited Mar 5 '17 at 17:24
Zanna
50.5k13133241
asked Mar 3 '17 at 11:55
JackJack
9318
edited Mar 5 '17 at 17:24
Zanna
50.5k13133241
edited Mar 5 '17 at 17:24
Zanna
50.5k13133241
edited Mar 5 '17 at 17:24
Zanna
50.5k13133241
50.5k13133241
asked Mar 3 '17 at 11:55
JackJack
9318
asked Mar 3 '17 at 11:55
JackJack
9318
asked Mar 3 '17 at 11:55
JackJack
9318
9318
Have you triedsudo apt install linux-image-4.4.0-65-generic? The "no archive" would DS like it means it's just not in your cache.
– Nonny Moose
Mar 3 '17 at 13:06
An update was offered yesterday for linux-generic for a brief time which included this kernel, but then it seems to have been pulled. One of my xenial systems got this update, the other didn't. You may have gotten caught in the transition. You shpuld probably fall back to -64. I'm not decided what to do on my one system that got this now-orphaned update.
– Organic Marble
Mar 3 '17 at 13:20
@NonnyMoose thanks for the help but it didn't work. Anyway I've found a solution by myself.
– Jack
Mar 3 '17 at 13:35
1
@ Organic Marble thanks! With your suggestion I managed to find a solution!
– Jack
Mar 3 '17 at 13:36
Just download and re install the kernel using dpkg -i and you should be fine. ubuntuupdates.org/package/canonical_kernel_team/xenial/main/…
– Tomas
Mar 14 '17 at 15:01
|
show 1 more comment
Have you triedsudo apt install linux-image-4.4.0-65-generic? The "no archive" would DS like it means it's just not in your cache.
– Nonny Moose
Mar 3 '17 at 13:06
An update was offered yesterday for linux-generic for a brief time which included this kernel, but then it seems to have been pulled. One of my xenial systems got this update, the other didn't. You may have gotten caught in the transition. You shpuld probably fall back to -64. I'm not decided what to do on my one system that got this now-orphaned update.
– Organic Marble
Mar 3 '17 at 13:20
@NonnyMoose thanks for the help but it didn't work. Anyway I've found a solution by myself.
– Jack
Mar 3 '17 at 13:35
1
@ Organic Marble thanks! With your suggestion I managed to find a solution!
– Jack
Mar 3 '17 at 13:36
Just download and re install the kernel using dpkg -i and you should be fine. ubuntuupdates.org/package/canonical_kernel_team/xenial/main/…
– Tomas
Mar 14 '17 at 15:01
Have you tried
sudo apt install linux-image-4.4.0-65-generic? The "no archive" would DS like it means it's just not in your cache.– Nonny Moose
Mar 3 '17 at 13:06
Have you tried
sudo apt install linux-image-4.4.0-65-generic? The "no archive" would DS like it means it's just not in your cache.– Nonny Moose
Mar 3 '17 at 13:06
An update was offered yesterday for linux-generic for a brief time which included this kernel, but then it seems to have been pulled. One of my xenial systems got this update, the other didn't. You may have gotten caught in the transition. You shpuld probably fall back to -64. I'm not decided what to do on my one system that got this now-orphaned update.
– Organic Marble
Mar 3 '17 at 13:20
An update was offered yesterday for linux-generic for a brief time which included this kernel, but then it seems to have been pulled. One of my xenial systems got this update, the other didn't. You may have gotten caught in the transition. You shpuld probably fall back to -64. I'm not decided what to do on my one system that got this now-orphaned update.
– Organic Marble
Mar 3 '17 at 13:20
@NonnyMoose thanks for the help but it didn't work. Anyway I've found a solution by myself.
– Jack
Mar 3 '17 at 13:35
@NonnyMoose thanks for the help but it didn't work. Anyway I've found a solution by myself.
– Jack
Mar 3 '17 at 13:35
1
1
@ Organic Marble thanks! With your suggestion I managed to find a solution!
– Jack
Mar 3 '17 at 13:36
@ Organic Marble thanks! With your suggestion I managed to find a solution!
– Jack
Mar 3 '17 at 13:36
Just download and re install the kernel using dpkg -i and you should be fine. ubuntuupdates.org/package/canonical_kernel_team/xenial/main/…
– Tomas
Mar 14 '17 at 15:01
Just download and re install the kernel using dpkg -i and you should be fine. ubuntuupdates.org/package/canonical_kernel_team/xenial/main/…
– Tomas
Mar 14 '17 at 15:01
|
show 1 more comment
2 Answers
2
active
oldest
votes
I've found a solution:
I installed a new kernel.
Following this Ubuntu handbook guide I deleted old kernels versions
After that I discovered that the linux-image-4.4.0-65-generic was in a very bad inconsistent state.
So I removed it using this command: sudo dpkg --remove --force-remove-reinstreq <image-to-remove>.
Now it works :)
edited Mar 5 '17 at 17:25
Zanna
50.5k13133241
answered Mar 3 '17 at 13:33
JackJack
9318
add a comment |
I've also followed the tip to run the following command:
sudo dpkg --remove --force-remove-reinstreq <image-to-remove>.
However, my packages was so "corrupted" that when I ran this command I was followed by a list of dependencies that refused to remove the package. And with that upgrading the system was also a failure.
Finally I found out that I could edit /var/lib/dpkg/status and change the row of the damaged package:
Status: deinstall reinstreq half-installed
To
Status: install ok installed
With this changed, rerunning apt-get remove was suddenly successful.
A footnote of this is that in my case, it was linux-headers that needed to be reinstalled and linux-image-extra that was a dependency.
Also, after manipulating the file I've got a few warnings:
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 1950 package 'linux-headers-4.4.0-65-generic':
missing description
dpkg-query: warning: parsing file '/var/lib/dpkg/updates/0066' near line 7 package 'linux-headers-4.4.0-65-generic':
missing description
They however disappeared right after running apt-get autoremove/upgrade, so I suspect that this is not the best way of removing packages that is impossible to remove.
answered Jan 6 at 22:01
Tomas TornevallTomas Tornevall
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f889126%2fpackage-linux-image-4-4-0-65-generic-needs-to-be-reinstalled%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've found a solution:
I installed a new kernel.
Following this Ubuntu handbook guide I deleted old kernels versions
After that I discovered that the linux-image-4.4.0-65-generic was in a very bad inconsistent state.
So I removed it using this command: sudo dpkg --remove --force-remove-reinstreq <image-to-remove>.
Now it works :)
edited Mar 5 '17 at 17:25
Zanna
50.5k13133241
answered Mar 3 '17 at 13:33
JackJack
9318
add a comment |
I've found a solution:
I installed a new kernel.
Following this Ubuntu handbook guide I deleted old kernels versions
After that I discovered that the linux-image-4.4.0-65-generic was in a very bad inconsistent state.
So I removed it using this command: sudo dpkg --remove --force-remove-reinstreq <image-to-remove>.
Now it works :)
edited Mar 5 '17 at 17:25
Zanna
50.5k13133241
answered Mar 3 '17 at 13:33
JackJack
9318
add a comment |
I've found a solution:
I installed a new kernel.
Following this Ubuntu handbook guide I deleted old kernels versions
After that I discovered that the linux-image-4.4.0-65-generic was in a very bad inconsistent state.
So I removed it using this command: sudo dpkg --remove --force-remove-reinstreq <image-to-remove>.
Now it works :)
edited Mar 5 '17 at 17:25
Zanna
50.5k13133241
answered Mar 3 '17 at 13:33
JackJack
9318
I've found a solution:
I installed a new kernel.
Following this Ubuntu handbook guide I deleted old kernels versions
After that I discovered that the linux-image-4.4.0-65-generic was in a very bad inconsistent state.
So I removed it using this command: sudo dpkg --remove --force-remove-reinstreq <image-to-remove>.
Now it works :)
edited Mar 5 '17 at 17:25
Zanna
50.5k13133241
answered Mar 3 '17 at 13:33
JackJack
9318
edited Mar 5 '17 at 17:25
Zanna
50.5k13133241
edited Mar 5 '17 at 17:25
Zanna
50.5k13133241
edited Mar 5 '17 at 17:25
Zanna
50.5k13133241
50.5k13133241
answered Mar 3 '17 at 13:33
JackJack
9318
answered Mar 3 '17 at 13:33
JackJack
9318
answered Mar 3 '17 at 13:33
JackJack
9318
9318
add a comment |
add a comment |
I've also followed the tip to run the following command:
sudo dpkg --remove --force-remove-reinstreq <image-to-remove>.
However, my packages was so "corrupted" that when I ran this command I was followed by a list of dependencies that refused to remove the package. And with that upgrading the system was also a failure.
Finally I found out that I could edit /var/lib/dpkg/status and change the row of the damaged package:
Status: deinstall reinstreq half-installed
To
Status: install ok installed
With this changed, rerunning apt-get remove was suddenly successful.
A footnote of this is that in my case, it was linux-headers that needed to be reinstalled and linux-image-extra that was a dependency.
Also, after manipulating the file I've got a few warnings:
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 1950 package 'linux-headers-4.4.0-65-generic':
missing description
dpkg-query: warning: parsing file '/var/lib/dpkg/updates/0066' near line 7 package 'linux-headers-4.4.0-65-generic':
missing description
They however disappeared right after running apt-get autoremove/upgrade, so I suspect that this is not the best way of removing packages that is impossible to remove.
answered Jan 6 at 22:01
Tomas TornevallTomas Tornevall
1
add a comment |
I've also followed the tip to run the following command:
sudo dpkg --remove --force-remove-reinstreq <image-to-remove>.
However, my packages was so "corrupted" that when I ran this command I was followed by a list of dependencies that refused to remove the package. And with that upgrading the system was also a failure.
Finally I found out that I could edit /var/lib/dpkg/status and change the row of the damaged package:
Status: deinstall reinstreq half-installed
To
Status: install ok installed
With this changed, rerunning apt-get remove was suddenly successful.
A footnote of this is that in my case, it was linux-headers that needed to be reinstalled and linux-image-extra that was a dependency.
Also, after manipulating the file I've got a few warnings:
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 1950 package 'linux-headers-4.4.0-65-generic':
missing description
dpkg-query: warning: parsing file '/var/lib/dpkg/updates/0066' near line 7 package 'linux-headers-4.4.0-65-generic':
missing description
They however disappeared right after running apt-get autoremove/upgrade, so I suspect that this is not the best way of removing packages that is impossible to remove.
answered Jan 6 at 22:01
Tomas TornevallTomas Tornevall
1
add a comment |
I've also followed the tip to run the following command:
sudo dpkg --remove --force-remove-reinstreq <image-to-remove>.
However, my packages was so "corrupted" that when I ran this command I was followed by a list of dependencies that refused to remove the package. And with that upgrading the system was also a failure.
Finally I found out that I could edit /var/lib/dpkg/status and change the row of the damaged package:
Status: deinstall reinstreq half-installed
To
Status: install ok installed
With this changed, rerunning apt-get remove was suddenly successful.
A footnote of this is that in my case, it was linux-headers that needed to be reinstalled and linux-image-extra that was a dependency.
Also, after manipulating the file I've got a few warnings:
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 1950 package 'linux-headers-4.4.0-65-generic':
missing description
dpkg-query: warning: parsing file '/var/lib/dpkg/updates/0066' near line 7 package 'linux-headers-4.4.0-65-generic':
missing description
They however disappeared right after running apt-get autoremove/upgrade, so I suspect that this is not the best way of removing packages that is impossible to remove.
answered Jan 6 at 22:01
Tomas TornevallTomas Tornevall
1
I've also followed the tip to run the following command:
sudo dpkg --remove --force-remove-reinstreq <image-to-remove>.
However, my packages was so "corrupted" that when I ran this command I was followed by a list of dependencies that refused to remove the package. And with that upgrading the system was also a failure.
Finally I found out that I could edit /var/lib/dpkg/status and change the row of the damaged package:
Status: deinstall reinstreq half-installed
To
Status: install ok installed
With this changed, rerunning apt-get remove was suddenly successful.
A footnote of this is that in my case, it was linux-headers that needed to be reinstalled and linux-image-extra that was a dependency.
Also, after manipulating the file I've got a few warnings:
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 1950 package 'linux-headers-4.4.0-65-generic':
missing description
dpkg-query: warning: parsing file '/var/lib/dpkg/updates/0066' near line 7 package 'linux-headers-4.4.0-65-generic':
missing description
They however disappeared right after running apt-get autoremove/upgrade, so I suspect that this is not the best way of removing packages that is impossible to remove.
answered Jan 6 at 22:01
Tomas TornevallTomas Tornevall
1
answered Jan 6 at 22:01
Tomas TornevallTomas Tornevall
1
answered Jan 6 at 22:01
Tomas TornevallTomas Tornevall
1
answered Jan 6 at 22:01
Tomas TornevallTomas Tornevall
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f889126%2fpackage-linux-image-4-4-0-65-generic-needs-to-be-reinstalled%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you tried
sudo apt install linux-image-4.4.0-65-generic? The "no archive" would DS like it means it's just not in your cache.– Nonny Moose
Mar 3 '17 at 13:06
An update was offered yesterday for linux-generic for a brief time which included this kernel, but then it seems to have been pulled. One of my xenial systems got this update, the other didn't. You may have gotten caught in the transition. You shpuld probably fall back to -64. I'm not decided what to do on my one system that got this now-orphaned update.
– Organic Marble
Mar 3 '17 at 13:20
@NonnyMoose thanks for the help but it didn't work. Anyway I've found a solution by myself.
– Jack
Mar 3 '17 at 13:35
1
@ Organic Marble thanks! With your suggestion I managed to find a solution!
– Jack
Mar 3 '17 at 13:36
Just download and re install the kernel using dpkg -i and you should be fine. ubuntuupdates.org/package/canonical_kernel_team/xenial/main/…
– Tomas
Mar 14 '17 at 15:01