Not starting after HD size increase

[BRS]

Hi,
I have ubuntu guest installed on windows 10 laptop. I initially had 10 GB HD (VDI) allocated then as the space got used I increased it to 13 GB. Now, the image boots, I can see the ubuntu logo, dots moving and then the blank black screen. Please help I have lots of my work that I don't want to loose.

Virtual Box Version 6.0.4 r128413 (Qt5.6.2)

Thanks,
BRS

[mpack]

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.

[BRS]

Hi, Thanks for looking into this. find attached the log file as requested.

[mpack]

I find it hard to believe that this VM ever ran.

The host software is way out of date (6.0.4) and the Guest Additions are even older (6.0.0). No extension pack is installed. Unless your host OS updates are frozen too then you need to keep VirtualBox relatively up to date.

Only one CPU core is assigned, 2 would be better.

Only 16MB graphics RAM, 64MB would be better. Or even 128MB and also enable 3D acceleration to improve graphics performance.

That all said, the log shows the guest OS reaching the point of loading those ancient GAs, so clearly the guest OS does start. Perhaps if you fix the lack of graphics RAM you'll be able to see what's going on.

Btw, 13GB isn't enough either for disk space. I would never give a modern desktop OS less than 32GB hard disk space, and it would be 64GB if I used it a lot. Obviously physical PCs are used to way more than that.

[BRS]

It's office provided laptop (i5, 16 GB RAM and 160 GB SSD) and software, I can't install any updates etc. on that. Normally, periodic updated do happened may be this software got left out. will need check with them.

Meanwhile; I Increased the CPU Cores, Memory and Graphics. still the same.
attached is the new log file..

Thanks
B Ravi Shankar

[mpack]

I'm afraid you've now gone too far in the other direction.

00:00:01.799129 Host RAM: 16106MB (15.7GB) total, 6022MB (5.8GB) available
...
00:00:01.937429 RamSize <integer> = 0x00000002be000000 (11 777 605 632, 11 232 MB, 10.9 GB)

Your host has 16GB total and is running 64bit Windows - so no way it can afford 11GB for a VM. I would reduce that to 4GB.

You can also reduce the number of cores back to the 2 I suggested before. 3 is not better, that leaves the host (where VirtualBox runs) short of CPU. You have a 4 core host, therefore the fairest division is 2 cores each.

As I said before, your guest OS definitely starts. I see however that guest has a rather small 13GB main drive. I am told that a black screen in Ubuntu can be symptom of being low on disk space, but I have no direct experience of it.

[BRS]

Tried many different combinations before before posting above logs. none worked. any other setting etc. to check. or boot in safe mode kind of so that I can copy my work?

[BRS]

I booted into safe mode (Press and hold left shift while booting) and choose "clean" it freed some 300+ MB and uninstalled some old versions of drivers etc. The ubuntu is booting now. Thankyou for your help .

[mpack]

I'm glad you are up and running again, but if 300MB made that much difference then I fear it will not last long.

In your first post you mentioned enlarging the drive. Did you also run a partition manager in the guest OS to make the new space available to the OS? It will be unusable until you've done that.

A complicating factor with Linux guests is that they often have a swap partition located immediately next to the main system partition. That swap partition needs to be moved up the drive image as far as possible to allow room for the main partition to be increased in size. The relevant Linux guest tool is usually gparted.

Finally, 13GB really isn't enough. I suggest you enlarge it some more before turning to the partition manager. I typically give my VMs around 32GB as a dynamic VDI, usage of my Linux VMs typically seems to sit around 23GB (I'm not a heavy Linux user).

[BRS]

Tried with gDisk followed steps from interne and then disk got corrupt.
restored from snapshot then tried gparted and it helped thanks