Deployment Solution

 View Only
  • 1.  problem imaging with Linux boot agent

    Posted Apr 17, 2009 03:04 PM
    I'm trying to use a new linux boot agent CD to image a Dell optiplex 740.  we were having issues using the Dos boot disk with and storing the images on our san (the drive was too large and dos couldn't recognize it. I am able to pull and image to that drive from the linux disk however I can't push that image from the san to the dell.

    the command line that is running:

    /mnt/ds/RDeploy/Linux/rdeployt -noprompt -md -f/mnt/dir/740/740-St.img -dsstatus:10.60.15.103:402 -mcint:10.60.39.138 -dsconfig:./Temp/c5001344.cfg

    in the log file I get the following:
    status = 6 (0x6)
    aSource File = imglib/common/acrash.cpp
    line number 311 (0x137)
    if you need the stack trace I can copy and paste it.
    note = signum i 1
    imaging library revision = 9024 (linux-x86-release build,...)




  • 2.  RE: problem imaging with Linux boot agent

    Posted Apr 18, 2009 01:27 PM
    Try running the command manually and see if it will give you a more descriptive error.  I'd also suggest trying to browse the SAN drive (ls command) to see if you can actually see the image file.


  • 3.  RE: problem imaging with Linux boot agent

    Posted Apr 23, 2009 10:30 AM
    Manually running the command just hangs.  I can browse to the share and see the image files.  I was also able to pull an image of another computer to the san.

    Running the Job from the Server looks like it's working for about 3-4 minutes then the system just freezes without outputting an error.

    -Jason



  • 4.  RE: problem imaging with Linux boot agent

    Posted Apr 23, 2009 10:53 AM
    Job 1 error:

    Error description: The image is invalid.
    (Note: Current volume is NTFS from source slot 1.)

    Possible causes:
    Data has been corrupted (e.g. in an image or on the network).
    A gigabit ethernet card is being used.
    Possible resolutions:
    Repeat the operation to see if the problem occurs in the same manner again. Simplify the network by removing routers, etc. that might corrupt data.
    If a file is being read, recreate the file.
    Disable 'TCP Checksum Offloading' on the servers with the gigabit NICs wher
    e the image is stored.


    ==================== Technical details ====================
    Logfile = created Thu Apr 23 14:42:38 2009
    Build = rdeployt 6.9 (9024)Cmdline = /mnt/ds/RDeploy/Linux/rdeployt -noprompt -md -f/mnt/dir/740/740-St.img
    -dsstatus:10.60.15.103:402 -mcint:10.60.32.189 -dsconfig:./Temp/c5001344.cfg

    Status = 120 (0x78)
    Source file = imglib/img/image6.cpp
    Line number = 2564 (0xa04)
    Stack trace = 0x80911c3 0x806ed17 0x80604b2 0x8060cea 0x806152a 0x80617a6 0x80521ab 0x805d73e 0x804edaf 0x805aee5 &Known=0x8156860
    Note = Current volume is NTFS from source slot 1.
    Imaging library revision = 9024 (linux-x86-release build, Thu Jan 29 15:53:47 2009)

    Job 2 error:

    Error description:
    The operating system reported a fatal exception.
    (Note: signum is 11)
    Possible causes:
    There was an internal program error.

    Possible resolutions:
    Try the operation again. If you are unable to resolve this problem, please
    report it to Altiris, Inc.

    ==================== Technical details ====================

    Logfile = created Thu Apr 23 14:46:52 2009
    Build = rdeployt 6.9 (9024)Cmdline = /mnt/ds/RDeploy/Linux/rdeployt -noprompt -md -f/mnt/dir/740/740-St.img -dsstatus:10.60.15.103:402 -mcint:10.60.32.189 -dsconfig:./Temp/c5001344.cfg

    Status = 6 (0x6)Source file = imglib/common/acrash.cpp
    Line number = 311 (0x137)
    Stack trace = 0x814f46e 0xb7f6a420 0x80c20e8 0x80a2c1c 0x80a2dbb 0x80a2e80 0x8060521 0x8060cea 0x806152a 0x80617a6 0x80521ab 0x805d73e 0x804edaf 0x805aee5 &Known=0x8156860
    Note = signum is 11
    Imaging library revision = 9024 (linux-x86-release build, Thu Jan 29 15:53:47 2009)

    -Jason



  • 5.  RE: problem imaging with Linux boot agent

    Posted Apr 23, 2009 02:32 PM
    These errors seem related to the server rather than the client(s) being used.  A DOS  client can handle images and drives larger than what it can address (2Gb) by breaking it up into 2 GB sections.  We have been using it for years.  An image may have 10 or more 2 Gb sections.  We currently use all three (DOS, PE2.1, and Linux) depending on the task and the speed of the respective client.  I have never seen errors like these.  I think I would reinstall the DS (whatever version you are using) and see if anything changes.  I would also look at the PXE install and would probably reinstall that to make sure all drivers install cleanly.  Good luck.