Can not upgrade Kali,not enough space in /var/cache/apt/archives2019 Community Moderator ElectionWhy is Kali...

What does the "3am" section means in manpages?

Should my PhD thesis be submitted under my legal name?

Can a Gentile theist be saved?

I'm in charge of equipment buying but no one's ever happy with what I choose. How to fix this?

My boss asked me to take a one-day class, then signs it up as a day off

Have I saved too much for retirement so far?

How to deal with or prevent idle in the test team?

Lightning Web Component - do I need to track changes for every single input field in a form

Would it be legal for a US State to ban exports of a natural resource?

Can the electrostatic force be infinite in magnitude?

Adding empty element to declared container without declaring type of element

Calculating the number of days between 2 dates in Excel

Why are all the doors on Ferenginar (the Ferengi home world) far shorter than the average Ferengi?

Did US corporations pay demonstrators in the German demonstrations against article 13?

Identify a stage play about a VR experience in which participants are encouraged to simulate performing horrific activities

Meta programming: Declare a new struct on the fly

Teaching indefinite integrals that require special-casing

Can I Retrieve Email Addresses from BCC?

Can I rely on these GitHub repository files?

Why isn't KTEX's runway designation 10/28 instead of 9/27?

Is a naturally all "male" species possible?

Is it okay / does it make sense for another player to join a running game of Munchkin?

Could solar power be utilized and substitute coal in the 19th century?

How can I successfully establish a nationwide combat training program for a large country?



Can not upgrade Kali,not enough space in /var/cache/apt/archives



2019 Community Moderator ElectionWhy is Kali Linux so hard to set up? Why won't people help me?Disk management issuedf says I have 20G more disk space used than du. Why?Moving /usr to its own filesystem/logical volumethe difference in used hard drive space as shown by df and du is HUGE!How to mount a filesystem from a given USB bus:deviceHow to mount sdb directly or using LVM partitions on sda?Ubuntu Server 16.04 filesystem usagedpkg: error processing archive /var/cache/apt/archives/dictionaries-common_1.27.7_all.deb (--unpack)apt-get upgrade won't work on kaliMerge mount pointsapt-get update stopped working












3















I installed Kali Linux on VM VirtualBox(my host is Ubuntu 18.04). I am newbee to Kali,but the two linked questions are not related to my problem.
When I try to upgrade Kali



apt upgrade

926 upgraded, 81 newly installed, 0 to remove and 4 not upgraded.
Need to get 1,503 MB of archives.
After this operation, 622 MB of additional disk space will be used.
E: You don't have enough free space in /var/cache/apt/archives/.
root@kali:~# df -H
Filesystem Size Used Avail Use% Mounted on
udev 4.2G 0 4.2G 0% /dev
tmpfs 837M 9.8M 827M 2% /run
/dev/mapper/kali--vg-root 12G 11G 250M 98% /
tmpfs 4.2G 14M 4.2G 1% /dev/shm
tmpfs 5.3M 0 5.3M 0% /run/lock
tmpfs 4.2G 0 4.2G 0% /sys/fs/cgroup
/dev/sda1 247M 63M 172M 27% /boot
tmpfs 837M 17k 837M 1% /run/user/130
tmpfs 837M 33k 837M 1% /run/user/0


How should I change my filesystem configuration?
udev is not used at all,why?



Output with nodes
df --o



Filesystem                Type      Inodes  IUsed   IFree IUse% 1K-blocks     Used   Avail Use% File Mounted on
udev devtmpfs 1015859 390 1015469 1% 4063436 0 4063436 0% - /dev
tmpfs tmpfs 1021292 744 1020548 1% 817036 10016 807020 2% - /run
/dev/mapper/kali--vg-root ext4 701760 395200 306560 57% 10985352 10165868 241744 98% - /
tmpfs tmpfs 1021292 45 1021247 1% 4085168 5340 4079828 1% - /dev/shm
tmpfs tmpfs 1021292 3 1021289 1% 5120 0 5120 0% - /run/lock
tmpfs tmpfs 1021292 17 1021275 1% 4085168 0 4085168 0% - /sys/fs/cgroup
/dev/sda1 ext2 62248 339 61909 1% 240972 60868 167663 27% - /boot
tmpfs tmpfs 1021292 24 1021268 1% 817032 16 817016 1% - /run/user/130
tmpfs tmpfs 1021292 32 1021260 1% 817032 32 817000 1% - /run/user/0


pvscan



root@kali:~# pvscan
PV /dev/sda5 VG kali-vg lvm2 [12.40 GiB / 20.00 MiB free]
Total: 1 [12.40 GiB] / in use: 1 [12.40 GiB] / in no VG: 0 [0 ]
root@kali:~# pvdisplay
--- Physical volume ---
PV Name /dev/sda5
VG Name kali-vg
PV Size 12.40 GiB / not usable 2.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 3175
Free PE 5
Allocated PE 3170
PV UUID R2DnVQ-PUE9-OHbq-2jkh-J5U6-UBik-yJdQGg


And it warns about disk usage
enter image description here










share|improve this question

























  • You're running LVM for your root filesystem so you may be able to extend it. Have you checked if there's any space in your PV? (pvs and then maybe lvextend).

    – roaima
    yesterday











  • Since it's Kali and you won't be using it as a primary OS you may be able to delete whatever has filled up your root partition. That would get you back several GB.

    – roaima
    yesterday











  • @roaima How to delete tmpfs?

    – MikiBelavista
    yesterday






  • 2





    This is, IMHO, not a duplicate of the "Why is Kali so hard" question. It's a fairly obvious case of not having allocated enough space for a disk in VirtualBox.

    – Kusalananda
    yesterday






  • 1





    There's no point deleting a tmpfs as it's memory-based. You need either to review the stuff you've created but not deleted or to increase the sieve available in Vbox for your root PV, and thence your root LV. It really would be worth drilling down into /usr to see what's eating all the disk space.

    – roaima
    yesterday


















3















I installed Kali Linux on VM VirtualBox(my host is Ubuntu 18.04). I am newbee to Kali,but the two linked questions are not related to my problem.
When I try to upgrade Kali



apt upgrade

926 upgraded, 81 newly installed, 0 to remove and 4 not upgraded.
Need to get 1,503 MB of archives.
After this operation, 622 MB of additional disk space will be used.
E: You don't have enough free space in /var/cache/apt/archives/.
root@kali:~# df -H
Filesystem Size Used Avail Use% Mounted on
udev 4.2G 0 4.2G 0% /dev
tmpfs 837M 9.8M 827M 2% /run
/dev/mapper/kali--vg-root 12G 11G 250M 98% /
tmpfs 4.2G 14M 4.2G 1% /dev/shm
tmpfs 5.3M 0 5.3M 0% /run/lock
tmpfs 4.2G 0 4.2G 0% /sys/fs/cgroup
/dev/sda1 247M 63M 172M 27% /boot
tmpfs 837M 17k 837M 1% /run/user/130
tmpfs 837M 33k 837M 1% /run/user/0


How should I change my filesystem configuration?
udev is not used at all,why?



Output with nodes
df --o



Filesystem                Type      Inodes  IUsed   IFree IUse% 1K-blocks     Used   Avail Use% File Mounted on
udev devtmpfs 1015859 390 1015469 1% 4063436 0 4063436 0% - /dev
tmpfs tmpfs 1021292 744 1020548 1% 817036 10016 807020 2% - /run
/dev/mapper/kali--vg-root ext4 701760 395200 306560 57% 10985352 10165868 241744 98% - /
tmpfs tmpfs 1021292 45 1021247 1% 4085168 5340 4079828 1% - /dev/shm
tmpfs tmpfs 1021292 3 1021289 1% 5120 0 5120 0% - /run/lock
tmpfs tmpfs 1021292 17 1021275 1% 4085168 0 4085168 0% - /sys/fs/cgroup
/dev/sda1 ext2 62248 339 61909 1% 240972 60868 167663 27% - /boot
tmpfs tmpfs 1021292 24 1021268 1% 817032 16 817016 1% - /run/user/130
tmpfs tmpfs 1021292 32 1021260 1% 817032 32 817000 1% - /run/user/0


pvscan



root@kali:~# pvscan
PV /dev/sda5 VG kali-vg lvm2 [12.40 GiB / 20.00 MiB free]
Total: 1 [12.40 GiB] / in use: 1 [12.40 GiB] / in no VG: 0 [0 ]
root@kali:~# pvdisplay
--- Physical volume ---
PV Name /dev/sda5
VG Name kali-vg
PV Size 12.40 GiB / not usable 2.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 3175
Free PE 5
Allocated PE 3170
PV UUID R2DnVQ-PUE9-OHbq-2jkh-J5U6-UBik-yJdQGg


And it warns about disk usage
enter image description here










share|improve this question

























  • You're running LVM for your root filesystem so you may be able to extend it. Have you checked if there's any space in your PV? (pvs and then maybe lvextend).

    – roaima
    yesterday











  • Since it's Kali and you won't be using it as a primary OS you may be able to delete whatever has filled up your root partition. That would get you back several GB.

    – roaima
    yesterday











  • @roaima How to delete tmpfs?

    – MikiBelavista
    yesterday






  • 2





    This is, IMHO, not a duplicate of the "Why is Kali so hard" question. It's a fairly obvious case of not having allocated enough space for a disk in VirtualBox.

    – Kusalananda
    yesterday






  • 1





    There's no point deleting a tmpfs as it's memory-based. You need either to review the stuff you've created but not deleted or to increase the sieve available in Vbox for your root PV, and thence your root LV. It really would be worth drilling down into /usr to see what's eating all the disk space.

    – roaima
    yesterday
















3












3








3








I installed Kali Linux on VM VirtualBox(my host is Ubuntu 18.04). I am newbee to Kali,but the two linked questions are not related to my problem.
When I try to upgrade Kali



apt upgrade

926 upgraded, 81 newly installed, 0 to remove and 4 not upgraded.
Need to get 1,503 MB of archives.
After this operation, 622 MB of additional disk space will be used.
E: You don't have enough free space in /var/cache/apt/archives/.
root@kali:~# df -H
Filesystem Size Used Avail Use% Mounted on
udev 4.2G 0 4.2G 0% /dev
tmpfs 837M 9.8M 827M 2% /run
/dev/mapper/kali--vg-root 12G 11G 250M 98% /
tmpfs 4.2G 14M 4.2G 1% /dev/shm
tmpfs 5.3M 0 5.3M 0% /run/lock
tmpfs 4.2G 0 4.2G 0% /sys/fs/cgroup
/dev/sda1 247M 63M 172M 27% /boot
tmpfs 837M 17k 837M 1% /run/user/130
tmpfs 837M 33k 837M 1% /run/user/0


How should I change my filesystem configuration?
udev is not used at all,why?



Output with nodes
df --o



Filesystem                Type      Inodes  IUsed   IFree IUse% 1K-blocks     Used   Avail Use% File Mounted on
udev devtmpfs 1015859 390 1015469 1% 4063436 0 4063436 0% - /dev
tmpfs tmpfs 1021292 744 1020548 1% 817036 10016 807020 2% - /run
/dev/mapper/kali--vg-root ext4 701760 395200 306560 57% 10985352 10165868 241744 98% - /
tmpfs tmpfs 1021292 45 1021247 1% 4085168 5340 4079828 1% - /dev/shm
tmpfs tmpfs 1021292 3 1021289 1% 5120 0 5120 0% - /run/lock
tmpfs tmpfs 1021292 17 1021275 1% 4085168 0 4085168 0% - /sys/fs/cgroup
/dev/sda1 ext2 62248 339 61909 1% 240972 60868 167663 27% - /boot
tmpfs tmpfs 1021292 24 1021268 1% 817032 16 817016 1% - /run/user/130
tmpfs tmpfs 1021292 32 1021260 1% 817032 32 817000 1% - /run/user/0


pvscan



root@kali:~# pvscan
PV /dev/sda5 VG kali-vg lvm2 [12.40 GiB / 20.00 MiB free]
Total: 1 [12.40 GiB] / in use: 1 [12.40 GiB] / in no VG: 0 [0 ]
root@kali:~# pvdisplay
--- Physical volume ---
PV Name /dev/sda5
VG Name kali-vg
PV Size 12.40 GiB / not usable 2.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 3175
Free PE 5
Allocated PE 3170
PV UUID R2DnVQ-PUE9-OHbq-2jkh-J5U6-UBik-yJdQGg


And it warns about disk usage
enter image description here










share|improve this question
















I installed Kali Linux on VM VirtualBox(my host is Ubuntu 18.04). I am newbee to Kali,but the two linked questions are not related to my problem.
When I try to upgrade Kali



apt upgrade

926 upgraded, 81 newly installed, 0 to remove and 4 not upgraded.
Need to get 1,503 MB of archives.
After this operation, 622 MB of additional disk space will be used.
E: You don't have enough free space in /var/cache/apt/archives/.
root@kali:~# df -H
Filesystem Size Used Avail Use% Mounted on
udev 4.2G 0 4.2G 0% /dev
tmpfs 837M 9.8M 827M 2% /run
/dev/mapper/kali--vg-root 12G 11G 250M 98% /
tmpfs 4.2G 14M 4.2G 1% /dev/shm
tmpfs 5.3M 0 5.3M 0% /run/lock
tmpfs 4.2G 0 4.2G 0% /sys/fs/cgroup
/dev/sda1 247M 63M 172M 27% /boot
tmpfs 837M 17k 837M 1% /run/user/130
tmpfs 837M 33k 837M 1% /run/user/0


How should I change my filesystem configuration?
udev is not used at all,why?



Output with nodes
df --o



Filesystem                Type      Inodes  IUsed   IFree IUse% 1K-blocks     Used   Avail Use% File Mounted on
udev devtmpfs 1015859 390 1015469 1% 4063436 0 4063436 0% - /dev
tmpfs tmpfs 1021292 744 1020548 1% 817036 10016 807020 2% - /run
/dev/mapper/kali--vg-root ext4 701760 395200 306560 57% 10985352 10165868 241744 98% - /
tmpfs tmpfs 1021292 45 1021247 1% 4085168 5340 4079828 1% - /dev/shm
tmpfs tmpfs 1021292 3 1021289 1% 5120 0 5120 0% - /run/lock
tmpfs tmpfs 1021292 17 1021275 1% 4085168 0 4085168 0% - /sys/fs/cgroup
/dev/sda1 ext2 62248 339 61909 1% 240972 60868 167663 27% - /boot
tmpfs tmpfs 1021292 24 1021268 1% 817032 16 817016 1% - /run/user/130
tmpfs tmpfs 1021292 32 1021260 1% 817032 32 817000 1% - /run/user/0


pvscan



root@kali:~# pvscan
PV /dev/sda5 VG kali-vg lvm2 [12.40 GiB / 20.00 MiB free]
Total: 1 [12.40 GiB] / in use: 1 [12.40 GiB] / in no VG: 0 [0 ]
root@kali:~# pvdisplay
--- Physical volume ---
PV Name /dev/sda5
VG Name kali-vg
PV Size 12.40 GiB / not usable 2.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 3175
Free PE 5
Allocated PE 3170
PV UUID R2DnVQ-PUE9-OHbq-2jkh-J5U6-UBik-yJdQGg


And it warns about disk usage
enter image description here







filesystems kali-linux disk-usage






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited yesterday









Jeff Schaller

43.9k1161141




43.9k1161141










asked yesterday









MikiBelavistaMikiBelavista

3862719




3862719













  • You're running LVM for your root filesystem so you may be able to extend it. Have you checked if there's any space in your PV? (pvs and then maybe lvextend).

    – roaima
    yesterday











  • Since it's Kali and you won't be using it as a primary OS you may be able to delete whatever has filled up your root partition. That would get you back several GB.

    – roaima
    yesterday











  • @roaima How to delete tmpfs?

    – MikiBelavista
    yesterday






  • 2





    This is, IMHO, not a duplicate of the "Why is Kali so hard" question. It's a fairly obvious case of not having allocated enough space for a disk in VirtualBox.

    – Kusalananda
    yesterday






  • 1





    There's no point deleting a tmpfs as it's memory-based. You need either to review the stuff you've created but not deleted or to increase the sieve available in Vbox for your root PV, and thence your root LV. It really would be worth drilling down into /usr to see what's eating all the disk space.

    – roaima
    yesterday





















  • You're running LVM for your root filesystem so you may be able to extend it. Have you checked if there's any space in your PV? (pvs and then maybe lvextend).

    – roaima
    yesterday











  • Since it's Kali and you won't be using it as a primary OS you may be able to delete whatever has filled up your root partition. That would get you back several GB.

    – roaima
    yesterday











  • @roaima How to delete tmpfs?

    – MikiBelavista
    yesterday






  • 2





    This is, IMHO, not a duplicate of the "Why is Kali so hard" question. It's a fairly obvious case of not having allocated enough space for a disk in VirtualBox.

    – Kusalananda
    yesterday






  • 1





    There's no point deleting a tmpfs as it's memory-based. You need either to review the stuff you've created but not deleted or to increase the sieve available in Vbox for your root PV, and thence your root LV. It really would be worth drilling down into /usr to see what's eating all the disk space.

    – roaima
    yesterday



















You're running LVM for your root filesystem so you may be able to extend it. Have you checked if there's any space in your PV? (pvs and then maybe lvextend).

– roaima
yesterday





You're running LVM for your root filesystem so you may be able to extend it. Have you checked if there's any space in your PV? (pvs and then maybe lvextend).

– roaima
yesterday













Since it's Kali and you won't be using it as a primary OS you may be able to delete whatever has filled up your root partition. That would get you back several GB.

– roaima
yesterday





Since it's Kali and you won't be using it as a primary OS you may be able to delete whatever has filled up your root partition. That would get you back several GB.

– roaima
yesterday













@roaima How to delete tmpfs?

– MikiBelavista
yesterday





@roaima How to delete tmpfs?

– MikiBelavista
yesterday




2




2





This is, IMHO, not a duplicate of the "Why is Kali so hard" question. It's a fairly obvious case of not having allocated enough space for a disk in VirtualBox.

– Kusalananda
yesterday





This is, IMHO, not a duplicate of the "Why is Kali so hard" question. It's a fairly obvious case of not having allocated enough space for a disk in VirtualBox.

– Kusalananda
yesterday




1




1





There's no point deleting a tmpfs as it's memory-based. You need either to review the stuff you've created but not deleted or to increase the sieve available in Vbox for your root PV, and thence your root LV. It really would be worth drilling down into /usr to see what's eating all the disk space.

– roaima
yesterday







There's no point deleting a tmpfs as it's memory-based. You need either to review the stuff you've created but not deleted or to increase the sieve available in Vbox for your root PV, and thence your root LV. It really would be worth drilling down into /usr to see what's eating all the disk space.

– roaima
yesterday












2 Answers
2






active

oldest

votes


















4














As you surmised, the issue is simply that you don't have enough space in your VirtualBox instance.



This line says it all:



/dev/mapper/kali--vg-root   12G   11G  250M  98% /


So you only have 250 MB of vacant space. And as apt is helpfully telling you:




After this operation, 622 MB of additional disk space will be used.




The solution is simple. Just extend the Logical Volume (LV) that your Virtualbox instance is living on. lvextend should do it. man lvextend should give you sufficient information. Ask on the site or in chat if you need more help.






share|improve this answer
























  • pvs shows there is nothing free and available to extend within the existing space

    – roaima
    17 hours ago













  • @roaima Yes, we covered that in chat. He's not allocated space to the VB instance properly. He has plenty of space available in the host, though he isn't using LVM there.

    – Faheem Mitha
    17 hours ago



















4














Backup the virual machine ( clone it) then resize the virtual hard drive:



To incrase the kali.vdi from ~10 G to ~20 G use the following command (from Ubuntu):



VBoxManage modifyhd /Path/to/kali.vdi --resize 20000


Then download Gparted or use a linux live USB.



From Virtualbox, navigate to Setting > Storage > Controller IDE , then attach the gparted.iso



Configure the Virtual-Machine to boot from the optical drive (under Settings > System > Motherboard)



The virtual machine will boot into Gparted, you will be able to resize the virtual hard drive (10 ~> 20 G), apply changes , exit (shutdown)



Remove the attached gpartd.iso from the Controller IDE, then boot your virtual machine.






share|improve this answer



















  • 1





    Why do you suggest all the juggling with a live iso? IMHO all that's needed is to run fdisk /dev/sda (or any other partitioning tool) from Kali, enlarge sda5 (delete & recreate with the same start sector), reboot and pvextend. Or if OP is not brave enough to play with sda5, create a new partition, pvcreate and vgextend.

    – TooTea
    yesterday













  • It's a virtual machine with root on an LV. Extend the allocated disk. Extend the PV. Extend the LV. At most only the first operation requires the VM to be shut down, and possibly not even that.

    – roaima
    17 hours ago













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f508276%2fcan-not-upgrade-kali-not-enough-space-in-var-cache-apt-archives%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









4














As you surmised, the issue is simply that you don't have enough space in your VirtualBox instance.



This line says it all:



/dev/mapper/kali--vg-root   12G   11G  250M  98% /


So you only have 250 MB of vacant space. And as apt is helpfully telling you:




After this operation, 622 MB of additional disk space will be used.




The solution is simple. Just extend the Logical Volume (LV) that your Virtualbox instance is living on. lvextend should do it. man lvextend should give you sufficient information. Ask on the site or in chat if you need more help.






share|improve this answer
























  • pvs shows there is nothing free and available to extend within the existing space

    – roaima
    17 hours ago













  • @roaima Yes, we covered that in chat. He's not allocated space to the VB instance properly. He has plenty of space available in the host, though he isn't using LVM there.

    – Faheem Mitha
    17 hours ago
















4














As you surmised, the issue is simply that you don't have enough space in your VirtualBox instance.



This line says it all:



/dev/mapper/kali--vg-root   12G   11G  250M  98% /


So you only have 250 MB of vacant space. And as apt is helpfully telling you:




After this operation, 622 MB of additional disk space will be used.




The solution is simple. Just extend the Logical Volume (LV) that your Virtualbox instance is living on. lvextend should do it. man lvextend should give you sufficient information. Ask on the site or in chat if you need more help.






share|improve this answer
























  • pvs shows there is nothing free and available to extend within the existing space

    – roaima
    17 hours ago













  • @roaima Yes, we covered that in chat. He's not allocated space to the VB instance properly. He has plenty of space available in the host, though he isn't using LVM there.

    – Faheem Mitha
    17 hours ago














4












4








4







As you surmised, the issue is simply that you don't have enough space in your VirtualBox instance.



This line says it all:



/dev/mapper/kali--vg-root   12G   11G  250M  98% /


So you only have 250 MB of vacant space. And as apt is helpfully telling you:




After this operation, 622 MB of additional disk space will be used.




The solution is simple. Just extend the Logical Volume (LV) that your Virtualbox instance is living on. lvextend should do it. man lvextend should give you sufficient information. Ask on the site or in chat if you need more help.






share|improve this answer













As you surmised, the issue is simply that you don't have enough space in your VirtualBox instance.



This line says it all:



/dev/mapper/kali--vg-root   12G   11G  250M  98% /


So you only have 250 MB of vacant space. And as apt is helpfully telling you:




After this operation, 622 MB of additional disk space will be used.




The solution is simple. Just extend the Logical Volume (LV) that your Virtualbox instance is living on. lvextend should do it. man lvextend should give you sufficient information. Ask on the site or in chat if you need more help.







share|improve this answer












share|improve this answer



share|improve this answer










answered yesterday









Faheem MithaFaheem Mitha

23.2k1884137




23.2k1884137













  • pvs shows there is nothing free and available to extend within the existing space

    – roaima
    17 hours ago













  • @roaima Yes, we covered that in chat. He's not allocated space to the VB instance properly. He has plenty of space available in the host, though he isn't using LVM there.

    – Faheem Mitha
    17 hours ago



















  • pvs shows there is nothing free and available to extend within the existing space

    – roaima
    17 hours ago













  • @roaima Yes, we covered that in chat. He's not allocated space to the VB instance properly. He has plenty of space available in the host, though he isn't using LVM there.

    – Faheem Mitha
    17 hours ago

















pvs shows there is nothing free and available to extend within the existing space

– roaima
17 hours ago







pvs shows there is nothing free and available to extend within the existing space

– roaima
17 hours ago















@roaima Yes, we covered that in chat. He's not allocated space to the VB instance properly. He has plenty of space available in the host, though he isn't using LVM there.

– Faheem Mitha
17 hours ago





@roaima Yes, we covered that in chat. He's not allocated space to the VB instance properly. He has plenty of space available in the host, though he isn't using LVM there.

– Faheem Mitha
17 hours ago













4














Backup the virual machine ( clone it) then resize the virtual hard drive:



To incrase the kali.vdi from ~10 G to ~20 G use the following command (from Ubuntu):



VBoxManage modifyhd /Path/to/kali.vdi --resize 20000


Then download Gparted or use a linux live USB.



From Virtualbox, navigate to Setting > Storage > Controller IDE , then attach the gparted.iso



Configure the Virtual-Machine to boot from the optical drive (under Settings > System > Motherboard)



The virtual machine will boot into Gparted, you will be able to resize the virtual hard drive (10 ~> 20 G), apply changes , exit (shutdown)



Remove the attached gpartd.iso from the Controller IDE, then boot your virtual machine.






share|improve this answer



















  • 1





    Why do you suggest all the juggling with a live iso? IMHO all that's needed is to run fdisk /dev/sda (or any other partitioning tool) from Kali, enlarge sda5 (delete & recreate with the same start sector), reboot and pvextend. Or if OP is not brave enough to play with sda5, create a new partition, pvcreate and vgextend.

    – TooTea
    yesterday













  • It's a virtual machine with root on an LV. Extend the allocated disk. Extend the PV. Extend the LV. At most only the first operation requires the VM to be shut down, and possibly not even that.

    – roaima
    17 hours ago


















4














Backup the virual machine ( clone it) then resize the virtual hard drive:



To incrase the kali.vdi from ~10 G to ~20 G use the following command (from Ubuntu):



VBoxManage modifyhd /Path/to/kali.vdi --resize 20000


Then download Gparted or use a linux live USB.



From Virtualbox, navigate to Setting > Storage > Controller IDE , then attach the gparted.iso



Configure the Virtual-Machine to boot from the optical drive (under Settings > System > Motherboard)



The virtual machine will boot into Gparted, you will be able to resize the virtual hard drive (10 ~> 20 G), apply changes , exit (shutdown)



Remove the attached gpartd.iso from the Controller IDE, then boot your virtual machine.






share|improve this answer



















  • 1





    Why do you suggest all the juggling with a live iso? IMHO all that's needed is to run fdisk /dev/sda (or any other partitioning tool) from Kali, enlarge sda5 (delete & recreate with the same start sector), reboot and pvextend. Or if OP is not brave enough to play with sda5, create a new partition, pvcreate and vgextend.

    – TooTea
    yesterday













  • It's a virtual machine with root on an LV. Extend the allocated disk. Extend the PV. Extend the LV. At most only the first operation requires the VM to be shut down, and possibly not even that.

    – roaima
    17 hours ago
















4












4








4







Backup the virual machine ( clone it) then resize the virtual hard drive:



To incrase the kali.vdi from ~10 G to ~20 G use the following command (from Ubuntu):



VBoxManage modifyhd /Path/to/kali.vdi --resize 20000


Then download Gparted or use a linux live USB.



From Virtualbox, navigate to Setting > Storage > Controller IDE , then attach the gparted.iso



Configure the Virtual-Machine to boot from the optical drive (under Settings > System > Motherboard)



The virtual machine will boot into Gparted, you will be able to resize the virtual hard drive (10 ~> 20 G), apply changes , exit (shutdown)



Remove the attached gpartd.iso from the Controller IDE, then boot your virtual machine.






share|improve this answer













Backup the virual machine ( clone it) then resize the virtual hard drive:



To incrase the kali.vdi from ~10 G to ~20 G use the following command (from Ubuntu):



VBoxManage modifyhd /Path/to/kali.vdi --resize 20000


Then download Gparted or use a linux live USB.



From Virtualbox, navigate to Setting > Storage > Controller IDE , then attach the gparted.iso



Configure the Virtual-Machine to boot from the optical drive (under Settings > System > Motherboard)



The virtual machine will boot into Gparted, you will be able to resize the virtual hard drive (10 ~> 20 G), apply changes , exit (shutdown)



Remove the attached gpartd.iso from the Controller IDE, then boot your virtual machine.







share|improve this answer












share|improve this answer



share|improve this answer










answered yesterday









GAD3RGAD3R

27.4k1858114




27.4k1858114








  • 1





    Why do you suggest all the juggling with a live iso? IMHO all that's needed is to run fdisk /dev/sda (or any other partitioning tool) from Kali, enlarge sda5 (delete & recreate with the same start sector), reboot and pvextend. Or if OP is not brave enough to play with sda5, create a new partition, pvcreate and vgextend.

    – TooTea
    yesterday













  • It's a virtual machine with root on an LV. Extend the allocated disk. Extend the PV. Extend the LV. At most only the first operation requires the VM to be shut down, and possibly not even that.

    – roaima
    17 hours ago
















  • 1





    Why do you suggest all the juggling with a live iso? IMHO all that's needed is to run fdisk /dev/sda (or any other partitioning tool) from Kali, enlarge sda5 (delete & recreate with the same start sector), reboot and pvextend. Or if OP is not brave enough to play with sda5, create a new partition, pvcreate and vgextend.

    – TooTea
    yesterday













  • It's a virtual machine with root on an LV. Extend the allocated disk. Extend the PV. Extend the LV. At most only the first operation requires the VM to be shut down, and possibly not even that.

    – roaima
    17 hours ago










1




1





Why do you suggest all the juggling with a live iso? IMHO all that's needed is to run fdisk /dev/sda (or any other partitioning tool) from Kali, enlarge sda5 (delete & recreate with the same start sector), reboot and pvextend. Or if OP is not brave enough to play with sda5, create a new partition, pvcreate and vgextend.

– TooTea
yesterday







Why do you suggest all the juggling with a live iso? IMHO all that's needed is to run fdisk /dev/sda (or any other partitioning tool) from Kali, enlarge sda5 (delete & recreate with the same start sector), reboot and pvextend. Or if OP is not brave enough to play with sda5, create a new partition, pvcreate and vgextend.

– TooTea
yesterday















It's a virtual machine with root on an LV. Extend the allocated disk. Extend the PV. Extend the LV. At most only the first operation requires the VM to be shut down, and possibly not even that.

– roaima
17 hours ago







It's a virtual machine with root on an LV. Extend the allocated disk. Extend the PV. Extend the LV. At most only the first operation requires the VM to be shut down, and possibly not even that.

– roaima
17 hours ago




















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f508276%2fcan-not-upgrade-kali-not-enough-space-in-var-cache-apt-archives%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Fairchild Swearingen Metro Inhaltsverzeichnis Geschichte | Innenausstattung | Nutzung | Zwischenfälle...

Pilgersdorf Inhaltsverzeichnis Geografie | Geschichte | Bevölkerungsentwicklung | Politik | Kultur...

Marineschifffahrtleitung Inhaltsverzeichnis Geschichte | Heutige Organisation der NATO | Nationale und...