Get Error When Trying to Download Image

  • I have a lab of Asus 1000HE netbooks. I imaged these a few years ago with XP and Fog .29 and had no issues. A few months ago I imaged these with Win7 and fog .29. To upgrade to windows 7 I had to install a bios update. Again no issues. Now I want to go back to XP. I’m now using fog .32. The image fails when downloading. See image link below. I’ve tried the old xp image and I’ve created a new xp image and both do the same thing. To install xp I have to change IDE Configuration setting in bios from AHCI to IDE. I’ve tried deploying with fog and setting up golden images on a few different netbooks to make sure it’s not a single computer issue. Could it be bios related? I tried to downgrade. I don’t think it’s possible.

    Before I install the OS I follow these steps:
    list disk [See which drive is which]
    select disk 1 [corresponding to disk on your computer]
    create partition primary
    select partition 1
    format fs=ntfs quick

    When I’m finished creating the golden image I run [CODE]chkdsk /f[/CODE] reboot twice and then [CODE]chkdsk /x c:[/CODE] reboot twice and then upload to fogserver.


    [CODE]Changing hostname…NTFS signature is missing.

    Failed to mount ‘/dev/sda1’: Invalid argument

    The device ‘/dev/sda1’ doesn’t seem to have a valid NTFS.

    Maybe the wrong device is usied? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)" Or the other way around?

    unmount: can’t unmount /ntfs: Invalid argument[/CODE]


  • For the life of me, I cannot figure out why these image drops keeping timing out on the second partition. I’ve even tried a single partition Win7 that I created, still no go. Too many days trying to sort this all out, has to be a better way…

  • Since you have not done an update on your kernel, I will give you step by step instructions (Hope you don’t mind).

    1. Log into your Fog Server and then click on the Question Mark icon (When you mouse over the icon it will say “Other Information”
    2. A list will come up on the left side. One of the links will say “Kernel Updates”. Click on that.
    3. You will then be presented with lots of Kernel versions that fog has made. Scroll dow the page until you see Kernel - KS (older KS seem to work as well).
    4. Click on the icon below the Kernel name and description.
    5. Another screen will come up. Leave the default name “bzImage” alone and click “Next”.
    6. Your server will down load the kernel from sourceforge and install it. It will tell you when it is done. At that point you can try to deploy your image again.

    Please let me know if you need screen shots (these directions were for the fog interface 0.32).

  • Teena, Thanks for the update. I’ve never done that before. Do I simply put the text [SIZE=13px][FONT=arial][COLOR=#000000][B]Kernel - KS[/B] in the Host Kernel input box for the host? Would I need to download the kernel from ASUS and drop it somewhere on the fogserver?[/COLOR][/FONT][/SIZE]

  • We were having problems imaging 1000HA netbooks with a Linux image. It turns out the pxe kernel that ships with 0.32 no longer has the correct drivers for the netbook. You can go into the web interface of your fog server and change the kernel you are using. The kernel that got our netbooks up and running again is
    [LEFT][SIZE=13px][FONT=arial][COLOR=#000000]Kernel - KS. This is an older kernel and is farther down on the list for “Kernel Updates”. I hope that fixes your problem as well. [/COLOR][/FONT][/SIZE][/LEFT]

  • I started the process again. This time it automatically started. It imaged 100% in 5 min. When I entered the command [B]/usr/sbin/ntfsresize /dev/sda1 -f -b -P[/B]
    I received ERROR (22) Opening /dev/sda1 as NTFS failed…doesn’t have a valid NTFS.

    When I boot to the hd I get an error that says something like OS missing


  • Hard to say, i’ve gotten segmentation fault errors before when there is trouble writing to the hard drive. I am also not sure why your filesystem is RAW, or why you where asked to simulate the restore. It should have automatically just started.

  • This image is the result of the option “Simulation of the Restoration”.

    What does this mean?


  • I’m following the troubleshooting tutorial. After entering the following command on step 7 I get the image that I uploaded below.
    /usr/sbin/partimage restore /dev/sda1 /images/AsusXP [B]-f3 -b[/B]

    Which Option should I select?


  • Thanks for your help! I’ll try this in the morning and post back.

  • I misjudged where that error is occurring. That error is just the result of a previous task not finishing correctly but not sure which one. Have you tried doing a manual deploy from debug mode using this guide:

  • Yep. Same results 😞

  • Sorry I gave you the wrong dd command. This probably won’t change anything but the command should have been:
    [B]dd if=/usr/share/fog/mbr/xp.mbr of=/dev/sda bs=512 count=1[/B]

  • Tried to image and got the same results. I’m stumped.

  • Ok. sda is the hd. I ran [B]dd if=/usr/share/fog/mbr/xp.mbr of=/dev/sda[/B]
    and got these results:
    1+0 records in
    1+0 records out

    I’ll try to reimage now.

  • Debug mode is in the fog pxe boot menu. It is also possible that sda is not your hard drive, it might be sdb. You can run these commands to find out:
    [B]fdisk -l[/B]
    [B]partprobe -d -s[/B]

  • Let me clarify. I use diskpart before installing the OS on the “golden image” machine. I do not diskpart on the machines downloading the image.

    How do I enter debug mode? Are you refering to booting to xp hd and pressing f8? What are the steps required to perform the process you describe above?

  • There is no reason to using diskpart before starting the image deploy. When fog restores the mbr it will take care of this. Try restoring the default windows xp boot record. Enter debug mode and enter:
    [B]dd if=/usr/share/fog/mbr/xp.mbr of=/dev/sda[/B]
    Then try deploying your image again

  • I should add that that imaging these netbooks to xp with clonezilla works just fine. It just takes a lot longer and is very inconvenient.