Install Redhat Via Kickstart on Dell Optiplex 760 - Unable to boot to Linux Automation

 Hello lryder,

The Linux Automation environment starts up and tries to run the ADLAgent. This should be reported on the DS console. When you create the boot image using Boot Disk Creator (in PXE I suspect) you have the option to use the ADLAgent form the image or from the Deployment Server.

In order for the ADLAgent to run over the network Linux needs to be able to access the network.

I think there could be a problem in the networking or ADLAgent.

Are you trying to signal that my comment doesn't answer your question lryder?

If so I guess you could try to tell me what I missed or in which manner this doesn't help, so I can try to answer or help you. A reply would have done just as well if not better than a vote down ;).

Ludovic,

The negative vote was from me.  In my opinion your post was not exactly helpful.  lryder may or may not agree (and they can also vote positive or negative in either case, just as you can).  To make your post better (or more helpful) you might have offered some hints of where they can continue their troubleshooting.  Or if that was not possible, maybe requesting more information to help you help them.

 Ah ah, my bad not considering that voting can come from many different places.

I was kind of trying to get started there, because this isn't a clear cut problem. If the ADLAgent is not starting because of network issue the troubleshooting is limited to getting networking up, and that's something you can do mostly hands on (specially with drivers).

Then if it's an issue with DS you can alway s delete the computer from the console and make sure your initial deployment instructs the ADLAgent to wait.

In which case you can take control of the console to check things out.

Oh, and of course there's the option to drop a dir job from the DS console in automation, some script like "ls -lart > /dev/tty0" as we only have 2 consoles on the Linux preboot environment and the default is 0.

I guess I could have said all of this directly.

Hi Ludovic -I'm following you..... ;-)

Iryder -I've said this many a time, but I can't help it. I'm addicted to it. Wireshark is your friend. If you've never used it before, then solving this problem might give you a good motivation to start. You could see if there are any comms from the client, and you can even see the instructions being sent.

Anyway.... that aside.....

If Linux automation restarts really quickly... I'm thinking that the network is might be OK. I can't recall the last time I had a nic problem with Linux automation, but I'm sure that when it did it took ages for automation to give up and reboot. So, is it possible that Altiris is perhaps expecting you to be booting into a different Linux automation environment than what its getting?

If you are PXE booting your client you should be getting the right one (if you have several configured). However if you are booting from an embedded partition, CD or USB stick its concievable that its DS is not happy with the automation environment you're providing.

I've seen this with WinPE in the past, not with Linux though. So its entirely possible i'm barking up the wrong tree.

Kind Regards,
Ian./