Blinking cursor on boot after image deploy.
I have an issue with a blinking cursor on boot after deploying an Windows 7 x64 image made from a Lenovo E525 Laptop.
The image deploy works with original laptop used to make the master image. But doesn’t work with any of the subsequent laptops of the same make and model.
So what I have done to get machine ready to upload an image was…
- Use a ‘Multiple Partition Image - Single Disk (Not Resizable)’
- Run Sysprep with an unattended.xml
- Shutdown PC
- Run image task
Has anyone had any issues with a blinking cursor and the machine not booting after a deploy? IF so what was the steps you took to fix the issue?
Corey Cochran last edited by
I have a similar issue, but it doesn’t seem to be related to the OS install. I get the black screen with blinking cursor after the fog menu. If I change bios and boot directly to the HD and skip the fog boot screen the pc boots fine. Of course this is not a solution for us as we have over 360 pcs that we need to be able to image or reimage monthly or quarterly (student lab). This setup was working fine on Thursday of last week, but on Monday all 360 pcs only boot to flashing cursor. Ideas?
rakarn last edited by
I know this is an older thread, but i remembered a way of getting around this issue.
With windows 7 issues, boot to a windows 7 disk, go to command prompt and type in [I][FONT=verdana][COLOR=#323232][B]BootRec.exe /fixmbr should fix your issue has done on the last 250 levonos so far, now if i could only add this option to fog…[/B][/COLOR][/FONT][/I]
Steve Ropiak last edited by
So, you have 100 new laptops, all with OEM licensing? Like Altitude said, do a fresh install and when you sysprep it, I believe you can set it so it prompts for the license key.
Spencer last edited by
[COLOR=#595959][FONT=Century Gothic]How do I get the laptop windows key to work different on each one? I have to clone like a 100 new laptops for the school I work for.[/FONT][/COLOR]
This post is deleted!
Simply put, FOG doesn’t support cloning OEM disk partitions. Obtain a Windows 7 install disk, remove all partitions, and allow Windows to create its own partition scheme and these problems will disappear.
Spencer last edited by
I have the same problem, Tried every thing.
Update1: Well I deleted the third partition, Extended the OS partition, syspreped, uploaded a new image, and deployed to another machine and now I get a ‘A disk read error occurred Press Ctrl+Alt+Del to restart’. Basically a no go. I am going to try pop in gparted and see if i can get the machine to boot.
Update2: Gparted wouldn’t boot in the machine. I have been working on this for to long so I am giving up on Fog. Only because I have to image these machines by Friday and can’t waste anymore time. But thank you for your help.
[quote=“BryceZ, post: 650, member: 2”]Is this a standard installation of Windows 7 from the DVD or a preinstalled OEM installation? Single Partition is the preferred image type for standard Windows installations as it allows you to deploy to HDDs with different geometries. With deploying a non-resizable image to a different model of HDD can potentially cause problems.
The problem you’re describing sounds like a “corrupt” MBR that doesn’t match the disk geometry.[/quote]
Yes this is a OEM pre-installed installation. The computers have three partitions which stoped me from using the re-sizable option.
- 100MB Windows System Partition
- 250GB OS Parition
- 10GB Lenovo System Restore Partition
From what you are saying I think I should delete the third partition and make the image again using the re-sizable option. And if that doesn’t work re-install the OS from a DVD of Windows 7 x64 and make a new image.
Thanks for the help I will report back on the success of this in a few hours for others encase they run into he same problem.
BryceZ last edited by
Is this a standard installation of Windows 7 from the DVD or a preinstalled OEM installation? Single Partition is the preferred image type for standard Windows installations as it allows you to deploy to HDDs with different geometries. With deploying a non-resizable image to a different model of HDD can potentially cause problems.
The problem you’re describing sounds like a “corrupt” MBR that doesn’t match the disk geometry.