" E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. " then it say no space left on device, and when ever I try another thing, it return same problem
1
-
1Did you try deleting some unwanted packages to create some space, then?– jobinDec 6, 2013 at 4:03
Add a comment
|
2 Answers
Check your free disk space with df in a terminal or terminal emulator. If your disk Use% is full (above 90-95%) then you need to remove some packages or upgrade to a bigger hard drive.
-
it says:Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda8 18273204 16613040 743380 96% / udev 1801900 4 1801896 1% /dev tmpfs 723688 880 722808 1% /run none 5120 0 5120 0% /run/lock none 1809212 2264 1806948 1% /run/shm /dev/sda7 24489984 299520 24190464 2% /media/DISK2_VOL4 /dev/sda6 48817600 2248832 46568768 5% /media/DISK2_VOL3 /dev/sda5 39060480 4720864 34339616 13% /media/DISK2_VOL2 /dev/sda1 19535008 9247252 10287756 48% /medi Dec 6, 2013 at 4:18
-
this one, how to delete in there, /dev/sda8 18273204 16613040 743380 96% Dec 6, 2013 at 4:18
-
2I solved the trouble, it was cause the Inodes was on 100% used on the root. I deleted the old Linux kernels, this reduced it to 30% so now all work again. Dec 6, 2013 at 8:10
-
+1, nice work, df is the number one tool to get you headed in the right direction when you're having space issues! Glad to help. If my answer helped lead to your solution, please select it as the best answer with the checkmark next to it. Enjoy open source freedom my friend!– DeeJayhDec 7, 2013 at 18:17
-
2You can't remove packages if you need to run
dpkg --configure -afirst...– chefarovMay 11, 2018 at 10:53
I had a problem with the same initial symptoms, but the accepted answer did not work for me, as I can not (neatly) remove packages as long as the only thing the package manager does is to ask me to run sudo dpkg --configure -a even though running this any number of times did not change anything.
--pending instead of -a
For a reason unknown to me – according to the manpage, they should be equivalent – sudo dpkg --configure --pending, as recommended in this answer to dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. solved the problem for me.
-
2The OP's issue was clearly a lack of disk space, which could be solved by deleting any files (in the OP's case, old kernel files), not only by cleaning up unused, or pending, packages - which, again, in the OP's case, probably wouldn't have worked, due to the lack of disk space. Nov 9, 2021 at 14:10
-
@Greenonline And a specific solution that helps precisely the person who happened to ask the question first helps people having the same question for different underlying reasons how exactly? This is still a valid answer to the question posted, verbatim. My problem was also a lack of disk space so I definitely don't know why we need to shout that … Aug 20, 2022 at 8:26
-
No one is shouting... emphasising maybe, but not shouting. Nevertheless, if you think that, then why did you shout "
--pendinginstead of-a"? :-) Aug 20, 2022 at 9:58 -
Well, I'll disagree with your choice of bold+italics for emphasis then when italics would have been enough, but okay, it was not my intention to derail this into a typography discussion, mea culpa. And I marked up the heading as a heading because I'm of the opinion that it (a) is such semantically and (b) should be easily discernible for any reader skimming the answers. I still don't see how in your initial comment (paraphrased) “The OP had the same problem as you and yours is not the only answer that worked in that one case.” constitutes a helpful comment for me or anyone else. Aug 23, 2022 at 3:02