Linux PE - asmbmount command file missing??
Created: 23 Sep 2009 | 3 comments
Hi all,
We recently installed a new Altiris DS Server running 6.9 SP3.
The install went fine, without any hitches... great.
I was then able to install the latest FreeDOS / LinuxPE packages from the Symantec D/L site.
I then configured two new boot images - one for FreeDOS which works fine, but when using the LinuxPE, the process gets as far as trying to mount the
windows SMB eXpress share, and errors out.
The error states that the 'asmbmount commnad file missing'.
I was able to manually mount the share using the 'mount' command, but i really need to find out why / where this file is missing?
Does anyone have any ideas, or have you seen this before?
Cheers,
Chris
Discussion Filed Under:
Comments
Same
I am now having the same problem, but with SP4. What makes it even stranger, is that I have a working Linux PE, but I am trying to make a new one and I keep getting this command.
I know this is an old post, but did you find out how to fix this?
I've never seen this before.
I've never seen this before. Have you tried using BootDisk Creator to 'reload' you Linux automation environment? Just for piece of mind, download a fresh version and import this again.
Other than that, either the file really is missing or it's a path problem in your environment.
Put you Linux automation into a 'Wait' state with a wait task. This will allow you to rummage around. Then type,
You should see the following files,
also try,
this should output the following paths (colon delimeted),
One of those will tell you what your real problems is. But hopefully, the Linux automation reload will sort your problem.
Ian Atkin, Senior Developer for the ICT Support Team, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads<
Problem found
Ok, so that narrows down the problem. The rdeploy folder is missing. I have all the other echo $path folders, except the rdeploy folder. Also when I tried going to the directoy you mentioned I found it did not exist (did that first before the echo).
So I would do the "reload" except I have a customized Linux that we use at a bunch of different locations, and I really don't want to break our build process just to fix some testing I am trying to do. (I have done a reload and it is gave me a bunch of problems with our build process and I would rather not chance this problem spreading to that build.) Anyways, we are moving to a new DS server, hopefully later this week, so I will just build the new ones on there. That is, if the reload is my only option.
Would you like to reply?
Login or Register to post your comment.