Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Discussions related to using VirtualBox on Linux hosts.
AnnNing
Posts: 10
Joined: 10. Aug 2021, 09:09

Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by AnnNing »

My Ubuntu server refused to start that really puzzled me.

I used it as a database server. This morning I wanted to run a test which needs a huge number of data, since the server only has 20G disk space, I decide to enlarge it. I used gparted software to help. I resized vdi settings first, which is success(I can see it through gparted interface) ,I resized the disk, so far so good, but when I click the apply button, everything went wrong.

VirtualBox suspended my server, when I try to restart, it suspended again.

Here is the log.

Code: Select all

000000.674219 Displayi_handleDisplayResize uScreenId=0 pvVRAM=00007ffbba4ec000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
000003.143389 PIT mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
000003.143779 VMMDev Guest Log BIOS Boot  bseqnr=1, bootseq=0023
000003.144445 VMMDev Guest Log BIOS CDROM boot failure code  0003
000003.144725 VMMDev Guest Log BIOS Boot from CD-ROM failed
000003.145072 VMMDev Guest Log BIOS Boot  bseqnr=2, bootseq=0002
000003.145244 Displayi_handleDisplayResize uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
000003.167977 VMMDev Guest Log BIOS Booting from Hard Disk...
000004.215226 Displayi_handleDisplayResize uScreenId=0 pvVRAM=00007ffbba4ec000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
000050.245246 Displayi_handleDisplayResize uScreenId=0 pvVRAM=00007ffbba4ec000 w=640 h=480 bpp=0 cbLine=0x280 flags=0x0 origin=0,0
000050.269650 Displayi_handleDisplayResize uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
000050.656952 GIM KVM VCPU  0 Enabled system-time struct. at 0x0000000213f53000 - u32TscScale=0x96f12b0c i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x13c3cc1d2b uVirtNanoTS=0xba758e9dd
000050.657096 TM Switching TSC mode from 'VirtTscEmulated' to 'RealTscOffset'
000050.887102 GIM KVM Enabled wall-clock struct. at 0x0000000213fd3000 - u32Sec=1628570605 u32Nano=575385491 uVersion=2
000050.950284 PIT mode=2 count=0x12a5 (4773) - 249.98 Hz (ch=0)
000050.951141 APIC0 Switched mode to x2APIC
000050.969055 IEM rdmsr(0x4e) - #GP(0)
000051.078098 PIT mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0)
000051.085222 APIC1 Switched mode to x2APIC
000051.085267 GIM KVM VCPU  1 Enabled system-time struct. at 0x0000000213f53040 - u32TscScale=0x96f12b0c i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x13c3cc1d2b uVirtNanoTS=0xba758e9dd
000051.085863 IEM rdmsr(0x4e) - #GP(0)
000051.089823 APIC2 Switched mode to x2APIC
000051.089855 GIM KVM VCPU  2 Enabled system-time struct. at 0x0000000213f53080 - u32TscScale=0x96f12b0c i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x13c3cc1d2b uVirtNanoTS=0xba758e9dd
000051.090474 IEM rdmsr(0x4e) - #GP(0)
000051.094336 APIC3 Switched mode to x2APIC
000051.094385 GIM KVM VCPU  3 Enabled system-time struct. at 0x0000000213f530c0 - u32TscScale=0x96f12b0c i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x13c3cc1d2b uVirtNanoTS=0xba758e9dd
000051.094909 IEM rdmsr(0x4e) - #GP(0)
000051.574216 OHCI Software reset
000053.023322 PIIX3 ATA Ctl#0 RESET, DevSel=0 AIOIf=0 CmdIf0=0x00 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
000053.023322 PIIX3 ATA Ctl#0 finished processing RESET
000053.027670 PIIX3 ATA Ctl#1 RESET, DevSel=0 AIOIf=0 CmdIf0=0xa0 (-1 usec ago) CmdIf1=0x00 (-1 usec ago)
000053.027772 PIIX3 ATA Ctl#1 finished processing RESET
000053.033812 EHCI Hardware reset
000053.034861 EHCI USB Operational
000053.059749 OHCI USB Reset
000053.181279 OHCI Software reset
000053.181568 OHCI USB Operational
000053.183023 EHCI USB Suspended
000053.854017 AHCI#0 Reset the HBA
000053.854056 VD#0 Cancelling all active requests
000053.858401 AHCI#0 Port 0 reset
000053.859655 VD#0 Cancelling all active requests
000053.895485 Displayi_handleDisplayResize uScreenId=0 pvVRAM=00007ffbba4ec000 w=800 h=600 bpp=32 cbLine=0xC80 flags=0x1 origin=0,0
000101.580001 AIOMgr Flush failed with VERR_INVALID_PARAMETER, disabling async flushes
000101.955115 IO cache Error while writing entry at offset 32615956480 (4096 bytes) to medium ahci-0-0 (rc=VERR_INVALID_PARAMETER)
000101.955221 VM Raising runtime error 'BLKCACHE_IOERR' (fFlags=0x6)
000101.955274 IO cache Error while writing entry at offset 32616243200 (688128 bytes) to medium ahci-0-0 (rc=VERR_INVALID_PARAMETER)
000101.955294 VD#0 Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.955355 AHCI#0P0 Write at offset 46038016000 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.955381 Changing the VM state from 'RUNNING' to 'SUSPENDING'
000101.955582 PDMR3Suspend after     0 ms, 1 loops 1 async tasks - ahci0
000101.957435 VD#0 Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.957450 AHCI#0P0 Write at offset 83887415296 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.957482 VD#0 Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.957490 AHCI#0P0 Write at offset 97846059008 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.957504 VD#0 Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.957512 AHCI#0P0 Write at offset 293535506432 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.957527 VD#0 Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.957535 AHCI#0P0 Write at offset 322258100224 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.957548 VD#0 Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
000101.957556 AHCI#0P0 Write at offset 419431735296 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
000102.719066 AIOMgr Endpoint for file 'homemyNameVirtualBox VMsMyVMSnapshots{5376fcba-f0e2-41c1-86de-84eb923f3b02}.vdi' (flags 000c0781) created successfully
000103.210167 PDMR3Suspend Driver 'VD'0 on LUN#0 of device 'ahci'0 took 1 252 517 995 ns to suspend
000103.267427 PDMR3Suspend 1 311 917 520 ns run time
000103.267457 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
000103.267478 Console Machine state changed to 'Paused'
000103.268067 Console VM runtime error fatal=false, errorID=BLKCACHE_IOERR message=The IO cache encountered an error while updating data in medium ahci-0-0 (rc=VERR_INVALID_PARAMETER). Make sure there is enough free space on the disk and that the disk is working properly. Operation can be resumed afterwards
Here is vdi Info

Code: Select all

Name                   Virtual Size       Actual Size
main.vdi                     2.0 TB           5.86 GB
 caputre1.vdi                20 GB           11.62 GB
  caputre2.vdi               20 GB            1.49 GB
   caputre3.vdi              2.0 TB           3.11 GB
    caputre4.vdi(now)        2.0 TB             41 MB
Here is my phsical server info

Code: Select all

Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs   32G     0   32G   0% /dev
tmpfs          tmpfs     6.3G  2.6M  6.3G   1% /run
/dev/sda2      ext4       29T  3.9T   24T  15% /
tmpfs          tmpfs      32G   17M   32G   1% /dev/shm
tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs          tmpfs      32G     0   32G   0% /sys/fs/cgroup
/dev/sda1      vfat      511M  6.3M  505M   2% /boot/efi
tmpfs          tmpfs     6.3G   28K  6.3G   1% /run/user/125
tmpfs          tmpfs     6.3G   64K  6.3G   1% /run/user/1000
Virtual Box version

Code: Select all

ii  virtualbox-6.0                             6.0.8-130520~Ubuntu~bionic                      amd64        Oracle VM VirtualBox
Please help, thank you.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by mpack »

The only reason VirtualBox would suspend a VM is if you run out of space in the host partition (the one the VDI is located on). There will be a safety margin on that, sufficient to allow a saved state to be written.

Your depiction of your VDI's bothers me. You show them indented as if they are snapshots, but they are not named like snapshots should be. Also I can't tell what partition they're stored on.

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
AnnNing
Posts: 10
Joined: 10. Aug 2021, 09:09

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by AnnNing »

mpack wrote:The only reason VirtualBox would suspend a VM is if you run out of space in the host partition (the one the VDI is located on). There will be a safety margin on that, sufficient to allow a saved state to be written.

Your depiction of your VDI's bothers me. You show them indented as if they are snapshots, but they are not named like snapshots should be. Also I can't tell what partition they're stored on.

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
They are snapshots actually. There is a lot of words so I simplified it, and I thought it was clear enough. My mistake.

The log file is in the attachment, thank you.
Attachments
VBox.zip
VBox.log
(31.78 KiB) Downloaded 8 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by mpack »

I see that the VM is located on a NAS share. If the connection is a typical 1Gbps Ethernet link then that will of course have a performance impact (125MB/s max theoretical bandwidth). However that isn't what we're here to discuss.

Unfortunately, because the VM is located on a network share, I still don't know where and what size the host partition is. And being a NAS, there's also a possibility that a storage quota has been set. I'm frankly unsure what complications a NAS adds. I don't trust snapshots at the best of times, plus I resent the space they take up, and the thought of locating them on a network share is just something I wouldn't consider - so I simply don't know what the practical limits are (e.g. on file size).

The VirtualBox version is rather old too (6.0.8 - released May 2019), though I don't expect that really matters.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by mpack »

Here is the relevant portion of the log regarding the switch to a suspended state. I have highlighted what I believe are the important lines. It looks like you are getting some kind of I/O error on the host drive.
00:00:53.895485 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=00007ffbba4ec000 w=800 h=600 bpp=32 cbLine=0xC80 flags=0x1 origin=0,0
00:01:01.580001 AIOMgr: Flush failed with VERR_INVALID_PARAMETER, disabling async flushes
00:01:01.955115 I/O cache: Error while writing entry at offset 32615956480 (4096 bytes) to medium "ahci-0-0" (rc=VERR_INVALID_PARAMETER)
00:01:01.955221 VM: Raising runtime error 'BLKCACHE_IOERR' (fFlags=0x6)

00:01:01.955274 I/O cache: Error while writing entry at offset 32616243200 (688128 bytes) to medium "ahci-0-0" (rc=VERR_INVALID_PARAMETER)
00:01:01.955294 VD#0: Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.955355 AHCI#0P0: Write at offset 46038016000 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.955381 Changing the VM state from 'RUNNING' to 'SUSPENDING'
00:01:01.955582 PDMR3Suspend: after 0 ms, 1 loops: 1 async tasks - ahci/0
00:01:01.957435 VD#0: Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.957450 AHCI#0P0: Write at offset 83887415296 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.957482 VD#0: Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.957490 AHCI#0P0: Write at offset 97846059008 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.957504 VD#0: Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.957512 AHCI#0P0: Write at offset 293535506432 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.957527 VD#0: Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.957535 AHCI#0P0: Write at offset 322258100224 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.957548 VD#0: Write (0 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:01.957556 AHCI#0P0: Write at offset 419431735296 (688128 bytes left) returned rc=VERR_INVALID_PARAMETER
00:01:02.719066 AIOMgr: Endpoint for file '/home/freenas/VirtualBox VMs/OdorMatrix/Snapshots/{5376fcba-f0e2-41c1-86de-84eb923f3b02}.vdi' (flags 000c0781) created successfully
00:01:03.210167 PDMR3Suspend: Driver 'VD'/0 on LUN#0 of device 'ahci'/0 took 1 252 517 995 ns to suspend
00:01:03.267427 PDMR3Suspend: 1 311 917 520 ns run time
00:01:03.267457 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
I'm going to assume that the exact nature of the I/O error is that offset 32616243200 is beyond the end of the host partition or share quota. By my reckoning that offset is a bit over 30GB.
AnnNing
Posts: 10
Joined: 10. Aug 2021, 09:09

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by AnnNing »

Yes, I noticed that too. What confused me very much is, the host seems has enough space(24T left), but the log says only 688128 bytes left.

I tried to export the guest, it failed also.

Result code: VBOX_E_FILE_ERROR.(0x80BB004) Component: MediumWrap.

I/O error on the host drive, does it mean there are badsectors ? Can I avoid it?
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by mpack »

AnnNing wrote: I/O error on the host drive, does it mean there are badsectors ?
Yes it could mean there is a bad sector, though I think it's more likely that the VDI has been located inside a partition with less space than you believe.

I've been searching for previous reports of BLKCACHE_IOERR while using VDI, and I'm not finding much: most reports involve using raw vmdk. Did you change any VM settings recently, e.g. did you disable the hdd cache in the VM settings (<settings>|Storage|SATA controller) ?

On the raw VMDK comparison, the underlying issue there is that raw disk usually requires elevated permissions, so perhaps you have a similar permissions issue on the NAS. E.g. most OS's will not like read-only disks.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by fth0 »

@mpack:
As an expert for the VDI format, what would you recommend after looking at the Virtual Size column of the snapshot chain? ;)
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by mpack »

Well, now that I know that it is actually a snapshot chain, I don't think I believe everything in that column. If the base disk was 2TB then the snapshots must be as well, since VirtualBox doesn't offer a capacity reduction feature IIRC. So the capacity is going to be 2TB all the way down.
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by fth0 »

I was thinking about a VM with a 20 GB dynamically allocated VDI with initially 3 snapshots. The natural but wrong way (*) to enlarge it would be to enlarge the base disk to 2 TB. Then taking 1 additional snapshot later on. I'm not sure which problems would occur after this procedure ...

(*) Either in the Virtual Media Manager, or via VBoxManage using the well-known VDI name. At least I'd assume that it's wrong to do that?
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by mpack »

Yes, that could account for it too.

1. It is incorrect to resize the base, or any other non-current state. Ideally they should be treated as frozen unless case 3 is applied.

2. More correct is to resize the current state only. But, ISTR having different capacities in different elements of the chain has led to bugs in the past. There is a lot of complex detail in the snapshot merging code.

3. The correct and relatively safe way to resize a snapshot chain is to resize every element individually.

4. Even safer would be to make a VM backup, then delete all the snapshots using the snapshots manager, then resize the remaining base disk. Or, just clone the VM (current state only) then resize the disk: now you don't need the VM backup.
AnnNing
Posts: 10
Joined: 10. Aug 2021, 09:09

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by AnnNing »

Hey, guys. Sorry for replying late.

@fth0 Yes, I suppose I did that. I remember when I tried to enlarge the current state, which must be weeks ago, some errors occured. So I enlarge the base one when there was three snapshots already. I must enlarged a snapshot later, I'm not sure.

@mpack I'm not sure what do you mean by
still don't know where and what size the host partition is

Code: Select all

Disk /dev/sda: 29.1 TiB, 32003999137792 bytes, 62507810816 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 62C380B5-3BA2-49C3-830E-EFC17AFB135A

Device       Start         End     Sectors  Size Type
/dev/sda1     2048     1050623     1048576  512M EFI System
/dev/sda2  1050624 62507808767 62506758144 29.1T Linux filesystem
Is that what are you referring to?

As the hdd cache in the VM settings, I'll tell exact what I saw, make sure there is no misunderstanding.

Code: Select all

Controller: IDE
      Empty
Controller: SATA
      Type: AHCI
      use Host I/O cache: disabled
      VDI
           Hard Disk: SATA Port0
           Solid-state Drive: disabled
           Hot-pluggable: disabled
Does that mean there could be a solution? Eager to know.

Thank you guys, that's really helpful.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by mpack »

AnnNing wrote: @mpack I'm not sure what do you mean by
still don't know where and what size the host partition is
I mean that the size of a vdi is bound by the size of the host partition you store it in, not by the size of the host disk. The log shows write errors and bad parameters probably indicating that it's writing beyond the end of the partition. And specifically you need only care about which partition the latest snapshot is stored in, since that's the only one that's written to. The latest snapshot is the "{5376fcba-xxxx}.vdi" one.

Inside the log I can see where a VDI is stored relative to its' filesystem path, but I don't know what partition contains that filesystem. Here is what I know about the VDI files involved.

Code: Select all

File system of '/home/freenas/VirtualBox VMs/OdorMatrix/Snapshots/{5376fcba-f0e2-41c1-86de-84eb923f3b02}.vdi' is ext4
...
(level 5) "/home/freenas/VirtualBox VMs/OdorMatrix/Snapshots/{5376fcba-f0e2-41c1-86de-84eb923f3b02}.vdi" (cb=93)
(level 6) "/home/freenas/VirtualBox VMs/OdorMatrix/Snapshots/{063e193b-a7a1-404c-a614-93715538fd5a}.vdi" (cb=93)
(level 7) "/home/freenas/VirtualBox VMs/OdorMatrix/Snapshots/{738684f5-628a-47dd-866c-d0e5488a777f}.vdi" (cb=93)
(level 8) "/home/freenas/VirtualBox VMs/OdorMatrix/Snapshots/{41796be7-11e2-4fd3-8272-6a1c6a919974}.vdi" (cb=93)
(level 9) "/home/freenas/VirtualBox VMs/OdorMatrix/OdorMatrix.vdi" (cb=55)
So I guess what I'd like to see is some indication of what partition the "/home/freenas" folder is in, and what the actual usable free space is in there. Because the NAS is throwing errors on that score.

Track 2: one previous report of a similar issue claimed that it was fixed by enabling the host cache feature as previously described. I have no way to verify that claim, but it sounds harmless to try.
AnnNing
Posts: 10
Joined: 10. Aug 2021, 09:09

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by AnnNing »

Here is the host partition info.

Code: Select all

df -m {5376fcba-f0e2-41c1-86de-84eb923f3b02}.vdi

Filesystem     1M-blocks    Used Available Use% Mounted on
/dev/sda2       30398391 4036366  24835965  14% /
I enabled the host i/o cache few minutes ago. It didn't work, but it could lead to a recovery mode, I guess it's getting better?
fth0
Volunteer
Posts: 5668
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Ubuntu in VirtualBox can’t start after gparted resize disk while i see there is enough space

Post by fth0 »

I'd also suggest to use one of mpack's suggestions from his number 4., to consolidate the 5 virtual disk images into 1. If this doesn't work, try his suggestion number 3., and use only the VBoxManage command (not gparted) to resize the virtual disk images that still have a virtual size of 20 GB.

@mpack:
The host is a rack server that probably has TrueNAS or FreeNAS installed on its local hard disk, with 24 TB of free space, a local user account with username freenas, and the VM is run headless on this server.
Post Reply