Last active 2 months ago
I face another problem on one Notebook (Acer Switch 3).
When I boot from the usb I get the message "Could not open "\EFI\BOOT\fallback.efi": 14".
I tried to turn off the secure boot option in the BIOS, I also tried different usb-keys and kernels (x64 and also not the x64).
BIOS is on the newest version.
Someone who also got this error?
I changed the whole BIOS settings, also checked if an update is available...nothing that would solve my problem so far.
It's the GRUB menu:
No, every model is different, but this is the same type then one other, just different hardware (CPU, SSD-storage,...)
I've imaged about 30 notebooks with the same USB-key (always the same kernel too, the 4.16.1x64) successfully.
With one I have now the problem that I can't boot from the USB-key completely. The device boots to the menu, then it doesn't matter if I choose "Clone Deploy" or "Client Console", the notebook always reboots after pressing enter.
I've tried 2 other kernels (4.13.2x64 and 4.5x64) and a different usb-key with exactly the same failure.
I've also tried to "play" with the BIOS settings (secure boot, fast boot, UEFI/Legacy,...) without success.
With the same usb-key and a windows installation image, the notebook boots without problems, so the failure seems to be not the notebook.
Thanks for the solution, with the 4.16.1 kernel we could finally image this device!
I've tried the 4.5 and 4.4.3 kernel, but with both of them the USB-stick needs about 1-2 hours to boot up.
With the latest 4.13 it boots up in just a few seconds, so something doesn't work with older kernels.
And when I try to modify the image schema I receive the following error message:
(Is it possible to send us one boot version in which you modified it, that the mentioned drive wouldn't be detected?)
Object reference not set to an instance of an object
Description: HTTP 500.Error processing request.
Details: Non-web exception. Exception origin (name of application or object): CloneDeploy-ApiCalls.
Exception stack trace:
at CloneDeploy_ApiCalls.ImageSchemaAPI.GetHardDrives (CloneDeploy_Entities.DTOs.ImageSchemaRequestDTO schemaRequest) [0x00046] in <5df48af3d9ca457bb8547b662c075122>:0
at CloneDeploy_Web.views.images.profiles.views_images_profiles_deploy.PopulateHardDrives () [0x00035] in <94184fea75a34047942dfffb6df3fb46>:0
at CloneDeploy_Web.views.images.profiles.views_images_profiles_deploy.chkModifySchema_OnCheckedChanged (System.Object sender, System.EventArgs e) [0x00019] in <94184fea75a34047942dfffb6df3fb46>:0
at System.Web.UI.WebControls.CheckBox.OnCheckedChanged (System.EventArgs e) [0x00019] in <6bd7a846f9aa4f0bae143ad0f36ee3bd>:0
at System.Web.UI.WebControls.CheckBox.RaisePostDataChangedEvent () [0x0002f] in <6bd7a846f9aa4f0bae143ad0f36ee3bd>:0
at System.Web.UI.WebControls.CheckBox.System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent () [0x00000] in <6bd7a846f9aa4f0bae143ad0f36ee3bd>:0
at System.Web.UI.Page.RaiseChangedEvents () [0x0001e] in <6bd7a846f9aa4f0bae143ad0f36ee3bd>:0
at System.Web.UI.Page.ProcessRaiseEvents () [0x00025] in <6bd7a846f9aa4f0bae143ad0f36ee3bd>:0
at System.Web.UI.Page.InternalProcessRequest () [0x001a7] in <6bd7a846f9aa4f0bae143ad0f36ee3bd>:0
at System.Web.UI.Page.ProcessRequest (System.Web.HttpContext context) [0x0005f] in <6bd7a846f9aa4f0bae143ad0f36ee3bd>:0
Here are the logs we've found.
We have one Notebook with an eMMC storage and Windows 10S, which causes problems with deploying an image with the following error message: "Unknown Error Occured While Determining Minimum HD Size Required"
This happens always to the same partition "/dev/mmcblk0rpmb". The thing is, this partition isn't shown whitin gParted.
Also to mention is that we can't disable the hibernate mode cause in Windows 10S as you can't use the cmd.
I just deleted the hiberfil.sys with a Linux Live distribution which allowed to upload the image successfull, however errors are shown with the above mentioned partition.
Is there a possibility to deploy the image without this partition? So can I skip one partition?
Or is this problem maybe related to this special eMMC storage?
Ohh perfect, that's pretty good news, thanks!