Problems with deploying on Windows 10S with eMMC storage

  1. 6 months ago

    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?

    I created a new kernel 4.16.1 with the patches to remove that special drive. Can you test. You'll need to upload the image again.

    https://sourceforge.net/projects/clonedeploy/files/kernels/4.16.1/

  2. clonedeploy

    6 Apr 2018 Administrator

    I think I need a clearer picture of the partitions, can you attach the upload and deploy logs?

  3. Here are the logs we've found.

  4. clonedeploy

    7 Apr 2018 Administrator

    I have a few things for you to try.
    In the older kernels, I think I modified them so the /dev/mmcblk0rpmb drive wouldn't be detected. Can you try using kernel 4.5 or older.

    The other option is to manually specify the destination drive.
    In the image profile deploy options, check modify image schema
    then in the destination box put /dev/mmcblk0

  5. Edited 6 months ago by danieltyraj

    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?)

    System.NullReferenceException
    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

  6. clonedeploy

    9 Apr 2018 Administrator Answer

    I created a new kernel 4.16.1 with the patches to remove that special drive. Can you test. You'll need to upload the image again.

    https://sourceforge.net/projects/clonedeploy/files/kernels/4.16.1/

  7. Thanks for the solution, with the 4.16.1 kernel we could finally image this device!

  8. 4 months ago

    Hi, having a similar issue but i think im getting stuck on /dev/mmcblk0boot0 and /dev/mmcblk0boot1 ?

    ** An Error Has Occurred **

    ...... Could Not Delete MBR Partitions

    This is with the 4.16.1 kernel also..

 

or Sign Up to reply!