Error: Image chromiumos_image.img does not have a system partition (corrupted?)

[sethbacon]

Using Method 1: Linux Mint 19.1 in Virtual Box on Windows 10 with shared folders Downloaded and extracted ATB Special Build Camd64OS_R72-11316.B-Special.7z to chromiumos_image.img I tried with both R69 and R72 multiple times. Download is not corrupt. Ideas?

[alesimula]

It may actually be corrupted (you interrupted the script midway?) try redownloading it

[costeldrbrr]

I've had the same problem on ubuntu vbox, because i moved the .img to a different folder before fully extracting from the archive, or renaming it to chromium.img before fully extracted. I haven't noticed the little circle in the corner. After double-checking, I've managed to create a working image that booted. I've used the same image that you used.

[csytan]

Also have had this happen with FydeOS as the chromium image:

I do not think the image is corrupt, as I tested on two systems (Mac and ChromiumOS) and the .img file extracted correctly.

I'm also getting the error: losetup: cannot find an unused loop device

[flipside101]

HI, has anyone found a workaround for this, im getting the same error using either the vanilla or special ATB builds

[danielisdaniel]

Seems to be working now. I'll edit this again.

Same issue here. Kubuntu.

root@calico-ThinkPad-T430:/media/calico/HD-SP1/ArnoldTheBat# sudo bash chromefy.sh chromiumos_image.img chromeos_11316.165.0_peppy_recovery_stable-channel_mp-v3.bin swtpm.tar Image chromiumos_image.img does not have a system partition (corrupted?) aborting... root@calico-ThinkPad-T430:/media/calico/HD-SP1/ArnoldTheBat#

[moyunkz]

I had the same issue when using virtual machine with shared folders. I supposed your files are in the shared folder. So copy all the required files from your shared folder to e.g. VM Desktop then run the script with {path} to your VM Desktop. Hope this helps.

[Botanium]

Also I am getting the same error. Any solution so far?

[Botanium]

bash croissant.sh chromiumos_image.img chromeos_11895.95.0_eve_recovery_stable-channel_mp.bin swtpm.tar Image chromiumos_image.img does not have a system partition (corrupted?) aborting...

[lewas-0]

Try unzip with terminal

7z x yourFile.7z

it works for me

[dudeisbrendan03]

The same thing happens to me, trying to generate image outside of ChromeOS and I get losetup: cannot find an unused loop device followed by the system partition error.

Is it trying to mount the image to check (and if so is the error appearing because it cannot mount)?

[dudeisbrendan03]

@sethbacon @csytan Can you run modprobe loop and send the output here?

[cedoromal]

The same thing happens to me, trying to generate image outside of ChromeOS and I get losetup: cannot find an unused loop device followed by the system partition error.

I know I'm very late for this conversation but I'm having the exact same thing. Are there any updates on what has happened?

I've tried flashing and booting the chromium image on my flash drive and it doesn't seem to be corrupted at all.

[MuntashirAkon]

losetup: cannot find an unused loop device

and

Image chromiumos_image.img does not have a system partition (corrupted?)

are not the same.

If you see the former error followed by the latter error, it means the latter error is irrelevant.

[tapasfun]

I'm facing the same. Can anyone help, please?

localhost /home/chronos/user/Downloads # sudo bash chromefy.sh FydeOS_PC_v8.1-stable.img.xz recovery.bin swtpm.tar losetup: FydeOS_PC_v8.1-stable.img.xz: Warning: file does not fit into a 512-byte sector; the end of the file will be ignored. Image FydeOS_PC_v8.1-stable.img.xz does not have a system partition (corrupted?) aborting...

Thanks...

[TheBeast941]

@tapasfun A file ending with .xz or anything else other than common image files means it is either compressed, converted into another file type or had its extension changed. In your case, .img.xz simply means it has been compressed and you will need to decompress it first before working on the file.

[hacker1024]

I do not think the image is corrupt, as I tested on two systems (Mac and ChromiumOS) and the .img file extracted correctly.

@csytan macOS cannot natively mount ext4 images, and it does not use loopback devices like Linux.

[davidabsenta]

Does anyone know why this happens $ sudo bash chromefy.sh chromiumos_image.img chromeos_12739.94. 0_eve_recovery_stable-channel_mp-v2.bin losetup: cannot find an unused loop device Image chromiumos_image.img does not have a system partition (corrupted?)

[pipip]

This problem occurs if you haven't updated to WSL 2

[davidabsenta]

Este problema se produce si no ha actualizado a WSL 2

You can solve this problem but now the wifi does not work for me. how can i load drivers?

[mambo06]

i believe most of you forget to put disk destination after *.sh

cheers

[LeoNg628]

This problem occurs if you haven't updated to WSL 2 Thanks it works!

for who wasn't update, please download and install this: https://docs.microsoft.com/zh-tw/windows/wsl/wsl2-kernel

[wynntee]

I faced the same problems and found the solutions by manually running the commands in chromefy.sh to see what was going on.

For "losetup: cannot find an unused loop device", I had to enable loopback device support in the kernel (CONFIG_BLK_DEV_LOOP).

For "Image chromiumos_image.img does not have a system partition (corrupted?)", I had to enable ext2 filesystem support in the kernel.

I have a customized kernel with those features disabled.