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












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
    20 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
    19 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
    20 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
    20 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
    19 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
    20 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
    19 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
    20 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
    19 hours ago



















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

    – roaima
    20 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
    19 hours ago

















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

– roaima
20 hours ago







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

– roaima
20 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
19 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
19 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
    20 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
    20 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
    20 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
    20 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
20 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
20 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

Færeyskur hestur Heimild | Tengill | Tilvísanir | LeiðsagnarvalRossið - síða um færeyska hrossið á færeyskuGott ár hjá færeyska hestinum

He _____ here since 1970 . Answer needed [closed]What does “since he was so high” mean?Meaning of “catch birds for”?How do I ensure “since” takes the meaning I want?“Who cares here” meaningWhat does “right round toward” mean?the time tense (had now been detected)What does the phrase “ring around the roses” mean here?Correct usage of “visited upon”Meaning of “foiled rail sabotage bid”It was the third time I had gone to Rome or It is the third time I had been to Rome

Slayer Innehåll Historia | Stil, komposition och lyrik | Bandets betydelse och framgångar | Sidoprojekt och samarbeten | Kontroverser | Medlemmar | Utmärkelser och nomineringar | Turnéer och festivaler | Diskografi | Referenser | Externa länkar | Navigeringsmenywww.slayer.net”Metal Massacre vol. 1””Metal Massacre vol. 3””Metal Massacre Volume III””Show No Mercy””Haunting the Chapel””Live Undead””Hell Awaits””Reign in Blood””Reign in Blood””Gold & Platinum – Reign in Blood””Golden Gods Awards Winners”originalet”Kerrang! Hall Of Fame””Slayer Looks Back On 37-Year Career In New Video Series: Part Two””South of Heaven””Gold & Platinum – South of Heaven””Seasons in the Abyss””Gold & Platinum - Seasons in the Abyss””Divine Intervention””Divine Intervention - Release group by Slayer””Gold & Platinum - Divine Intervention””Live Intrusion””Undisputed Attitude””Abolish Government/Superficial Love””Release “Slatanic Slaughter: A Tribute to Slayer” by Various Artists””Diabolus in Musica””Soundtrack to the Apocalypse””God Hates Us All””Systematic - Relationships””War at the Warfield””Gold & Platinum - War at the Warfield””Soundtrack to the Apocalypse””Gold & Platinum - Still Reigning””Metallica, Slayer, Iron Mauden Among Winners At Metal Hammer Awards””Eternal Pyre””Eternal Pyre - Slayer release group””Eternal Pyre””Metal Storm Awards 2006””Kerrang! Hall Of Fame””Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Bullet-For My Valentine booed at Metal Hammer Golden Gods Awards””Unholy Aliance””The End Of Slayer?””Slayer: We Could Thrash Out Two More Albums If We're Fast Enough...””'The Unholy Alliance: Chapter III' UK Dates Added”originalet”Megadeth And Slayer To Co-Headline 'Canadian Carnage' Trek”originalet”World Painted Blood””Release “World Painted Blood” by Slayer””Metallica Heading To Cinemas””Slayer, Megadeth To Join Forces For 'European Carnage' Tour - Dec. 18, 2010”originalet”Slayer's Hanneman Contracts Acute Infection; Band To Bring In Guest Guitarist””Cannibal Corpse's Pat O'Brien Will Step In As Slayer's Guest Guitarist”originalet”Slayer’s Jeff Hanneman Dead at 49””Dave Lombardo Says He Made Only $67,000 In 2011 While Touring With Slayer””Slayer: We Do Not Agree With Dave Lombardo's Substance Or Timeline Of Events””Slayer Welcomes Drummer Paul Bostaph Back To The Fold””Slayer Hope to Unveil Never-Before-Heard Jeff Hanneman Material on Next Album””Slayer Debut New Song 'Implode' During Surprise Golden Gods Appearance””Release group Repentless by Slayer””Repentless - Slayer - Credits””Slayer””Metal Storm Awards 2015””Slayer - to release comic book "Repentless #1"””Slayer To Release 'Repentless' 6.66" Vinyl Box Set””BREAKING NEWS: Slayer Announce Farewell Tour””Slayer Recruit Lamb of God, Anthrax, Behemoth + Testament for Final Tour””Slayer lägger ner efter 37 år””Slayer Announces Second North American Leg Of 'Final' Tour””Final World Tour””Slayer Announces Final European Tour With Lamb of God, Anthrax And Obituary””Slayer To Tour Europe With Lamb of God, Anthrax And Obituary””Slayer To Play 'Last French Show Ever' At Next Year's Hellfst””Slayer's Final World Tour Will Extend Into 2019””Death Angel's Rob Cavestany On Slayer's 'Farewell' Tour: 'Some Of Us Could See This Coming'””Testament Has No Plans To Retire Anytime Soon, Says Chuck Billy””Anthrax's Scott Ian On Slayer's 'Farewell' Tour Plans: 'I Was Surprised And I Wasn't Surprised'””Slayer””Slayer's Morbid Schlock””Review/Rock; For Slayer, the Mania Is the Message””Slayer - Biography””Slayer - Reign In Blood”originalet”Dave Lombardo””An exclusive oral history of Slayer”originalet”Exclusive! Interview With Slayer Guitarist Jeff Hanneman”originalet”Thinking Out Loud: Slayer's Kerry King on hair metal, Satan and being polite””Slayer Lyrics””Slayer - Biography””Most influential artists for extreme metal music””Slayer - Reign in Blood””Slayer guitarist Jeff Hanneman dies aged 49””Slatanic Slaughter: A Tribute to Slayer””Gateway to Hell: A Tribute to Slayer””Covered In Blood””Slayer: The Origins of Thrash in San Francisco, CA.””Why They Rule - #6 Slayer”originalet”Guitar World's 100 Greatest Heavy Metal Guitarists Of All Time”originalet”The fans have spoken: Slayer comes out on top in readers' polls”originalet”Tribute to Jeff Hanneman (1964-2013)””Lamb Of God Frontman: We Sound Like A Slayer Rip-Off””BEHEMOTH Frontman Pays Tribute To SLAYER's JEFF HANNEMAN””Slayer, Hatebreed Doing Double Duty On This Year's Ozzfest””System of a Down””Lacuna Coil’s Andrea Ferro Talks Influences, Skateboarding, Band Origins + More””Slayer - Reign in Blood””Into The Lungs of Hell””Slayer rules - en utställning om fans””Slayer and Their Fans Slashed Through a No-Holds-Barred Night at Gas Monkey””Home””Slayer””Gold & Platinum - The Big 4 Live from Sofia, Bulgaria””Exclusive! Interview With Slayer Guitarist Kerry King””2008-02-23: Wiltern, Los Angeles, CA, USA””Slayer's Kerry King To Perform With Megadeth Tonight! - Oct. 21, 2010”originalet”Dave Lombardo - Biography”Slayer Case DismissedArkiveradUltimate Classic Rock: Slayer guitarist Jeff Hanneman dead at 49.”Slayer: "We could never do any thing like Some Kind Of Monster..."””Cannibal Corpse'S Pat O'Brien Will Step In As Slayer'S Guest Guitarist | The Official Slayer Site”originalet”Slayer Wins 'Best Metal' Grammy Award””Slayer Guitarist Jeff Hanneman Dies””Kerrang! Awards 2006 Blog: Kerrang! Hall Of Fame””Kerrang! Awards 2013: Kerrang! Legend”originalet”Metallica, Slayer, Iron Maien Among Winners At Metal Hammer Awards””Metal Hammer Golden Gods Awards””Bullet For My Valentine Booed At Metal Hammer Golden Gods Awards””Metal Storm Awards 2006””Metal Storm Awards 2015””Slayer's Concert History””Slayer - Relationships””Slayer - Releases”Slayers officiella webbplatsSlayer på MusicBrainzOfficiell webbplatsSlayerSlayerr1373445760000 0001 1540 47353068615-5086262726cb13906545x(data)6033143kn20030215029