search

unraid / usb-creator-next

The home of the Next-Gen Unraid USB Creator, a fork of the Raspberry Pi Imager
https://unraid.net/getting-started
Other
9 stars 4 forks source link

Urgent Bug: Flash Backup Restoration Does not Copy /config or /efi folders when using "use local zip" creation method for USB drive #48

Open elibosley opened 3 months ago

elibosley commented 3 months ago

I could reproduce what the customer is compaining, using the flash backup from Connect with the new USB tool creates a flash drive missing the /config and /EFI folders, they are in the zip.

elibosley commented 3 months ago

It looks like Zips from our Flash Backup service do not get restored properly, both of those folders listed are ones that we modify using code in the USB creator, so I wonder if the lifecycle happens before the restore can finish.

I'll attach a link to a zip for you to test with.

keesfluitman commented 3 months ago

This happened to me as well. It is not a bootable device and not working. Did this after taking a .zip from my backup flash.

elibosley commented 3 months ago

Thanks for the feedback @keesfluitman - please write the last working version (rather than the folder) and then copy over the "config" folder from your backup zip to fix this for now.

keesfluitman commented 3 months ago

tested with both 1.0.0 and 1.0.1. 1.0.1. first came with config, but without efi. manually adding efi would boot it, but not work at first. So I redid it, copied config and efi manually and also executed the make_bootable script, then it worked.

This has to be fixed. Untill then, it should at least be in the docs as a clear Note! Cause it confused me at first (I crashed my own server by rm -rfing the shit out of it. But I recovered the important stuff, and was confused as to whether I damaged too much...but that shouldnt be the case, as at least, it should always boot... Makes you doubt yourself and maybe if unpatient..make you do worse by starting all over.

JosephHobbs commented 1 day ago

tested with both 1.0.0 and 1.0.1. 1.0.1. first came with config, but without efi. manually adding efi would boot it, but not work at first. So I redid it, copied config and efi manually and also executed the make_bootable script, then it worked.

This has to be fixed. Untill then, it should at least be in the docs as a clear Note! Cause it confused me at first (I crashed my own server by rm -rfing the shit out of it. But I recovered the important stuff, and was confused as to whether I damaged too much...but that shouldnt be the case, as at least, it should always boot... Makes you doubt yourself and maybe if unpatient..make you do worse by starting all over.

I just ran into this as well and am currently struggling through getting my server back online... Some sort of mention in the documentation would be great.