- This topic is empty.
12. October 2011 at 9:03 #6876
dear people of freewysemonkey,
i’m an intern at a fairly large company and have been bothered with the task of creating a new image for the 941G client. this hasn’t been an easy task because the client doesn’t support USB booting for as far as i have found. and a lot of things didn’t really go easy because documentation is low and even on this site i had a hard time finding stuff about this client.
but after alot of fighting and attempting i finally got WDM to work with the client. at first it didn’t want to image the test client i had but this was probably due to faulty hardware. but i got the another client to boot properly and accept the image.
but now the real problem come’s in alot of the clients have been stored in a warehouse but they will be just again with the new image. the problem is that on more than half of the clients i have tested the operating system seems te be gone. they boot up and give the PXE screen say there is no bootfile name and exit. but then they say boot disk failure, insert system disk and press enter. i checked the BIOS and the HDD is set as second boot device and the boot other device option is enabled but they won’t boot an OS.
i can add them to WDM manually because i know the MAC Address and the IP they will receive from the DHCP server. so i add them manually and set the scheduled package to next time the client boots. and then set it to roll to boot. the client then starts and receive the package and i get this screen that it is starting to image but than i get an error. on the screen it says FAILURE (or no archive) and if i look at the error in the package manager it says WISard-failure-media_and_archive_size_check.
i tried updating the Hagent to the newest available version for the 941G but it seems that it is not possible because he just ignores it every time i boot it. is there anybody around who can help me with my problem ?
sorry if my english is a bit bad it is not my native language.12. October 2011 at 21:33 #21188ConfGenKeymaster
- Total Post: 11485
- Jedi Master
from what you have written here it looks like either the flash module is corrupt or missing.
Can you put a flash module of a working (flashable) unit in a non-working one and try to flash it?
CG13. October 2011 at 18:22 #21193
thanks for the fast reply. and i indeed noticed that from one unit at least the flash was missing.
i will have to take a look if i can find the time to try out the flash of a working one. but if i find the time i will report back here.
Edit: i had the time to test it today. so i took a known working flash module from a different j400 and put it in the non working one. in the primary IDE slot it gave the same error. but i noticed that in the working client it was in the secondary slot. so i decided to try that and the known working module worked.
so after that i decided to try the non working module again but then in the secondary slot. and now it worked. so i think something is wrong with the primary IDE or maybe it just doesn’t work on primary.
SacredRose16. October 2011 at 11:36 #21202ConfGenKeymaster
- Total Post: 11485
- Jedi Master
The default is indeed to use the secondaey slot. This is by default.
CG17. October 2011 at 6:07 #21204
i see, kinda strange in my opinion i would assume the primary slot would be the one for imaging and stuff.
but well the problem is fixed and if we encounter these problems during the full scale re-imaging we will know what to check.
thank you very much for helping with the problem :).
- You must be logged in to reply to this topic.