Ubuntu 22.04 Guest on Windows 10 host showing error on startup.

Discussions about using Linux guests in VirtualBox.
Post Reply
Ayoudh
Posts: 1
Joined: 11. Feb 2023, 07:11

Ubuntu 22.04 Guest on Windows 10 host showing error on startup.

Post by Ayoudh »

I recently updated my VirtualBox from 7.0.6 to 7.0.8 and after updating the extension pack I went on to updating my Ubuntu VM's Guest Addition, but the problem is my VM doesn't seem to boot.
It shows the following error :-

Code: Select all

/dev/sda5 contains a file system with errors, check forced. 
Inodes that were part of a corrupted orphan linked list found.
/dev/sda5: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. (i.e., without -a or -p options) The root filesystem on /dev/sda5 requires a manual fsck
fsck exited with status code 4

BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands.

(initramfs) -
I have so far not tried out anything to solve this, except restarting the VM multiple times (which didn't work, I keep on getting the same error every time).

Can anyone help me in solving this issue?

Logs (compressed into ZIP because of the file size limit) attached below with this post.

Thanks
Attachments
Ubuntu 22.04-2023-05-12-12-29-24.zip
Ubuntu 22.04 VM logs
(33.18 KiB) Downloaded 6 times
multiOS
Volunteer
Posts: 800
Joined: 14. Sep 2019, 16:51
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: WIN11,10, 7, Linux (various)
Location: United Kingdom

Re: Ubuntu 22.04 Guest on Windows 10 host showing error on startup.

Post by multiOS »

To me, the error message appears to be reporting an internal problem (file system corruption) in the VM's OS and is not a VirtualBox error. It directs you possible Linux/BusyBox action/procedures to to be taken via the Linux command line. I would suggest you need to check this via the Ubuntu/BusyBox channels if you are unsure what the guidance means.

I don't see any indication of an error in the Log which seems to run normally until:
00:00:34.274004 VD#0: Cancelling all active requests
00:00:34.934333 AIOMgr: Async flushes not supported
00:00:36.792516 NAT: Link up
00:00:59.888892 Changing the VM state from 'RUNNING' to 'SUSPENDING' [NOTE THE TIME GAP BETWEEN THIS AND PREVIOUS LINE]
00:00:59.890199 AIOMgr: Endpoint for file 'G:\Ubuntu 20.04\Ubuntu 22.04\Ubuntu 20.04.vdi' (flags 000c0781) created successfully
00:00:59.908641 PDMR3Suspend: 19 707 551 ns run time
00:00:59.908641 Changing the VM state from 'SUSPENDING' to 'SUSPENDED'
00:00:59.908641 Console: Machine state changed to 'Paused'
00:01:00.805006 GUI: Request for close-action to power VM off.
The only potential configuration limitation I see from the Log is:
00:00:10.646095 NumCPUs <integer> = 0x0000000000000002 (2)

00:00:13.149886 CPUM: Physical host cores: 2
Running 2 64-bit Operating Systems in parallel on a Dual-Core processor is asking a lot of the system and may lead to problems when the load on either OS is heavy.
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 22.04 Guest on Windows 10 host showing error on startup.

Post by mpack »

CPU overkill would lead to performance problems, I don't think it would lead to this.

The error message looks straightforward: filesystem corruption. Many things could cause that, from errant software inside the guest, to hardware or user errors during the handling of host VDI files.

Here are a few of the classics:
  • Bad sectors on host drive.
  • User transporting large (>2GB) vdi file on FAT formatted drive, and not noticing error messages.
  • User locating a large VDI file on an external USB drive, and removing that drive by yanking the plug while the VM is running.
  • User locating a VDI file on cheap USB flash drive, which overheats and fails when you do too many writes.
  • And many, many more! Call now!
Post Reply