Cannot install Ubuntu distros on Win10 host (Errno5)

[vowe]

Hi,

on my freshly installed Win10 host, I cannot install any Ubuntu distros (Ubuntu, Kubuntu, Xubuntu, Lubuntu) because the corresponding installer mostly returns with an error (Errno 5), throws a stack trace or freezes:

Errno5_Xubuntu.png (92.18 KiB) Viewed 4562 times

Errno5.png (113.5 KiB) Viewed 4562 times

This is not reproducible and happens at different places within the installation. What I tried to get closer to the problem:

• I tried using a dynamically allocated memory section and a static one
• I tried using different performance settings: display memory, CPU cores, ...
• I checked md5 and sha256 of the downloaded Linux images
• I tried to run VB in admin mode and not (and learned that you shouldn't do that).

In my opinion, this error is a result of writing to a bad memory section. But how can this be possible when the ext4 partition is freshly created? Could hardware caching be a problem here?

Details:
ThinkPad T590
Win10 Host
Version 6.1.4 r136177 (Qt5.6.2)
Ubuntu distros mostly with LTS 18.04 builds

Thanks a lot for any support.

[scottgus1]

Does this happen with other installers? Can you try a Windows 10 ISO from the Microsoft Media Creation Tool? Are you using the ISO files in the guest's CD drive, or burning to a DVD first then installing from your PC's DVD drive? What happens if you let the Ubuntu CD/ISO boot to the LiveCD environment?

Also try turning off your antivirus or setting an exception for all Virtualbox processes and folders.

[vowe]

I got a little bit further with my investigations.

Does this happen with other installers?

It happened with every installer I tried so far.

Can you try a Windows 10 ISO from the Microsoft Media Creation Tool?

I will give it a try today.

Are you using the ISO files in the guest's CD drive, or burning to a DVD first then installing from your PC's DVD drive?

I am using them as images in the emulated CD drive. No burning on physical mediums.

What happens if you let the Ubuntu CD/ISO boot to the LiveCD environment?

Booting succeeds, but writing on a newly created virtual disk fails (see below)

Also try turning off your antivirus or setting an exception for all Virtualbox processes and folders.

No antivirus software is present on the system I am trying to install Linux in the VM.

In the meantime, I achieved to install a version of Lubuntu into a virtual disk drive. However, what was a success at the first glace, lead to many hash errors for downloaded files. I tried to install some software, but for every software package I downloaded, the provided hash sum check failed. The root cause seems to be the writing on the created virtual disk (or the created disk itself). Are there any settings for this?

As an alternative, I led a colleague of mine to create the whole virtual machine for me. As a result, this runs as intended with no errors. In my opinion, something must be buggy while creating a virtual disk ...

[dreymar]

I am facing the same issue with the same setup. What other things could I try to get this to work?

[scottgus1]

@vowe, Wow, very strange problem! Running the LiveCD (in memory only) works (this eliminates the process of reading the ISO.) But installing to the virtual disk fails. Writing to the virtual disk is really writing to a file on the physical disk. Have you tried a host disk check?

[vowe]

@vowe, Wow, very strange problem! Running the LiveCD (in memory only) works (this eliminates the process of reading the ISO.) But installing to the virtual disk fails. Writing to the virtual disk is really writing to a file on the physical disk. Have you tried a host disk check?

The SSD of my Win10 host delivers no errors when checking with system means. That is why my guess is that the creation of the virtual disk (or the handling) is erroneous.

Overall I think that the combination of hardware, drivers and virtualbox version somehow is faulty.

[scottgus1]

Definitely something unusual going on. Try selecting the guest's disk controller in Storage Settings and toggle "Use Host I/O Cache"?

[vowe]

Ya, I played around with this option but nothing changed. Gonna try the new version of virtualbox released today.

[bingolingo]

I had this issue as well (Windows 10 Enterprise 10.0.18363 on a Dell XPS 9560). Here's what I did to solve it: (almost certainly not all of this is relevant but I can't determine what was needed)

• Uninstall docker for windows (the Docker Desktop app, apparently sets up Hyper-V or something that screws up VirtualBox)
• Downgrade virtualbox to 5.2.40
• Disable Hyper-V with this post: stackoverflow <dot> com <slash> a <slash> 47081422 (can't post URLs because of the forum)
• Follow steps on this post: forums.virtualbox <dot> org <slash> viewtopic <dot> php <question> p <equals> 470557 <pound> p470557
• Upgrade virtualbox back to 6.1.6
• Install the virtualbox extension pack for 6.1.6

[scottgus1]

Disable Hyper-V

This could very well be the problem. Any of the OPs or others coming here with Windows hosts and the faulty-but-not-faulty-ISO problem, or hashes not calculating, please zip and post a guest vbox.log before trying to fix anything, so we can see if Hyper-V is enabled.

Lines like this in the log indicate the interfering presence of Hyper-V:

{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x/AMD-V is not available
{timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

For further info, see I have a 64bit host, but can't install 64bit guests and https://www.tenforums.com/tutorials/139 ... puter.html

[vowe]

I had this issue as well (Windows 10 Enterprise 10.0.18363 on a Dell XPS 9560). Here's what I did to solve it: (almost certainly not all of this is relevant but I can't determine what was needed)

• Uninstall docker for windows (the Docker Desktop app, apparently sets up Hyper-V or something that screws up VirtualBox)
• Downgrade virtualbox to 5.2.40
• Disable Hyper-V with this post: stackoverflow <dot> com <slash> a <slash> 47081422 (can't post URLs because of the forum)
• Follow steps on this post: forums.virtualbox <dot> org <slash> viewtopic <dot> php <question> p <equals> 470557 <pound> p470557
• Upgrade virtualbox back to 6.1.6
• Install the virtualbox extension pack for 6.1.6

Thanks for the reply! I formerly solved it by letting a colleague create the image for me. However, I am sure that I need to create another image soon and will try your solution. Thanks!

PS: I was not able to solve the problem with the newest version of VB.

[scottgus1]

vowe, please note my request above about the pre-fix log before you try to fix stuff, so we might be able to pin this down.