Windows could not create partition on disk 0 about windows

[masterherby88]

After Cleanup, the setup starts in manual mode and i was able to load the correct disk driver.
Installation is currently running!
would be interesting, if it's a driver issue, or format / allocation type did the trick :)
i give it a try and write back soon!

UPDATE:
Automatic works now, with Format RAW and Allocate NO set

[slayerofmadness]

sorry, didn't see the post. with this setting automatic install works flawlessly :)

[kroese]

I guess this can be closed now! If other people run into the same issue, hopefully they will use the search function and end up here.

[kroese]

This error

BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found

is normal. It means it cannot boot of the harddrive (because it is empty because Windows has not installed anything on it yet). And because of that it boots from CD-ROM (which is exactly what we want). So you can ignore it, you will not see it again after a succesful install.

The second error is more problematic. Where do you see that? Can you attach a screenshot here? Do you also get it when you install Windows 10 or 8 for example? Do you also get it when performing manual installation? Just so that we can pinpoint what is causing it.

[slayerofmadness]

Ok, got it. I thought the first error was a real problem, great :). I will try it with another Win Version. UPDATE: The Winver doesn’t change anything.

OK, no problem, here is a screenshot:

[kroese]

Do you have any more information about the system you are trying to install this on?

What is the operating system? What is the filesystem? Is it possible for you to use a different drive or partition to mount the /storage folder on, just to see if it makes a difference?

[masterherby88]

Hi kroese,
i'm currently struggling with the same error. - Trying on Unraid 6.12, Filesystem is xfs. i'll give it a try, running on an btrfs cache drive :) will post back soon

[kroese]

@masterherby88 Could try the manual installation method from the FAQ (by adding a container variable: MANUAL=Y) and see if it can create partition?

[masterherby88]

hm :-/
after providing the MANUAL Variable, i'm unable to connect to GUI - "SyntaxError: The requested module '../core/util/browser.js' does not provide an export named 'isAndroid'"
doesnt matter, if MANUAL variable is still set or not.

[slayerofmadness]

I am on the newest Unraid 6.12 with xfs drives. Other drive makes no difference. Tried the template from store, started from scratch, tried to use manual install and other win ver. Nothing helped 🤔

[masterherby88]

@slayerofmadness
as you are on Unraid too, did classic virtualization with virtIO work for you?
i'm also struggling with this, so maybe, we both have compatibility issues with virtIO :)

[slayerofmadness]

I would say yes 🤔😜 I’m running two VMs (Debian and home assistant) without any problems. Until now I didn’t try a win VM.

[kroese]

@masterherby88 This 'isAndroid' error is not related, I get it too sometimes. It has something to do with noVNC javascript in the browser cache. If you open the same URL in an ignito tab (or clear the browser cache) it will work.

[kroese]

@slayerofmadness Can you make a screenshot of the container configuration in unRaid?

[slayerofmadness]

no problem, first I added the container manually, later I tried the Template

[kroese]

I did not know there was a template? Cool!

I see nothing wrong in these settings. Only the "Privelegierte Rechte" should be off I guess.

Have you already tried setting /mnt/cache/xxx instead of /mnt/user/xxx?

Is there anything special about your system that differs from most other Unraid instances?

Can you add two container variables: DISK_FMT=raw and ALLOCATE=N. This will create the disks in raw format instead of qcow2 format. Maybe that helps?

[masterherby88]

It wont enter Manual Mode.

docker run
  -d
  --name='WindowsinDocker'
  --net='bridge'
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="herby-unraid"
  -e HOST_CONTAINERNAME="WindowsinDocker"
  -e 'VERSION'='win11x64'
  -e 'CPU_CORES'='2'
  -e 'RAM_SIZE'='4G'
  -e 'DISK_SIZE'='64G'
  -e 'MANUAL'='Y'
  -e 'DISK_FMT'='raw'
  -e 'ALLOCATE'='N'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8006]'
  -l net.unraid.docker.icon='https://github.com/dockur/windows/raw/master/.github/logo.png'
  -p '8006:8006/tcp'
  -v '/mnt/user/domains/WindowsInDocker/':'/storage':'rw'
  --device='/dev/kvm'
  --cap-add=NET_ADMIN
  --stop-timeout=120 'dockurr/windows'

[kroese]

@masterherby88 Did you remove all files in mnt/user/domains/WindowsInDocker before you start the container? Because if there already exists an .iso or .qcow disk, they will not be created again, so the new flags will be ignored.

If you are sure you started cleanly, please post the logfile from the container (after the download progress).

[slayerofmadness]

I can confirm that the manual install works (after deleting the files). It has to be something with the driver selection in automatic install.

[kroese]

So the automatic install still doesnt work even if you start cleanly?

What letter does the CD ROM drive have during the manual install?

[slayerofmadness]

trying at the moment, will tell you soon.
When installing manually the drive letter is D:

[kroese]

Okay.. That is correct.. Because in the XML file I have hardcoded the location of the drivers to D:\ so if it had a different letter that would be a problem.

[kroese]

I now see this message from @masterherby88

UPDATE:
Automatic works now, with Format RAW and Allocate NO set

So it means it is a qcow2 problem..

[slayerofmadness]

automatic install still doesn't work

My Unraid isnt special. It's an Intel i5 8500 in a HP G4 Mini PC with 2 SSDs. The whole config is, I would say, near standard config

[kroese]

But did you set DISK_FMT=raw?