Unable to pull image from D90D7

  • This topic is empty.
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #7700
    Avatararhub
    Member
    • Total Post: 5
    • Newbie

    So I actually posted this same topic over in the official Dell wyse forums but the thread was overtaken by spam posters and I didn’t get any real responses. So posting here for some help

    I have a D90D7 that is a 8GB Flash 4GB Ram device, when I push the latest image to it from the Dell Wyse website it gets rid of the data partition and makes 1 big C drive even though I told it to preserve the data partition. Thats fine in itself because I would rather have 1 big C drive, however I think it is causing imaging errors when I pull an image.

    When I try and pull an image from it, it goes through the process and when its almost done it ends with the following error.

    Try  1:Merlin-Process-FAILURE [Fri Feb  1 17:40:51 2013][os validation stage][upload os image failed http error code 221][os upload operation failed][make sure that network is up and the flash or harddrive is connected to the device properly]

    If I take a fresh D90D7 out of the box and pull an image from it without updating it or doing anyting it works fine, which leads me to believe it is failing because it has 1 big OS partition and no “E”. Does anyone have any thoughts?

    Thanks

    #23422
    ConfGenConfGen
    Keymaster
    • Total Post: 9810
    • Jedi Master
    • ★★★★★★★

    Which WDM Version are you using? Is it 4.9.1 including the needed hotfix?
    Are you using http or ftp for storing the Image in the repository?

    CG

    #23424
    Avatararhub
    Member
    • Total Post: 5
    • Newbie

    Yes I am using 4.9.1 and have gotten the patch from Wyse for the D90 series thin clients.

    Also I am using FTP for the repository, and using the free Workgroup edition of WDM.

    #23425
    ConfGenConfGen
    Keymaster
    • Total Post: 9810
    • Jedi Master
    • ★★★★★★★

    Theoretically WDM should split the pulled image into 4GB pieces as IIS cannot handle bigger files. Can you check if WDM is at least trying to create more than one file (par1.img, par2.img, parx.img)?

    CG

    #23427
    Avatararhub
    Member
    • Total Post: 5
    • Newbie

    When it fails if I check the repository folder, there isn’t even a folder for the image created.

    #23428
    ConfGenConfGen
    Keymaster
    • Total Post: 9810
    • Jedi Master
    • ★★★★★★★

    Have you upgraded the Boot Agent with the latest one that comes with the hotfix?

    CG

    #23430
    Avatararhub
    Member
    • Total Post: 5
    • Newbie

    Thank you that’s exactly what it was. I’m still new to WDM, and I didn’t even realize it had installed a new Boot Agent, after I pushed that to the thinclient I was able to image it.

    So my question is do I have to push that Boot Agent out to all my clients first or can I just push the image I created and will it include the new Boot Agent?

    #23448
    ConfGenConfGen
    Keymaster
    • Total Post: 9810
    • Jedi Master
    • ★★★★★★★

    If the push works to the old clients, you are fine as the BA will be updated along with the image.

    CG

    #23458
    AvatarhajocaPerry
    Member
    • Total Post: 2
    • Newbie

    I am having the same error, except mine is error code 226.

    I have WDM 4.9.1 with the hotfix installed. I also updated my machine to latest HAgent.

    I have a D90D7 with one 8GB partition.

    I originally had this as two 4GB partitions but WDM was only pulling the C partition when I grabbed an image, not both the C and E.

    Any help is appreciated.

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.