hernandezma@, Can you send a feedback report from the recovery tool?

Hi Kalin, I just did, I put in the comments ' crbug.com/705555 '.

The report is not yet up. Meanwhile can you share what media(usb stick, sd-card, size) are you using to store the image?

Nevermind, I see it on the screenshot.

It's a SanDisk USB stick 4GB. I'm able to create images from different devices in the same USB stick, and they work perfectly.

I created successfully recovery build image for Lenovo N22(Touch):
- Patriot 7.9GB
- SanDisk Cruzer 3.7GB
All stages - Downloading, Unpacking, Writing, and Verifying - finalized.

I still can't see the feedback you sent, so I can't link here.

Can you try 'Erase recovery media before starting the process', and try again?
Another (but same type/model) stick?

Hi,

I tried erasing the media before, and it still fails. I have not tried with a different USB since I do not have any other available at the time.

Please note that I've also tried:

- Using a different Chromebook to create it.
- Using different USB ports.
- Downloading the image, then use the local image file.
- Tried creating images of Samsung Chromebook, and Dell Chromebook 13, those are successfully created, and I can recover Chromebooks with no problem. (Using the same exact USB stick after it fails to create the Lenovo N22(touch))

I'll try with a different USB when I'm back home, I have a couple USB sticks there to try. I'll submit feedback and post here when it's done.

+stephenlin

An update here. I just tried, and it seems like the image is created correctly now. I suspect that this may have been triggered due to limitation in the device storage. I just checked the file size that's downloaded from this model, and it's 977mb, If I randomly select other models, the file size is around 500mb, and there may be a problem unpacking and writing to a temp location. 

I'm not sure why the image of this particular one is almost 1gb, but users may face this problem if they try to create images in Devices that are running out of space. Anyhow, the Chromebooks where I tried did not show up a low storage warning and had around 2gb of free space.

I'm closing this one as WontFix. Thanks a lot!

Hi,

Reopening the bug since the issue still persists for the user that reported it. 

Please note that they tried using:

- Different USB (Verbatim 8GB, Staples 16GB and SanDisk 16GB)
- Windows and Chromebook (Lenovo N22 and Lenovo21) on creating the image

Recovery Log: 

https://lenawee-my.sharepoint.com/personal/ann_iott-uphaus_sc-aggies_us/_layouts/15/guestaccess.aspx?docid=156b9a2059bd644e3a77eb49f56371c44&authkey=AfnU514pbOSQNtmzO7fN-eE

I can reproduce this on 56.0.2924.110 (9000.91.0) with two different usb.
I believe it is related to https://bugs.chromium.org/p/chromium/issues/detail?id=670544 and https://bugs.chromium.org/p/chromium/issues/detail?id=653954.
  

Deleted: unzip_lenovo.jpg 11.3 MB

	unzip_lenovo.jpg 11.3 MB View Download

to clarify - I can reproduce on Lenovo N22 

My Lenovo N22 has been updated to ver. 57 this morning and that seem to fix the issue.

@rcabantog, as kalin@ mentioned in #c3, please submit a feedback after you reproduce the issue. 

Just to confirm - User saw error "Unable to unzip file" in recovery tool when they tried to create a recovery image for Lenovo N22, right?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This is most likely a storage space issue on the Chromebook, not the usb drive.

Closing this old issue. Feel free to reopen if the issue can be recreated and the Chromebook can be shown to have enough free space to download and unzip the image file. 3GB should be sufficient for this I think; 4GB to be safe. You can check the Files app Settings menu to see how much storage is still available on the device.