A Word About ChromeOS

There are literally hundreds of installation videos available, created by Chrome / Brunch users. 

Many of these video procedures will only work when used with very specific hardware.
You should seek installation support from the creator of the video.

If you need support for Chrome issues, you must go to a Chrome or Brunch support group for help.

Check out the site where you downloaded your Chrome or Brunch files for support.

Chrome installation and import instructions are here   Importing ChromeOS Config Files

You should understand that Grub2Win simply loads the Chrome or Brunch kernel into memory.

       Then Grub2Win is then removed from memory.

       Chrome or Brunch is now in control of your machine, Not Grub2Win.

There are several reasons I cannot provide support for Chrome errors:

The boot code generated by Brunch sometimes contains errors that prevent Grub2Win from loading the Chrome kernel.

These errors often include incorrect search paths, filenames and UUIDs.

The Chrome kernels currently available for download are extremely hardware sensitive. 

Users often experience black screens and system hangs when they try to boot these kernels on Windows PC's.

The GNU Grub code required to boot Chrome is both complex and not predictable.

The Linux parms for Chrome are not well documented.

Example:

       linux (loop,gpt9)/kernel boot=local noresume noswap loglevel=7 disablevmx=off \

       cros_secure cros_debug loop.max_part=16 img_part=$img_part img_path=$img_path

The Chrome partition configuration is also very complex.

It requires up to 12 partitions on a single disk.

Often, the partitions are loaded from a disk image .img file or from a virtualized disk.

In addition, several of the partitions employ proprietary filesystem formats unique to Chrome. 

These are not normally readable from Windows or other Linux distributions.

Here is a typical disk layout for Chrome installation:

Disk  5     Style GPT   Sector 512        Size 1 TB         Used 7 GB  0.7%          Free 925 GB    WDC WD10EZEX                   

Partition 11   Chrome OS Firmware                                     Size   8 MB                   

Partition 6    Chrome OS Kernel                         FS OTHER      Size 512 Bytes                

Partition 7    Chrome OS Root FS                        FS OTHER      Size 512 Bytes                

Partition 9    Chrome OS Future Use                                   Size 512 Bytes                

Partition 10   Chrome OS Future Use                                   Size 512 Bytes                

Partition 2    Chrome OS Kernel                         FS OTHER      Size  16 MB                   

Partition 4    Chrome OS Kernel                         FS OTHER      Size  16 MB                   

Partition 8    Linux Filesystem                         FS EXT4       Size  16 MB    54% Full       Label = OEM    

UUID = B13EA26E-E754-4FC3-9B8C-5F0DBBD3667E

** Unallocated Space **                                               Size  64 MB

Partition 12   ** Other EFI **                          FS FAT16      Size  32 MB                   Label = EFI-SYSTEM    

Partition 5    Chrome OS Root FS                        FS OTHER      Size   2 MB                   

Partition 3    Chrome OS Root FS                        FS EXT2       Size   3 GB    95% Full       Label = ROOT-A    

UUID = 00000000-0000-0000-0000-000000000000

Partition 1    Linux Filesystem                         FS EXT4       Size   4 GB    56% Full       Label = STATE    

UUID = 978542BF-0712-4937-B2D9-425592990800

** Unallocated Space **                                               Size 925 GB

Created with the Personal Edition of HelpNDoc: Easily Add Encryption and Password Protection to Your PDFs