Also is it possible that the SATA controllers are configured differently? You might pop into the BIOS and check that out and confirm that they are all set the same as the laptop you built the image on.
I have a bunch of these ST250LT007 Seagate drives (the same Momentus line of drives, but with no encyption) and they work just fine. However, 4K advanced format drives are not supported in FOG yet. You’d have to use FOG .33 (beta still) to image those drives. That is what I am using now and it is working. The beta is not “feature complete” yet, but 4K drive imaging works.
I’d recommend downloading the beta release to a spare system and doing a few image tests. You could report your success/failures to this forum post:
Well I solve my own problem! Tends to happen a lot.
The problem ended up being the Bios version wasn’t supported, and it was the latest and greatest.
The fix, I remembered an option in Clonezilla to use PXE boot. So for the giggles I booted off the Clonezilla CD, selected iPXE boot. then FOG started working, but an error came along saying “unsupported bio’s version”. So i let it sit for a little bit, under 2 minutes and it just started going! It’s imaging the computer right now as I type.
I find this quite remarkable and think it should be sticky’d. This will help a lot of people with these problems.
Yes, it kinda defeats what FOG is trying to accomplish, but hey it still beat going through all the lines of clonezilla to get an image rolling.
And my other error was due to my user in FOG being the same on ubuntu, same password and all. So that’s all fixed and ready to go!
I took the WD harddisk from one of the GX745’s that worked, put it in the GX755 that has the issue, then reimaged with the same image, works fine; I then took the Seagate harddisk that was originally in the GX755 and put it in the GX745 and tried to reimage, and it works as well…go figure, am totally confused as to why FOG images the Seagate fine in the GX745, but not in the GX755…
I have exactly the same problem and know for fact that it’s not the FOG service.
I finaly fix it by putting the password for account in registry under HKLM\software\microsoft\windows NT\current version\winlogon
I setup the key called DfaultUserPassword.
there is a program called windowsautologin.exe that does all that for you.
I also noticed that the password will be removed from registry after the number of autologon is over.
I appreciate if you tell mw what solution you found.